If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I’ve updated 4.3 with an additional parameter named « cswap »
I upgraded to 1027, but it doesn't seem to change. This is display_config
SPI:width=160,height=80,cs=12,reset=22,back=14,spe ed=8000000,driver=ST7735:x=26:y=1,rotate,VFlip,inv ert,cswap
I upgraded to 1027, but it doesn't seem to change. This is display_config
SPI:width=160,height=80,cs=12,reset=22,back=14,spe ed=8000000,driver=ST7735:x=26:y=1,rotate,VFlip,inv ert,cswap
It probably has nothing to do with the problem but I'm surprised you are using such a high value at X offset?
Does anything change if you set the value to zero for a test?
No change at all in colors with or without cswap? We are talking about 4.3 (only in the build artefact, right?)
Yes, this update: "add color swap BGR/RGB and generalize invert option ESP-IDF v4.3.1 #117: Commit dd519b9 pushed by philippe44"
After double checking that there was no effect, I tried a few other settings in the string. But I ended up getting the device in a boot loop. I have been able to recover the device, but I can't get the screen to show anything anymore, not even the SqueezeESP32 message during booting.
Originally posted by piPlayer
It probably has nothing to do with the problem but I'm surprised you are using such a high value at X offset?
I agree that the x:26 seems totally arbitrary, but that is what puts it in the right position...
I upgraded to 1027, but it doesn't seem to change. This is display_config
SPI:width=160,height=80,cs=12,reset=22,back=14,spe ed=8000000,driver=ST7735:x=26:y=1,rotate,VFlip,inv ert,cswap
I have a squeezelite-esp32 running on a ESP32 Audio Kit.
I have an SD1322 screen attached and all works fine.
My player "now playing information" is set to "Spectrum Analyzer and Progress Bar and Remaining Time".
I'm living it playing 24/7 as a kind of stress test.
I keep getting the spectrum hung after around a day.
Today, I saw it hung after 26 hours playing nonstop a radio station.
The "remaing time" is still counting up (as it is a radio) but the bars won't move.
I did connect through telnet and saw nothing special.
I still get the kind of "I (108026916) httpd_handlers: serving /status.json to peer 192.168.141.6 port 21641" line from time to time.
Rotating the know will display the volume "slider" and the following lines appear as soon as I leave the know idle for a while (and the slider get's off the screen):
Code:
[13:31:16.289068] visu_handler:1214 Stopping visualizer
[13:31:20.824881] visu_handler:1212 Visualizer with 32 bars of width 0:7:1:0 (w:256,h:32,c:0,r:32,s:0.25)
[13:31:20.877117] visu_handler:1214 Stopping visualizer
[13:31:22.325311] visu_handler:1212 Visualizer with 32 bars of width 0:7:1:0 (w:256,h:32,c:0,r:32,s:0.25)
We are then back on tracks for a few other hours.
Is there anything I should collect to help debug this behaviour ?
I have a squeezelite-esp32 running on a ESP32 Audio Kit.
I have an SD1322 screen attached and all works fine.
My player "now playing information" is set to "Spectrum Analyzer and Progress Bar and Remaining Time".
I'm living it playing 24/7 as a kind of stress test.
I keep getting the spectrum hung after around a day.
Today, I saw it hung after 26 hours playing nonstop a radio station.
The "remaing time" is still counting up (as it is a radio) but the bars won't move.
I did connect through telnet and saw nothing special.
I still get the kind of "I (108026916) httpd_handlers: serving /status.json to peer 192.168.141.6 port 21641" line from time to time.
Rotating the know will display the volume "slider" and the following lines appear as soon as I leave the know idle for a while (and the slider get's off the screen):
Code:
[13:31:16.289068] visu_handler:1214 Stopping visualizer
[13:31:20.824881] visu_handler:1212 Visualizer with 32 bars of width 0:7:1:0 (w:256,h:32,c:0,r:32,s:0.25)
[13:31:20.877117] visu_handler:1214 Stopping visualizer
[13:31:22.325311] visu_handler:1212 Visualizer with 32 bars of width 0:7:1:0 (w:256,h:32,c:0,r:32,s:0.25)
We are then back on tracks for a few other hours.
Is there anything I should collect to help debug this behaviour ?
I don't have much log messages there as it is a very CPU-consuming item. I'll try on my side.
I don't have much log messages there as it is a very CPU-consuming item. I'll try on my side.
As you speak about CPU consumption, I noticed that for that particular station, the spectrum bars were not moving so "fluidly".
Maybe that station is using an encoding that is taxing too much the esp32 cpu ?
As you speak about CPU consumption, I noticed that for that particular station, the spectrum bars were not moving so "fluidly".
Maybe that station is using an encoding that is taxing too much the esp32 cpu ?
Be careful, if you leave this station running for 24+ hours, you may get addicted
I will try - Usually aac, ogg or even opus consume more CPU. Of course if you use the 32 bits version then it can be a bit ugly. I strongly recommend against doing that.
Yes, this update: "add color swap BGR/RGB and generalize invert option ESP-IDF v4.3.1 #117: Commit dd519b9 pushed by philippe44"
After double checking that there was no effect, I tried a few other settings in the string. But I ended up getting the device in a boot loop. I have been able to recover the device, but I can't get the screen to show anything anymore, not even the SqueezeESP32 message during booting.
I agree that the x:26 seems totally arbitrary, but that is what puts it in the right position...
I will try - Usually aac, ogg or even opus consume more CPU. Of course if you use the 32 bits version then it can be a bit ugly. I strongly recommend against doing that.
I've read too many times the github pages and posts in this forum to stick to the 16bits version ;-)
Sorry about the delay. Turns out it's not a great idea to flash over USB while also copying a few TB to a backup USB drive. You get random errors and funky messages while booting.
Now all is recovered. And it's working properly on 1030!
(However, the 'credits' menu seems to be broken in 1030, so I couldn't get to the NVS tab. Neither in Firefox nor Chrome. So for testing, I reverted to 1027, adjusted display_config and then back to 1030.)
Sorry about the delay. Turns out it's not a great idea to flash over USB while also copying a few TB to a backup USB drive. You get random errors and funky messages while booting.
Now all is recovered. And it's working properly on 1030!
(However, the 'credits' menu seems to be broken in 1030, so I couldn't get to the NVS tab. Neither in Firefox nor Chrome. So for testing, I reverted to 1027, adjusted display_config and then back to 1030.)
Thanks once again!
That’s weird, I’ll try on my own but I had no issue so far. Maybe I’ve. It updated the whole webapp package on my mirror system
That’s weird, I’ll try on my own but I had no issue so far. Maybe I’ve. It updated the whole webapp package on my mirror system
Part of the website gets cached in the browsers. So after updating, the Credits menu actually continues to work. But after a forced refresh with CTR+SHIFT+R, it doesn't anymore.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment