MIDI Input Defaults?

[bayswater]

I often start a new project with a blank template with only Bundles defined. I press Shift-Command-I to get an Instrument track, and assign a piano VI to start trying out some ideas.

It's a minor problem, but the MIDI input to the VI always defaults to a BCF2000 I still have, and not the Roland keyboard I'm using. The Roland is the first in the Bundles list, and the only one with defined inputs and outputs, so I'd expect it to choose that rather than something that is never used to send notes and has no defined I/O

I've gone through the places in the manual looking for places to specify a MIDI Input default but found nothing. Perhaps there is a way to trick DP into assigning the keyboard by default, but I can't find it. Logic does choose the Roland by default.

I do have other templates with an instrument and it's I/O defined, so I could use them, but I don't always want the same instrument.

Does this sound like a familiar thing? Any ideas?

[cuttime]

It's a good question, because every time I go into Multi-Record I get "Network-any"". I have no idea why, but it might have something to do with the MacOS Audio MIDI Setup order?

[HCMarkus]

Why not just disable MIDI Multi Record and not worry about what instrument is assigned?

[monkey man]

That's what I was thinking Brother Sir Markus.

Whatever my settings were back in the day, all I remember is that I never concerned myself with, nor did I see any mention of (in the app) which particular MIDI controller I used. My understanding was simply that DP doesn't care and sees MIDI-input data as data, plain-and-simple.

Maybe Steve requires some newfangled, fancy-schmancy scenario I'm ignorant of?

Please forgive the technical terms.

[bayswater]

Yes, I supposed disabling multi-record will deal with it. At least I won’t have to change a setting every time I use the template. Still, seems odd that DP does not have a way to change the default.

On the order of items in audio-MIDI setup, I’ve always seen a graphic representation with no particular order, but going back, I see there is a “list” view. Maybe that will do something …

[HCMarkus]

I just find the non-Multi MIDI approach so useful... any controllers I grab address whatever VI I have record-enabled. 88 note hammer action keys, expression pedals, mod and pitch wheels from the 61 key controller sitting atop the 88, drum pads and BC directly connected to USB are all active simultaneously. This suits me perfectly for the vast majority of my work.

Sure, it doesn't work when one wants to address two or more separate VIs independently at the same time, but that's what overdubs are for. In those less-typical situations (at least for me) when two performers will be recording MIDI stuff together, or one musician needs to trigger different VIs in a single pass, MIDI Multi-record is great.

[bayswater]

You’re right of course. There are many more situations where multi record is not the best option. I guess I have an unhealthy attachment to templates with tidy well defined signal paths. But one more template without multi-record is the thing to do.