Hello, I have not been here in a while after completing a project
last year (September ?) of ripping about 1300 CDs to Flac.
I had a question regarding the procedure I used 6 to 8 CD/DVD
drives to rip the CDs in parallel to Flac (level 0 compression initially).
I have noticed that a few songs seem to be "contaminated" by
another song. I have noticed maybe about 3 I have come across
and even noticed 1 or so song is missing from the CD ripped to flac.
But I did notice that a song may start out fine but then I hear another,
different song that cross contaminated the song expected or
the song expected has a portion of another song .
So far when I discover these, I just redo the rip individually from
a wav source I performed a few months before the flac conversion
using iTunes.
Is this common? It is just I have not listened to ALL (let us say) 20,000 songs
converted from the CD to flac and I just come upon these as I listen to
songs I may never have encountered before in my library.
I just have to take a note to re-rip or convert a solid .wav source to flac
and move on.
Did I do something wrong with the first process of running the software in parallel
having multiple CD/DVD drives active in the conversion process (not really using the
batch ripping feature at the time). Could something have gone wrong with the
processor cores used... like 7 of them?
I was considering redoing the entire project onto a fresh hard drive but take a little
longer time and not have too many DVD/CD drives actively running ...not having 8 of them
going at once, but maybe 2, 3 ? 4 or 5 running and redoing the conversions over fresh.
Thank you. But so far so good...I have not noticed too much "cross-contamination" of
audio files (Flac) and I did have to convert level 0 compression to level 5 because
I noticed level 0 was not totally compatible with the Pioneer AVH-4200NEX car stereo
device. I also performed a conversion to uncompressed lossless (like having the .Wav with
metadata).
Oh back to the "cross contamination" I noticed these in the level 5 as well as the original flac
source of the level 0 compressed file(s) I started with. Maybe I should not have used level 0 in the first place?
This is why I was just thinking to start fresh and use level 5 this time around.
So the summary of my question:
did the occasional "cross contamination" and omission of 1 or so song(s)
from the ripped CD album come from using level -0 compression initially or could it
come from running the software with up to 8 optical drives in parallel and or not
taking advantage of the batch ripping (I did not feel comfortable with that at the
time) or could it be caused by running software with multiple (too many ) cores?
Could the processors get crossed and the effect would be an audio file that may
contain another song's data; and if so, how to lessen or eliminate this from
occurring so I can be assured there will be NO cross contaminated files-- since I really
cannot listen to ALL 20 thousand songs-- some songs on albums (filler) are junk
I may have to take time to save space on the hard drive to deleting songs that
just don't cut it.
last year (September ?) of ripping about 1300 CDs to Flac.
I had a question regarding the procedure I used 6 to 8 CD/DVD
drives to rip the CDs in parallel to Flac (level 0 compression initially).
I have noticed that a few songs seem to be "contaminated" by
another song. I have noticed maybe about 3 I have come across
and even noticed 1 or so song is missing from the CD ripped to flac.
But I did notice that a song may start out fine but then I hear another,
different song that cross contaminated the song expected or
the song expected has a portion of another song .
So far when I discover these, I just redo the rip individually from
a wav source I performed a few months before the flac conversion
using iTunes.
Is this common? It is just I have not listened to ALL (let us say) 20,000 songs
converted from the CD to flac and I just come upon these as I listen to
songs I may never have encountered before in my library.
I just have to take a note to re-rip or convert a solid .wav source to flac
and move on.
Did I do something wrong with the first process of running the software in parallel
having multiple CD/DVD drives active in the conversion process (not really using the
batch ripping feature at the time). Could something have gone wrong with the
processor cores used... like 7 of them?
I was considering redoing the entire project onto a fresh hard drive but take a little
longer time and not have too many DVD/CD drives actively running ...not having 8 of them
going at once, but maybe 2, 3 ? 4 or 5 running and redoing the conversions over fresh.
Thank you. But so far so good...I have not noticed too much "cross-contamination" of
audio files (Flac) and I did have to convert level 0 compression to level 5 because
I noticed level 0 was not totally compatible with the Pioneer AVH-4200NEX car stereo
device. I also performed a conversion to uncompressed lossless (like having the .Wav with
metadata).
Oh back to the "cross contamination" I noticed these in the level 5 as well as the original flac
source of the level 0 compressed file(s) I started with. Maybe I should not have used level 0 in the first place?
This is why I was just thinking to start fresh and use level 5 this time around.
So the summary of my question:
did the occasional "cross contamination" and omission of 1 or so song(s)
from the ripped CD album come from using level -0 compression initially or could it
come from running the software with up to 8 optical drives in parallel and or not
taking advantage of the batch ripping (I did not feel comfortable with that at the
time) or could it be caused by running software with multiple (too many ) cores?
Could the processors get crossed and the effect would be an audio file that may
contain another song's data; and if so, how to lessen or eliminate this from
occurring so I can be assured there will be NO cross contaminated files-- since I really
cannot listen to ALL 20 thousand songs-- some songs on albums (filler) are junk
I may have to take time to save space on the hard drive to deleting songs that
just don't cut it.
Comment