Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Ripping CDs: Rescue pregap- & postgap-lengths Information (Read 2703 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Ripping CDs: Rescue pregap- & postgap-lengths Information

2 Requests and 1 Suggestion:

R1 "rescue the pregap length":
If i rip as "generate multi-track files" ==> a pregap (if exists) will be documented in the embedded cuesheet ==> CUETools can test the ripped cd in AccurateRip, later (after ripping). (This processes fine, CUETools writes (if wanted) the results as metadata in coresponding Tags: Fantastic! It runs for "generate multi-track files" also  )

But if i rip as "convert each track to an individual file" than no pregap is writen in a Log File or in the flac files. The pregap information of the CD is lost and CUETools could not test AccurateRip, if a pregap exists

Hence i think fb2k should write a log file for rescue the length of an existing pregap of the CD, in the folder of the generated flac files.
(It would be nice to have a Log file "a standard (that comes from EAC)" in fb2k also.)

In the case of "generate multi-track files", the log file could be written in a tag in the generated flac file.
(..., if the Log File contains more information, e.g.: Error state of each ripped track, Date & Time of ripping, AccurateRip status, Disc- or AccurateRip-ID, ...)


R2 "rescue the postgap lengths":
The pause between 2 tracks will be appended at the end of the 1. track. Please write the length of this pause in a new tag "POSTGAP" in the 1. track (the track to which the pause is appended). This would be fine, since this information (that is a important e.g. for classical CDs) could be rescued by this way (instead of estimation it later with less or more effort). (And it is an advantage over EAC, also).


S1 "naming":
"generate multi-track files" should better be named as "generate a multi-track file" (instead of "files"), because it creates only 1 file!

Ripping CDs: Rescue pregap- & postgap-lengths Information

Reply #1 –
Quote from: anaono on
"generate multi-track files" should better be named as "generate a multi-track file" (instead of "files"), because it creates only 1 file!

Do you refer to the converter option? It can create several files. It depends on the grouping pattern.

Quote from: anaono on
The pause between 2 tracks will be appended at the end of the 1. track. Please write the length of this pause in a new tag "POSTGAP" in the 1. track (the track to which the pause is appended). This would be fine, since this information (that is a important e.g. for classical CDs) could be rescued by this way (instead of estimation it later with less or more effort). (And it is an advantage over EAC, also).

It seems that POSTGAP command has different meaning.

Ripping CDs: Rescue pregap- & postgap-lengths Information

Reply #2 –
Thanks for rapid answer and the Link to the cue-sheet syntax/semantik

Quote from: cue-sheet syntax/semantik link=msg=0 date=
This command is used to specify the length of a track postgap.

I think: The pause after a track is the postgap.


Quote from: cue-sheet syntax/semantik link=msg=0 date=
The postgap data is generated internally by your cdr software.

OK, fb2k-CD-ripping is a cdr software.


Quote from: cue-sheet syntax/semantik link=msg=0 date=
No data is consumed from the current data file.

The pause has no data (only 0 samples). But you are right, there is silence appended at track-end (and if played, this 0-sample-data is consumed):

You mean?:
The POSTGAP contains the length of 0-samples (the pause) that must be generated (by a (cd-) player). And fb2k-ripping has this pause appended already as 0-samples. Hence nothing silence must be generated. The silence exists at track-end already, and must only be played.

OK:
Hence, the tag should be named "POSTGAP-PAUSE" (a pause that exists as 0-samples and must not be generated) instead of "POSTGAP" (a pause that must be generated).

An important hint. Thank you

Ripping CDs: Rescue pregap- & postgap-lengths Information

Reply #3 –
Quote from: lvqcl on
Quote from: anaono on
"generate multi-track files" should better be named as "generate a multi-track file" (instead of "files"), because it creates only 1 file!

Do you refer to the converter option? It can create several files. It depends on the grouping pattern.


You are right. I thought 1 CD = 1 track with embedded cuesheet. But "name format & grouping pattern" gives me the opportunity to produce several tracks (each with an embedded cuesheet, e.g. by using %track%). For CD ripping this (probably) does not make sense, but for other applications already.

Hence S1 "naming" is obsolete!  Or it could be named "generate a/ multi-track file/s"