11 & 12 HD Co-install

[deanrichard]

I must be wrong. I had to give up my PT11 license when I upgraded. I assumed everyone had to.

Originally Posted by Eric Lambert

I've had friends upgrade who reported the same thing.

[Southsidemusic]

Originally Posted by deanrichard

I must be wrong. I had to give up my PT11 license when I upgraded. I assumed everyone had to.

Correct - When you upgrade you surrender the PT11 license but in the bundle you recieve with that surrender you get PT10/11/12 licenses so thats what I think he meant.

[nigelpry]

I HAVE a perfectly valid reason for wanting to co-install 11 and 12 on a single boot partition AND have them both accessible as working apps, not for trial/testing purposes. I do not want to have to reboot to another partition every time I wish to switch between versions.

I've not had the guts to co-install yet to try it for myself, but does anyone actually have real experience of doing the renamng thing, rather than just giving out advice on alternatives or saying why they think there is no need to do it?

MY reason for WANTING 11/12 co-install is simple ...I have 11HD which I will not be upgrading, and 12 vanilla acquired as a free student upgrade.

So if PT12 ever comes out with a 'cool new feature' that is a) actually of use to me, and b) not restricted to HD|Software, I'd lke to be able to use the new features in 12 then flip to 11HD for its HD only features as required by the particular needs of the moment.

My main concerns keeping me from trying co-install so far are that I'm unsure about the knock-on effects (no that's not a new stock plugin) on what would be shared folders, used to store plugins, plugin settings, templates, track preset workarounds etc. etc. Is V11 going to see already installed V12 stock plugins as 'wrong versions' and reinstall them every time it launches after V12 has run, and then 12 will have to reinstall its versions next time it runs, or might V12 plugins be left alone by V11 but then not work properly.

I don't think any stock plugins have actually been updated yet, I think they are currently still at V11, but it's only a matter of time (presumably).

This could get even more complex when updates to, or new, third party plugins start coming through that might be fine with 12 but not with 11. Or do people think the AAX format is fixed to the extent that there will be no changes to it (and therefore full compatibility with 11) during the lifetime of PT12.

[JFreak]

Renaming works but isn't supported

[nigelpry]

Originally Posted by JFreak

Renaming works but isn't supported

I knew it wasn't supported!

As for "Renaming works" I also know that, in itself, it works, but are you confirming that there are no knock-on effects on any shared folders that would make it a bad idea?

[JFreak]

Originally Posted by nigelpry

I knew it wasn't supported!

As for "Renaming works" I also know that, in itself, it works, but are you confirming that there are no knock-on effects on any shared folders that would make it a bad idea?

It will be a bad idea once some plugin works with PT12 but not with PT11 or vice versa, but otherwise no.

[midnightrambler]

Originally Posted by nigelpry

I do not want to have to reboot to another partition every time I wish to switch between versions.

Ah come on it's not that bad. Just get another fast drive. I'm swapping between v10 and v12 at semi-regular intervals for printing incompatible plugs etc. . A separate boot drive is by far and away the safest thing to do....

[nigelpry]

Originally Posted by midnightrambler

Ah come on it's not that bad. Just get another fast drive. I'm swapping between v10 and v12 at semi-regular intervals for printing incompatible plugs etc. . A separate boot drive is by far and away the safest thing to do....

No, absolutely, it's not that bad, but nowhere near as good as not having to do that, if it will be stable.

Time is money, especially in front of clients, and therefore, so long as, and until, there's no screw up caused by having different PT versions accessing the same shared folders for plugins, settings etc., I'd rather be able to switch between versions without having to reboot.

We already have enough downtime caused by having to reboot when 9173 errors occur mid session, sometimes I've had to do it several times in a single session, others thankfully reboot free, so I want to keep the number of reboots to only those that are actually needed.

Of course all this is hypothetical as yet, there has been nothing in PT12 so far to convince me it is worth even installing it on my studio or home computers (other than a test partition at home, which showed no improvement for me over PT11).

[JFreak]

One thing to try is installing PT12 on a fresh Yosemite system drive and see how snappy and stable it is. PT10 coinstall mandates Mountain Lion, but that isn't what Avid techs had in mind when they did PT12

[s0nguy]

Can I install 11HD and 12 non-HD on the same machine?

retina macbook pro 2014..

thanks

s0nguy