I've done some searches but I haven't been able to find this answer explicitly - and I was hoping that the knowledgeable people here could help.When I first started to digitize my collection, I did flac images with cue sheets because my squeezebox supported it.

There was a version during the 7.x switch that it became flaky so I completed the activity by ripping to individual tracks.

I was building a new DIY NAS and I noticed that with 7.5.4 the splitting wouldn't work unless I used Windows. Which is fine.

I wanted to split the images into individual tracks and I know that Medieval Cue Splitter doesn't maintain file quality integrity.

Perusing the forums, I see that people recommend foobar2000 or CueTools - my question is, but splitting files, is the quality preserved, or should I just rip all 70 discs to individual tracks?

I even think jitter is the wrong term here. It seems in some places there is jitter used as explanation when Medival Cuesplitter breaks up the files at the wrong positions and not a frame boundary. When you split with Cuetools and really have a bad CUE file that was created under some strange circumstances Cuetools even is warning you about such a problem.Since you ripped all your cds correctly with CUE file Cuetools should have no problem and even creates a log file after splitting that lets you check the CRC against your original log. You can´t ask for more

Even i have several albums with single flac and a .cue sheet. ripped securely with EAC. I wish to split them individually. And my priority is that the quality shouldn't change a bit and also the track lengths shold remain perfect.Is cuetools the best software for this as i want everything to be accurate?And will the individual tracks be exactly similar if i had to rip the same CD to individual tracks?Please clear these doubts..

And my priority is that the quality shouldn't change a bit and also the track lengths shold remain perfect.

It won’t; they will.

QUOTE

Is cuetools the best software for this as i want everything to be accurate?

Any program that wasn’t completely broken would produce the same results, so it’s not “the best” in terms of accuracy, but it’s probably the one with the most complete set of features for dealing with cue-sheets and also the most accessible developer.

QUOTE

And will the individual tracks be exactly similar if i had to rip the same CD to individual tracks?

Now i don't understand this report at all Can you please explain to me what this actually means? Are the tracks mathching those with the accurate rip database?What does the CRC , v2, staus mean (0+0/1) No match??What does this mean 01 [c2230611] (1/1) Accurately rippedWhat is This Track Peak [ CRC32 ] [W/O NULL] ?And when there are only 3 songs why are there 4 rows under track peak -- 98.8 [F5DA5076] [9418DE63] ??

Post Script- In the CUEtools under the extra menu there are 3 options .Pregap 00:00:00.Data Track 00:00:00.Offset 0I left this as it is ,should i have fillled any of these especially the offset because my drive has an offset value of +676.

Yes, after the bitstream has been moved 676 samples in one direction. The reason is that CD burners do not agree upon how many 0's to write before the first 1 (roughly speaking), so different pressings of the same bitstream, will start at slightly different times.

QUOTE

What does the CRC , v2, staus mean (0+0/1) No match??

Old AccurateRip didn't take everything into account. New database entries have a second checksum too. 0+0 means no match in either (before the 676 correction is done), and /1 means there is one entry in the database.

QUOTE

What does this mean 01 [c2230611] (1/1) Accurately ripped

That means that -- after moving the bitstream by 676 -- it matches the one in AccurateRip. Good news.

QUOTE

What is This Track Peak [ CRC32 ] [W/O NULL] ?

Track peak is in % of full volume, CRC32 is a checksum (different than the AccurateRip checksum) of the entire file, W/O NULL is the same algorithm applied but after removing nullsamples. (Which can be useful in case of offset differences -- if two pressings differ only in that one of them has a nullsample at the beginning which the other has at the end, they will have different CRC32 but same W/O NULL checksum.

QUOTE

And when there are only 3 songs why are there 4 rows under track peak -- 98.8 [F5DA5076] [9418DE63] ??

In this accurip log that was generated after splitting the Doors album using CUEtools why is the audio offsetted by so many different values? -1268,-373,-309,-200,928,962? And of these which offset value did CUEtools use for creating my tracks.CUE tools even generated a 426ms "00. (HTOA).flac" file HIdden track . Is it necessary to preserve this track along with the others or simply delete this. It contains no audio.

In this accurip log that was generated after splitting the Doors album using CUEtools why is the audio offsetted by so many different values? -1268,-373,-309,-200,928,962?

These are other rips in the database that have the same structure as your disc. The offsets vary due to different pressings of the disc or rips without offset correction. Nothing to worry about. Just means the title is popular.

QUOTE

And of these which offset value did CUEtools use for creating my tracks.

Provided no offset was set to be applied the files are split with zero offset correction. It would tell you at the top of the log if offset were applied. The first results shown are your files and how many rips they match. These are at zero offset.

QUOTE

CUE tools even generated a 426ms "00. (HTOA).flac" file HIdden track . Is it necessary to preserve this track along with the others or simply delete this. It contains no audio.

It does represent the Pregap length 00:00:32 and may not be 100% digitally silent. If you discard the HTOA file you should edit the cue with the pregap to keep the original disc structure. It is possible to set CUETools so it doesn't create the HTOA file. This is not recommended but unless there is actual audio, a pregap should be fine.

QUOTE

And while splitting the tracks is it necessary to fill the values PREGAP, DATA track and Offset in the CUEtools extra menu.