Reason drifts with HW buffer changes?

[sgladm]

Hey,

I created a beat in reason on one pc, recorded a million tracks to it on that same pc. locked perfect.
now opened the session on another computer, and the reason beat is off. i set the buffer to 1024, it's very off, set it back to 512, it's closer, but still off. 256 keeps chocking on me with error.

Do HW buffer changes alter latency in reason tracks running in rewire mode? Does this mean I should keep track of what the HW buffer i'm running everytime i'm using reason in rewire otherwise it'll be off if changed?

is it possible this same 'rewire' latency (which i never new exists until now, am i wrong about it?) differs from pc to pc? Right now, how can i get these tracks to lock on this new computer?!? (i don't want to 'nudge' all the audio until it 'sounds right', that's crazy. i'd rather get reason to 'sit' back where it should if possible, locking to the audio tracks.) help anyone?
thanks.


i'm running pt 6.9, mbox, reason 3.0, pentium D dual core 2.8, 1gb ram, xp sp2.

[neeel]

I have experienced a similar problem. Not when transferring to another pc but when the session first opens on the same PC.

The way I have fixed it is to increase the buffer setting to 1024 and then return it to 128 (mbox). This then seems to lock the session and regions back to where you know you recorded it.

Had me puzzled for a while.

Weird.

[sgladm]

hey neeel thanks for the reply, i'll try that.

were your original reason tracks always programmed with a 128 buffer also?


ps. my reason beat was sequenced (and is being controlled) by a midi track in pro tools.

[neeel]

Hi,

You do exactly the same as I do.Pro tools midi tracks that control reason (other than complex automation)

...and yes my buffer is always set to 128 when recording.