Only able to load one track from an ssd stored album

Hi Volumio Team!
How can it be, that suddenly I’m not able to load an album from SSD? It just adds 1 track. Has worked in the past. Oh boy, I’m really getting tired of volumio. I participated almost from the beginning- and- this distro is still full of bugs- really annoying- 15 years, I think, since that project started as raspify. Don’t you see that bugs??? Have wav files on the ssd- and that for sure won’t change. Next thing- Qobuz- Sorting never worked- now you have added A-Z sorting-fine- but- it doesn’t work- have to choose it again after every album added- MAD! Are you sleeping? Or is noone complaining about that constant bugs? If Usb Audio Player Pro will once work on a Pi, I will reach salvation and quit with Volumio. Take the efforts of UAPP as an example and orientation- this distro works perfect in performance, sound and features!
Sorry guys, I’m frustrated. Volumio has such a big potential, Fusion DSP-GREAT! And many other good implementations- but please, PLEASE, make it stable finally!

Cheers!

Greetingz, Robert

Leaving frustration aside, lets focus on what is being reported, which is quite confusing. Please expand on every and each item what is that you experience and how it can be replicated.
List of problems:

  1. Files stored on SSD in wav format
  2. Sorting
  3. A-Z sorting
  4. Adding albums

No problem with:

  1. Fusion DSP

Before moving further - please post link from your device log capturing above points:

Hi Nerd!

  1. SSD: When I choose an album and add it to queue, there is only the first track added- Im for sure not going to add each track extra. It worked for years- but actually it doesnt. In addition I have cue sheets saved within each album (all wav files)- but picking one of the ‘.cue’ ended entries also just puts the first track to queue- nothing else. In this condition not useable. But as I said- it worked for a long time with the same ssd and music files.

This is the only issue, that really bothers me. I can live with the following, it anyway never worked for years;- )

  1. Sorting in Qobuz: When I choose ‘A-Z sorting’ and select an album in Qobuz, sorting falls back to ‘last date added’ every time I have selected an album- so I am back on top and have to switch to 'A-Z sorting `again. Would be good to have it fixed for all times if once chosen- or at least till I change it.
    But- thats a minor issue.

  2. BT, WIFI activated by default: To me BT and WIFI are completely useless gimicks- moreover I prefer to reduce radiation I’m daily exposed- I’m an ethernet cable guy (faster, better)- so it would be good, having it disabled by default. Every time when a new FW- update is executed, I have to open ssh again, crawl into the depths of volumio in order to set lines to disable bluetooth and wifi in config.txt. At least a virtual button in 'system ’ would be good to easily activate or disable these functions. (Makes no sense having these facilities activated constantly if not in use at all).

No idea, how to handle log links, no experience with that- don’t know if this would be helpful anyway in particularely this case.

Thanks for response!

Best regards, Robert

Quite the opposite. It will actually tell the technical details of your build, information related to 1 and 2 as well as clarify potential presence of additional configuration files for 3.

Please follow instructions from:

Copy to clipboard and post in this thread resulting link:
image

From the link I can retrieve your device and Volumio OS build details. This will speed-up troubleshooting.

Depending on the Volumio release build, custom changes to the init can be stored in additional config files which are not touched by upgrade process. As an exaple config file userconfig.txt has been prepared for this very reason and need to be placed in /boot (if not present). I can guide you further once I can see your device details from generated log link.

Hi Nerd,

have sent the log link now (have been very busy for a while). In addition is to say, that when I choose the album directly as a whole like ever before, volumio restarts- weird.
Here’s the link, that I’ve already sent:

http://logs.volumio.org/volumio/aEY8xMN.html

Greetingz, Robert

Hey Robert,

I can see process waiting on incorrect .cue files.
From logs - you are 3.361 build. Enable test mode and apply update to latest beta from System menu. Once update completed, disable test mode.

Test your music tracks.

Hi Nerd, just tested it- almost the same as before- when I klick clear and play having chosen an album player restarts and puts only the first track to the end of the cue- so it doesn`t delete the cue after clicking ‘clear and play’ either- also I can’t see the tracks in the album- only numbers of them. That was working flawlessly for years with the same content and hardware- Really strange. Must be gotten dysfunctional after one of the last updates. I didn’t play from ssd for a while. With streaming there is no problem at all- except for sorting in Qobuz ;- ) but that never worked.

Hey Robert,

I think there is a bit of confusion. Queue is the where you manage tracks to be played. Whilst .cue are files capturing last position of played track for resume.

Lets dig further. Please replicate your actions as many times you can without reboot and provide link to the new set of logs, like you did before.

Ok, will do.

I just try to choose complete albums- thats the only scenario in praxis- I never choose single tracks.
Will send new link.

Hi Nerd,

have tried to choose several albums- again without success- here the link:

http://logs.volumio.org/volumio/HYt7JqF.html

Probably you won’t be able to see all actions, cause of volumio player always restarting after choosing an album on ssd.

I think you’ll find the solution in earlier versions of volumio, look into a configuration that was uploaded at least one year ago. As I said it was working under the same circumstances for years without any problems.

Cheers

“The devil leaves in the details” and:

main kernel: usb 2-2: Product: PSSD T7 Shield
main kernel: usb 2-2: Manufacturer: Samsung
main kernel: usb 2-2: SerialNumber: S6YGNS0TA11212L
main kernel: scsi 0:0:0:0: Direct-Access Samsung PSSD T7 Shield 0 PQ: 0 ANSI: 6

main kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock
main kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
main kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock

The USB device complaints about partition table and first partition’s sperblock. It is matter of time before layout will become unrecoverable without map backup. This is common “unsafe unplug” whilst device busy. I suggest to take a backup of your music and re-format the drive.

This is where things are getting really interesting, repeatedly crashing on .cuetools.wav.cue files:

`main volumio[781]: info: ALBUMART /albumart?cacheid=200&path=%2Fmnt%2FUSB%2FT7_Shield%2FMUSIK%2FADRAMELCH%2FOpus%2FOpus.cue&metadata=false’

main volumio[781]: info: URI /mnt/USB/T7_Shield/MUSIK/ADRAMELCH/Opus/Opus.cue

main volumio[781]: |||||||||||||||||||||||| WARNING: FATAL ERROR |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

main volumio[18860]: info: URI /mnt/USB/T7_Shield/MUSIK/ASHBURY/Something Funny Going On/Something Funny Going On.cuetools.wav.cue

main volumio[18860]: info: ALBUMART /albumart?cacheid=200&path=%2Fmnt%2FUSB%2FT7_Shield%2FMUSIK%2FASHBURY%2FSomething%20Funny%20Going%20On%2FSomething%20Funny%20Going%20On.cuetools.wav.cue&metadata=false

main volumio[18860]: info: URI /mnt/USB/T7_Shield/MUSIK/ASHBURY/Something Funny Going On/Something Funny Going On.cuetools.wav.cue

main volumio[18860]: |||||||||||||||||||||||| WARNING: FATAL ERROR |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

The only way is to find and delete all .cuetools.wav.cue files created by MS Windows CUETools. Volumio OS does not use it, hence does not understand how to handle them.

Hi Nerd, btw, thanks for effort!

Can’t delete cue sheets- I need it for other distros- btw it would take a horrible amount of time to delete all the cue- files from more than 1000 albums;- ). I have stored them on every drive- and have an album art jpg. stored for every album. UAPP plays the same drive without any problems- it just ignores the cue-files, other distros handle them right. I think upgrades of volumio-versions at some point destroyed the ability to handle my drives as they are. I have the wav-files stored in every folder + the cue-sheet+ album art jpg. Isn’t there a way to restore the old, working standard in next update?
The only thing I can try for now is to reformat the drive and store the content again.
Which format do you recommend?
One other way would be to change to moode for ssd music play and staying with volumio when just streaming. Never had an issue like this.

Cheers

You can use existing format as your USB drive already has: exfat.

We can try to train mpd to ignore .cue files altogether.

Inside of the T7_Shield/MUSIK folder, create file:
.mpdignore
Each line of that file may contain a list of shell wildcards. Matching files (or directories) in the current directory and all subdirectories are excluded. Place the following content filter:
*.cue

This way all files ending with .cue will be ignored.

1 Like

Hi Nerd, succeeded in the end- it works perfecty now- but only with your beta version of volumio- with the official version it doesn’t. Have formatted the drives and recopied all the albums- included cue-sheets no problem anymore.

http://logs.volumio.org/volumio/af4Lfvq.html

Please take into account your magic you`ve done now in the beta for next official volumio-release.

Thanks a lot for your efforts! Happy Easter!

Hey Robert,

The beta is from an upcoming official release channels, awaiting further testing and perhaps fixes (if any are required). I will pass by devs internally the .cue hiccup and discuss what we can do about it. No promises though.

In case of not being taken into account I’ll stay with this version for all times ;- )
Maybe you can instruct me how to do my individual changes for this then.
For now I will test the beta and report, if something fails.

Greetingz