Don’t update your Primo with it. Even if the thinkerboard will work, the internal Dac won’t…
You’ll be informed when Primo will receive update OTA.
Thank you for the update, I’ll hang on then.
There is some problem with your music collection. There are very many errors in the log like:
[src/libmpg123/readers.c:1184] error: Cannot open file /var/lib/mpd/music/NAS/FRITZ_NAS/Abba/ABBA, the Album/02 Fernando.mp3: Stale file handle
Oct 24 06:52 : mpg123: libmpg123 failed to open /var/lib/mpd/music/NAS/FRITZ_NAS/Abba/ABBA, the Album/02 Fernando.mp3: A generic mpg123 error.
[src/libmpg123/readers.c:1184] error: Cannot open file /var/lib/mpd/music/NAS/FRITZ_NAS/Abba/ABBA, the Album/03 Happy New Year.mp3: Stale file handle
Oct 24 06:52 : mpg123: libmpg123 failed to open /var/lib/mpd/music/NAS/FRITZ_NAS/Abba/ABBA, the Album/03 Happy New Year.mp3: A generic mpg123 error.
[quote=“volumio, post:1, topic:50284”]
To report, please make sure you add the following info:
RP4 with hifiberry DAC + DSP
TO really use DSP part I have to install "dsptoolkit from GitHub - hifiberry/hifiberry-dsp: DSP toolkit " which needs PIP3 to be installed.
As soon as install PIP3, the system becomes very unstable ( reboots in less than 2-3 mins) audio is noisy. Inshort unusable
http://logs.volumio.org/volumiobuster/MVPx6bX.html
But Volumio 2 works. How is is this possible? And is there is possibility to repair the files?
Hi
I just installed the beta on Raspberry Pi 1 with a generic i2c DAC. It works well . Three
comments
- I couldn’t get the SD card imager to work using a Windows 10 laptop. Windows 10 seems to get confused in creating the files and the flash fails. I solved this by using the latest Raspberry Pi imager from the Raspberry Pi website. This has an option to select an Iso file.
- On the raspberry Pi 1 the time from switch on to audio output tones is about 3.5 minutes rather than 2.5 minutes on the previous version.
- Various of the volumio selection of web radios give a curl failure. Try Smooth Jaz Global radio for example. This is common to the previous version. It did work when I originally installed Volumio about a year ago.
If everything was working fine in 2.9xx, I think I would remove the NAS share & add it again. It is unlikely that something has actually happened to your audio files.
Hello !
I’ve just installed Volumiobuster-3.114-2021-10-15-pi on a RPI4.
Seems to work fine for now, Volumio is scanning my NAS’s files, but i can’t find where to setup my Qobuz account.
Could you tell me ?
Sorry for that basic question.
Edit : I’ve subscribe to Virtuoso but still can’t find where to set up Qobuz. Do i need a pluggin ?
You have to enable Myvolumio on the device.
Then in sources, you should the Qobuz login fields
My USB-CD-Player is not recognized in 3.114 RPI 4 and Volumio Superstar .
No Probs with 2.x
PI 4
Volumio : 3.114
HiFiBerry DAC Amp2
Log Link
http://logs.volumio.org/volumiobuster/WozfCZT.html
Regardless of the startup volume settings, it always starts at 100% volume.
Oh yes, thanks.
I also needed a reboot.
Works fine
There are some other reports of this around (Start up volume always 100%). I had similar issues and patched the code on device (for software mixers), if you don’t find the issue let me know, will dig up the patch…
The lastest v Volumiobuster-3.114-2021-10-15-x86_amd64 on intel NUC & USB Pro Ject Pre Phono Box S2
Not playing native MQA files from NAS (writes flac 48)
Iphone interface - working very bad. Sometimes playing position stops at some place & didn’t move until reopen app
No touches can be make FF or RW
It still plays but no usefull interface
From Pluses
Sound more better
Still needs
Some playing infos (Art. Biografy of some track info etc)
So I move back to Daphile
If you find it that would be useful
- RPI4, Volumio 3.114, USB DAC Topping D50s
- The D50s has an auto power on/off feature that make it turning ON when music is beeing played and turn off if he doesn’t receive signal for 10 sec. The Dac doesn’t turn off when Volumio stop playing music (with pause button).
- http://logs.volumio.org/volumiobuster/wJgEB7f.html
RP3, Volumio RC1 (3.114), USB DAC Topping E10s
https://logs.volumio.org/volumiobuster/jH1dpdw.html
I keep getting weird freezes, when I try to play a track from Qobuz (under purchased tracks). I have a feeling that Volumio reboots when this happens.
I tried to send a log, but even though the live log says that a log was sent, no log can be found:
info: CoreCommandRouter::volumioReplaceandPlayItems
info: CoreStateMachine::ClearQueue
info: CoreStateMachine::stop
info: CoreStateMachine::setConsumeUpdateService undefined
UNSET VOLATILE
info: CorePlayQueue::clearPlayQueue
info: CorePlayQueue::saveQueue
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushQueue
info: CoreStateMachine::addQueueItems
info: CorePlayQueue::addQueueItems
info: Adding Item to queue: albums://B%C3%A9la%20Fleck%20And%20The%20Flecktones/Flight%20Of%20The%20Cosmic%20Hippo
info: Exploding uri albums://B%C3%A9la%20Fleck%20And%20The%20Flecktones/Flight%20Of%20The%20Cosmic%20Hippo in service mpd
info: CALLMETHOD: system_controller system sendBugReport [object Object]
info: CoreCommandRouter::executeOnPlugin: system , sendBugReport
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 2
info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0
info: touch_display: Setting screensaver timeout to 120 seconds.
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl -p 7
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
info: Log sent successfully, reply: {"status":"OK","link":"http://logs.volumio.org/volumiobuster/jH1dpdw.html"}
[Vollibrespot] : API Token expired, refreshing...
Live log shows http://logs.volumio.org/volumiobuster/jH1dpdw.html
When the UI comes back to life, I still can’t play any tracks until I restart the system.
I noticed stops when Qobuz is played via the Volumio interface. My first idea was that this appears when using the iOs app. But same with volumio.local. There was/is never such a behaviour when I reach the Pi via McConnect. Therefore I believe that is not an issue of Qobuz…
Can you make Volumio hide this linux system meta garbage from album folders…
I added the log url from the live log, it does exist