Helpful ReplyWeird midi problem

Author
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
2018/05/05 21:22:19 (permalink)

Weird midi problem

I have programmed several knobs of a hardware controller to send several cc messages to Cakewalk, and I have found out that for some strange reason, Cakewalk will not see cc 101, out of a fair bunch of them. The controller (an Emu Command Station, actually, but it does not matter) is sending cc 101, and it is correctly detected by Bome Send Syx and by Reaper, but Cakewalk does not see it. The midi activity lights in the midi track light up, so something is arriving there, but nothing gets sent out, or recorded. I have inserted a VST midi monitor in the track (Piz Midi Monitor), and it does not show anything. I have tried sending it from other knobs that work fine with other cc numbers, but cc101 just is ignored. I have also tried to draw the cc 101 in the Controllers pane, and it does not get sent out. Same with the Step Sequencer, cc101 gets ignored for some reason. I am sending 30 other cc numbers correctly, and as far as I can see, everything is fine with them, so I am really puzzled with this.

I have tried this with Sonar Platinum, and with CbB, with a blank project with nothing but a midi track, and same results. This is a new Windows 10 PC with less than one month. As I said above, this works correctly in Reaper, and Bome SendSyx. Any ideas?
#1
noynekker
Max Output Level: -66 dBFS
  • Total Posts : 1235
  • Joined: 2012/01/12 01:09:45
  • Location: POCO, by the river, Canada
  • Status: offline
Re: Weird midi problem 2018/05/05 23:11:45 (permalink)
. . . from a website I have saved, to remind me of the  usage of various continuous controllers, there is a section that shows cc101 has some mysterious "registered parameter (msb)" . . . sorry, don't know what that is ?
Now you've got me curious too.
  • It's probably best not to use the group below for assigning controllers.
  • 96 Data Button increment
  • 97 Data Button decrement
  • 98 Non-registered Parameter (LSB)
  • 99 Non-registered Parameter (MSB)
  • 100 Registered Parameter (LSB)
  • 101 Registered Parameter (MSB)

Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.

 
#2
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
Re: Weird midi problem 2018/05/05 23:43:05 (permalink)
Umm...but even so, if I wanted to send the RPN MSB to a synth, it should be possible to do it. It seems as if Sonar/CbB is filtering it. By the way, Rapture Pro standalone works fine with my knobby controller, cc101 included. Waldorf synths, at least a couple I have, use cc101 as fixed controller for Amp Envelope Attack rate. Something good to have a knob or a slider for.
#3
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Weird midi problem 2018/05/06 00:16:27 (permalink)
I believe CbB and SONAR expect CC 100 and 101 to be used together. If not sent together, the data is ignored as a bad insttruciton.
#4
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
Re: Weird midi problem 2018/05/06 00:36:25 (permalink)
scook
I believe CbB and SONAR expect CC 100 and 101 to be used together. If not sent together, the data is ignored as a bad insttruciton.


Could somebody confirm this? If so, it is an uncalled for limitation, since cc101 is not always reserved for RPN, and most modern synths do not even use RPN's at all. In my case, this just breaks the possibility of remote controlling and automating some synths. Waldorf Largo, Micro Q, Q, and possibly Blofeld use cc101 as fixed controller number for Amp Envelope Attack.
#5
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
Re: Weird midi problem 2018/05/06 10:46:12 (permalink)
I just checked if sending cc 100 along made its most significant other pass through, but it not only did not, but it also got left out of the gate, so I just made a quick event list with all the controller numbers and found out that there are half a dozen controllers that are blocked or ignored: 6, 38, 98, 99, 100 and 101.

Could someone please check if this is so?
#6
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
Re: Weird midi problem 2018/05/06 11:02:42 (permalink) ☄ Helpfulby iRelevant 2018/05/06 12:23:21
Nevermind. Page 908 of the FM. Continuous controllers 6, 38, 98, 99, 100 and 101 are automatically converted to NRPN and RPN data. This is bad implementation, IMO. There should be an option in MIDI preferences. Something like "Convert CC to RPN and NRPN", not just hijack those cc's.
#7
Noel Borthwick [Cakewalk]
Cakewalk Staff
  • Total Posts : 6475
  • Joined: 2003/11/03 17:22:50
  • Location: Boston, MA, USA
  • Status: offline
Re: Weird midi problem 2018/05/06 12:52:14 (permalink)
Most likely CbB is receiving the sequence for a valid NRPN and therefore interpreting it as such. You could try looking at this in MIDIOx. I bet you will see it interpreted as a NRPN as well. You can also look at it in the event list view.
 
The convention of a pair of controllers being used to denote RPN's and NRPN's has been in the MIDI spec for decades and every version of Cakewalk has implemented it this way historically. 
 
I suppose there could be a preference to translate CC's to NRPN's but its not like were hijacking them. This is the official MIDI specification behavior.
 
 

Noel Borthwick
Senior Manager Audio Core, BandLab
My Blog, Twitter, BandLab Profile
#8
IfItMovesFunkIt
Max Output Level: -90 dBFS
  • Total Posts : 38
  • Joined: 2014/11/25 13:24:17
  • Status: offline
Re: Weird midi problem 2018/05/06 13:48:17 (permalink)
100 (LSB)  & 101 (MSB) are indeed used as 2 halves of a larger amount of data that needs 2 CC's to be able to send the required information (LSB = Least Significant Byte, MSB = Most Significant Byte)
 
Last used it with Roland MT32 sometime in the Last Milleniumn !!! 
#9
chris.r
Max Output Level: -86 dBFS
  • Total Posts : 206
  • Joined: 2014/12/20 20:18:15
  • Status: offline
Re: Weird midi problem 2018/05/06 14:03:57 (permalink)
Shouldn't the destination instance in your MIDI setup (i.e. the hardware or software synth) convert CC data to (N)RPN by itself rather than the host program? That can quickly get in a way when programming MIDI data for gear that don't use official MIDI spec.
#10
JoseC.
Max Output Level: -81 dBFS
  • Total Posts : 471
  • Joined: 2003/11/10 14:46:11
  • Location: León, Spain
  • Status: offline
Re: Weird midi problem 2018/05/06 15:10:03 (permalink)
Noel Borthwick [Cakewalk]
Most likely CbB is receiving the sequence for a valid NRPN and therefore interpreting it as such. You could try looking at this in MIDIOx. I bet you will see it interpreted as a NRPN as well. You can also look at it in the event list view.
 
The convention of a pair of controllers being used to denote RPN's and NRPN's has been in the MIDI spec for decades and every version of Cakewalk has implemented it this way historically. 
 
I suppose there could be a preference to translate CC's to NRPN's but its not like were hijacking them. This is the official MIDI specification behavior.
 
 


Thanks for answering, Noel. I am just sending cc101 values to the synths, not the whole combo needed for an RPN value, so CbB just ignores it. If I manually enter the data, using any method in CbB, those values are also ignored and not sent out.

My point is exactly what Chris above says, it should be converted on destination, if applicable, not by CbB. All those synths I mentioned above, including Blofeld, use controller numbers 38 (OSC FM), 100 (Filter envelope release) and 101 (Amp Envelope Attack). This implementation makes it impossible to automate or remote control those parameters from CbB (or Sonar). Every other program capable of receiving midi that I have currently installed, including Rapture Pro standalone, recognize those cc numbers as controllers by themselves.
#11
Noel Borthwick [Cakewalk]
Cakewalk Staff
  • Total Posts : 6475
  • Joined: 2003/11/03 17:22:50
  • Location: Boston, MA, USA
  • Status: offline
Re: Weird midi problem 2018/05/06 15:28:35 (permalink)
Many VST's are completely unaware of the MIDI spec as far as RPN's or NRPN's are concerned. I don't think in itself thats precedent for hosts to also ignore the MIDI spec however considering that MIDI pre-dates all these synths :) I think it was a poor choice for these synths to hardwire these controllers in the first place since they have a special meaning in MIDI.
I havent looked at the code but I assume that when you enter a RPN combo in Cakewalk we're internally using that as a trigger to identify the MIDI event as an RPN. 
 
I understand your point however.

Noel Borthwick
Senior Manager Audio Core, BandLab
My Blog, Twitter, BandLab Profile
#12
chris.r
Max Output Level: -86 dBFS
  • Total Posts : 206
  • Joined: 2014/12/20 20:18:15
  • Status: offline
Re: Weird midi problem 2018/05/07 01:37:22 (permalink)
I still have my Cakewalk 3.0 (MIDI only) installation files from '90-ties somewhere. Sometimes when working on more specific MIDI problems (like this above) in Sonar, I'm forced to go back to Cakewalk 3.0 to get the job done actually. Never let me down. The way it handles MIDI files always helped me solve the problems I otherwise had in Sonar. It's Event List is showing everything. I always did enter (N)RPN or MSB/LSB and Data Entry even SysEx messages manually there and it worked perfectly. For me it's foolproof when cleaning odd MIDI files or checking if there's something going on wrong or simply managing SysEx banks.
post edited by chris.r - 2018/05/07 23:19:54
#13
Jump to:
© 2024 APG vNext Commercial Version 5.1