| Arghhhh...no sample accurate object editing [message #104466] |
Thu, 24 December 2009 09:52  |
drfrankencopter
Messages: 137
Registered: July 2009
|
Senior Member |
|
|
Paris is frustrating me big time folks...maybe someone can help me out if this is user error, or if there is a workaround.
I've got drums spread across 12 tracks, and have been doing spot edits to tighten up the kick and snare. I've been doing this right in the editor window (view 2) as opposed to in the wave editor. But, I've run into the following problems:
- despite using the 'time locked tool' to copy my snare track to another channel it is not always necessarily sample accurate with the source track. Doing a null test confirms this. I've had my best success by splitting the snare track by doing a 'break at now line', and moving one segment to a new channel. This seems to work, whereas using 'copy' didn't line up at all
- Somehow I must have done editing without noticing the offset, and now I have rendered my edits and have a snare track that is 60 samples late (using Analog-X sample-slide I get a pretty good null with the original snare track at 60 samples). Now the problem is that I can't accurately slide rendered snare track forward in time by 60 samples. It seems there's some kind of lower time resolution limit with Paris.
-If I use the regular (not time locked) select tool, and try to drag the track back, there is a rather coarse range, and I can either have my snare early, or late...
-I selected 'delete time' and chose 60 samples, and got basically the same result as using the regular select tool to slide the track back.
-I opened the wave editor, and selected 60 samples and said delete and still couldn't get a null
Any suggestions for how to fix this? Any way to get finer resolution with the non time locked select tool?
Help....I don't want to have to re-edit these tracks.
Cheers
Kris
|
|
|
|
|
|
| Re: Arghhhh...no sample accurate object editing [message #104472 is a reply to message #104466] |
Thu, 24 December 2009 13:05  |
|
|
Nope, there is *no sample accurate editing* on the playing field. The "now line" and the "nudge" function do NOT represent sample- precise values; Deej and others contributed much more accurate values so just ignore the values or consider them as "rough guides".
Welcome back to the 20th Century - have you figured out where the coal chute is on your MEC, or has it just not needed refuelling yet? 
Seriously - I would have thought the timelocked selector should have been sample-accurate (never occurred to me to check), so I don't know what went on in your track. Are you doing a null test on a track with all edits intact - or have you already rendered the snare after editing? If so, possible bad news: the rendering process can induce timing errors under certain circumstances.
The good news is that it tends to fail in certain places on a track rather than randomly - everything after that "fail" (there may be more than one) should be consistently off.
If that's what bit you - I'd suggest adjusting sample-slide until you get a "null" off the top of the edited track, make a note of the setting, and then continue down the track until you hear the null failing. Cut the track at that point and re-adjust SampleSlide until the section after the cut nulls once again; make a note of that setting. Repeat if necessary (you might only need to do it in one or two places to regain the "null"). After you know what needs adjusting you can trim samples, or I suppose you could even put your snare on two (or more) tracks with different settings of SampleSlide.
BT's loopback rendering trick (sending your track out of one of your digital outs and recording it back to a new track via a digital in) is an easy way to avoid this bug.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Thu, 24 December 2009 13:09] Report message to a moderator |
|
|
|
|
|
| Re: Arghhhh...no sample accurate object editing [message #104477 is a reply to message #104472] |
Thu, 24 December 2009 21:26 |
drfrankencopter
Messages: 137
Registered: July 2009
|
Senior Member |
|
|
| kerryg wrote on Thu, 24 December 2009 13:05 |
Seriously - I would have thought the timelocked selector should have been sample-accurate (never occurred to me to check), so I don't know what went on in your track. Are you doing a null test on a track with all edits intact - or have you already rendered the snare after editing? If so, possible bad news: the rendering process can induce timing errors under certain circumstances.
The good news is that it tends to fail in certain places on a track rather than randomly - everything after that "fail" (there may be more than one) should be consistently off.
|
Timelocked selector seems to work, but copy and paste do not result in sample accurate values. Oh, and another complication is that if you use 'delete time', you can't clear items into the audio bin, and drag them back into the right spot on the timeline...instead they ignore the deleted time and go back where they were initially recorded.
I ended up having to render the track, because all the edits were resulting in 'assertion failure' errors which crashed Paris hard.
Looks like I'll need to re-edit these tracks, while keeping a more watchful eye on the sync.
Cheers, and merry Christmas everyone
Kris
|
|
|
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
