Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

Mnyb wrote: > Well LMS is gapless when the files supports it Flac or lame encoded mp3 > . ( seen some cue + MP3 old mp encoders did not support gapless, many > still don't afaik) > > One big file would however be gapless even on players that don't support > gapless ? > > However you easilly

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

cdmackay wrote: > This is exactly why I did the same. > > Recently, in these forums, people have told me that there is nothing > that FLAC-per-track cannot emulate; i.e. FLAC-per-track can provide a > 100% clone of the original CD. > > It seems to be that these two statements cannot both be

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

Well LMS is gapless when the files supports it Flac or lame encoded mp3 . ( seen some cue + MP3 old mp encoders did not support gapless, many still don't afaik) One big file would however be gapless even on players that don't support gapless ? However you easilly convert cue+flac/wav with

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

stephenkca wrote: > Yes, one FLAC per disc, cuesheet dividing into tracks. Did it to solve > the gap-gapless playback problem This is exactly why I did the same. Recently, in these forums, people have told me that there is nothing that FLAC-per-track cannot emulate; i.e. FLAC-per-track can

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

After a good bit of research, and finally finding the specification (as far as it can be called a specification) in Appendix A of the Golden Hawk Technology CDRWin User's Guide version 3.8 (difficult to find), I have concluded that "REM COMPOSER" is the correct tag. This is on the basis that

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

Does anyone know a definitive answer to the question: Should a COMPOSER tag in a cuesheet be formatted "COMPOSER" or "REM COMPOSER", or can it be one or the other? If it should be "REM COMPOSER" there's a bug in EAC 1.1 that I need to report (and a bit of work writing something to go and fix

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

DJanGo wrote: > You should go that route unless you have one flacfile and a cue sheet > that divides them into separate Tracks. > If you spotted some eroor and change that in the cue file - imho all the > files listed in the cue file where listed as new instead of the one with > the misspelled

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

gregklanderman wrote: > Hi Jan, sorry to hijack the thread, but what are you using on *nix > these days for ripping, managing tags, etc? I need to update my > tools, and would like to start re-ripping my collection to FLAC. There is a current thread about that in the "Linux" subgroup. >

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

gregklanderman wrote: > > On April 6, 2016 DJanGo forums.slimdevices.com> wrote: > > > under *ux the whole thing is a simple task. > > Hi Jan, sorry to hijack the thread, but what are you using on *nix > these days for ripping, managing tags, etc? Hi Grep, please open a new Thread for

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

> On April 6, 2016 DJanGo > wrote: > under *ux the whole thing is a simple task. Hi Jan, sorry to hijack the thread, but what are you using on *nix these days for ripping, managing tags, etc? I need to update my tools, and would like to

Re: [SlimDevices: Beta] COMPOSER-cuesheet parsing

stephenkca wrote: > (And yes, I should probably cross the bridge of embedding the cuesheet > metadata in the FLAC files. But that's another project, and the > simplicity of text files makes it really easy to fix errors as I spot > them.) > You should go that route unless you have one flacfile

[SlimDevices: Beta] COMPOSER-cuesheet parsing

Hi forum: I've recently upgraded, at last, to 7.9, and begun to explore its capabilities. This has led me to discover some inconsistencies in my collection with regard to COMPOSER. The bulk of my collection is FLAC/cuesheet, converted from CD by EAC (various versions). It appears that