CC#100 not being chased

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

Moderator: James Steele

Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Post Reply
User avatar
csansom
Posts: 138
Joined: Sat Jan 15, 2011 4:24 am
Primary DAW OS: MacOS
Location: London
Contact:

CC#100 not being chased

Post by csansom »

I'm using SampleModeling's excellent brass instruments, which use CC#100 for muting. For some reason, DP is not chasing these events even though my Setup -> Event Chasing... is set to include All Controllers. It's not that the VI isn’t responding to the events, because if I 'play through' the event it works. I wonder if maybe it's because that controller is normally used as an on/off switch or something, so it won’t chase a change from, say, 0 to 30 (not crossing the 63/64 boundary). Any thoughts?
iMac Pro (2017), macOS 12.7.6 Monterey, MOTU M4, Adam A7 monitors, DP 11.3 94678, Finale 27.4.1.146, VIs from NI, SampleModeling, AudioModeling, Spitfire, Soniccouture, IK, UVI, Modartt, etc. Studiologic acuna88 keyboard
User avatar
Shooshie
Posts: 19820
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Dallas
Contact:

Re: CC#100 not being chased

Post by Shooshie »

You may be on to something. I used to have Pedal 64 and 67 controllers in continuous data mode, rather than switches, and those wouldn't chase, either. I figured it had something to do with the fact that they were 'Switch' controllers being used as continuous data. All those years I used those, and it never occurred to me to ask MOTU if there was some reason why they would not chase.

I ended up creating Custom Consoles for pedals, such that I could hit a button and zero any pedal. Otherwise, they stayed open until a circuit breaker tripped off the powerful solenoids that held them. (Yamaha Disklaviers)

I suggest you talk to MOTU about that.

Shoosh
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
User avatar
csansom
Posts: 138
Joined: Sat Jan 15, 2011 4:24 am
Primary DAW OS: MacOS
Location: London
Contact:

Re: CC#100 not being chased

Post by csansom »

Thanks, Shoosh. I've submitted a new 'techlink' to MOTU, though judging by past experience I'm not optimistic about getting a response any time soon... I'd prefer not to have to phone them from the UK if I can avoid it! Maybe I'll send the same thing to Simon Stock at Music Track, the UK supplier, and see if he can exert any pressure.
iMac Pro (2017), macOS 12.7.6 Monterey, MOTU M4, Adam A7 monitors, DP 11.3 94678, Finale 27.4.1.146, VIs from NI, SampleModeling, AudioModeling, Spitfire, Soniccouture, IK, UVI, Modartt, etc. Studiologic acuna88 keyboard
User avatar
csansom
Posts: 138
Joined: Sat Jan 15, 2011 4:24 am
Primary DAW OS: MacOS
Location: London
Contact:

Re: CC#100 not being chased

Post by csansom »

Much to my amazement I have had a pretty prompt reply from MOTU, saying they've been able to reproduce the problem, and it may be because CC100 is an RPN (I'd forgotten about those), and suggesting I look into reassigning to an undefined CC number within the VI. Offhand I can’t remember if this is possible, and I won’t be able to investigate it for a couple of days, but in due course I will.
iMac Pro (2017), macOS 12.7.6 Monterey, MOTU M4, Adam A7 monitors, DP 11.3 94678, Finale 27.4.1.146, VIs from NI, SampleModeling, AudioModeling, Spitfire, Soniccouture, IK, UVI, Modartt, etc. Studiologic acuna88 keyboard
User avatar
Shooshie
Posts: 19820
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Dallas
Contact:

Re: CC#100 not being chased

Post by Shooshie »

If you are able to change the CC in the VI, try using #67, which is normally reserved for the piano's una corda pedal. That's the one I specifically had the most trouble with years ago. (You have to have the "switches are continuous data" pref selected.) It's definitely not an RPN, but is usually used as a switch.

Shooshie
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
User avatar
csansom
Posts: 138
Joined: Sat Jan 15, 2011 4:24 am
Primary DAW OS: MacOS
Location: London
Contact:

Re: CC#100 not being chased

Post by csansom »

I can remap the CC#s in SampleModeling's lovely brass instruments (in fact, to my relatively untutored eye, it looks as if you probably can in any VI within Kontakt), and 67, as it turns out, works fine, so I'll use that in future. Thanks!
iMac Pro (2017), macOS 12.7.6 Monterey, MOTU M4, Adam A7 monitors, DP 11.3 94678, Finale 27.4.1.146, VIs from NI, SampleModeling, AudioModeling, Spitfire, Soniccouture, IK, UVI, Modartt, etc. Studiologic acuna88 keyboard
Post Reply