I come back to standby.
set to "Never" the screen remains lit even after a full night it is still active suddenly. OK
the trouble is that I leave the pi continuously running and suddenly the screen also stays on, I would like it to go to sleep to avoid wear.
with Volumio I don't have this problem of the screen going into deep sleep after an hour, a small gesture wakes it up instantly.
So problem not solved...
set to "Never" the screen remains lit even after a full night it is still active suddenly. OK
the trouble is that I leave the pi continuously running and suddenly the screen also stays on, I would like it to go to sleep to avoid wear.
with Volumio I don't have this problem of the screen going into deep sleep after an hour, a small gesture wakes it up instantly.
So problem not solved...
Are you saying you think it might be in the userID and password? I can try that, but I might try zeroing out the "config.txt" file as below first.
@aditya Yes, I thought the HDMI would be more robust also.
I think the problem may be similar (or the same) because you also get the initial 640x480 or so text boot up screen. Does that panel provide a "no signal" screen?
I watched the old card boot up, can't read the text scrolling by, but it gets to the login prompt: On the old system the screen blanks, I get an "HDMI" indicator from the screen, then a white box, then the UI initializes. On the new system I just get a blank grey panel.
SSH in I see
I don't really know what I am looking for yet, but I did find this difference:
on the old system the "config.txt" file in the /boot directory is empty. On the new system it is not. EDIT: Took it out because zeroing out that file didn't work.
So I am trying a new image again, this time using:
Hostname: moode.local
Username: pi
Password: moodeaudio
We'll see if that's the trick.
Last edited:
So did you use your own user id and passowrd or the old one like which ptrkollias suggested.
congratulations for your success. 🙂
if it is the original screen, i do not think there will be any wear since it is a LCD and not an AMOLED / OLED. only thing that i saw with my Original PI screen is Fungus growth between the Glass and Display and this could be do with the distance to sea is 1.2KM and or something to do with QC of the display 😛
@aditya I followed @ptrkollias advice
I used the Raspberry Pi imager, setting the following options:
Hostname: moode.local
Username: pi
Password: moodeaudio
(and my wifi ssid and password)
On first boot it rebooted twice as it does set-up things (expanding the card file system, etc.)
Settles into the local blank grey screen.
I then went to the web interface:
"m" in the upper right -> Configure -> System
In the "Local Display" section, I moved "Display" to "ON".
Hit the "SET" button.
Then:
"m" in the upper right -> Power -> Restart
I used the Raspberry Pi imager, setting the following options:
Hostname: moode.local
Username: pi
Password: moodeaudio
(and my wifi ssid and password)
On first boot it rebooted twice as it does set-up things (expanding the card file system, etc.)
Settles into the local blank grey screen.
I then went to the web interface:
"m" in the upper right -> Configure -> System
In the "Local Display" section, I moved "Display" to "ON".
Hit the "SET" button.
Then:
"m" in the upper right -> Power -> Restart
The LCD is given for 50,000 hours, or almost 6 years, leaving it lit all the time. 🤔
Gotcha, well for me I listen for some time and switch off - I normally switch of things as the meter keeps running and every drop counts.
Yes indeed At the current price of energy in Europe, I'm going to change the method and turn off the whole system when I'm not listening to music.
It's more reasonable.
It's more reasonable.
its world over - i guess we should switch to SBC and LInux and ditch the Laptops... ( food for thought )....
In my Country i just now got the news that a supply company was forced to increase the cost by 10 digits so yeahh if i cross a slab i will be paying 30% more and its Summer here ( begining )
I was looking for a way to use UPnP with Foobar2000 and PGGB-RT running on a desktop. Then use Moode UPnP Client for MPD to stream from the desktop. Unfortunately, the Foobar2000 UPnP/DLNA Renderer, Server, Control Point by bubbleguuum is 32 bit only and PGGB-RT is x64 only. Any other options?
Use an older 32bit version of PGGB-RT -
https://www.foobar2000.org/components/view/foo_pggb_rt/release/1.50
Is there a block diagram detailing the relationships of the MPD input cache, audio buffer and output buffer, and the operations performed on the data (e.g., flac to wav conversion)? Does the input cache contain the unaltered file from the data source (flac, for example)? Where does conversion from flac to wav occur? What about polarity inversion? Does the output buffer contain PCM wav data ready for the output device (DAC)?
So that mean when we set up a new user id and password this account lacks the drivers for DSI Display ?
AFAIK the only documentation for the MPD Input Cache is at the link below
https://mpd.readthedocs.io/en/latest/user.html#configuring-the-input-cache
At a macro level the MPD/ALSA pipeline looks something like below.
INPUT (file or stream) --> DECODE (convert to PCM) --> DSP --> OUTPUT --> DEVICE
The INPUT stage would contain the file or stream in its original format. Files are either read from storage media or from the Input Cache. The file or stream is then passed to the DECODE stage where an appropriate CODEC is used to convert the original format to PCM. Next the PCM samples are processed, if any is indicated for example volume, resampling, polarity inversion, etc. The final PCM samples are then passed to the OUTPUT stage where that are sent to the audio DEVICE.
I had used other than "pi" userid and was not able to use the DSI display even with the Local display turned on