IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
fb2k.9 and flac embedded cuesheets
gharris999
post Mar 20 2006, 21:13
Post #1





Group: Members
Posts: 99
Joined: 13-January 04
Member No.: 11204



The old fb2k behavior was to read the flac embedded cuesheet and populate the playlist with all the tracks. The new version only lists the flac file in the playlist. Is this by design? Anyway to get the old behavior back? (other than by reinstalling the old version?)

edit: sp

This post has been edited by gharris999: Mar 20 2006, 21:13
Go to the top of the page
+Quote Post
gharris999
post Mar 20 2006, 21:37
Post #2





Group: Members
Posts: 99
Joined: 13-January 04
Member No.: 11204



OK, I think I see what's going on. The new version is MUCH, MUCH less forgiving about tags in the cuesheet. In my case, FB2K.9 is barfing on the following tags, which I have in ALL my cuesheets:

DISC_ID (cdplayer.ini index)
CDDB_ID (freedb lookup index)
COMPOSER (yup, you guessed it: the composer)
COMMENT (album and track comments)
GENRE (genre name)
YEAR (year of recording)

This is true for album tags and for track tags.

Soooo....just what the heck's the dang deal here, anyways? Is FB2K now in the business of enforcing someone's idea of what constitutes a clean cuesheet? Why not have a "relaxed cuesheet parsing" option so that FB2K ignores tags it doesn't understand?

Edit: PS: Slimserver uses the COMPOSER, GENRE, COMMENT and YEAR tags. I might be able to live with out some of the others, but GENRE is a necessity.

This post has been edited by gharris999: Mar 20 2006, 21:39
Go to the top of the page
+Quote Post
Jimbo51
post Mar 21 2006, 12:34
Post #3





Group: Members
Posts: 65
Joined: 2-October 04
Member No.: 17440



I'm having similar problems to you.
http://www.hydrogenaudio.org/forums/index....showtopic=42637

Can we at least have some information on the syntax we need to get things working? This new parser is annoying.
Go to the top of the page
+Quote Post
Florian
post Mar 21 2006, 13:06
Post #4


Mp3tag developer


Group: FB2K Moderator (Donating)
Posts: 854
Joined: 5-May 03
From: Dresden, Germany
Member No.: 6411



The new cuesheet parser reads cuesheets which are compliant to the cuesheet specification.

If your cuesheet isn't parsed correctly, you'll find an notification message on the console ('View > Console') about that.


--------------------
Mp3tag - universal multi-format tag editor
http://www.mp3tag.de/en/
Go to the top of the page
+Quote Post
Synthetic Soul
post Mar 21 2006, 13:20
Post #5





Group: Super Moderator
Posts: 4887
Joined: 12-August 04
From: Exeter, UK
Member No.: 16217



QUOTE (gharris999 @ Mar 20 2006, 08:37 PM)
Edit: PS: Slimserver uses the COMPOSER, GENRE, COMMENT and YEAR tags.  I might be able to live with out some of the others, but GENRE is a necessity.
According to the spec the available commands are only:
  • CATALOG
  • CDTEXTFILE
  • FILE
  • FLAGS
  • INDEX
  • ISRC
  • PERFORMER
  • POSTGAP
  • PREGAP
  • REM
  • SONGWRITER
  • TITLE
  • TRACK
Is there anyway you can tell Slimserver to prefix (non-standard) commands with "REM "?


--------------------
I'm on a horse.
Go to the top of the page
+Quote Post
gharris999
post Mar 21 2006, 22:47
Post #6





Group: Members
Posts: 99
Joined: 13-January 04
Member No.: 11204



QUOTE (Synthetic Soul @ Mar 21 2006, 04:20 AM)
QUOTE (gharris999 @ Mar 20 2006, 08:37 PM)
Edit: PS: Slimserver uses the COMPOSER, GENRE, COMMENT and YEAR tags.  I might be able to live with out some of the others, but GENRE is a necessity.
According to the spec the available commands are only:
  • CATALOG
  • CDTEXTFILE
  • FILE
  • FLAGS
  • INDEX
  • ISRC
  • PERFORMER
  • POSTGAP
  • PREGAP
  • REM
  • SONGWRITER
  • TITLE
  • TRACK
Is there anyway you can tell Slimserver to prefix (non-standard) commands with "REM "?
*



Slimserver doesn't create cuesheets. It reads them. It's a music indexing and playback system. Where is this "standard" you are refering to documented? The spec quoted above is laughably inadequate for cataloging and indexing classical music. Without GENRE and COMPOSER tags, my music library would be totally broken. The COMMENTS tag is helpful too...I put composer biographical info and performance details there. Why not just have FB2K ignore tags it doesn't understand and at least parse the PERFORMER, TITLE and TRACK tags? Then, if the user modifiys the cuesheet in FB2K, put up a warning dialog about the fact that they are about to loose their unsupported tags when the cuesheet gets rewritten.

BURRRRN doesn't have a problem with my cuesheets, by the way.

Edit: typos

This post has been edited by gharris999: Mar 21 2006, 22:54
Go to the top of the page
+Quote Post
foosion
post Mar 22 2006, 00:34
Post #7





Group: FB2K Moderator (Donating)
Posts: 4409
Joined: 24-February 03
Member No.: 5153



See Appendix A of the CDRWIN manual for the specification of the cue sheet format. (Edit: available as PDF online)

Per specification cue sheets are restricted to ASCII encoding. Add to that the rather limited set of metadata fields. All in all, cue sheets appear laughably inappropriate for storing metadata in general to me.

This post has been edited by foosion: Mar 22 2006, 00:35


--------------------
http://foosion.foobar2000.org/ - my components for foobar2000
Go to the top of the page
+Quote Post
Synthetic Soul
post Mar 22 2006, 10:03
Post #8





Group: Super Moderator
Posts: 4887
Joined: 12-August 04
From: Exeter, UK
Member No.: 16217



As long as apps support the "REM <tag> <value>" syntax then I don't see too much of an issue. Personally I'm happy with TITLE and PERFORMER. REM DATE is nice, but not necessary.

QUOTE (gharris999 @ Mar 21 2006, 09:47 PM)
Slimserver doesn't create cuesheets.  It reads them.  It's a music indexing and playback system.
Then I guess it has no place messing with the cuesheet standard. If it is going to support cuesheets it should adhere to "the standard". Note: The CDRWIN Appendix is the unofficial standard, but it's the only one there is, written by the originators of the cuesheet (IIRC). If Slimserver have developed their own standard then they can't really complain about other software not understanding it. As foosion points out, if they require meta data storage then they should probably have gone with an alternative system.

NB: foobar does understand REM GENRE; REM DATE; and REM COMMENT statements, e.g.:

REM DATE 2006
REM GENRE Rock
REM COMMENT "This value has spaces, so is quoted"


QUOTE (gharris999 @ Mar 21 2006, 09:47 PM)
BURRRRN doesn't have a problem with my cuesheets, by the way.
I guess Burrrn just ignores lines that are irrelevant to burning a CD with CD Text, much as 0.8.3 presumably did.

Maybe you should be speaking to the Slimserver guys?


--------------------
I'm on a horse.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 22nd July 2014 - 22:10