I am using the R2R reasond 12. I have a problem that has me baffled. I have project saved, and it is looking fine from inside the DAW. It's at 110 BPM and I turned on the click and it stays with everything through the whole song. The problem is when I render the tracks to audio. I get the audio and check it against a click and it drifts off. It's no longer at 110. Anyone?

 

Is the problem specific to only this one project? You noticed this happen after bouncing in Realtime, or offline?

I don't use Reason, but I have never heard of this in any program.

 

I have only tested the one project. Seems fine in the DAW. Stays with the click on both audio and midi tracks. When I "bounce" stems they wander off the metronome. I may need to use another method to bounce?

 

Not 100% is it latency problems??

 

All I know is that it stays with it in the DAW. Seems to be happening druing the render fuction. They call it "bounce" in the DAW. Wonder if other r2r users have this issue. I have legit reason 11 on the mac. I should test it.

 

It is a Reason Studios issue, not an R2R issue.
Reason Studios = software developer
R2R = protection scheme bypassed/patched

 

If that is true, then I can expect my legit copy of r11 to do the same thing. It is Reason Studios. When you say "patched" you are talking about r2r. It will be interesting to see how the legit works. So if this is true in v12 because r2r patched it, I would call that totally an r2r thing.

 

I have the audio cable installed. Hoping I can use it to dump to a different DAW. I am also hoping I can use the VST part of reason to get it into another DAW. Testing. This is a game changer for me. Hope I find a work around.

 

Nope. Boils down to user error here folks. I put the rendered stems on the tempo they should be at and it syncs. It helps to be using the correct BPM! I had it set to 110, and when I double checked myself it was supposed to be at 108. DUH! That's actually good news! Moving too fast!

 

Are you sure it's drifting in an out? Is it possible that your project is something like 44khz, and you're rendering to 48khz, and importing it back in (out of tempo)?

Edit: I see you snuck in a post to say you got it figured out. Good to hear!

 

It was user error. I double checked my settings and found the problem.I thought about just deleting this thread but that could leave some of you hanging. There is no problem except my moving too fast and not double checking myself.

 

a small bpm difference like 1-2 bpm will look like it is drifting; because the error is small, it takes a little bit of time for it to accumulate into a variance that is enough for you to hear the difference. Like if you were DJing with turntables.

I was going to tell you to put a quarter note kick drum loop at your "real" bpm, and tuck it underneath the rest of the track.

People often say cracked software has all these types of things wrong with it; but in reality it is 99.99999% of the time an issue in the original software.