Basically, I’ve removed the NFS mounts, rebooted, entered correct mounting convention and thought everything was good. After reboot, same thing…the shares shows mounted but there’s no info on number of songs/artist/tracks/playtime and going into the library thru “Music” tab shows nothing under the NAS…following your steps and updating and rescanning did not do anything. This is not happening on my Pi4 or PC, just the Pi5. Here’s a log.
I noticed your logs are filled with CUE files, which are not supported by Volumio. This was already mentioned in this forum topic.
Your logs also show repeated MPD errors like: error: MPD error: The expression evaluated to a falsy value:
These are most likely triggered by the unsupported CUE files. As a result, the library scan fails, and the database isn’t saved, so after a reboot, your music library appears empty.
I see. I wasn’t aware that they’d affect the system that way. I don’t rely on nor do I use CUE files. They are more a remnant of my 20+yrs library. But again, this is not an issue on my Pi4 or PC.
I suppose I should get on with cleaning up my library.
I use CUETools. Very simple to use, just drag the cue file to the CUETools window.
Why doesn’t Volumio just ignore CUE files during the scan to avoid issues?
Hi and good morning, all.
Sorry, was away from keyboard a while…
Just installed 4.021 (coming from 4.020) via OTA - went without problems.
Capability of reboot from installer/GUI re-appeared, reboot from terminal not tried, yet.
Actually all of the system is working as excepted.
Really NICE, great job! Thanks a LOT!
(HW) Config:
Pi5,
Raspi 2 Display (DSI),
Two rotary encoders on several GPIOs
Working BT remote
Testing:
Spotify plugin, works again (my only use case).
Touch display (and corresponding plugin) works
“Now Playing” plugin works
Bluetooth_remote plugin works
Rotary encoders are both working
WiFi is working (can access from laptop / phone).
BT remote working
CORRD link still only leads to app-store, no intergrations as far as I can see.
Sorry if this has been asked and answered before !
Are all the Settings preserved when updating? For example Sources, Network Drive paths, Playback Options etc.
I posted a couple weeks ago about an issue with songs seem to be playing but sound stops. I can see the time increase if I refresh the player and logs show that songs still continue to rotate through the playlist its just that sound stops unless I click play or skip then sound will resume.
Last time I posted someone saw there were a lot of errors in my MP3 files. I used foobar2000 to verify and fix issues. I also created a new playlist instead of the one I saved from the old Volumio install. Still seem to have the issue though.
The last song I remember playing was this one around 11:20am Aug 17 11:20:17 volumio volumio[1181]: verbose: ControllerMpd::sendMpdCommand add "NAS/proxmox-share/Music/Mole Suit Choir/Doomsday Lamp/Mole Suit Choir - Doomsday Lamp - 03 Big Blue River.mp3"
So some where between that song and when I noticed there was no sound I took note this song was playing at 11:36am Aug 17 11:36:20 volumio volumio[1181]: verbose: ControllerMpd::sendMpdCommand add "NAS/proxmox-share/Music/Studio One Dub Fire Special Chapter 3/03-callie-roots.mp3"
Yes. This is true from the beginning of Corrd.
But „listening to corrd on a mobile phone app“ is nothing I prefer to do.
Simply not my use case.
On my „whishlist“ is a corrd stream on Volumio with the ability to click a favourite buttton if a song is played I would like to remember…
THIS would be a usecase for me
Regards,
Ralf
Volumio 4.0.21 on 32GB Sandisk USB stick. Booting with Dell Wyse 5070.
Next I tried to install Volumio to the Dell’s internal SSD, on which I had previously had Audiolinux.
After Volumio completed the install to the internal SSD and I rebooted the Dell, it still tried to boot into Audiolinux. Apparently Volumio did not initialize the internal SSD completely prior to the install.
EDIT: I found that the Dell Wyse 5070 has an eemc storage besides the internal SSD. Adjusted the default boot drive accordingly and everything is well. Volumio install was not at fault.
issue: oh media via upmdcli not showing up on Home assistant or any other ohmedia client.
To reproduce:
install fresh voumio 4.021
try to access oh media renderer.
Volumio 4.0.21. I have put together a CM5 / IO board with an Audiophonics ES9038Q2M HAT and an Audiophonics OLED screen. After installing the Audiophonics Evo Sabre 2.0.1 plugin, everything seems to work.
However the instruction for the plugin tell me to select DSD over PCM (DoP), which limits DSD to DSD128.
If I choose DSD direct, the OLED screen tells me that I am playing upsampled PCM 352.8 or 384kHz.
Thanks for the detailed report and for including the log. At this stage, we’re trying to determine where the failure is actually occurring, and whether it’s a Volumio-side regression or something in how your OpenHome clients (like Home Assistant) are performing discovery.
To move forward, we’d need the following:
Confirm whether a DAC is physically connected at boot, and retry with it powered and recognized.
Clarify what integration Home Assistant is using to detect OpenHome:
Is it the native dlna_dmr, upnp, or something else?
Is it polling over SSDP or looking for a specific OpenHome XML descriptor?
Provide a log or debug output from the client side, showing what is (or isn’t) being discovered.
Let us know whether your expectation is that OpenHome should be available even without any output device (e.g. metadata-only mode).
Right now, we cannot confirm a regression, because the service chain may simply be aborting early due to missing output. If that’s the case, we can reproduce and check whether Bookworm changed upmpdcli’s behavior in this condition.
You’re in the best position to clarify this with Audiophonics directly, since you have the hardware on hand and you’re already observing behavior that may not match their advertised capabilities.
If the ES9038Q2M HAT is indeed a direct upgrade from the ES9028Q2M, as Audiophonics claims, then native DSD512 should be electrically supported. But if DSD Direct is not working as expected in Volumio, the remaining unknowns likely depend on:
Whether the HAT asserts the DSD_EN line correctly
Whether Audiophonics expects software-side support or plugin config
And what their own validation path is for native DSD (versus DoP)
We’re happy to help confirm Volumio-side behavior, but the hardware vendor needs to clarify how their board is wired and what they officially support. Let us know what they say if you reach out.
Thanks @nerd
Audiophonics have confirmed to me that the ES9038Q2M HAT and its drivers do NOT support DSD native. The ranges that are supported are PCM to 384kHz and DSD to DSD128. This is according to the specs audiophonics give for the device.
They have also confirmed to me that the correct driver to use for the ES9038Q2M HAT is the “audiophonics iSabre ES9028Q2M” one.
