KVR Audio

zvenx · Post by **zvenx** » Tue Dec 08, 2015 2:12 pm

Since the newer upgrades don't overwrite the previous ones, there should be no issues in keeping older versions around for either older project compatibility. Although I only have Nuendo 7 as a 64 bit installed on my PC, I have I think 5.5,6 and 6.5 as both 32 and 64 bit versions installed...

rsp

VitaminD · Post by **VitaminD** » Tue Dec 08, 2015 2:15 pm

That kills backwards compatibility with cpr project files though..

I wonder if multiple versions of Cubase can be installed and run without issue? Cubase 8.5 for old files (with 32-bit plugins) and Cubase 9+ in a different folder for newer ones (without 32-bit plugins).

edit: oh that is good to know.. so we might be able to do just that then. Can someone please confirm this is the case?

zvenx · Post by **zvenx** » Tue Dec 08, 2015 2:55 pm

Hi, why do you need different folders?
On PC, the 32 and 64 bit vsts are in different folders.
On Mac, you ensure that the application runs in 32 bit mode it runs the 32 bit versions of the plugins which can.

I am not sure what you mean backward compatibility being killed, please explain. I actually can open my Nuendo 7 files in Nuendo 6 and 6.5, even in Nuendo 5.5 (although the mixer is all screwy then)

I do this all day everyday btw (ok an exaggeration, but I do this often enough

)
rsp

lfm · Post by **lfm** » Tue Dec 08, 2015 3:00 pm

For those that have something that works with jBridge today, would probably work in future too.
I think it's transparent to daw and jBridge is all it sees and know about.

But I dropped everything 32-bit since 4 years back, too many issues regarding just that.
It did not matter if Reaper, Sonar or Cubase.

gravehill · Post by **gravehill** » Tue Dec 08, 2015 6:08 pm

Both 32 and 64 bit Cubase produce identical .cpr project files so no problems there.

Cubase has always installed new version completely separate from any old versions you might have so that's good as well.

I kind of wish more developers would follow suit - with a similar warning well in advance! Cubase 9 is probably a year away now so plenty of time to prepare. And even if you really need a new computer and can't afford one in next year or so, the old versions will still work as before.

Personally I have everything 64 bit now. The only issues I have with my system are with ILok (need to start PACE service manually every time even though it's set to automatic) and BCR2000 (driver won't install).

For transition period from 32 bit to 64, jBridge was awesome but I'm glad I don't need it anymore.

rustman · Post by **rustman** » Tue Dec 08, 2015 6:32 pm

FrankLaVerne wrote:Just found this:

http://www.steinberg.net/en/newsandeven ... -3469.html

Makes me quite happy that I went through the process changing everything (OS, Cubase, all plugins) to 64 bit, this way I'll be prepared.

Sad story though, since many people are still using 32 bit plugins - and I made quite some bad experience with not all, but at least a LOT of 32 bit plugins that didn't work for me and crashed Cubase big time. The VSTBridge never worked well for me, that's why I did it all in the first place, also I had to give up on some valuable plugins ...

I just spent a few hours re-organizing my plugin folders over the weekend and paired it down to only 2 remaining 32 bit plugins, which are wrapped in Jbridge. My hope was to be able to scan my plugins folders without multiple crashes and the obligatory complete computer restarts that come with each. It's amazing how convoluted things can become over the years with no industry standard for installers. I don't think I'll miss any of the 32 bit stuff, although STW should get of their chairs and update ReflexPro to 64 bit. It's why I had to buy Jbridge in the first place. At least Alchemy was 64 bit. I won't be losing that.

xbitz · Post by **xbitz** » Thu Dec 10, 2015 5:25 am

could somebody check MIDI export/import in Cubase,

something definitely wrong here ( https://www.steinberg.net/forums/viewto ... 26&t=89401 )

reimport is ok in Cubase, but Bitwig can import the older MIDIs flawlessly so somebody with both DAWs,

>> ok installed an Ableton Live, and it's ok in it so it's Bugwig

VitaminD · Post by **VitaminD** » Thu Dec 10, 2015 5:28 am

zvenx wrote:Hi, why do you need different folders?
On PC, the 32 and 64 bit vsts are in different folders.
On Mac, you ensure that the application runs in 32 bit mode it runs the 32 bit versions of the plugins which can.

I am not sure what you mean backward compatibility being killed, please explain. I actually can open my Nuendo 7 files in Nuendo 6 and 6.5, even in Nuendo 5.5 (although the mixer is all screwy then)

I do this all day everyday btw (ok an exaggeration, but I do this often enough )

Please see the page before this one (http://www.kvraudio.com/forum/viewtopic ... 2#p6322012) about changes coming to Cubase 9 and subsequent versions thereafter.

zvenx · Post by **zvenx** » Thu Dec 10, 2015 11:35 am

VitaminD wrote:
zvenx wrote:Hi, why do you need different folders?
On PC, the 32 and 64 bit vsts are in different folders.
On Mac, you ensure that the application runs in 32 bit mode it runs the 32 bit versions of the plugins which can.

I am not sure what you mean backward compatibility being killed, please explain. I actually can open my Nuendo 7 files in Nuendo 6 and 6.5, even in Nuendo 5.5 (although the mixer is all screwy then)

I do this all day everyday btw (ok an exaggeration, but I do this often enough )
Please see the page before this one (http://www.kvraudio.com/forum/viewtopic ... 2#p6322012) about changes coming to Cubase 9 and subsequent versions thereafter.

I did... what am I missing?
I was saying because of those changes coming, one can keep older versions around to run 32 bit if necessary, then someone asked if you need separate vst 32 and 64 bit plugin folders.
What am I missing?
thanks
rsp

Compyfox · Post by **Compyfox** » Thu Dec 10, 2015 3:46 pm

For those interested - this just dropped in my Twitter feed
http://www.steinberg.net/en/newsandeven ... -3469.html

Not surprised, this was "hinted" to me during C7.0 times already and it was only a matter of time. Aside from the slightly broken built in bit-bridge (which can be easily evaded with jBridge), I do support that move. Less maintenance for both Steinberg and for third party developers (focus on one bit computing architecture), which in turn could mean less bugs overall. So time to get rid of wasted HDD space - haven't used the x86 versions of CubEndo/Wavelab in quite a while now either.

My biggest fear is Windows compatibility. Chances are the next Cubase version could(!) drop Win7, now that Win10 is out and looks like going similar routes than OSX in terms of "updating" (read: chances are we may see comments like "only support down to the latest 2-3 dot-OS-updates", and the installer refusing to launch/work otherwise). Wouldn't surprise me if that happens. Maybe not with C9 yet, but we will never know.

Just a heads up in advance.

EDIT:
Looks like Steinberg aren't the fastest ones in terms of spreading news. I'm 2 days late, and this did NOT show up in the Launch Wizard in Cubase so far either. Oh well.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Thu Dec 10, 2015 5:57 pm

[DELETED]

4damind · Post by **4damind** » Thu Dec 10, 2015 6:35 pm

For me there are not so many wishes after 8.5. I've not found bugs yet and I love the improvements.
If Steinberg has no idea what to add with C9... I still miss spline based automation curves

qtheerearranger · Post by **qtheerearranger** » Thu Dec 10, 2015 6:43 pm

i wanted to demo 8 when 8 came out.. couldn't cause demo wasn't released lost interest by the time it did and same with 8.5.. i think steinberg is missing out on people demoing their products because of this delayed demo...

Compyfox · Post by **Compyfox** » Thu Dec 10, 2015 6:53 pm

Oh! There is no demo AGAIN?!

How long did it take last time to demo .0? 3-4 months or longer?
Steinberg really needs to step up on that game. Other companies do this at day 1. Even the smallest most unknown independent 3rd party programmer.

That alone is worth a facepalm moment for one of the big 4's.

4damind wrote:If Steinberg has no idea what to add with C9... I still miss spline based automation curves

If you mean "Bezier Curves"? Yes please - something that should have been in it since SX days (especially since the new engine was mostly ignoring MIDI at that time, and rather focusing on Audio), and/or since the implementation of VST3 (Stepless Automation and "Note expression").

chk071 · Post by **chk071** » Thu Dec 10, 2015 7:08 pm

Compyfox wrote:Oh! There is no demo AGAIN?!

How long did it take last time to demo .0? 3-4 months or longer?
Steinberg really needs to step up on that game. Other companies do this at day 1. Even the smallest most unknown independent 3rd party programmer.

That alone is worth a facepalm moment for one of the big 4's.

Your posts alone make for the best facepalm moments in Steinberg threads.

Seriously, don't you get tired of this sh**? I mean, Steinberg is doing well, have raised their product and upgrade prices, and still little Compyfox is crying his butt hurt heart out about how Steinberg more and more goes down the swanny. This is really internet amusement on its highest level, gotta admit that.

And no, you don't have anything useful to add to this thread, just your never ending vendetta, and then you claim that you don't post much anymore on KVR, because everyone picks on you. Yeeeeah riiiiight.

Cubase 8.5 here any day now...and the day has come