Reason is kicking my arse

GTE

Well, for one song anyway.

Through out a week of recording when a band wanted Reason for a synth or a piano I would switch on ReWire in Cubase 5 then open Reason 4.

The first time I did that in a project some of the tracks would get moved and some either wouldnt or be moved somewhere else. Luckily nothing was saved so I went back to the last saved project and all was fine.

Now though, Im mixing the tracks and low and behold for one track in particular its always doing this.

Any idea whats conflicting with what?

EDIT:
Well it worked with having the Reason file open then opening the Cubase project, which is the opposite to what Ive been taught. :S

Very odd problem and not at all consistent.

iamstop

I had Live open for the first time in a while and then opened Reason but it gave a warning about the order.
I dunno if some programs get 'host' status over other or what.

Neurojazz

Just checking the obvious.

Both programs updated fully to latest patches, and check on both user forums just in case people with same issue have found a work around.

GTE

I think its all up to date. Ill have a check of the forums to see what the story is.

Happening again today. Very annoying.

Thanks

trackmixstudio

Haven't used Reason in a long time (my wife would agree with me there:p)
But sometimes when Reason opened it would open at a default tempo and logic would match that tempo. Regions in the arrange window would be moved in time but stay in the same bar position. Regions starting at zero would stay put.
Could be a completely different issue but worth checking. Bit me in the ass plenty of times.

dav nagle

bbk wrote: »

Well, for one song anyway.

Through out a week of recording when a band wanted Reason for a synth or a piano I would switch on ReWire in Cubase 5 then open Reason 4.

The first time I did that in a project some of the tracks would get moved and some either wouldnt or be moved somewhere else. Luckily nothing was saved so I went back to the last saved project and all was fine.

Now though, Im mixing the tracks and low and behold for one track in particular its always doing this.

Any idea whats conflicting with what?

EDIT:
Well it worked with having the Reason file open then opening the Cubase project, which is the opposite to what Ive been taught. :S

Very odd problem and not at all consistent.

Make sure when your working on a song when using reason to take note of the tempo and always check that the correct tempo is set before you get stuck in, that type of thing sounds like mismatched tempos which is a bug that happens in reason.

dasdog

There is a difference between launching your DAW first, then Reason...or having both apps running and loading projects/songs in either app one before the other. The DAW needs to be loaded first Reason can slave off something in ReWire mode. But after that you should load projects in the DAW then your Reason equivalent file if you want the tempo/marker positioning that was last saved, which should be your DAW. As the two posts above say its one of those things that happens but you can avoid it with good opening/saving habits.

GTE

Thanks all, the points on the tempo do seem bang on whats happening.

Ill have a good check of it all when it happens again.