Announcement

Collapse
No announcement yet.

Squeezelite-ESP32 > 3 NEW OpenHardware Boards (MAKT32 - MAKT32CL - ESP32-ADF)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • cOOLio
    replied
    [new arrival] VI3W1MA - DAC: WM8960 (Voice Interaction Hat for Makepython)



    BTW ... instead of reviewing only 2 boards, mention earlier in this thread.
    I will review & compare all boards I got so far in one.
    Last edited by cOOLio; 2022-09-23, 08:13.

    Leave a comment:


  • cOOLio
    replied
    sneak-peek

    ...

    Leave a comment:


  • cOOLio
    replied
    Originally posted by mboxler View Post
    I just remembered an issue I had when I installed Logitech Media Server Version: 8.2.1 - 1652959290 on my PC a few weeks ago. I added all the plugins, including SqueezeESP32. A few days later I played music through an ESP32 and it sounded awful. Took a while before I realized that the equalizer settings on the newly installed plugin were not all zeros, and the lower octaves were so high that my speakers distorted. Zeroed them out and everything was fine.

    Completely forgot to post this issue until now .
    I have also noticed a few times that in the NVS editor other values were shown which were actually really in there. But that was always due to the browser cache. So now I always reload the page, but tell the browser not to use cache at all. By just reloading as followed (Linux/Windows - Firefox/Chromium/Chrome):
    • Hold both the Ctrl and ⇧ Shift keys and then press R .
    • Hold the ⇧ Shift key and click the Reload button on the navigation toolbar.
    • Hold the Ctrl key and press the F5 key.




    Originally posted by sle118 View Post
    Something to keep in mind is I wrote the NVS restore in a way that allows partial restores. In other words, you could restore a file with a couple of values for i2c and the rest would remain intact. The system does not delete values when you restore an incomplete file. It just loads whichever values you provide.
    Uhhhhhh, that's really well thought out.
    I really like

    Will definitely take this into account for my future NVS backups and only put in what is really necessary. Because with my very first cspot backup of 2.x. It has already happened that in my backup, data were in there, that you have changed in the next version and I therefore had problems.

    I really appreciate the hint.

    Leave a comment:


  • sle118
    replied
    Originally posted by cOOLio View Post
    Loading an old test NVS backup, by mistake, made finally the trick and then for sure analyzing what's was the different to the current NVS V1.0 backup.
    Something to keep in mind is I wrote the NVS restore in a way that allows partial restores. In other words, you could restore a file with a couple of values for i2c and the rest would remain intact. The system does not delete values when you restore an incomplete file. It just loads whichever values you provide.

    Leave a comment:


  • mboxler
    replied
    Originally posted by cOOLio View Post
    The extreme bass is now fixed. And it was not related to fw 2.x.
    I just remembered an issue I had when I installed Logitech Media Server Version: 8.2.1 - 1652959290 on my PC a few weeks ago. I added all the plugins, including SqueezeESP32. A few days later I played music through an ESP32 and it sounded awful. Took a while before I realized that the equalizer settings on the newly installed plugin were not all zeros, and the lower octaves were so high that my speakers distorted. Zeroed them out and everything was fine.

    Completely forgot to post this issue until now .

    Leave a comment:


  • cOOLio
    replied
    Originally posted by cOOLio View Post
    Originally posted by philippe_44 View Post
    Because the change I made only does something for Spotify
    This is very strange though

    I'm testing currently on MAKT32CL, before I was on MAKT32. Will cross check.
    BTW ... the most pops came from cspot not the DAC. Didn't realized it until you or Sle mentioned the pops related to cspot it in the 2.x thread.
    The extreme bass is now fixed. And it was not related to fw 2.x. But the current wifi boot stuck issue of fw 2.x and a mistake by myself. Loading an old test NVS backup, by mistake, made finally the trick and then for sure analyzing what's was the different to the current NVS V1.0 backup.

    When I got more time i will hopefully upload a new NVS config, this week, for both Makerfabs players. With the Audio fix and all buttons set in proper way. Since i'm the only one who are using these 2 players i will not go in the details of the fix. Unless someone already has one of the two players and wants to get rid of the extreme bass to get the full potental out of the EQ. In that case just post here.

    BTW ... I upgraded now all my players to FW 2.x to get the better recovery functions of that FW branch. Cause the 1.x isn't a big help in troubleshooting, I must say. Those Players I'm currently using as my new home test Multiroom solution, I downgraded them OTA, after a full 2.x flash, to the much better working FW 1.1050-16 of the 1.x master branch. But still having the much better NVS Editor etc. from 2.x in recovery.

    The DAC UDA1334ATS of those 2 Makerfabs players, has still a different more warmer (bass & mids) sound, like all the others boards I own so far. Which I like somehow. Therfore I will call it, the JBL sytle.

    And finaly, the MAKT32 and MAKT32CL boards seem to have a big potential, to be the boards for you, if you like to have a display (B/W or color) but with a different DAC Makerfabs offers. Cause they are like the ESP32-Lipo Boards (I'm also waiting for the delivery) but with an display already attached to the board.

    And next, I'll take a closer look at the OLiMex ESP32-ADF here and compare it to the ESP32-A1S Audio Kit V2.2. Since both offer very similar features.
    Last edited by cOOLio; 2022-09-19, 10:23.

    Leave a comment:


  • cOOLio
    replied
    Updated the initial post with the findings and results so far.

    Leave a comment:


  • cOOLio
    replied
    Originally posted by philippe_44 View Post
    Because the change I made only does something for Spotify
    This is very strange though

    I'm testing currently on MAKT32CL, before I was on MAKT32. Will cross check.
    BTW ... the most pops came from cspot not the DAC. Didn't realized it until you or Sle mentioned the pops related to cspot it in the 2.x thread.

    Leave a comment:


  • philippe_44
    replied
    Originally posted by cOOLio View Post
    [email protected] & Radio (FLAC/ACC)@LMS
    Because the change I made only does something for Spotify

    Leave a comment:


  • cOOLio
    replied
    Originally posted by philippe_44 View Post
    Where you using it with Spotify only?
    [email protected] & Radio (FLAC/ACC)@LMS

    Leave a comment:


  • philippe_44
    replied
    Originally posted by cOOLio View Post
    I'm now on Firmware I2S-4MFlash.16.1187.master-v4.3 and the 1st time no more extreme bass. Very nice
    The most of the pops are also gone. Only when power on & off. So no longer as crappy as I thought yesterday, this UDA1334ATS DAC.
    Were you using it with Spotify only?
    Last edited by philippe_44; 2022-09-18, 02:23.

    Leave a comment:


  • cOOLio
    replied
    I'm now on Firmware I2S-4MFlash.16.1187.master-v4.3 and the 1st time no more extreme bass. Very nice
    The most of the pops are also gone. Only when power on & off. So no longer as crappy as I thought yesterday, this UDA1334ATS DAC.

    Leave a comment:


  • cOOLio
    replied
    Originally posted by philippe_44 View Post
    Yes, this is correct. It will work only for the 16 bits version, but it will fully force resampling at that fixed rate
    Since the DAC is so bass heavy it needs definitely the 16 Band EQ. Therfore I'm using already only the 16bit Firmware.

    My current EQ settings with cheap headphones: -13,-13,-13,-9,-5,1,3,2,3,1

    I also noticed now that the pops also come when you skip to the next song manually. When it automatically switches to the next song there are no pops. The amplifier probably switches off (pop) very quickly and then on (pop) again ... Double tab ... oh no that was Zombieland.

    Is there any way to get the amp to stay on all the time, so even if no music is playing? (dreaming)

    This UDA1334ATS DAC is somehow crapy!

    Leave a comment:


  • cOOLio
    replied
    Originally posted by mboxler View Post
    Sorry if I don't understand what you are trying to do, but if you add -R -r "44100-44100" to the end of your autoexec1 statement, then the bitrate will be fixed at 44100 and the clocks should not change.
    Thanks for the hint! Didn't read anything about this @github. Will test.
    And the reason why I need a fixed bitrate, the DAC does not only pop when the amp starts, also when it stops and when it changes the sample rate.

    Leave a comment:


  • philippe_44
    replied
    Originally posted by mboxler View Post
    Sorry if I don't understand what you are trying to do, but if you add -R -r "44100-44100" to the end of your autoexec1 statement, then the bitrate will be fixed at 44100 and the clocks should not change.
    Yes, this is correct. It will work only for the 16 bits version, but it will fully force resampling at that fixed rate
    Last edited by philippe_44; 2022-09-17, 08:13.

    Leave a comment:

Working...
X