Bugzilla – Bug 1655
Files with CUE sheet filtered from index
Last modified: 2012-02-27 17:33:27 UTC
When a MP3 has an associated CUE sheet with it, the parent file is filtered from Browse Music Folder, Browse Artists, All of the searches, etc. It is very nice to index the various artists/titles from a single large MP3 but in a lot of cases it's necessary to be able to see the parent file as well. This is especially needed for Electronic Artists (DJs). Even though they mix multiple tracks from multiple artists, the DJ themself is often referred to as "The Artist", which is now not searchable because the file has a cue sheet with it. It would be nice to have a server option to filter/not filter based on the presence of a CUE sheet.
This conflicts a tad with a previously fixed bug 70. are there any features left that don't have to be optional? ;)
We'll need to look at this later. In the mean time, consider making another CUE file that points to the whole original file.
Current 6.2 (release) cue support is broken. cue sheets show up empty (not being "parsed"?) http://forums.slimdevices.com/showthread.php?t=17977 I'm very much for the filtering of the "parent mp3" I'd also like the option of cue file being associated with an mp3 simply by being in the same directory and having the same filename (with the exception of a .cue extension)
In an age old build, it was possible to "hide" the big mp3 file using operating system funtionality. Under linux, it was as simple as putting a dot prefix on the mp3 file, although you need to edit the cue to point to the new file too. These days even hidden files are scanned. A hidden .mp3 (not scanned) and a visible .cue could give you solution A. Keeping the mp3 visible could be used to list the mp3 in total against album level id3 tags (DJ as Artist etc.). Is it more complicated than this?
Steven, could you see if this still happens with 7.0?
CUE handling appears to work as designed in SqueezeCenter 7. More information can be found in bug 717. Resolving as worksforme, please reopen and add additional comments if it does not work for you.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.