Hi ashthespy!
this 2 Mb off file: tag_cache.
when you have time you can see my Pi4??
How do I get it to boot quickly, without being affected by the size of the file: tag_cache.
And where is the starting speed specified?
Please just let me know!
Thanks
Mac
Thanks
Hi ashthespy!
I was test again Volumio 3.0 vs Moodeaudio 6.7.
1- aAbout boot time:
Volumio 3.0 : 55 s
Moodeaudio 6.7 : 46 s.
2- The music file : 2.2 T music off 4 T Hdd (WD)
I use 32G Micro SanDisk Extreme Pro for write Volumio and Moodeaudio on Pi 4- 4 G,
Ok - after I scan all music to Volumio 3.0 and Moodeaudio, so I test and I see:
1- Moodaudio boot time is still 46 s, with full scan music file, and play well when boot again- no need scan again .
2- Volumio 3.0 boot time go up 1 m 20 s, and some time , it run scan again Hdd,
So I ask you : why Moodeaudio is well with boot time and scan music file??
Why Volumio 3.0 is bad off time boot and scan music auto again?
Oh, Volumio have many many member can support !
Thank you advice
Best regards!
Mac
New build - new bugs features! 
Raspberry Pi Volumio-3.014-2020-12-10-pi
Updates:
Known issues:
node packages have different binary locations, temp fix by symlinking:sudo ln -s "$(which node)" /usr/local/bin/node
sudo ln -s "$(which npm)" /usr/local/bin/npm
sudo ln -s "$(which npm)" /bin/npm
I installed this just now and had to manually resize the SD card. You posted the solution here (just need to add sudo of course):
One other thing: I have an Allo Boss card. I had to disable HDMI sound in my headless setup or the card was recognized as card 3. I appended this line to /boot/cmdline.txt:
snd_bcm2835.enable_hdmi=0
Also in that file, I changed this option:
snd-bcm2835.enable_compat_alsa=1
I did those two things to get the mpd2chromecast plugin to work. There may be another way. I havenāt tried adding those to /boot/userconfig.txt.
Before changing that second option, my sound card was not being properly recognized by mpd2chromecast. However, playback was working out of the analog output of my sound card before I changed that option.
Iāve only had it up for half an hour but my Pandora plugin is working. Looks good!
Virtual Keyboard 1.0.4 doesnāt workā¦ with latest touch display buster beta ā¦
Yes, I wrote that Virtual Keyboard does not work earlier. Not matchbox-keyboard is the problem but chromium browser. Workaround is to revert to the old chromium version that gets installed on Jessie based systems.
auto start 1.1.2 doesnāt revert to last played song ā¦ 6 songs later it playsā¦ seems to play random
but not set on randomā¦
default startup volume is not working set on 60 doesnāt jump to 60 , startup volume after reboot is 100%
system information 0.1.3 works okeā¦
backup / restore 0.7.2 is brokenā¦ creates no backupā¦
album art : /data/albumart/web <<< images not showing they are presentā¦
@truckershitch mpd2chromecast does not directly access the sound card. It does rely on a client connection to the onboard MPD server to continually query the current playback state and track/file details. It would almost suggest that MPD was not functional prior to those changes and hence the mpd2chromecast script fell foul of that. Iāll try updating my own volumio rpi to the same new beta and see if I can reproduce the same issue. I donāt however have any 3rd party sound device on my rpi as itās only use to stream audio to chromecasts.
I believe that this is the case. I should have been more specific in my message.
I think this is specific to add-on sound cards and your script. If I remember correctly, the first error that occurred was when your script queried the volume parameter of the mpd software status. mpc status did not show a valid value for volume. I tried a number of things until I changed
snd-bcm2835.enable_compat_alsa=1
in the /boot/cmdline.txt file. I donāt think that this is the proper fix, as I was unable to change the volume from your programās web page.
Iād be happy to help you out with this if you want. Maybe this should be on GitHub or on another thread here on the forum?
We (well @Darmur) had similar issues with the pi0 - the Audio jack doesnāt show up.
Are you running on a pi4? I really hope these bootflags do not need to be tuned on a per-pi basis!
What was the final combination that worked for you? Could you share the output of aplay -l?
Found some hints:
So snd-bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_hdmi=1 should work as before?
EDIT:Looks like they disabled the audio jack for the pi0
On 3.014beta trying to execute dtoverlay from the CLI fails with command not found.
On the Jessie based builts dtoverlay, dtoverlay-pre and dtoverlay-post are found in /usr/bin in the form of symlinks to the respective files in /opt/vc/bin. These symlinks are missing in Buster beta.
Executing
/opt/vc/bin/dtoverlay
results in
error while loading shared libraries: libdtovl.so: cannot open shared object file: No such file or directory
libdtovl.so is present in /opt/vc/lib though.
Edit: Just found that on Jessie /opt/vc/lib/libdtovl.so is symlinked to /usr/lib/libdtovl.so but canāt test ATM if adding that symlink (and maybe running ldconfig) already solves the issue.
All these quirks, if only we could just install libraspberrypi-bin which handles it! 
Does this work?
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/vc/lib /opt/vc/bin/dtoverlay <>
Will fix the Lib path in the next buildā¦
EDIT: Just tested, should be fixed in the next build
Will test and report back as soon as I get home tonight.
Okay, so it was my fault it seems. I had a lot of problems getting 3.010 to work with my card and I had to change a few things, and I didnāt get everything straight. I thought those changes would be necessary in 3.014 but I was wrong.
I just now started again from scratch. I did not change the configuration in /boot at all and merely went through the startup wizard on the web page. I rebooted and heard the startup sound.
Then I went to check and see if there was a volume value shown in the mpc client. There was not. It merely showed n/a. Choosing a station in Web Radio worked fine from my sound card. Playback seemed all right.
I looked at the sound settings, changed MPD Clients Volume Control to On, and checked again. The volume was at 60%. Success!
I think Iām fine from here. I let @dresdner353 know and I think my issue is finished.
Iāll try and break your beta through some other angle. 
This is a Pi 3B+ by the way. I donāt know exactly how that changes things but I guess itās in the audio devices somehow.
It suffices to add the symlinks:
sudo ln -s /opt/vc/lib/libdtovl.so /usr/lib/libdtovl.so
sudo ln -s /opt/vc/bin/dtoverlay /usr/bin/dtoverlay
sudo ln -s /opt/vc/bin/dtoverlay-pre /usr/bin/dtoverlay-pre
sudo ln -s /opt/vc/bin/dtoverlay-post /usr/bin/dtoverlay-post
After that dtoverlay command works 
FYI for those following the mpd2chromecast issue with this latest betaā¦ Iāve pushed changes now to handle the absence of volume from the MPD server.
Please share logs and details of how to trigger the error, as I donāt have issues hereā¦
just say how i can get the log ash btw is there a version 2.853 with a mpd upgraded to 0.21.16?
this is needed for the new youtube plugin ā¦
Either from the /dev page using the livelog feature or via ssh.
# Volumio logs
journalctl -f
Note try to include minimal steps that triggers the issues you are facing to reduce noise in the logs
No clue, to be honest I havenāt run a jessie volumio image for a few years now, been either on Stretch or Busterā¦
@ashthespy i think itās the wait between pressing buttonsā¦ of 30 secā¦
now itās seems to work on the 3.14ā¦ only bit slower than the 3.10
and getting pretty hot 67 Ā°C added extra fan ā¦ 48Ā°C
if i press a song i have to wait 30 sec before playingā¦and every song nextā¦
System information plugin : if closed on pc stays open on rpi 7inch screenā¦