I'm trying to set up the 6 x 16 port multiport template for my old Logic Pro on my old Mac Pro. My problem is that all the midi channels on a given port are sending midi data to channel 1. For example I have ports 33-38 assigned to the third of the six instances of VEP 7. All 16 channels on port 33 are sending to channel 1 of that port, All 16 channels on port 34 are sending to channel 1 of that port etc. Can anyone help me with this?
-
Logic Pro multiport template
-
Hello Sami,
Until now I hadn't tried to use an old (pre-AU3) VSL multiport template with VEPro7, but your plea for help spurred me to do some testing. Previously I had no problems using those templates with VEP6. Well, you're doing better than me with VEP7: testing the old VSL 6x16 Logic template with VEP7 I can't even find where any MIDI is being delivered in instances 2 through 6 .... ei saatana! (Sorry but In Finnish I know only how to curse, although I'm trying to be somewhat polite for the VSL forum, lol.)
It does seem something is very wrong somewhere but I'm still investigating. Thus far, I have MIDI communication working as expected only for VEP7 instance 1. When I try to play MIDI notes to a different instance, the MIDI indicator lights up in the correct instance tab in VEP but does not appear to be delivered to any of the 16 MIDI channels in any of the first 16 ports in the instance (perkele!!).
I'm currently using VEP 7.0.926 with LPX 10.4.8 in MacOS 10.13.6 on a 2017 5K iMac. What version of LPX are you using, Sami? I still have a copy of LPX 10.3.3 and I'm wondering if that might behave more like your version.
Apple have been tinkering here and there in recent versions of Logic's Environment, and I do NOT trust their tinkering in that particular area - for example, they've broken a certain function that I relied upon in the Transformer object and it hasn't been fixed in the last 4 Logic updates. If we can precisely pinpoint and define fault conditions in the old multiport operation with VEP7 then at least we can send sensible bug reports to both Apple and VSL.
Sorry this post is not exactly helpful; I'm continuing to investigate as far as I can.
-
I'm using:
- VEP 7.0.926
- LPX 10.3.2
- OS 10.11.6
- 2008 Mac Pro.My system is so old, that I'm banned from the AU3 party. Until this day I've been using the 2x48 multiport template and it has worked just fine. Now I need one VEP instance more, so I have to try to solve this problem.
-
AU3 won’t work with Logic Pro older then 10.4.5 The old multiport macros from vsl have some problems due to bugs in logicpro. I made some work around templates that work ok, but not as good as au3. See here: [url=https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=137085]https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=137085[/url]
-
AU3 won’t work with Logic Pro older then 10.4.5
I'm painfully aware of this. 😄
The old 2x48 multiport template is working just fine in my setup, but now I need three instances of VEP 7 so that's why I have to try to get the 6x16 template functioning. I think I should give your 4 instance multiport a try. What's the difference between MultiPort and Templates without Tracks? Is it difficult to delete the one instance I don't need or does it consume so little resources from the computer that it is pointless to delete it?
-
Trust me the old templates from VSL don’t work fine. You will have problems eventually with stuck notes, duplicate NoteOff's and weird stuff happening.
I have provided numerous templates at that link I provided, check them out they work and there are some at different numbers of instances. Its also explained on that other link how you can build up a totally custom template if you want but it’s not for the feint of heart
Regarding a couple of your questions, If you read the whole thread I linked to, or at least the first couple posts, all of your questions will be answered, and probably some other questions you didn't want to know. hehe.
But anyway yes you can delete tracks from a larger template. No problem. You can add tracks too if you want to get your hands dirty but generally that is a bit complicated and I don't reccomend it. Easier to start with a big one and just delete the tracks you don't want.
The templates without tracks, were done so that you can build up the tracks one by one...and not have to build up the underlying enviornment structure that is needed. They have all the enviornment structures there waiting for you, then you just add all the tracks you want in any order you want and reassign them to the proper environment objects to hit the right VEP instance. Its all explained in that other forum thread.
-
One more thing, I would reccomend you stick to a layout of 8 ports per instance. (and don't use midi channel 16 on the 8th port). The reason is because hopefully someday you may upgrade your system and be able to use AU3, which is a MUCH better approach. But AU3 is limited to 127 midi channels per VePro instance, across 8 ports (only 15 channels on port 8). So if you organize your template into 127 tracks per VePro instance, it will all translate well to AU3 down the road.
-
-
Sami, I've tried the old VSL 6x16 template with LPX 10.4.8 and 10.3.3, using VEPro 7.0.926 and 6.0.18504. I still can't get any expected delivery of MIDI beyond VEP instance 1. I've also tested the VSL 2x48 template with all these versions and it works fine for me, same as for you, on all ports and channels in both instances. Perhaps my MacOS is screwing up the 6x16 case, or there's something up with the 6x16 template itself, though on a brief inspection everything looks ok in the Environment (and I do know the Environment). Can't conclude anything definite, sorry.
Let us know how you get on with the alternative template.
-
-
One question Dewdman42. It says in your "important usage notes" of your multitrack templates that "make sure to select a track header of a dummy track".
What is a dummy track?
-
with LogicPro you should ALWAYS do the following in all logicPro projects.
create a blank audio or midi track. Label it dummy track or anything you want. I label mine "CLICK ON PLAY".
If you like you can right click on the track header and reassign the track to NO OUTPUT.
Whenever you are about to click play, make sure to select that track header first and get in the habit of doing that. You don't do this while recording tracks, since you have the tracker header selected of the track you are trying to record at that time. But when you're just playing back, always select that "dummy" track header before hitting play.
Why?
Because LogicPro will put itself into Live mode when there is a currently selected track that is actually armed and assigned to a mixer channel with plugins, etc. it dedicates one core for that track and is more likely to click and pop due to the fact that its not making full use of cores. Also, VePro can tell when LogicPro is in live mode. When it is not in live mode, VePro adds extra latency under the covers, you won't even notice it during play, but it makes sure to play more stuff without drop outs.
Anyway, this is an old LogicPro trick, and particularly important when using VePro.
-
