Volumio 3 RC1 - Open Beta Testing

Volumio Development Volumio Beta Testing
229

I get HTTP 404 from the URL in the log

image
image1532Ɨ356 39.6 KB

230

Works here, hope someone will have a look

1 Like
231

Can we get a new build now? Cant use at all without My wifidongle.

Thanks

232

Can you please be more precise?
HW
Version for Volumio
Without information, we donā€™t understand you, and canā€™t help.
Thanks

1 Like
233

Its allready reported and fixed.
Just nere a new build with fix included

234

We canā€™t build for each single issue, a beta image will be released when alpha testing has been done for a series of fixes.

1 Like
235

Send log, on and off
http://logs.volumio.org/volumiobuster/oPjAQ8i.html (wireless on)
http://logs.volumio.org/volumiobuster/0HpZghp.html (wireless off)

236

@danielfelix that could be why itā€™s running bad.
a lot of end points timmed out.

# volumio endpointstest ---------------
TESTING REMOTE ENDPOINTS
https://google.com, 5419 ms: FAILED
https://www.googleapis.com, 373 ms: OK
https://securetoken.googleapis.com, 622 ms: OK
https://myvolumio.firebaseio.com, 915 ms: OK
https://functions.volumio.cloud, 5667 ms: FAILED
https://oauth-performer.dfs.volumio.org, 1845 ms: OK
https://browsing-performer.dfs.volumio.org, 5139 ms: FAILED
http://cddb.volumio.org, 5141 ms: FAILED
https://functions.volumio.cloud, 5144 ms: FAILED
http://pushupdates.volumio.org, 5144 ms: FAILED
http://plugins.volumio.org, 5146 ms: FAILED
https://database.volumio.cloud, 5149 ms: FAILED
https://radio-directory.firebaseapp.com, 5152 ms: FAILED
----------
WARNING!!! Some remote endpoints cannot be reached!
Failing endpoints: 
https://google.com, 5152 ms
https://functions.volumio.cloud, 5152 ms
https://browsing-performer.dfs.volumio.org, 5152 ms
http://cddb.volumio.org, 5152 ms
https://functions.volumio.cloud, 5152 ms
http://pushupdates.volumio.org, 5152 ms
http://plugins.volumio.org, 5152 ms
https://database.volumio.cloud, 5152 ms
https://radio-directory.firebaseapp.com, 5152 ms
237

Yes, that is a very likely explanation.

@danielfelix do you have some firewall going on on your network? Maybe Pi-hole?

238

RP4, 3.114, Okto Research DAC8 Stereo via USB1 (with external RP4)
The DAC does not play DSD native, it converts to 24/352.8 PCM. Volumio shows DSD64 otuput.
DoP64 plays, the DAC plays, but there are crackles
DoP128, plays the DAC plays, but there are crackles
DoP256 is converted to 24/352.8kHz
I am also sending this to Okto Support

1 Like
239

Thanks Jacobacci!
No need to ask for their support, we might know where the issue is.
We might ask you more info in the future, thanks!

241

I use the windows firewall, I have Volumio 2 working on the same network without problems.

1 Like
242

RPI4, V3 RC1 3.114, Topping D10 DAC

regarding DSD

DSD 64 direct plays fine no problems other than you need volumio volume at 100% otherwise you get static. (but that is normal right) The Dac reports correctly saying DSD 2.82

DoP doesnt work at all, very quiet static with very feint music, Dac reports PCM 176 ok. if you turn the volume to 100% the everything works, but the DAC then reports it back to DSD

OOOOPs forgot this. http://logs.volumio.org/volumiobuster/0KbsobH.html

DoP set in options , rebooted, then played, slowly upping vol to 100% (at about 1 min) dropped vol a couple of times after, dac switching between pcm(no sound) and dsd( playing ok)

243

Update on this post,

The new release seems to have problems supporting mConnect. While mConnect connects to Volumionpi4, it often has problems playing anything and provides an error message that says. ā€œDevice sent an error Response.ā€

1 Like
244

WE NEED LOGS! PLEASE SEE INSTRUCTIONS ON HOW TO REPORT BUGS ON FIRST POST

Thanks :wink:

2 Likes
245

Hey guys , officially paying for volumio for a year and love it so far, just what I needed. Gapless at last :slight_smile:

Wonder if there is a pulldown for Android app so it stays on top or easy to access again like other players? Probably n the settings but couldnā€™t find much.

Thanks!

246

While you are at it, any chance of guestures on Android (swipe back)? :stuck_out_tongue:

1 Like
247

That ._XXXX stuff is the result of MacOS creating its own meta information on the rpi filesystem. Normally this detail goes into dedicated placeholders on native Apple filesystems but when mounting files on a remote server, it uses hidden files to store this metadata.

You canā€™t avoid this. MacOS will continue to create these files every time you have it copy files onto the rpi.

If you can ssh into the same system, it would be possible to locate/purge these files with a find command:

# replace /path/to/where/music/is/stored with the actual path 
# for your music location on the SD

# locate these files using the appropriate path on your SD
find /path/to/where/music/is/stored -name '._*' -print 

# locate and delete these files 
# Only do this if you are certain that files you found were the files you 
# wish to purge
find /path/to/where/music/is/stored -name '._*' -print -exec rm \{} \;
248

@dresdner353 thanks for explaining this!

I think we could solve it by adding a pattern to mpdignore

Do you have a suggestion on how we could achieve that?

249

Iā€™d start with adding:

._*

to /var/lib/mpd/music/.mpdignore and see how it goes.

1 Like