PDA

View Full Version : Slimserver 6.3.0 and CUE Sheets / Images



autopilot
2006-07-07, 06:42
Firstly, sorry if this has been covered elsewhere. I did post in the thread regarding compilation album grouping issues, but did not get a response. I am not sure this is related directly to that problem anyway.

What i am seeing is that when i have an image file and CUE, the album is being listed twice - once for the cue and once again for the image file. One correctly shows the track info and the other just has lists the image file as a track.

This is a royal pain in the but. i have gone back to 6.2.2 and i personally think that 6.3.0 should be pulled by Slim Devices and 6.2.2 should go back up in the meantime. i am sure i am not alone in thinking this. just think about all the new SB3 owners who will be downing it only to be confronted with all these issues.

Anyway, is there a fix/workaround or will we have to wait for the next release (which i hope comes around quicker this time)?

autopilot
2006-07-08, 03:26
Anyone?

Oh well, i have submitted a bug for this - http://bugs.slimdevices.com/show_bug.cgi?id=3716

I guess I should have expected something wrong regarding CUE sheets. Every version has had some kind of issue with CUE sheets, SD have never really made this a priority and fully got to grips with them. (6.2.0 does not display album art for CUE sheets, but at least it can actually play them unlike previous versions).

Anyway, i guess i should stop moaning here now. Keep up the otherwise good work chaps :)

Cheers.

PS - Before someone says use internal CUE sheets, yes i did think of that. Problem is that they dont work with all formats.

trixpan
2006-07-09, 18:03
Dominic,

I posted a comment on your bug. I have the same issue and it's starting to be quite anoying. I had been recomending SB for a lot of people but I'm starting to give up. The SlimServer is growing bigger and bigger but basic functions like PROPER CUE support still a BIG PROBLEM. It seem that there is no Q&A at all.


One single word to describe SlimServer. disappointing

autopilot
2006-07-10, 04:51
I have always been very disapointed with CUE support. It's a real shame because i think CUE+Image is the best way to archive CD's and any format can be used.

But most importantly, it's also the best way to ensure perfect gapless playback, which much of my collection requires.

To be honest, i never bother with it anymore because it's always been so poor. The problem is that i have a few older rips that are MP3 at a fairly low bitrate (before i knew any better). The original CD's are very old and are either lost or damaged. I could split the image into tracks, but to ensure perfect gapless playback i would need to transcode to someting like OGG. This would reduce the quality.

Nobody who works on SS really seems to take it seriously, as far as i can tell, and are quite happy to leave it broken in official releases. I do find this a little odd. Personally it should either be fixed or completely disabled. It's listed as a feature and is therefore a selling point, so it should be working or they are misleading people.

kdf
2006-07-10, 08:27
On 10-Jul-06, at 4:51 AM, dangerous_dom wrote:

>
> Nobody who works on SS really seems to take it seriously, as far as i
> can tell, and are quite happy to leave it broken in official releases.
>

sorry....have to cry bs here.
every effort is made by a lot of people.
it is bloody painful to handle all of the formats, and some get broken.
It is painful to have to handle all of the broken CUE's that get
reported as breaking slimserver and someone does fix them. Claiming it
isn't taken seriously is just crap. sorry, I know that doesn't fix the
problem, but report the bug and we'll work on it.
-k

autopilot
2006-07-10, 10:12
sorry....have to cry bs here.
every effort is made by a lot of people.
it is bloody painful to handle all of the formats, and some get broken.
It is painful to have to handle all of the broken CUE's that get
reported as breaking slimserver and someone does fix them. Claiming it
isn't taken seriously is just crap. sorry, I know that doesn't fix the
problem, but report the bug and we'll work on it.
-k

Sorry kdf, i know you and everyone else involved do work very hard. And for that i am very grateful for all your efforts in making this great product so good.

There are aspects of SS people obviously take very seriously, but i can't help but feel CUE support is very low down the list. Maybe there are good reasons for this, such as not many people use CUE's (but looking in the tagging/ripping forum it seems more and more people are interested in it).

The reason i think this is the case, is that when i got my SB3 and downloaded SS for the first time, CUE sheet support was completely broken. Could not play my albums ripped in this way at all. The next official release also had problems. After that the next releace (6.2.2, which i have had to go back to now) would play them, but wont display thier album art. Now this in 6.3.0. So basicallly, every official release (i have tried anyway) has had some kind of CUE related bug. With that, and the slow and limited responce to this thread and bug report, does make think that much less effort is put made regarding CUE's.

I have tried a few Beta's, but they had other issues that prevented me from using them. The last 6.5 beta was even worse.

And can i just say that the Squeezebox 3 is simply awesome and that i am really greatful for peoples, such as kdf, efforts.

Thanks.

kdf
2006-07-10, 11:06
Quoting dangerous_dom
<dangerous_dom.2aqoyz1152551701 (AT) no-mx (DOT) forums.slimdevices.com>:

> There are aspects of SS people obviously take very seriously, but i
> can't help but feel CUE support is very low down the list. Maybe there
> are good reasons for this, such as not many people use CUE's (but
> looking in the tagging/ripping forum it seems more and more people are
> interested in it).

I'd suggest that the reasons are much simpler. Those who work on
slimserver, paid and unpaid, probably have their own music in other
formats. For me, I can't see point of a CUE sheet-based system. If I
want to move tracks to another location, work computer or music
player, I want to move single tracks, not whole albums. I ripped
these from CD and have no intent to burn back to cd as I have the CD's
all packed away in sleeves in case I ever need them. On many
occasions, I've created samples and worked out a few bugs in order to
help. I've found along the way that "the right way" for CUE sheets
still seems to allow for a great deal of variation. Somewhere along
the way, slimserver seems to have also picked up non-standard features
that were requested.

I don't think that anyone deliberately puts CUE sheets into a ghetto,
nor is any other format. Their complexity makes them a bit more time
consuming, and it is often harder to get examples of problems becuase
the files are so large. Priority becomes far less of a factor than
the complexity of the problem itself. CUE sheets get fixed only after
hours of effort, and the result is "works for me, thanks" from one
user and 10 new ones saying "my CUE sheet is broken". Add in the
continual dictation as to HOW cue sheets should be handled and appear,
well...that just makes me want to avoid it altogether. At least with
single files, there is no question: parse the tags and list them. Cue
sheets: do you show the whole file, or not. Does the cue sheet
metadata override tags or not or both? Ask a number of users and you
might get lucky with a consensus. However, once implemented, the other
camps will then appear fuming about how their setups used to work and
are now broken. Unfortunately, it isn't policy on slimserver to
simply say 'no' when it comes to making changes for the latest and
loudest request.

I know this does less than nothing to help you solve your issue. I
can certainly understand the frustration of having your library in a
non-working state. Believe me, being a developer doesn't mean that
you get the server wokgin just the way you want either. However, my
hope is that by outlining at least my take on the issues, that you and
others who come across this may understand that it isn't any
deliberate sleight against CUE sheets, that it most certainly is a
priority to get all supported formats working and parsed correctly.

my current plan is to try and look at 6.3 parsing during lunch, just
to see if it is an obvious problem. I just have to hope the download
to my work computer can complete before lunchtime.

-kdf

autopilot
2006-07-11, 02:14
Thanks KDF, hopefully by 6.3.1 my complete library will be working. Looking at the responce to the bug report i filed, i would seem that it is indeed being taken seriously now.

My apoligies if i seemed a little 'off' in my previous posts in this thread. I am glad you realise this is just due to my frustration at not being able to use some of my library.

Furthermore, i understand that us CUE fans are in a minority and understand why this is. Very few products support them, in fact i can't name a single one. Thats probably another reason people must wonder what all the fuss is about. For that i am very gratful to Slim Devices for leading the way with there excellent format support and forward thinking. Once CUE support is fixed and OGG decoding is implemented in the firmware, i think that the SB3/SS will be the most near perfect product i have ever owned.

Mr SA
2006-07-25, 00:38
I'm running the latest 6.3.1 on Linux. Still broken.

I haven't had this working since I retired my old server 18 months ago. That was running on an ancient version that honoured operating system specification of hidden files (dot prefix) and the database would not index cue-sheeted mp3 files that were named with a dot prefix.

Is there any chance we can go back to simple funcitonality like that? It worked. It was simple. It was logical. What business might SlimServer possibly have indexing hidden files?

For me, this is all to do with gapless playback. The only reason i have any cue sheets is to get gapless. I now have a legacy of very high quality mp3 rips (Lame preset extreme/EAC) with cuesheets. The answer is the difference between retranscoding and a feature that should either work or at least show stable behaviour from version to version. It strikes me that the development hasn't pinned down exactly what certain functions are for.

FWIW, 6.3.1 does play my cuesheet files; it does honour symlinks in my mp3 library. This is a good build. I'm just petrified that the next build will break these things.