IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Fixing wrong offset
geopoul
post Jan 27 2005, 04:12
Post #1





Group: Members
Posts: 42
Joined: 12-December 04
Member No.: 18631



A friend gave me some eac cd rips in the form of a single wav+cue sheet. The read offset in eac had not been set during the ripping process so I want to correct it now. I know that the actual read offset of the drive used is 1858 and I am considering mounting these cue sheets to virtual drive with daemon tools and then rerip with eac having set -1858 as read offset. Will this process fix the wrong offset issue?

Edit: Topic Title meant to be "Fixing wrong offset".... Sorry for bad my english!

This post has been edited by geopoul: Jan 27 2005, 04:17
Go to the top of the page
+Quote Post
precisionist
post Jan 27 2005, 17:31
Post #2





Group: Members
Posts: 739
Joined: 16-January 04
From: Germany
Member No.: 11279



You'd need an entered read offset correction of +1858, if the virtual drive's actual offset is 0.

Anyway, I recommend you a more easy method:
Open the image in a wav editor (EAC's editor should be enough). Delete 1858 samples at the end and add 1858 samples at the beginning of the wav. Hopefully there are only null samples at the wrong-offset source wav's end and beginning...Leave the cue file unchanged, wav-splitting by cuesheet shouldn't be influenced by the manual offset (re-)shift.


--------------------
I know that I know nothing. But how can I then know that ?
Go to the top of the page
+Quote Post
F1Sushi
post Jan 27 2005, 18:28
Post #3





Group: Members
Posts: 158
Joined: 30-August 02
Member No.: 3236



QUOTE (geopoul @ Jan 26 2005, 11:12 PM)
A friend gave me some eac cd rips in the form of a single wav+cue sheet. The read offset in eac had not been set during the ripping process so I want to correct it now. I know that the actual read offset of the drive used is 1858 and I am considering mounting these cue sheets to virtual drive with daemon tools and then rerip with eac having set -1858 as read offset. Will this process fix the wrong offset issue?

Edit: Topic Title meant to be "Fixing wrong offset".... Sorry for bad my english!
*


Why bother? unsure.gif
Go to the top of the page
+Quote Post
precisionist
post Jan 28 2005, 11:12
Post #4





Group: Members
Posts: 739
Joined: 16-January 04
From: Germany
Member No.: 11279



QUOTE (F1Sushi @ Jan 27 2005, 06:28 PM)
Why bother?  unsure.gif
*

Perhaps somewhen he gets the CD a second time and wants to compare the wavs easily ?
He can't restore lost audio data, if some of the 1858 cutted samples at the beginning had been non-null samples, though.


--------------------
I know that I know nothing. But how can I then know that ?
Go to the top of the page
+Quote Post
batagy
post Jan 28 2005, 11:31
Post #5





Group: Members
Posts: 105
Joined: 26-October 04
Member No.: 17847



This is a surprise for me, thanks for this info. rolleyes.gif
Before this I knew one program which can fix an offset, it's called Fix Wav Offset:
http://www.lameb.fsnet.co.uk/

But now there are two other method:
- Mount with Daemon Tool, and re-rip with good offset.
- Manually fix the offset with a Wav Editor (I think Fix Wav Offset above do the same)

Thanks. wink.gif

This post has been edited by batagy: Jan 28 2005, 11:31
Go to the top of the page
+Quote Post
precisionist
post Jan 28 2005, 14:05
Post #6





Group: Members
Posts: 739
Joined: 16-January 04
From: Germany
Member No.: 11279



QUOTE (batagy @ Jan 28 2005, 11:31 AM)
- Manually fix the offset with a Wav Editor (I think Fix Wav Offset above do the same)
*

This also gives you great insight into offset issues - and that it's only a few null samples. Great method for all non-precisionists to ensure themselves that I'm insanely anal about offsets. wink.gif


--------------------
I know that I know nothing. But how can I then know that ?
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 28th July 2014 - 05:13