Page 6 of 7

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 07 Apr 2024, 17:36
by Beelzebassie
I'll give it a spin.

Thanks for the heads-up about the xz-utils backdoor too!

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 02 May 2024, 02:12
by tomp
0.6 is working great for me on a pi 4b with a HifiBerry digi2 pro hat.

I really appreciate the continued effort to keep the classic RuneAudio alive! Thank you!!!

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 10 Jul 2024, 08:10
by Stephane
I am facing a problem with my music collection, the Library tab only displays directories to the letter D!
If I search the database for artists past letter D then no problem, I can see the result on the screen (local or remote).
So maybe it's a limitation of the number of lines that it can display?
I'm running version 0.6b , made a git pull and my my other Rune system (0.5) does not do this.
Anyone with the same behaviour?

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 10 Jul 2024, 09:36
by janui

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 10 Jul 2024, 14:50
by Stephane
There are 54 files and 176 directories displayed. On the local screen (chromium) or on a remote Firefox.
No modifications in the UI except one, the name of the player just before the MENU (top left).

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 10 Jul 2024, 17:49
by janui

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 11 Jul 2024, 10:44
by Stephane
Thank you for the tips Janui, the culprit is the last album displayed. Once deleted I see all my music collection.
Now I have to analyse the MP3 files.

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 11 Jul 2024, 18:28
by janui

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 14 Jul 2024, 15:34
by janui

Re: RuneAudio 0.6-beta for most Raspberry Pi models

PostPosted: 15 Jul 2024, 10:49
by Stephane
Anyway, the last directory scanned contains OK at the end so maybe the problem is here.
I removed it, did a DB rebuild, put it back and no problem with the DB rebuild.
Problem solved. Thank you.

PS: I will test your patch during the week.