Hi!

I can confirm this. Seeing the same on my Threadripper 3970X.

The amount of aux channels determines the ASIO load in Cubase. Everything else has barely any effect.

Just wanting to defend Jay here. I do similar consultation work and on occasion myself have sent users a PM if they were stuck.

I think offering a service in a civil manner is not a crime - there is no obligation to go along with it and I'm sure Jay doesn't mind if people don't want to spend the $$ for some private help. Jay has worked hard to learn what he knows and I see no reason why he should be chasticed for seeing a business opportunity.

In any case, I think the topic has been answered satisfactorily. Allow me to refer to my tutorial at http://orchestraltemplates.com/tutorial.html which also contains a section about aux setup with some screenshots.

This driving me mad :(

I can't get the instances to stay minimized. Is there any preference file I could delete or something like that? It definitely only affects the instances created before checking the option for the first time. on huge metaframes it takes ages to close all those windows every time.

I did some testing over the weekend: When the "Load instances minimized" setting is not active when creating an instance, activating it later will not have any effect. Any new instance properly load minimized. Tested with 3 different machines on Win 8 Pro.

Thanks for your answer!

Unfortunately it does not work :(

I do not have Avira AntiVir installed and never had (the PC is brand new) The Antimalware Service Executable according to the Task manager belongs to Windows Defender.

Hi!

Win 8, newest VE Pro. When loading a metaframe, all instances open maximized even though I have "open instances minimized on load" checked in the preferences. This has not happened before on OSX. Is there any registry setting I need to set?

Also during loading, VE Pro becomes unresponsive ("inactive" label in the task manager) every few seconds. When it does this, the antimalware service executable" uses CPU time. Is this a security feature of Windows Defender? Something I can set to make defender ignore VE Pro?

Thanks!

Novatlan

Hi!

The whole process is described in the tutorial with pictures, actually :)

If you're stuck, send me an email via my website (http://www.orchestraltemplates.com/contact/index.php) :)

Tobias

It works, but I prefer one instance per section. I think multicore usage is better this way.

Hi!

Yes, it is. I explain this in my VE Pro and Logic tutorial, which you can find at http://novatlan-sound.de/tutorials.php

If you have difficulties, drop me a line via my website contact form.

Tobias

Hi!

I suppose you were referring to my tutorial about VE Pro and Logic. Your template questions are pretty involved and not easily answered in a short text. Basically its a matter of workflow. Planning the stuff is quite challenging, I'd recommend to sit down on a secluded spot and carefully think about what you really need in there. As much as I'd like, I can't help you much without knowing your needs. Maybe you know that I help people set up VE Pro remotely; fee free to drop me a line if you are interested via my website: www.novatlan-sound.de

Cheers :)

Tobias

Hi Steve!

Sorry for taking so long to reply. Unfortunately, I cannot really help you. I program all CC values by recording fader movements to a copy of the corresponding MIDI track. So every single MIDI track as has a second one that is used for modulation and all other CCs. I record these with an Evolution UC333e, where I have several presets for fader assignments for different instruments. I have never used the Event List. Maybe you could try to use a second MIDI track for all CCs.

Ok, looking forward to your feedback. Feel free to drop me a line on my website in case I miss your post here.

In fact, I use CC11, too, so the CC7 thing really isn't that big of an issue, but still: I try to minimize problems. And it is _really_ bad if you accidentally mess up all your levels^

Hi!

If you use any multi instruments the faders in Logic control the whole VI instead of only the one channel, so all your instruments on all channels will change volume with CC7. This is why I insert a transformer in the environment which makes the sliders effectively send not CC7 but another CC for volume. As you cannot (easily) add a transformer to the "regular" multi instruments, I chose to use external midi tracks, which also allows me to only activate the MIDI channels I really need. Behind the scenes, the Logic multi instrument activates all channels. But if I only want 6 channels, with external MIDI I can only activate those 6 and leave the others switched off. Minimises interference.

Furthermore, with the regular multi instruments, you have the first channel as well as the first output on the instrument channel, but for all further midi channels you need extra tracks and auxes. It works, but the first channel looks different than the others. I want it to be as easy as possible which is why I don't use MIDI channel 1 (which is on the track the VI is instantiated on), but start with 2 and use external midi tracks. Those allow me to cable everything to my liking in the environment and so far I could not find any disadvantages. Because channel 1 is not even activated, there is no need to have the VI slot visible, which is why I hide it. It is out of the way and I only see my instrument tracks. Why would you want the actual plugins to appear on the arrange page? They are VE Pro plugins, which you never need to touch after they are set up. I felt these tracks are visual clutter, so I am glad to get rid of them.

There is one last reason: Those multi instruments you use only came with Logic 8. My method works with earlier versions, too. This wasn't a big decision to use it as I use Logic 9, but I had a lot of people following the tutorial who still use Logic 7.

As for bounce in place: Yes, you cannot do this with external midi tracks, but I have never missed it, actually. I didn't even think of this. But you are right, I will put it in the next update for the tutorial.

Hope that helps :)

EDIT: I forgot one thing: If you use the transformer to route the fader to a different CC, you can easily make the fader control a parameter just by changing the CC. So if you want to use the fader for, say, breath control, remap it to CC2 in the transformer. This only works with external midi tracks, if I am not mistaken.

Works fine here.

Exactly :)

It always worked for me this way.

You should be able to switch between machines without problems as long as the name of the VE Pro instance stays the same. Basically, if you name everything the same way on the new machine and have the same patches loaded, all projects should load fine.

I do this daily because both my machines have the same instances of VE Pro. Depending on how much instruments I need I will load them on one single machine or spread them on both. You can mix PC and Mac, that's what I do, too.

Oh, sorry, that was indeed my fault! There are two other people out there who have the same name, one is of questionable political views (illegal views over here) and people constantly confuse me with him. A bit of a sore spot :(

I chose to transform the CCs because some instruments react to CC11 and others don't. Besides CC11 is not always mapped to volume. So to leave the pre-programmed CCs untouched and to be absolutely sure that Kontakt will react to fader changes, I used the transformer. I have also had some instances where my hardware controller would freak out when using CC11. Basically the whole transformer thing is a huge workaround. Most people I helped setting up their templates chose to do it this way, too, but it is not a must. I'll make that more clear in the next update.

I have found that I prefer to run my instances coupled, but I know that most people prefer them uncoupled, so I just chose to not give any advice at all on this matter and let people decide for themselves. If you find the time, I'd be glad if you would tell me the other things you'd change.