I'll take a look, but it's just strange that it would only start doing that after the 1.1 download...plus, why would the keys on my keyboard be used to transfer transport commands?
-
@vibrato said:
This ibad newwwsss!!!
I just ordered Cubase 4 - solely for the purpose of composing in a better way and for using VI.
IS it only happening with Chamber strings or all of the VI on Cubase 4?
I hope there is a solution to this - otherwise I might have to wait until its resolved.
VSL: Plz keep us posted of possible solutions.
Best,
Tanuj.
Don't get your knickers in a twist yet. Logic means Mac. Wait until it doesn't work on PC and then scream. [8-)]
DG
-
I am using Cubase 4 on the macpro and have not had any problems. Am I just lucky?
jay
-
Hi all,
Steinberg Austria did some tests for us and confirmed that they didn´t encounter any problems when loading Vienna Instruments in Cubase 4 either.
Make sure that you have OS 10.4.8 installed and please get the latest update from the Steinberg Server (Cubase 4.0.1.2074), moreover it might help to check out the following:
1) Is VST2 plug in manager active? (picture1)
http://vsl.co.at/upload/forum/VST_plugin_Manager1.png">
2) Is ViennaInstruments.vst visible in the plug in list? (picture2)
3) If not visible, please reassign the VST 2.x Plug In Path. (picture3)
Best regards,
M a y a
-
Well, no - I haven't tried reinstalling Cubase...That's not something I really want to do considering every other plugin I have is working fine. VSL works fine in Logic - and the standalone works fine as well. I have deleted VSL out and reinstalled, but I have the same problem - no gui...Maya, Christian? Any help would be appreciated. If we can't get it up and running, can you re-sell this product?
-
@Jay Weigel said:
I am using Cubase 4 on the macpro and have not had any problems. Am I just lucky?
jay
You're using Chamber Strings (or equivalent) with Cubase 4 on a Mac Pro and you're having no problems? Can you help me out? If you bring up your plugin manager, does it say that Vienna Instruments is vst version 2.3? The reason I ask is the only other plug I'm having trouble with is BFD, and it's the only other plug that shows up version 2.3.
-
Sorry, I have been in a spotting session for a couple of days will get to my studio tonight and see what it says. It is the chamber strings and it is cubase 4.
-
-
Well I now have the exact same problem that you described. Not sure what could possible be different, but I think you are right about the vst 2.3 issue. Other plugins that are 2.3 don't work either. I thought for sure that I had loaded VI into the macpro, buit maybe not. Ihave no problems with Cubase 4 on the G5 or as an au plugin in Logic on the Macpro. But definetly it is now a probem on Cubase 4. As you stated everything looks as Maya suggests it should. Maybe there is some difference between the German version pf C4 and the English, I am in New Orleans. The screenshots she posted where in German. Don't know what to say, but I hope they clear this up.
-
I'm wondering if The Austian team really tried it with Mac Pro/Cubase 4/VSL Chamber Strings...I don't know why it would work for some people and not work for others. This really shuts me down - so we really need to know that someone is going to work on this to get it resolved. Maya, Christian?
-
john, the ordered macPro has not been shipped yet and cubase4 is still not delivered here in europe - this makes work somehow difficult, because it seems to be a VST/intelMac issue on the steinberg side ... we will keep you updated. one more time it looks like VSL has to do the support for third parties.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
I really do appreciate your help. You guys have been very forthcoming and open about the situation - which is more than I can say for some other companies. It sounds like C4 left you guys in somewhat of the lurch considering they dropped functionality for vst 2.3 and lower. Sounds like they put out the product and you guys now have to write code for this to work. Steinberg is telling me that it's a VSL problem. Either way, I want to get this resolved and I appreciate your help.