Steve
For me the main reason for paying out is that as I’m sure you know the studio market is very competitive. I feel that it’s important to be advertising that you have the latest software.
I’m 54 and I’ve been playing the upgrade game forever and I know the new features do not mean improved mixes for my punk, rock, pop, indie bands but I need to get them through the door in the first place.
I hear that. That’s a tough row to hoe.
My thinking as well, although it was pretty frustrating to see C7 on sale before I’ve used it for a single day (I imagine being on 6.5.5 for another six months at least). So probably from now on I won’t do that anymore.
The discussions on CB7 is mostly concerend about the mixer. It can be devided in two:
Errors experienced
Likeness towards the new lay out and functions
I think the further discussions should distinguish between the two. To me it is very difficult to understand why there is so much fuzz around the new mixer. In my studio there are no errors experienced. I like the new lay out, so to me everything with the new mixer is fine and dandy. I am gonna “fight” to keep it as it is.
However if people experience errors, that is another case, a case I think Steinberg should take very seriously, but this is where the distinguishion comes into play. I think Steeinberg is more than willing to hear about errors, but not as much the “don’t like” for any reason. There are thousands of customers out there. Compared to all the customers it is only a fraction that complains (on this forum). I think the new lay out is here to stay (at least I hope so). Most of the errors will be ironed out over time, especially if they are reported without a flavor of “don’t like”.
Agreed and well put.
+1
{‘-’}
Take a screenshot of MySteinberg, to show you have access to both 6.5.5 and 7.
Only full 64-bit plug-in are usable in the 64-bit Cubase 7. The bit-bridge is a useless joke. Steinberg would do better to put those resources to fix all the problems that people seem to have.
Maybe so but unless it is known, instability in the application itself cannot be assumed.
All bridges have their flaws and the current situation is: if you want to add 32 bit plugins to your 64 bit Cubase, be prepare to do a lot of testing. Some will work on Cubase’s bridge, others will work better on jBridge, and some others won’t work at all.
I’m staying full 64 bit at the moment because it is one less thing to crash.
Care to explain me why the three 32 bits plug-ins (2 VSTis and one FX) that I still have are working flawlessly with Cubase VSTBridge ?
And, more than this, care to explain how I am supposed to use these plug-ins without it ? Jbridge ? I had my share of problems using it with C5, especially concerning access rights on a Windows limited account : error messages all over the place, this without talking about the convoluted installation process…
The fact is that the VSTBridge wasn’t working well with C5, but has been improved to a point that I no longer worry if the plug-ins I use are 32 or 64 bits with C6.5…
Of cause I would. Which are the 32-bit plug-ins you refer to?
For every plug-in I’ve tried (VST or VSTi), the bit-bridge has worked like this: The plug-in interface opens in a mini-window. To access the interface you need to click in this mini-window. This, however, also stops the music, which can only be started again by closing the plug-in interface.
This means that to make a setting you must:
- Stop the music
- Make your setting
- Start the music
- Listen to the result
- If not satisfactory, back to step 1 (repeat until satisfied)
I find this totally unusable. Plug-ins must be settable in realtime. Had this been the normal operation of the VST/VSTi system, it wouldn’t have been so much as a footnote in history.
I have found that I’ve been forced to throw out all 32-bit plug-ins. Some I’ve been able to replace with (working) 64-bit versions. Others not. Sadly, the latter includes Arturias Brass, which Artura no longer supports and won’t be updated. This is sad because most most plug-ins can be replaced. Brass was unique though.
Of cause it wasn’t. Cubase 5 wasn’t a 64-bit application, and there was therefore no need for a bit-bridge!
I am sure that many can empathize, myself included.
For me the solution will be to set up a secondary system and use VST System Link but the problem boils down money.
I do have a secondary system but currently it is has an older sound device, XP and Cubase 6.5.5, which means I must wait to EOL and replace hardware. Then there is the issue of having to unplug/plug in the dongle so I am thinking of getting Cubase Elements at some point and purchasing a second dongle specifically for the purpose.
The plugin(s) that constitute my sore point are TC Electronic Powercore 
Here they are :
- GSi Mr Ray 73 Mk2
- GSi VB3 1.4
- Ariesverb 0.76
Beside this, using C6.5, I never went to problems while tweaking in a bridged VSTi window, even if there is a playback running, but I admit that I don’t remember doing so with Ariesverb.
About C5, you should reconsider Cubase history more accurately, because I have presently C5.1.1 installed only in its 64 bits flavor : I purchased JBridge especially for it…
A bit thoughfull that Logic Pro 9 is able to run 32 bit plugs in 64 bit projects with fully operateable GUIs.
To extend the availability of 32 bit plugs not supported anymore, but still desired in CB 7, I have:
- Installed Reaper and I rewire that into CB 7. Reaper/Rewire for some reason is fully capable of running some 32 bit plugs CB wont.
Have a second PC with CB 4,5 and use VST link
On the same second PC run VEPro ethernet to ethernet.
This set up gives me access to almost all my old pluggs, and also some great free plugs made only for PC/XP. And it works perfectly. The only plug I can not run is Broomstick Bass. Before upgrading to Mountain Lion, Reaper was able to run it, but alas not now. So I have set up a third PC and I have started to make a Kontakt version of Broomstick. Sometimes you need to take the long way home.
Given all the cost and time involved to upgrade, I have decided to FREEZE all my hardware and software for 5 years now. It all works now and if I can fight the “Must have” feeling, I think I will be spending more time making music than doing time in the upgrading jail.
Just in case you missed it, This is a Cubase forum. 
Seriously, your suggestion appears a bit “messy”. A neater solution would be to try to dig out an ancient Steinberg product called “V-STack”, and use this a virtual rack on the second computer. “V-STack” should even be able to run Broomstick Bass. However, that is beside the point. The point being running 32-bit plug-ins within a 64-bit Cubase 7 and for that Steinbergs bit-bridge solution is useless.
The statement of Logic is a relevnat comparison to CB 7. (In case you missed it). I am also very tired of all the “police work” done by forum members that set themselves above others and tell what the limits of the forum are or not. As mentioned in this case it is very relevant that a competitor is able to do what Steinberg is not, due to lack of focus.
The rest in my posting is not a suggestion. It is a discription of my own set up. If you find that messy, then go for another solution. It works perfectly here regardless.
If I understand your problem correctly, you may have the option to allow other applications to take over sound when Cubase is in the background.
It’s in Device Settings, if you untick the box, then Cubase will keep running audio even when the bit bridge shows up.
Maybe not so relevant now that Logic 9 is discontinued.
VST Bridge was always a stop-gap measure, and as it appears so were any 3rd party solutions.
I agree with your approach however but it does take time.
BTW, are getting much added latency?
it’s very quite so far this week from the mods which normally means …