... You might need to have both VS2005 and VS2008 installed to build them. FLAC also requires nasmw...
For example, if it says that it has an offset of 6, does one enter 6 into the offset correction box and tell it to fix offset or do they enter -6 to bring it back to 0?
It doesn't hurt your files to use the Extra:Offset box to Verify your rip. If it says 6 then enter 6. If it says -6 then enter -6. This is actually the only way to see ARv2 entries at other offsets.
For those rips that don't immediately show an AR match in the rip log, I like to use CueTools to Verify. I'd love to also be able to check against ARv2 entries at other offsets.
I made the assumption the OP was referring to CUETools, with "it" being the CUETools Verify Log and correcting the offset when results came back non-zero. So my answer is based on that assumption. I agree after rereading the question that the OP could have meant something else and should've asked for clarification.QuoteFor those rips that don't immediately show an AR match in the rip log, I like to use CueTools to Verify. I'd love to also be able to check against ARv2 entries at other offsets.When you don't see results in the verify log except at another offset "Offsetted by xxx:" and tracks show "No match (V2 was not tested)" in 2.1.4 or "No match but offset" in 2.1.2a then there's a chance of ARv2 entries (see notes below). You can enter the value xxx in the Extra:Offset box and verify again to see if the ARv2 entries exist. Note1: "No match (V2 was not tested)" and "No match but offset" can also indicate a partial match or alternate mastering which still means "No Match".Note2: Even if all tracks show ARv1 entries at another offset there can still be ARv2 entries that weren't tested.
I've checked the CUEtools website to see what they mean but I still don't understand what they're trying to say
"Padded some input files to a frame boundary File(s) truncated and do not align on a frame (sector) boundary, zeroes padded to next frame (sector) boundary "
"Truncated 4608 extra samples in some input files Extra 4608 zero samples at end of file(s) detected and removed (Detection can be disabled) "
@ Gregory Any news/info regarding the upcoming v2.1.5 Stable version
Some erroneous FLAC encoders add an extra 4608 NULL (zero) samples at the end of each file.
Quote from: NetRanger on 19 June, 2012, 03:57:05 PM@ Gregory Any news/info regarding the upcoming v2.1.5 Stable versionSorry, this will probably take a few weeks more. I've just started on a new job and am somewhat overwhelmed at the moment.
I've just started on a new job and am somewhat overwhelmed at the moment.
I still remember that old signature of yours
I remember similar problems caused by old version of Microsoft .NET Framework 2.0. Try to install Microsoft .NET Framework 2.0 SP2, if you don't have it installed.