@cm said:

welcome Johnkenn,
unfortunately it seems steinberg has decided to not deliver cubase 4 in europe so far (what i personally do not understand at all - it is announced to arrive *somewhen in november* :-/) so we do not even have a copy to check out this behaviour.
however, assuming you're on a mac please provide some additional info about your system
christian

Hey Christian - thanks for the response. I sent some screenshots to Maya last night. I really think the issue is that VSL is still vst 2.3. I used Logic for a few months while I waited for Cubase 4 to come out, and I got vsl to work as an AU plug with Logic 7.2.3. However, when I updated to vsl 1.1, vsl acts really strangely. It will work for a little while and then the sounds won't work - and sometimes, certain notes in the upper register will trigger the "play" button in Logic and the "auto punch" feature...very strange. If we can get it working in Cubase, I could care less about Logic - just thought I would pass that info along. Here's some of my info.

Dual 2.66 Xeon
3 ghz RAM
250 Gig Mac HD
300 gig Sounds HD
100 gig Songs HD

I run the apps on the Mac HD, write to the Songs HD, and use the Sounds HD to store and pull libraries from.

@Johnkenn said:

[...] sometimes, certain notes in the upper register will trigger the "play" button in Logic and the "auto punch" feature...very strange. [...]

This has most certainly to do with Logic's option to trigger the transport-commands by MIDI - just a preference that can be activated or de-activated. Take a closer look at these options.

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

Hey guys,

the problem with VI and Cubase 4 is presently being investigated. As soon as I have received further details, I´ll let you know.

Best,

M a y a

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

Everything is exactly like you instructed in the plug-in manager - but I'm still having the same problem...I sent you an email.

Does the Standalone tool work on your setup?

M a y a

yes - the standalone worked the last time I tried it - I'll try it again and get back to you. I still have Logic loaded - but I'm selling it - should I get rid of Logic on this computer?

Two suggestions:

1/ Did you try repairing the permissions? (Disk Utility)

2/ Did you try completely uninstalling VI / Logic / Cubase 4 and reinstalling them?

That's where I would start.

Good luck [;)]

Jerome

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.

Can anyone help me?

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.

Thanks, man. Of course if you have a Mac Pro, VSL Chamber Strings and Cubase 4 and it works, then I guess there's not much you can tell me. I would appreciate if you can check in your plugin manager to see what VST version VSL is. I have no idea why mine is having a problem...

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?

The problem is presently being investigated.

Best,

M a y a

Any update? Any idea when this will be worked on?