MIDI and Auxes are greyed out- NOT RESOLVED

[Killahurts]

I wasn't sure if this should go here or on the troubleshooting forum, sorry if it's in the wrong place!

I've noticed for quite some time that when I load a document or a template that has VI's, the MIDI outputs will often be greyed out. I presume this is because the MIDI track loaded before the VI did, so it thinks the VI is off-line. I've always just gone to the output and re-selected it and all is fine, a minor annoyance. But now I have a really big template I'm working with, using VE Pro and a slave machine, and I notice that all the (many) aux inputs from the slave are all greyed out too. Now that's a lot of mousing to do, to reselect all those channels every time!

Is there some kind of input/output "reset" I can do to make all those come back online once all the VI's are loaded? Or, is there a way to make the system "wait" until everything is loaded before it determines what is on or off?

In VE Pro, I could preserve the state of the instances on the slave and just close and start the DP file again, but it seems like a lot of trouble, and I prefer having the slave setups open and close with my song files, mostly.


I keep thinking there must be something I'm overlooking...

[Killahurts]

Figured it out. It WAS something I overlooked, in Audio Bundles. When you make an Aux track and select the input by making a new one with the flip-down menu (where VE Pro shows the available inputs, in my case), you have to go into Audio Bundles and physically make the connections in the instruments page.


Update: Apparently though, saving that didn't work, so it has to be done every time.

[Killahurts]

Redid it several times by hand in the Audio Bundles window, saving each time, and it finally took... weird.

[James Steele]

I have a similar issue when using DrumCore 3. If I use an aux output from DC3 other than the main stereo pair, when I reopen a project, that DC3 output is greyed out as an input and I have to enable/disable the track on which DC3 is (the VI track) to get it to reactivate.

[Killahurts]

I have a similar issue when using DrumCore 3. If I use an aux output from DC3 other than the main stereo pair, when I reopen a project, that DC3 output is greyed out as an input and I have to enable/disable the track on which DC3 is (the VI track) to get it to reactivate.

Yeah I tried that in my situation but no joy.

One would think that when you make a new bundle for an Aux input, it would automatically set it up in the Audio Bundle's windows, but apparently not.

I'm still perplexed though, about why I had to re-do and save it several times before it took. The Audio Bundles are supposed to save with the document, right?

Oh well, it's working now.

[Killahurts]

Oh well, it's working now.

Well, not really.

I can't get the Bundles to remember the setup as a new template. It's driving me nuts, actually. The entire setup is working perfectly in a document, then I save as new template, and when I make a new file from that template, it "forgets" the bundle assignments, and I have to assign them all over again. It does see the Aux inputs (in the bundles window), it just doesn't remember the grid assignments.

Am I gonna have to throw away prefs and start over? Damn this is frustrating!

[doctormelodious]

This happens to me not only with MIDI channels, but also with audio inputs when I'm using EZdrummer in multi-channel output mode. EZd publishes its outputs to CoreAudio, and these can be assigned as inputs to audio tracks. (I always print everything before I mix.)

When I come back to a saved project, some of these outputs DP will remember, and others it won't. For the ones it doesn't remember, it will sometimes substitute some other audio source that it does know about! I'm wondering if there's some kind of internal naming or numbering conflict going on. In any case, it's a major hassle to have to keep reassigning inputs every time I open a project and want to rerecord a VI track.

[doctormelodious]

Ah... check this out!

http://www.motunation.com/forum/viewtop ... 2&start=15" onclick="window.open(this.href);return false;

Some VIs don't seem to like the "pre-gen" thing. In the EZdrummer plug-in window, I went to the pop-up menu in the upper right-hand corner (the tiny circle with the right-pointing arrow), and selected "Default to real-time." Now all of the audio and MIDI outputs/inputs stay put! And because I set it as a default, every instance of EZdrummer I add -- to any project -- will behave the same way.

[Killahurts]

Interesting... I thought I had all that "pre-gen" thing turned off, but I'll go check and report back.

I was able to minimize the the problem by re-setting up all the instrument tracks in their correct numerical order, as in the 3 instances of VE Pro on the slave computer are set to instruments 1,2,3, etc.

But most of the time I still have to open up bundles and move the instrument I/O around in the grid when I open a document, even if I saved it in its correct state before.

[Killahurts]

Nope. My preferences are set to "All plug ins in real time".

[doctormelodious]

Ouch!

Okay, here's something I had discovered just before finding the post about turning off pre-gen.

I found that if I always kept the plug-in's (EZdrummer's) window open when I saved and closed the project, the bundles would be preserved when I reopened it. (I'm guessing that DP loads the plug-in earlier than when the window isn't open.) However, if thereafter I ever saved it with the plug-in's window closed, the bundles were messed up again when I reopened -- never to return until I reset them manually.

Of course, even if this solution does work for you, it's quite precarious. The first time you forget to leave the plug-in window open when you save and close, it's all over.

Good luck, man!

[doctormelodious]

Okay, new discovery...

The "turning off pre-gen" solution breaks if I'm in mix mode and switch mixes. (I was running with mix mode off before.)

I'm about ready to throw in the towel, and just run EZdrummer in stereo mode, printing the drums one at a time. Geez...