Project 3.x to 4.x compatibility...

audioguytodd · 08-01-2011, 01:47 PM

I think I saw a thread about this but I just want to make sure.
Are all 3.x Reaper projects %100 compatible with Reaper 4.x????
Anything special I need to know???

Thanks

Subz · 08-01-2011, 01:57 PM

i think the only real change is the panning law?

but this can be over run by setting the default panning law to the V3 panning law in the project settings for those projects,

or just touch up the mix with the new panning law

Subz

audioguytodd · 08-01-2011, 01:58 PM

Yeah, I thought about that too... Anything else anyone can think of??

Subz · 08-01-2011, 02:03 PM

not sure weather stretched files would use the new default algo?

i think i read that the old algo is there but hidden just for R3 compatibility

but i may have dreamed the hole thing after a splif?

audioguytodd · 08-01-2011, 05:36 PM

Anything else??? Devs?????

d.bop · 08-01-2011, 06:27 PM

Well, for the ones mentioned above.. I think that when you open a v3 project in v4, it will default to v3 panning automatically.

For elastique, I know that v1 is still in the installer for compatibility with older projects. That will also automatically be selected when older projects are loaded.

I don't think anything else will really affect your sound. I think I remember reading that this was a pretty big focus in v4 development.

tls11823 · 08-01-2011, 09:36 PM

What about going backwards? If I have a project created in 4.something, will friends running 3.whatever be able to work with it? I kind of suspect the answer is no, but I want to know if we need to all upgrade together.

bluzkat · 08-01-2011, 10:19 PM

Obviously... none of the 'new' stuff (4.x) will travel to a previous (3.x) version, but everything else would work just fine.

Did that make sense??

suntsu · 08-01-2011, 10:55 PM

Quote:

Originally Posted by d.bop

Well, for the ones mentioned above.. I think that when you open a v3 project in v4, it will default to v3 panning automatically.

In the fact, VST instruments with mono output(s) that comes from V3 are not automatically set as Mono channel in V4, instead, the channel will remains stereo with only the left channel occupied.

It is not really annoying but this could be improved to get a real transparent conversion ;-)

Excepted that panning thing, everything works awesome... I didn't noticed any glitch with V3 project importation !

tls11823 · 08-02-2011, 09:24 AM

Quote:

Originally Posted by bluzkat

Obviously... none of the 'new' stuff (4.x) will travel to a previous (3.x) version, but everything else would work just fine.

Did that make sense??

Yep, makes sense, and is a bit better of a response than I'd expected. So if a project doesn't include any new features, I can save it and expect it to work on the older releases. Of course that means that I'd have to restrict myself on sharable projects and make sure I don't use any new features other than editing and other things that don't affect the project as saved. It would be easier to just get everybody to the same release, and that's what I'm going to try to do. But I'm not sure if they'll all go for it. We'll see.

Anyway, thanks for responding.