Steinberg just repeated their warning, that from the following major versions of their hosts, the internal 32bit bridge will be removed. This came upon mixed reviews months ago already, as to some the bit bridge is still an essential tool (still way too many great VST2 plugins in 32bit out there), and to some it's a hated add on (due to random crashes). Their alternative recommendation is actually jBridge (surprisingly!).
Whether or not this is a blessing, is up to you.
In fact, did anyone of you notice that Steinberg works on an evasion of the Quicktime CODEC? IMO one of the best things they could do as this caused a lot of issues for Windows users, especially those that do not want to use Quicktime.
(in fact - speaking from personal experience - if you had iTunes on PC installed, but deinstalled it due to reasons, chances are that Steinberg crashes with a Video Engine error after you closed the host)
But this doesn't end here.
Steinberg is constantly moving forward. Even more so than ever, picking up speed, not knowing where the breaks are. Full on collision course! (anybody remembers the music video "Breakthrough" by Queen? Imagine that train!)
As can be seen with their upgrades for various VST Plugins (most notably VST Connect)/VST Instruments (Padshop, Halion, Groove Agent), but also their host announcements (Nuendo 7.1, Cubase 8.5.20, Cubasis 1.9.9 iOS with v2 on front doors, Wavelab 9.0.25, Sequel 3) - not to mention their host renaming (Cubase and Wavelab turned into Cubase Pro and Wavelab Pro respectively). With three major host upgrades/releases on the front door (Cubase 9 will probably hit late Autumn if we take the 1-year upgrade cycle into account, the former Sibelius programmer will release "Dorico" in Q4/2016 as well, Cubasis 2 in iOS).
Not counting integration from Yamaha hardware like the Nuage, their USB ADC's or even the Yamaha THR amp (well... not via control script or anything, but rather ADC drivers only, but still)
This pops up a lot of questions.
But the main one is - how do we go from here?!
Personally (as longtime Steinberg User), the following will happen in the foreseeable future - no doubt about it.
a) after the announcement of the drop of the 32bit Bit Bridge, the 32bit versions of the hosts will vanish eventually
This might not happen with Cubase 9 (2016) yet (though all signs are there - see links above), but maybe with Wavelab 9.5 and Nuendo 7.5 in 2017. Dorico might be released as x64 only tool already in Q4/2016. It's inevitable however.
in fact, certain programs in the audio and video realm only start/work on x64 OS's. Logic being a prime example (64bit only, first released for OSX10.8 ), from Adobe it's all of their programs since CS5 IIRC (I still remember Premiere and After Effects refusing to launch on a 32bit OS!). And from Magix, it's their video NLE (have kind of lost track of Samplitude). OSX turned fully 64bit since OSX10.6 - Snow Leopard, Windows 10 is still available in 32bit - but this wasn't necessarily planned IMHO.
b) future host versions will only support specific OS versions (due to backwards compatibility reasons) - for Windows I assume Windows 8.1 bar minimum, and for Mac I assume OSX10.10 Yosemite or even OSX10.11 El Capitan (OSX10.12 Sierra is on front doors).
By that, I not only mean "x64 only" but OS versions in general to keep the backwards compatibility at the essentials. It's no secret that OSX upgrades tend to break hosts and plugins, and Windows is going the same route now. In fact... Steinberg dropped XP and VISTA in secret during Cubase 6 days. Windows 10 has been officially out for almost a year (July 2015), and the Win7 Mainstream Support did end in January 2015 (according to Microsoft, the Extended Support goes until 14h January 2020). We can expect a drop of support for Win7 eventually in favor for Windows 10 and it's "upgrade engine". Less work for the developers, as they have to keep less eyes on old OS's.
So we might run into a "forced OS upgrade" situation like with Logic at some point. Which can be both good and bad (see OSX). When? Maybe already with Cubase 9, maybe later. But the warning signs are there.
c) due to the very negative response of the "forced VST SDK v3.x" (drop of the VST2.x SDK), and the backlash of the VST3 technology in general (especially from third party programmers and the JUCE framework creators!), not to mention seeing that the SDK is already at v3.6+, we'll eventually see VST4 (I guess by/around Summer 2017 soonest)
The hope is still, that the SDK developers sat together with Framework programmers and 3rd Party developers to iron out all issues that came up with the (barely documented) VST3 SDK (I can dream!), while keeping VST2 alive as long as possible. The majority of tools on the market are still VST2. Though we won't see native VST2 sidechaining in Cubase anymore - this ship is long gone.
d) a Cubase recode from scratch is inevitable
It already happened with Wavelab 9 - and it was IMO a really good move (if not the ultimate move) as this cleared a lot of bugs that got introduced with Wavelab 7 (the switch to the new GUI, the cross-platform support, QT5 as framework). Mainly VST3 support (funny enough). It's still not super bug free for certain third party developers. However previously non-working tools, do so now. Cubase always suffered from add-ons and spaghetti code. Due to this, the SX series was a complete recode from the old "VST branch", which did live on for nearly a decade at that point. Now we're at a boiling point again - and in fact, behind closed doors and through the flower, it was hinted at several times that "certain bugs can only be fixed if we code from scratch" (at trade shows, and forums - albeit those comments on the latter are now gone: deleted/edited). So a recode is ultimately inevitable.
Cubase 7 was a good start towards that direction, but it felt like tacked on code and got disimproved with every consecutive update. Cubase 8 on the other hand tried to fix even more stuff (new main window handling, ASIO Guard 2, some improvement to the Mix Console). This is reminiscent of Wavelab 7 and Wavelab 8 - trial and error. But a recode has to happen at some point rather than "refurbishing old code". So I guess by Cubase 9 or Cubase 10 (the infamous roman X might be used!), we might see a completely recoded Cubase. With Nuendo in close pursuit (Nuendo is based upon Cubase's code after all).
With the added bonus, that "workarounds in plugin code" from third party developers can finally be reduced again. I actually do welcome that.
e) Pure Speculation: we might maybe even see another upgrade of the Syncrosoft engine (since the USB keys turn a bit old at this point)
Currently, the USB key is upgraded as part of a maintenance update. But we never know how far this will go. Seeing as the iLok also got to v2 with the USB key (to kick off the overhauled/more secure iLok2 routines) and the manager is currently on v3 (aka EDEN3). Though crack groups might still be having a stab at unlocking copy protection in general - we sadly can't prevent that.
The USB keys also also known to "Not work forever". So this is another possible thing to talk about.
Those points for starters... though one thing might never happen I'm afraid - more interim dot-updates and a longer upgrade cycle.
What are your opinions on these topics? Is it too far fetched?
Are you also a longtime Steinberg user? Did you follow their history?
What are your predictions and theories?
Please discuss.
