183,807 users have contributed to 42,323 threads and 255,176 posts.
In the past 24 hours, we have 5 new thread(s), 21 new post(s) and 53 new user(s).
Hi,
I have loaded your template VE Pro 5 Multiport 6x16 Ports Logic Pro X.
How can I use the for example in Logic VE Pro 1 Midi Port 2 (Kanal: Sub 2) - how can I open a new plugin like Kontakt in VE 5 with that Midi Port 2 ?
Best
Rainer
VE Pro 5 Multiport 6x16 Ports Logic Pro X.logicx.zip-1696291948553-24dwd.zipI've loaded up the 6x16, but I am unclear on how it works. If I record enable a MIDI track, I cannot hear anything unless I also record enable the INST track that points to the VEP Instance. But if I record, then it records onto both tracks. Furthermore, if I delete the MIDI data from the INST track and just leave the MIDI track's MIDI data, then the track does not sound at all. Is there a tutorial that goes with these templates?
Nevermind. I figured out the problem. The default Templates supplied by VSL had errors in the Environment upon loading. I figured out where the mistakes were and fixed them, all is well and working now.
I know this post is a bit old, but I'm trying to figure out the VSL environment in Logic X now and I can't get it to work. Any chance you could explain what the 'errors in the environment' were, and how you fixed them? Or could VSL update their multiport layer with a corrected version? the newest one I see is over 2 years old.
When I load a VEP instrument in Logic, I can access 16 channels on that one instrument. But there's no way to access the other 'multi-ports' of MIDI, and when I assign channels to them, they go nowhere.
????
I'm also having this issue (using VE Pro 6 & Logic 10.3.3)
Is there an updated multiport template?
Thankyou.
Felix
I know this post is a bit old, but I'm trying to figure out the VSL environment in Logic X now and I can't get it to work. Any chance you could explain what the 'errors in the environment' were, and how you fixed them? Or could VSL update their multiport layer with a corrected version? the newest one I see is over 2 years old.
When I load a VEP instrument in Logic, I can access 16 channels on that one instrument. But there's no way to access the other 'multi-ports' of MIDI, and when I assign channels to them, they go nowhere.
????
Hi,
There is no updated Multiport Template, I'm afraid.
The template should work as intended if you don't change any parameters and follow the instructions in the manual... you can also send us your original logic song, to check.
Personally, I'd stick with multiple VE PRO instances and wait for AU v3, which is high on the to-do list after Synchron Player.
Best,
Paul
Personally, I'd stick with multiple VE PRO instances and wait for AU v3, which is high on the to-do list after Synchron Player.
Best,
Paul
Yes, avoid it like the plague 😊
Personally, I'd stick with multiple VE PRO instances and wait for AU v3, which is high on the to-do list after Synchron Player. Best,PaulYes, avoid it like the plague 😊 Ha ha! Okay, I will do! Thank you, F
Just about to set this up myself but with Play. So multiple instances are ok to use despite the manual stating that VE PRO "will generally perform best when running as few instances as possible"? I'm imagining that it needs to be an instance per port which would mean in my case at least 30-40 instances. Is this better than using the Event Input Plug-in? I will be using SkiSwitcher to manage articulation switching and 'CC Cloning'.
In this case what is the optimal setting for Multiprocessing? My CPU is a quad-core with hyper-threading so should I set it to 8?
Apologies for newbie questions but I'm just getting started!
Thanks,
Mark
I need to use several midi channels per instrument in order to cover all the different articulations of each instrument. So I envisage that each instance will correspond to one instrument with the possibility of up to 16 articulations. This is how I do it in Logic using Play/Hollywood Orch. Each Play instance is dedicated to a single instrument with all its articulations. Now I'm an absolute beginner when it comes to VEPro so I might have misunderstood how it works (just about to embark on my 2nd read through of the manual!) so I'll have to see what happens when I start to set it up.
I understand. That is the way I have my LASS currently set up. I have one instance for Violins, one instance for Violas and so on.
Other plugins, like Vienna Instruments, handle keyswitching on their own so there is no need for more than one midi channel.
I would suggest reading the manual regarding the multiprocessing - it depends upon your system and the way you use VE Pro.
Yes I am doing and have done so! However I don't find it clear as to what to do if you have multiple instances, in the region of 40 or so for example. With 4 instances and 8 virtual cores it seems clear that you'd set it to 2 threads, with 2 instances 4 threads and so on so that you use all your cores spread across the instances.
It says: "The general rule to follow is that the optimal number of threads on a system should be equal to the number of virtual cores present."
However it says nothing about numbers of instances that go way beyond your number of cores. Unless I'm missing something..
Do not forget that you can run your AU plug-ins inside Logic and send the audio to VEP and MIR
Normally this solution allow to spread better the load across your processors in Logic.
It is cheaper, CPU wise, to run an AU inside Logic than Inside VEP, because VEP adds another layer
Do not forget that you can run your AU plug-ins inside Logic and send the audio to VEP and MIR
Normally this solution allow to spread better the load across your processors in Logic.
It is cheaper, CPU wise, to run an AU inside Logic than Inside VEP, because VEP adds another layer
The extra CPU usage is not that much. I have helped set up a lot of LA composers with building VE Pro orchestral templates connected to Logic and they are pretty much all happy now.
Do not forget that you can run your AU plug-ins inside Logic and send the audio to VEP and MIR
Normally this solution allow to spread better the load across your processors in Logic.
It is cheaper, CPU wise, to run an AU inside Logic than Inside VEP, because VEP adds another layer
I've been running everything inside Logic for years but now I'm making use of a PC slave which has twice the amount of RAM, an SSD and a more powerful processor. So the whole point of me 'migrating' to VEPro is to host the plugins and samples on the slave through VEPro and then do all my recording and editing back in Logic on the Mac. This way I am in fact freeing up the Mac's processor, RAM and HD. Sorry, I didn't make that clear so far in this thread but I think it's a fairly standard way of doing things?
