VEPro7 and the Logic Template with more instances

garyhiebner

Active Member
I'm using VEPro 7 and Logic 10.4.4. I have created a VEPro template 4 Instances (WINDS, PERC, STRINGS, BRASS), and I want to use the Logic AU3 BETA Template. But the project only has 24 port with 3 instances. I know I could move merge my instances and then it would be fine. But I want there to be 4 distinct instances like this. How do I create another set of Instrument and MIDI ports in the Logic project that will connect to another instance. Does this need to be done in the envirnomnet? And ow do you set it up. Is there a guide somewhere? Sorry if this has been discussed before can't seem to find it in a post. And also don't wanna get into any single instances vs fewer multitimbral instances in Logic :)
 

Dewdman42

Senior Member
ps you will need to update LogicPro in order to use the AU3 beta. You need 10.4.6 and you need to be on at least the latest version of OSX High Sierra if you aren't already.
 

Dewdman42

Senior Member
really that's interesting. VSL said we needed High Sierra...I guess now that I think about it they didn't say we need 10.4.5 logic, but note that there were AU3 related bugs in 10.4.5 when VEP7 first came out and I reported them to Apple and they were fixed 10.4.6.
 
OP
G

garyhiebner

Active Member
In your guide you mention using Ctrl-Return to create the MIDI Channel with Channel 16. Is this the same as the command 'New Track with Next Channel'? This works fine for me to create the Port 1 Channel 16 channel. But then when I move onto the Port 2 Channel 1, and try create a new track with next channel with this one, I get the MIDI Channel 2, but the port option disappears. Any reason why that is happening?

But when I open your template project its fine. So it's obviously something wrong with the command I'm using. Just wanna figure out How I can build my own from scratch by following your instructions.

Thanks
 

Dewdman42

Senior Member
follow the instructions EXACTLY step by step. If you try to use ctrl-return (new track with next channel) from channel 16, then wrong things happen, it will basically try to create an entirely new instrument, which is why the port is disappearing. After you get it to work following the instructions, make sure to submit a feature request to Apple to complain about it, they need to fix Logic so that if we hit CTRL-RETURN from channel 16, it will automatically bump up to the next port, channel 1. Also they should allow us to create up to 127 multi-timbral parts to begin with using the new tracks wizard.
 
OP
G

garyhiebner

Active Member
Yeah I followed it exactly. I didn't create the new track with next channel after port 1, channel 16. I changed channel 16 to 15. Then I changed the previous port 1 channel 16 to port 2 and channel 1.

I then used the 'New track with next channel on the port 1 channel 15 and that created the port 1 channel 16.

But then when I go to the track with the now port 2 channel 1 settings. If. use the New Track with Next channel command, it creates a track only on channel 2. And there is no port option. Thats where its getting weird.
 

Dewdman42

Senior Member
If you select one of the multi-timbral tracks that is channel 16, look at the track inspector:

beforechange.jpg

Then hit CTRL-RETURN. Select the new track and look at the inspector:

afterchange.jpg

Notice that it changed this one to a totally new instrument channel in the environment! (Inst 2). That's why port is disappearing, its not pointing to Inst1 any more in this case, where the VEP AU3 plugin was.

Avoid hitting CTRL-RETURN anytime channel 16 is selected, because Logic is broken when you do that.

I had a hard time following what you said you did... but follow my instructions literally word for word exactly as I spelled out.

When you change the track attributes of the channel 16 track to port 1, channel 1, then its there waiting to be duplicated, still pointing to Inst1. Go back to channel 15 and duplicate that one again to get channel 16 back again, also still pointing to Inst1.

Then go back to the one that is now port 2, channel 1, which is also still Inst1 and you can CTRL-RETURN 15 times to do the whole process again.
 
Last edited:
OP
G

garyhiebner

Active Member
If you select one of the multi-timbral tracks that is channel 16, look at the track inspector:

Then go back to the one that is now port 2, channel 1, which is also still Inst1 and you can CTRL-RETURN 15 times to do the whole process again.
OK, SO I get to step 6. But when I use the 'New Track with Next Channel (Sorry I can't use Ctrl-Return, cos mine isn't assigned to that, mine is Option-Cmd-X) it does create a new track with a new Instrument.

Strange as it didn't create a new track with a new instrument when I choose the one with MIDI Channel 15 and used the shortcut.
 

Dewdman42

Senior Member
Make sure to submit a bug report to Apple.

The bug has nothing to do with whichever key command you have defined but rather it’s related to trying to do “new track with next channel” from channel 16.
 
Last edited:

reeltracks01

New Member
I was referring to OP's original issue that in 10.4.4 if you change Port 1 midi Channel 16 to Port 2 Midi Channel 1 and then hit Crtl-Return, Logic creates a new non multi Inst Track instead of Port2 Channel 2. That does not happen anymore in 10.4.6
 
OP
G

garyhiebner

Active Member
I was referring to OP's original issue that in 10.4.4 if you change Port 1 midi Channel 16 to Port 2 Midi Channel 1 and then hit Crtl-Return, Logic creates a new non multi Inst Track instead of Port2 Channel 2. That does not happen anymore in 10.4.6
Cool, thanks. I'll update Logic and check if it all works
 

A.G

Senior Member
Hi all,

Let me outline some info (you must bear in mind) which is based on a long time Logic Environment researches.

Here is the story. Me and the great Logic guru Dave Eager (Oink), who died around 2005 started a deep Logic Environment research project between 2000 - 2004. One of the project tasks was to find out the Environment object sizes, their CPU consummation, special behaviors etc. We published some of our work in a few old Logic forums during that time.

As far as I remember the Software Instrument Channel strip object was one of the Environment objects which gets a lot of Logic resources in comparison with the other Environment objects.
AU3 VSL templates are a sort of experiment at the moment and creating numerous Channel Strips for each MIDI Channel is not the brightest idea. The other known problems are the Mute & Solo etc locking.

I highly appreciate the Dewdman42 tutor, but you can go into serious problems with Logic MEGA AU3 templates.

PS. We are partners with VSL, so AG plans to release professional AU3 Orchestral templates in our ART Pro toolkit series.
 

Ashermusic

Senior Member
My belief as well, A.G, but I didn’t say to because Gary was clear he didn't want to hear it :)
 
Last edited: