Hello, I'm new to this list, and I would like to know about the current status of FLAC and surround formats (5.1, 7.1). I know it is possible to compress interleaved multichannel files with FLAC, but does it in any way have any multichannel matrix, that collects common information from all channels and use this when compressing? If not, wouldn't it be a great idea to have this feature!!! Cheerz! /Martin
--- Steve Lhomme <steve.lhomme@free.fr> wrote:> En réponse à Josh Coalson <xflac@yahoo.com>: > > > --- smoerk <smoerk@gmx.de> wrote: > > > good idea, i'm always putting *.cue files to the directory with > the > > > ripped audio files. but it would prefer one file per song and not > > one > > > big file for the whole cd. > > > > My vision of how the players should work is this: > > > > - make one album.flac with CUESHEET > > - player loads album.flac, sees CUESHEET, calculates CDDB id > > (or CDindex, or custom hash), looks up metadata in database > > Mmm, yes the CDDB feature would be great. Is it based on an ID per > disk or an ID > per track ? If so, how do you want to integrate it on a track basis ? > (CD ID + > track number ?)One CDDB id will get you all the metadata for the disc, but CDDB is a very barebones schema and the hashing mechanism is prone to collisions. There are better systems around (see http://www.musicbrainz.org) but if you are particular you will want to roll your own. Another thing the CUESHEET block will enable is pluggable metadata handling, e.g. the FLAC plugin can support multiple ways of hashing the CUESHEET and looking up info in an arbitrary database. Josh __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
--- smoerk <smoerk@gmx.de> wrote:> good idea, i'm always putting *.cue files to the directory with the > ripped audio files. but it would prefer one file per song and not one > big file for the whole cd.My vision of how the players should work is this: - make one album.flac with CUESHEET - player loads album.flac, sees CUESHEET, calculates CDDB id (or CDindex, or custom hash), looks up metadata in database - player presents album.flac as separate tracks - playlists can reference individual tracks in album.flac Josh __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
En r?ponse ? Josh Coalson <xflac@yahoo.com>:> --- smoerk <smoerk@gmx.de> wrote: > > good idea, i'm always putting *.cue files to the directory with the > > ripped audio files. but it would prefer one file per song and not > one > > big file for the whole cd. > > My vision of how the players should work is this: > > - make one album.flac with CUESHEET > - player loads album.flac, sees CUESHEET, calculates CDDB id > (or CDindex, or custom hash), looks up metadata in databaseMmm, yes the CDDB feature would be great. Is it based on an ID per disk or an ID per track ? If so, how do you want to integrate it on a track basis ? (CD ID + track number ?)> - player presents album.flac as separate tracks > - playlists can reference individual tracks in album.flacBTW, one option in MCF I didn't think of : the same way as you have in FLAC, you can have the whole CD in one file, and attach the cue file (the content is inside the same file).
En r?ponse ? Steve Lhomme <steve.lhomme@free.fr>:> En r?ponse ? Josh Coalson <xflac@yahoo.com>: > > > --- smoerk <smoerk@gmx.de> wrote: > > > good idea, i'm always putting *.cue files to the directory with the > > > > ripped audio files. but it would prefer one file per song and not > > one > > > big file for the whole cd. > > > > My vision of how the players should work is this: > > > > - make one album.flac with CUESHEET > > - player loads album.flac, sees CUESHEET, calculates CDDB id > > (or CDindex, or custom hash), looks up metadata in database > > Mmm, yes the CDDB feature would be great. Is it based on an ID per disk > or an ID > per track ? If so, how do you want to integrate it on a track basis ? > (CD ID + track number ?)Never mind, I found the information I wanted : http://www.freedb.org/modules.php?name=Sections&sop=viewarticle&artid=6 The CDDB ID is computed with data in the CD TOC. It's not something that is written on the CD (too bad). For integration on a Track basis, the ID would be to store in each track/file the Disc ID, the CD-track number and the CD-index number. Then when you have all files from a CD with all these informations you can reconstruct the CD the same way it was originally (well, not exactly, but a decent copy). So in MCF, I added a DiscID element in each Track, a DiscTrack and DiscIndex elements in the audio Track properties. To have a full CD, you will need to use a different Segment for each track. Otherwise you can use Chapters to "virtual cut" the data, but you'll be missing the CD features (Track number, index number).
On Wed, 2002-12-04 at 11:41, Josh Coalson wrote:> --- smoerk <smoerk@gmx.de> wrote: > > good idea, i'm always putting *.cue files to the directory with the > > ripped audio files. but it would prefer one file per song and not one > > big file for the whole cd. > > My vision of how the players should work is this: > > - make one album.flac with CUESHEET > - player loads album.flac, sees CUESHEET, calculates CDDB id > (or CDindex, or custom hash), looks up metadata in database > - player presents album.flac as separate tracks > - playlists can reference individual tracks in album.flac > > JoshDitto, thats how it works for REAL cd's, there kind of in one 'file' so to speak. Can you put single CD tracks in winamp playlists, I dont know, probably... I can see the other side of the arguement too tho, there may be many players around now, and in the future that will add flac support, but not flac-album support :( Dave