Thank you. It's been my mistake, to set the output of the I/O utility not to output 1/2. But now I got another problem. I got a big latency. Just when playing with the Event PlugIn. When I play VE Pro Slave directly, there is now latency.

Hi Karel,

My problem with this is that the manual is not clear, so can you give a walkthrough from scratch of how to automate a multichannel instance of VEP5 in Logic. e.g multichannel volume automation of the VSL instruments loaded in VEP5.

Also where in VEP5 is the Assign or Learn Function for the Parameters that appear in the Logic Automation List?

Thanks,

Simon.

OKay I will try it but it seemed that you also have to put an i/o on the VEP plugin track as well to keep it in live mode.  The addition of an i/o on the Event track didn't do anything...but will try agian.  My issue was that it worked when the transport wasn't running but failed with it was.

Chris

In my case: NO sound if not playing Logic project

Yes, it's important that every Event Input plugin track has the I/O Utility plugin as insert effect, set to Output 1-2, then Bypassed. Same with every Audio Input plugin track by the way. This is crucial for proper functionality.

If you want to have the same latency when playing from an Event Input plugin, you can also put the I/O Utility plugin on the main VE Pro plugin track to put it in Live mode. Note however that Logic throws all Live mode tracks processing on a single CPU core, so it is possible that you run into performance issues in some circumstances. The latency when playing from an Event Input track can also be reduced by setting Process Buffer Range to Small (instead of inserting the I/O Utility plugin on the main VE Pro plugin track).

Also make sure you're using the latest version of VE Pro 5 (currently 5.0.9753).

In terms of automation: The Event Input plugin has 512 automatable parameters (Param1 to Param512). Say you assign "Parameter 1" to "1 Master Bus/Volume" in the Automation Mapping window in VE Pro. The volume slider in the master bus will then work like any automatable parameter in a regular AU in Logic. So Param1 of the Event Input plugin that has "Use for automation" enabled directly represents the volume of the master bus in VE Pro.

For me having the i/o plugin on every track was the solution.  :)  I don't get individual volume control though unless I set up automation and I am not sure how this will work with Logic's channel strips which I use all the time for projects that aren't starting with a specific template.  At least it is working!

Chris

Indeed it seems that having the I/O Utility plugin on the main track solves all issues. Logic behaves inconsistent in that regard unfortunately.

Hi there,

I had an identical issue to the one in the video posted by 'jaumepardalito' . The curious thing is that I have two slave computers.... I setup the first slave with 1 VEP instance with 6 x Kontakt 5 Plugins running 16 channels. I used the event input plugin in Logic to create the 6 MIDI sends to VEP, these had I/O utility plugins inserted, sent to 1-2 and then bypassed. To return audio to logic I used the main VEP 2x16 stereo multi-out plugin, with the '+' button hit 5 times to give 6 stereo inputs from VEP in total. I DID NOT have I/O utility plugins bypassed on the additional AUX returnn channels, but I did have one inserted on the MAIN VEP 2x16 stereo multi-out plugin.

Everything worked fine. I was able to record and playback material no problem at all.

I then duplicated this setup identically to the second slave systems. When not in playback or record everything worked fine. When playing back or recording the ISSUSE arose - not all notes were getting through to VE (MIDI registered in Logic), there were MIDI drop-outs and sometimes I got NO SOUND AT ALL. Very frusrating.

I will try adding bypassed I/O plugins to every Vienna plugin in the UNIVERSE. See if that fixes it. If it doesnt this is a major issue as its a super important studio setup I'm working on.

Any help at all appreciated VIENNA!!!

Thanks,

CB.

oh yes....

I didn't have any issue with VEP MIDI port 1... only ports 2 upwards. even if I routed all audio to 1-2 out from VEP (coming into main VEP plugin in logic).... I got MIDI dropouts / silence. So its definitely a MIDI issue with the EVENT input plugin.

CB.

Yes indeed. The Audio/Event Input plugin has some issues in Logic at this point. It only seems to work well when putting an I/O Utility plugin on every VE Pro plugin track (both main Server Interface and Audio/Event Input tracks). I'm working on improving the behavior in Logic as first priority.

Hi Karel,

Thanks very much for the extremely prompt reply. I just wondered if anyone else has reported issues when using more than 1 external slave computer.

Are there any other threads I monitor that mention similar problems to those I described.... is this the main thread?

Very best,

Chris.

Oh a workaround is to use a separate VEP instance rather then multiple midi ports via the EVENT INPUT PLUGIN.

I read in the manul its best to use as few VEP instances as possible to aid processing and stability.... what's your opinion?

Best,

Chris.

Yes, there's only an issue with the Audio/Event Input plugins in Logic at this point. The old way of using multiple instances works just as well as it always has. In general less instances is better performance wise of course.

On the specific point of the Event Input plugin in Logic, any news on the session which had screenshots on this thread and was sent to VSL support by mail three days ago?

I'm not so sure about the Karel.  I created a test project today that used my orchestral template.  Mainliy I tested HS that is on a slave PC.  When using the Input Event plugin I would get occasional spikes in one audio thread.  When using the old method of one instance per track it ran like a dream.  I keep the audio streams low so it doesn't bog down the network.  I just though it was strange that I had worse performance and I doubt it was from the i/o plugin keeping things live as all the work was being done on the slave PC.  

I wish there was a way to detect what was causing the spike as my CPU meters (not in Logic) never jumped like Logic's did.

Chris

I just wanted to bump this because I would love to use this new feature but I seem to be getting CPU hits (an mainly a higher CPU usage) as opposed to running one VEP instance per instrument set...meaning running one for 1st vlns, one for 2nd vlns, etc.  I also have another slave with brass and that is set up with individual instances too.

Chris

EDIT:  I want to add that this seems to only be a problem with the PC slave running HS.  I just did another test with the brass on a slave Mac Mini and the CPU usage was as low as ever...must be something particular to my setup on the PC that is causing an ethernet spike thus causing a CPU spike...not sure how to find that one.

EDIT 2:  I figured out that it was actually a spike in Play on the slave PC that was being picked up in Logic.  This was caused by a doubled string line that maxed the drive (SSD).  Simply offsetting one of the lines fixed the problem.  All was well!

Since making sure every one of my 15 Event Input plugins had a bypassed IO utility plugin on it, I have had no MIDI dropouts or silence on playback/record issues. 

I am running one instance per slave machine and this is working really great... Practically no CPU usage on either slave Mac Mini. As discussed elsewhere one CPU core on my host Mac Pro has lots of activity, but so far no dropouts, clicks or overload messages due to this despite running a massive 256 track orchestral template.

So the software functions exactly as it should. The single core CPU mega-activity problem needs to be solved and be able to be spread over more cores. This sounds like a Logic issue when lots of tracks are forced into live mode with the IO plugin - still Vienna can surely fix this as you are able to run loads of Kontakts in Logic all in an apparent live mode without 1 core going bananas. 

Best,

chris. 

I disagree with your statement that "the software functions exactly as it should". The VEP5 marketing and product page boasted "Up to 48 MIDI input ports for ALL plugin standards (including AU & VST)" — it did *not* mention the required second half of the sentence, "Providing Logic users can afford to spend several weeks sifting through forum posts in order to figure out why an obscure workaround doesn't do what it should".

I've created a very simple Logic session that wasn't behaving as expected and sent it to VSL support. After two weeks with no reply I asked for news and the reply can essentially be summed up as "Ah, the Logic issue. Yes, well, we're working on it."

Logic, you know, that obscure and marginal DAW that nobody's heard of before.

However, I also strongly disagree with someone's post (elsewhere on these forums) qualifying VSL's products as crap. I've been working with VSL and VEP4 for a long time with essentially zero problems and I always found VSL's creativity very interesting to dig into. This is *precisely* the reason I paid for the VEP5 instantly, without even waiting for early adopters to test it beforehand. It's a good thing I did not install it on my main DAW. But the bottom line is that I shelled out over 100 euros only because I was interested in the MIDI ports feature, which is evidently *not* working as expected. Tricking Logic into something it was not designed to do and then blaming Logic for its single-processor issue isn't really a solution. That maddening problem with Logic has been known for a long, long time.

I'm still using VEP4 which is as stable as any piece of software can possibly be. I'm just very, very disappointed.

I agree the current IO plugin workaround is not ideal, but it is clearly explained that this needs to be used in the manual which you could have read prior to purchasing. Since you are aware of this as a maddening problem my advice would then have been not to purchase. 

That said VSL please do better then the IO plugin Logic workaround.