[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Traverso-devel] CDRDAO export
From: |
Nicola Döbelin |
Subject: |
Re: [Traverso-devel] CDRDAO export |
Date: |
Thu, 10 May 2007 11:18:49 +0200 |
> > One open question: Do we leave the standard 2 seconds of pregap
> > silence between songs? I'm thinking it should include "PREGAP
> > 0:02:00" before the first track of each song's set of tracks,
> > including before the very first track of the CD. So in the above
> > example, we'd get:
> >
> > 1: (PREGAP 0:02:00) song 1 mark 1
> > 2: song 1 mark 2
> > 3: song 1 mark 3
> > 4: (PREGAP 0:02:00) song 2 mark 1
> > 5: song 2 mark 2
> > 6: song 2 mark 3
>
> That's a good question. The standard says only that the first track of a
> CD should have a 2 seconds pregap. So I'd say we let the toc file
> generator put a 2 sec pregap before the first track in the toc, but not
> at the first track of each song!
According to wikipedia that is correct. Red Book CDs have a 2 second pregap
only before track 01. It's trivial to add it to the toc file, I'll do it
tonight.
> And I think that in the future, there should be special pregap markers.
> It could be visualised like if the track marks had a draggable start and
> end point, painted in a transparent color. like a range selection..
> And so the start edge would mean PREGAP and the end edge would mean
> start of TRACK. This way one can put whatever they whish inside the
> pregaps, and make them any length.
How about that: If there is no marker at position 0:0:0, write the part from
0:0:0 to the first marker into the pregap. That would allow to have a bonus
track before track 01, but it wouldn't allow to have pre-gaps between, say,
tracks 03 and 04.
Oh dear, this is getting complex. (I see tons of if() conditions coming.) I'd
rather prefer to add a fixed 00:02:00 pre-gap and not allow having any
additional pre-gaps at all. But I'll see if I can at least add the above
described compromise without messing it all up.
I would also like to ask for suggestions on key actions used for "add end
marker" and "add CD index". We only have <M> for "add CD track" ATM. The end
marker is added automatically, but since it can be deleted, it should also be
possible to re-add it. Any suggestions? How about <SHIFT M>, and <CTRL M>?
Greetings
Nicola
Remon: Is the stuff with the TEMP_* markers in Song::get_cdrdao_tracklist()
clean? I was not sure if they are deleted properly at the end of the function.
What it does is temporarily add a marker at 00:00:00 if there is none, and add
an end marker at the end of the track if no end marker is present. Then I can
iterate over mlist without having to bother about missing positions.
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
- Re: [Traverso-devel] CDRDAO export, (continued)
- Re: [Traverso-devel] CDRDAO export, Remon, 2007/05/09
- Re: [Traverso-devel] CDRDAO export, Jonatan Liljedahl, 2007/05/09
- Re: [Traverso-devel] CDRDAO export, Remon, 2007/05/09
- Re: [Traverso-devel] CDRDAO export, Nicola Döbelin, 2007/05/09
- Re: [Traverso-devel] CDRDAO export, ben levitt, 2007/05/09
- Re: [Traverso-devel] CDRDAO export, Jonatan Liljedahl, 2007/05/09
- Re: [Traverso-devel] CDRDAO export,
Nicola Döbelin <=
- Message not available
- Re: [Traverso-devel] CDRDAO export, Jonatan Liljedahl, 2007/05/10
- Re: [Traverso-devel] CDRDAO export, Nicola Döbelin, 2007/05/11
- Re: [Traverso-devel] CDRDAO export, ben levitt, 2007/05/11
- Re: [Traverso-devel] CDRDAO export, Nicola Döbelin, 2007/05/12
- Re: [Traverso-devel] CDRDAO export, Nicola Döbelin, 2007/05/12
- Re: [Traverso-devel] CDRDAO export, ben levitt, 2007/05/12
- Re: [Traverso-devel] CDRDAO export, Nicola Döbelin, 2007/05/13
- Re: [Traverso-devel] CDRDAO export, ben levitt, 2007/05/13
- Re: [Traverso-devel] CDRDAO export, Remon, 2007/05/14
- Re: [Traverso-devel] CDRDAO export, Jonatan Liljedahl, 2007/05/14