INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: CUE file format written by MC  (Read 2351 times)

Frobozz

  • Citizen of the Universe
  • *****
  • Posts: 641
  • There is a small mailbox here.
CUE file format written by MC
« on: July 08, 2010, 05:43:30 am »

I noticed that MC15 isn't writing the file type at the end of the FILE line in CUE files.  Valid file types being WAVE, MP3 and AIFF.  The Hydrogenaudio wiki has more info: Cue sheet

The FILE line should be of the form
FILE "foo.wav" WAVE
or
FILE "foo.flac" WAVE

I noticed this problem when I tried to open a CUE file created by MC15 in CueTools to verify and then split the tracks.  CUETools gave an error when trying to open the CUE file.  Manually editing the CUE file to add the word "WAVE" to the end of the FILE line fixed the problem and CUETools was able to open and process the file.

More of an issue with CUETools doing a poor job of parsing than MC15...
Logged

JohnT

  • Citizen of the Universe
  • *****
  • Posts: 4627
Re: CUE file format written by MC
« Reply #1 on: July 08, 2010, 01:23:08 pm »

Quote
I noticed that MC15 isn't writing the file type at the end of the FILE line in CUE files ...
Try the next build, it should be there.
Logged
John Thompson, JRiver Media Center

Frobozz

  • Citizen of the Universe
  • *****
  • Posts: 641
  • There is a small mailbox here.
Re: CUE file format written by MC
« Reply #2 on: July 09, 2010, 03:03:34 am »

Neat!

By the way, in my testing using CueTools to verify various MC15 rips, everything I tried compared.  CueTools has the ability to compare CUE files against AccurateRip and tries various offsets and recalculates various offsets to get matches even if the given CUE file has a different offset.  All the tracks and CUE files ripped with MC15 verified.  Tried single file CUE files in both FLAC and WAV format.  They verified.  Had CueTools generate a CUE file from separate tracks ripped by MC15.  That generated CUE file verified and the individual tracks verified.

Exactly as I expected.  No surprise.  Just goes to demonstrate that MC15 is doing the right thing when it comes to ripping. 
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
Re: CUE file format written by MC
« Reply #3 on: July 09, 2010, 04:37:11 am »

You can use CUETools for verifying MC rips as long as there is no pregap aka INDEX 00 entry before the first INDEX 01 entry.

MC is not designed to include the possibly existing INDEX 00 entries in the cue sheets.

If the album happens to have a pregap before the first track CUETools cannot find a match unless the value is given manully. It is possible to detect the gaps with EAC from the original CD (no need to re-rip) and then verify the MC rip with CUETools.

Naturally the album must already be in the Accurate Rip database before CUETools can verify it.
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755

Frobozz

  • Citizen of the Universe
  • *****
  • Posts: 641
  • There is a small mailbox here.
Re: CUE file format written by MC
« Reply #4 on: July 09, 2010, 01:07:51 pm »

The index00 pregap is what CueTools splits out as an HTOA track?

I'll have to hunt around to find a CD in my collection that has pregap and experiment.  In my experience there don't seem to be very many and I don't believe I have any that have actual music audio in the pregap.  It just seems to be a very short bit of silence and that's it.

I don't own anything that is on the Wikipedia list of albums that have hidden audio in the pregap (and there are very few in that list I would actually want to own).  I'll have to see if my local library has any of those CDs.

Is MC adding any pregap audio to the beginning of the first track or is it leaving it out?
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
Re: CUE file format written by MC
« Reply #5 on: July 09, 2010, 01:30:59 pm »

MC rips the tracks from the INDEX 01 entry to the next track's INDEX 01 entry, which is absolutely correct. The possibly existing INDEX 00 entries are useless with PC players.

The most common additional pregaps before the first track are silent and short. Some typical values are 32, 33 or 34 frames. (The time format in cue sheets is minutes, seconds and frames [mm:ss:ff]. Each frame is 1/75 s.)

The actual hidden tracks before the track one are very rare.
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755

Frobozz

  • Citizen of the Universe
  • *****
  • Posts: 641
  • There is a small mailbox here.
Re: CUE file format written by MC
« Reply #6 on: July 09, 2010, 03:23:05 pm »

MC ignoring the index00 info is fine and could be considered a good thing.  Makes no difference to what I actually care about when ripping tracks.

Is there any reason for the short and silent pregaps for the first track?  Maybe one brand of CD authoring software started doing that by default and for that reason it shows up on some CDs?  It doesn't make sense.
Logged
Pages: [1]   Go Up