Hi Paul,
VI SE seems to play fine thru the Built In Audio driver, which is strange as it's obviously not as powerful as the MLan. I think it may be a Logic/MLan conflict with VI as the standalone seems to be ok (but I have no way of testing with anything other than with live midi inputi.e no multiple instances).

VI is the only plug in with a problem in this setup though as Kontakt on the next track loaded with the Kontakt VSL sounds plays clean as a whistle.

Just to recap I'm running Logic 7.2.3, 10.4.9, G5 dual2g, 4.5g ram, with the 01X as MLan interface on the main front Firewire bus.

VI is installed on my main G5 HD and the library is on a second 500g SATA drive. Vienna Key is in the front USB. The system can usually run a substantial load of Kontakt instances with VSL intruments routed through Altiverb, so I think it should be powerful enough?

I've tried the Audio Hardware and Drivers buffer setting up to full (1024).

Is there anything else you can think of that I could tweak?

Thanks,

Simon.

p.s I can hear this is a fabulous instrument in spite of the clicks so congratulations on that anyway [:)]

Do you have the same pops and clicks if you run in stand alone mode? Are you running OSX 10.4.9???
Tim

Hi higman,

Yes I am running 10.4.9 and what happens is:

VI+Standalone+MLan = fine
VI+Logic+Built In Audio = fine
VI+Logic+MLan= clicks

Looks like a buffer problem but the buffer is on full 1024 and other
plugs can handle the same and much more without a problem. Also
Built In Audio can handle it, which is strange?

Maybe I'll reinstall all the MLan stuff but I did this before and it made no difference.

Thanks,
Simon.

Also, the System performance meter doesn't change for either Built In or MLan and seems relatively unstressed at about 25%.

To test atm I'm using the Bosendorfer and putting the pedal down and playing fistfuls of notes, with the aforementioned results.

Thanks

Hi Simon,

our development guru just posted that OS X 10.4.9 might also be the reason for this behaviour.

Here is the corresponding thread!

Maybe going back t 10.4.8 helps?

Best,

Paul

Yes, I agree, 10.4.9 has been a bit of a disaster for me. It has disabled both my G4 machines from Authorising in the iTunes Store and has broken the Authorisation for AudioFinder which is not fixable apparently. The G5 is mostly ok.

I'm not sure if I can face going back even if it's possible. I updated to 10.4.9 before buying VI and am in the middle of 4 months intensive scoring and Kontakt (my main sampler) and Logic are working well these days.

Maybe I'll just have to wait for some future fix to use all those lovely new articulations [:(]

I don't suppose there's any way of loading the VI stuff into Kontakt?

Thanks,

Simon.

Hi Simon,

you cannot load the VI content into any other sample player, that´s correct.

Maybe you can just roll back to 10.4.8 on one of your machines?

That´s the only solution I can think of right now....

Best,

Paul

Hi Paul,

I think rollling back is just too scary while in deadline territory. And I'm not 100% sure if it would fix it. Will you be trying to do things with 10.4.9?

It's very frustrating as I can lash up a connection Via Midipipe from Logic to VI
and get it to play fine. This would only give me one instance though and I would end up wallpapering through the letterbox in order to get the Audio back into Logic.

If you come with anything do let me know, but for the moment I guess VI has to
be parked in the driveway...

Thanks,

Simon.

Its all because of the Mlan-driver. It really sucks. This is what Yamaha says:

Yamaha announces takeover of mLAN driver development for Mac

January 12 th 2007 , Hammamatsu , Japan : Responding to continued speculation about the future of mLAN driver development for the Mac platform Yamaha Corporation has released the following statement on 01xRay.com:

Dear valued customers,

With regard to mLAN, which YAMAHA Corporation has proposed to the industry and promoted, we appreciate that many customers are enjoying its convenience under the Windows environment.

As many of you have acknowledged and those who run Intel-based Macs can experience for yourself, on the Windows OS, mLAN is very stable and a vast majority of end users are satisfied with its performance.

As for mLAN on the Mac OS X environment, however, we recognize that some of the performance does not satisfy specific use-cases. In the future, in order to assume more responsibility for the driver's performance and release timetables, the mLAN driver development for the 01X, i88x, mLAN16e and MY16 mLAN will be handled by YAMAHA's own software engineering team and some mLAN driver releases will be done by YAMAHA.[/quote]

I agree the whole MLan situation seems to be dodgy and I'm already feeling some premature Betamax-style obsolescence coming on.

But what I don't understand is why isn't a validated Audio Unit able to function as well as any other validated Audio Unit within Logic? Is it not a "standard"? Surely if one Audio Unit can play through a driver, then all Audio units can? or if not why do they get validated? Or why did the driver get "validated".

Why can't VI play a few string parts in a Logic song next to Kontakt which plays similar content multitimbrally(sp?) perfectly? (And God knows I've had my troubles with Kontakt over the years from beta tester to the present day).

The upshot is I've got £568 worth of plug in and content I can't use.

Just as a matter of interest has anyone got Vi SE running perfectly in Logic 7.2.3
and OSX 10.4.9.

Thanks,

Simon.

Just to elaborate on the above;

Audio Units from the following developers are fully functional under
Logic 7.2.3 and the Mlan driver in my setup.

Alphakanal
Apple
Camel Audio
Expert Sleepers
Fxpansion(including converted VSTs)
GMedia
Green Oak Software
Izotope
Korg
MOTU
Native Instruments
Ohmforce
Cycling74
REFX
Spectrasonics
U-he
YMCK
and
(Incompatible)-MOTU Mach Five)

Those not functioning;

Vienna Instruments.

So maybe not the MLan driver?

Thanks,

Simon.

@leuroj said:

Just as a matter of interest has anyone got Vi SE running perfectly in Logic 7.2.3
and OSX 10.4.9.

Working fine here.

On the other hand, I am running multiple instances of Vienna Instruments plugins within Logic 7.2.3 while running my G5 on OS 10.4.9 - - as well as Altiverb 6, Ozone, various NI libraries and, aside from variable loading times for the Vienna Instruments plugin, have encountered no problems, so far. However I am using a MOTU 2408 mk3/PCI 424 as the audio interface.

Just hooked up an old 828mkii and that works fine so it must be the combo of Logic/Mlan/VI that is a problem I guess.

All my plug-ins works fine for me too when I use a Mbox as audiocard , even VI. I guess the VI put an extra load on the processor/ disk in comparison to the other plug-ins.
Anyway, VI is useless with Logic, Motis ES and mLan. [*-)]

Trond

Trond:

I use multiple instance of VI with Logic everyday with few problems. In other words, in my experience, VI works very well with Logic.

Sorry, I should have been more spesific, VI and Logic isn´t the problem. Its Apple´s mLan (firewire)- driver, which Yamha use. Remember, not all companies use Apples firewire-driver, they apply their own.

two or three years ago i've been having my eyes on mLan for feeding audio into a mixer but finally decided optical connections would be simpler for a setup, mainly because i could not find a detailed specification for the (proprietary and patented) mLan.

possibly you just have a conflict or overload on your firewire-bus in case there are also other firewire devices (harddisks?) present.
christian

edit: have you already checked out this site - i just noticed mLan licenses are free now, at least that's the way i'm reading it, and there are certain updates.

I have just one eksternal disk, and its connected to another bus. No other firewire-devices.
Trond

just for technical clearness: are you saying to another bus (like a second firewire card or controller) or just another port (like another connector)?
please note that a single firewire controller can have up to 3 connectors (it is basically working like a hub) - we often noticed that certain firewire-audio-devices don't work properly if connected to the same controller as an external firewire-harddisk (especially if samples are streamed from there)
christian