did a 3rd and 4th pass.
much much better results this time. not exactly sure what i did differently.
so after the "recording" finishes, i save it immediately and then on a different PC i am importing the track into audacity and then trimming the front and back and aligning the start time exactly to the start of a normal secure rip, then chopping the end off past the number of samples, then Export again to 24 bit wav and create a "new" file (keep the original recording).
going to try a couple more time, this time doing the trimming right after its recorded so as to minimize the number of import/export in audacity.
edit: i compared the original recordings and bitcompare detected the offsets and it was identical result as the trimmed files, 682 mismatch; so its not the import/export in audacity changing anything. not bad either really. comparing in Beyond Compare as hex, its got minimal differences there too. so i am close, or maybe as close as i am going to get to resproducibility. my guess is its just not "secure rip" level data coming in from the bit stream maybe?
edit 2: i split the files to the tracks, and got MD5s of tracks.
10/14 tracks match md5, 4/14 are different.
BC hex compare:
928239200 same byte(s)
1690 left orphan byte(s)
1690 right orphan byte(s)
650 difference byte(s)
Differences found in compared tracks.
Zero offset detected.
Comparing:
"untitled-3.wav"
"untitled-4.wav"
Compared 154706916 samples.
Differences found: 682 values, 5:28.322086 - 58:27.964649, peak: 0.180267 (-14.88 dBTP) at 52:40.703492, 2ch
Channel difference peaks: 0.169952 (-15.39 dBTP) 0.180267 (-14.88 dBTP)
File #1 peaks: 0.988647 (-0.10 dBTP) 0.988617 (-0.10 dBTP)
File #2 peaks: 0.988647 (-0.10 dBTP) 0.988617 (-0.10 dBTP)
Detected offset as 0 samples.
Total duration processed: 58:28.093
Time elapsed: 0:03.385
1036.32x realtime
what do you guys think? will i get any more exact or do you think this is it? or should it be 100% every time?