Just got back into the studio and installed C4 and latest VI VST on the MacPro. I can confirm that it doesn't work in C4, although works fine in standalone mode.

In C4 when you try and launch the VI window you just get a small window as per the picture below:

Other plugins like RMX are working fine.

Let's hope we can get a fix to this soon.

Cheers

Tim

http://vsl.co.at/upload/users/2524/1copy.png">

Thank God, I'm not the only one!

BTW - VSL works in NI's Kore with the AU plug...

@Johnkenn said:

BTW - VSL works in NI's Kore with the AU plug...

.. but I don't really want to shell out £300 on Kore just to use AUs in Cubase... [8-)]

Oh - believe me - I understand...This should work in Cubase 4. I'm having the exact problem you're having...

Any news from the team on this yet? Have you guys received your MacPros and Cubase 4 yet?

TIA

Any word?

I have been using Cubase SX 4 on a Windows machine for the last month and have noticed a few interesting bugs, some of which I'm sure are VST 3 related, although the VI's orchestral strings have posed no problems. However, I recorded a MIDI track using the NI B4 II organ, and overdubbed controller data for the drawbars. Then I dropped the track to a stereo audio file without issue. When I wanted to make a few changes to the original MIDI track and redrop I discovere that the controller data, which looked fine, was playing back very badly- destroying the playability of the performance complete. I kept the notes, erased the controller data, and redid it, and things were fine. Perhaps this kind of issue is having with VI on the Mac side.

Hi Gary.

If only it were that simple. You can't even see the VI screen on the Mac....

Oh well! By the way... forgive my clumsy e-mail. A writer composing such a poor note! Unfortunately, I can't blame it on pre-holiday drinking!

G

Maya/Christian - you guys said you were receiving Cubase 4 in November. Are you guys working on a solution to this problem?

Anyone?

as far as i am up to date it is confirmed to be a problem with cubase 4 on intel-macs, unfortunately for a still unknown reason and it is already under investigation. so far a *known issue* with permissions for grafical resources seems to be not the cause.
christian

Thanks - just good to know it's being looked into...