MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
rnappi wrote: ↑Sun Jan 19, 2025 6:33 am...and how those in "DP Land" have had to live with generic Makie/HUI templates since forever.
This is why I decided to go with a used Avid S3 and Avid Control on iPad. Although if I was on a real budget, I'd pick up to of the older Euphonix or Avid Mix units and in conjunction with Avid Control for iPad, that would be an extremely powerful budget option.
DP's support for the EUCON protocol has come a long way, but still falls a bit short compared to Cubase, Logic. Certainly Pro Tools is best support which isn't surprising since Avid owns the EUCON protocol now.
I wish I didn’t have to use DP in multi record mode when using Raven 4 since if you aren’t in multi record mode, the record enabled MIDI track revives the MIDI messages assigned to ravens transport controls and faders. Using multi record forces you to specify a specific MIDI input and no longer have “any” selected ad the MIDI input. So then, I had to create a composite multi input instrument to maintain simultaneous MIDI input usage of my keyboard controller, hardware faders for MIDI cc and Metagrid. Not sure what changed in this regard from Raven 3 but this is annoying since I can no longer simply click on the next track I want to record on—I have to option click to avoid record arming more than one MIDI track. Anybody else annoyed by this?
Digiuser wrote: ↑Sun Jan 19, 2025 4:39 pm
I wish I didn’t have to use DP in multi record mode when using Raven 4 since if you aren’t in multi record mode, the record enabled MIDI track revives the MIDI messages assigned to ravens transport controls and faders. Using multi record forces you to specify a specific MIDI input and no longer have “any” selected ad the MIDI input. So then, I had to create a composite multi input instrument to maintain simultaneous MIDI input usage of my keyboard controller, hardware faders for MIDI cc and Metagrid. Not sure what changed in this regard from Raven 3 but this is annoying since I can no longer simply click on the next track I want to record on—I have to option click to avoid record arming more than one MIDI track. Anybody else annoyed by this?
Do you mean the "record enabled MIDI track
receives
the MIDI messages..."
It's too bad the Raven isn't connecting via old school MIDI cables connected to a MOTU interface. If so, I'd imagine you could block the offending MIDI messages coming from the Raven in Clockworks. However, I'm sure it's coming over USB.
I would imagine there might be some utility in software that would allow you to block incoming MIDI from reaching DP?
Come to think of it, could you use DP's Input Filter function to temporarily block incoming pitch bend and controller info, etc. and just allow Note On and Note Off, etc.? It wouldn't be perfect, but you might be able to setup a hotkey that would enable and disable Input Filtering and then attempt to filter/block as many of the unwanted MIDI messages as possible and still be able to record a performance?
Filtering incoming MIDI data is not an option in this case...that would be a nightmare for every fader and knob etc assigned to pitchbend which is what most of the data is.
Filtering incoming MIDI data is not an option in this case...that would be a nightmare for every fader and knob etc assigned to pitchbend which is what most of the data is.
Yeah. Was just thinking if you simply wanted to record note on and note off data into a track. Input Filter would just filter MIDI recorded into a track right? Not block it for control surfaces purposes?
Digiuser wrote: ↑Sun Jan 19, 2025 4:39 pm
I wish I didn’t have to use DP in multi record mode when using Raven 4 since if you aren’t in multi record mode, the record enabled MIDI track revives the MIDI messages assigned to ravens transport controls and faders. Using multi record forces you to specify a specific MIDI input and no longer have “any” selected ad the MIDI input. So then, I had to create a composite multi input instrument to maintain simultaneous MIDI input usage of my keyboard controller, hardware faders for MIDI cc and Metagrid. Not sure what changed in this regard from Raven 3 but this is annoying since I can no longer simply click on the next track I want to record on—I have to option click to avoid record arming more than one MIDI track. Anybody else annoyed by this?
A similar problem happens when I use the MPC Live II here in controller mode, it's not using standard MIDI protocol obviously for communication with the MPC VSTi plugin in DP, it doesn't work as a generic controller with other plugins etc. When you have Multircord off if you access the controls for the MPC plugin with another track armed you will hear sounds from that plugin when you hit the controls on the MPC hardware.
This is specifically a DP issue though, other DAWs have an Any or All setting for each track and multi record always. DP is the only DAW I use that separates out Any from Multi Record. I think the caveat is the issue we're facing but it must be said a benefit comes up with the Kontrol keyboards from NI. With them you can record enable any track that does not use the Kontrol s88, 61 etc. and keep them enabled while using the Kontrol buttons for select to enable record on that track that does use the Kontrol keyboard. It's similar to how other DAWs do it, but the thing is if you use the keyboard to switch tracks and virtual instruments in other DAWs it disables record input on your tracks that use other controllers like drum, clip and keyboards or your hradware gear etc.
M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
I would love one more "mode" for the MIDI input selection that would be great for situations like this when using a RAVEN where you don't want the other aspects of multi-record mode to become the norm in the session.
1] any
2] multi
3] a new mode where you can select a single specific MIDI input source that maintains the record enabling function of the "any" mode.
MIchael-
Are you getting empty channel strips in the raven mixer before the first track in the mixer and even after the last track?
For instance, create a session with 24 tracks in it, and only 24 tracks. Have those 24 tracks in your DP mixer and be in "pin to mixer" mode in control surface setup with the Raven. When I go to the 24 channel Raven Mixer, sometimes it shows Channel 1 in the 2nd position and there are a whole bunch of empty channels that I can "bank" to the left that are messing things up for me. Does this happen to you too? It looks like this:
Attachments
Screenshot 2025-01-21 at 12.21.31 AM.png (3.04 MiB) Viewed 2584 times
Digiuser wrote: ↑Mon Jan 20, 2025 9:21 pm
MIchael-
Are you getting empty channel strips in the raven mixer before the first track in the mixer and even after the last track?
For instance, create a session with 24 tracks in it, and only 24 tracks. Have those 24 tracks in your DP mixer and be in "pin to mixer" mode in control surface setup with the Raven. When I go to the 24 channel Raven Mixer, sometimes it shows Channel 1 in the 2nd position and there are a whole bunch of empty channels that I can "bank" to the left that are messing things up for me. Does this happen to you too? It looks like this:
Yep, it's probably a bug, but yeah, occasionally I've had it "miss" a track as well. Messing around with it a bit mostly seems to set it right again.
M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
Digiuser wrote: ↑Mon Jan 20, 2025 9:17 pm
I would love one more "mode" for the MIDI input selection that would be great for situations like this when using a RAVEN where you don't want the other aspects of multi-record mode to become the norm in the session.
1] any
2] multi
3] a new mode where you can select a single specific MIDI input source that maintains the record enabling function of the "any" mode.
Yep, if you've ever wondered how other DAWs do this, they have the "Any" or "All" selected as default, which you can then change to a specific plugin. This is why DP randomly selects some usually not so useful MIDI controller on input from your list if you're in Multi Record mode. I have a dozen controllers so it's always something useless.
M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
Hey all-
I put together this video today demonstrating some of the cool work flow streamlining that I have implemented with Raven 4 and DP 11.33. I'm only scratching the surface here....check it out:
Digiuser wrote: ↑Wed Jan 29, 2025 10:54 am
Hey all-
I put together this video today demonstrating some of the cool work flow streamlining that I have implemented with Raven 4 and DP 11.33. I'm only scratching the surface here....check it out: