![]() You can look at step 3 and step 10, to see how the Commander program handles midi. Here is my tutorial, i did so far (sorry it is in german): I have steps of +-65, instead of +-1, because Cubase has no other way to handle this. If you do not program the encoders, then the encoders will behave like in your video (2´s complement example) but i do not have in/decrements of 1. I attached you the code-definitions for the common midi-controllers, that the software uses, to program the encoders. Here is the Commander software described: Cubase is not able to recognize the encoders properly, without the C4 Commander software and your MTP program. Like i wrote before, this is some kind of a hack, i did here. I am a novice with midi, i do not know what is really needed for feedback on the rings, but i think \"from Cubase back to my controller\" is essential for the rings :). My guess is, it expects input that is relative again, not absolute. Cubase can send out, but the \"middle-ware\" program Commander C4, refuses to accept the Cubase midi-out and says, this is no Mackie C4 input :( and stops the midi-stream. Yes, that is my problem, no feedback to the LED rings. Do you see it when looking at your log window?\" \"Or is the issue that you have the encoders now recognized in Cubase but no feedback to the LED rings of your encoders? Is Cubase sending any MIDI out when you turn a knob. Help only needed, if i did something wrong here. \"So your encoders send out 2\'s complement but Cubase is looking for absolute? Did you get that working (even if no MIDI feedback)? Is that what you need help with?\" I guess that i need to do something with the virtual midi-out, so that the C4 commander program does not complain about the midi-in (from the virtual out). My biggest hope, is that you might have a solution for me. In fact, i am very close to be satisfied, except i do not have feedback from the DAW. I would like to remove this necessary step, but the program also defines the LCD labels for the encoders. As soon as i defined the encoders, i can start to use them in Cubase. This is one of my main reasons, why i need to use the C4 commander program. You (or DAW) need to mask/define the encoders initially, to get them work properly (like you do in the video). I do not know how other DAW controllers work, but i think that all DAW controllers, have passive encoders. I really hope you understand my problem and if not, feel free to ask :). If i use the midi-out of the virtual cable to go back into the C4, the Commander program complains that the incoming midi is not from a C4 and stop the midi-stream. But the definitions for the encoders (you create in the program) allows only midi-out. The C4 Commander program has of course global midi-settings (in and out), so that the program knows, how the C4 is connected. Anything i do with a mouse in Cubase, is not reflected on the LED rings of the C4 encoders. My problem is, that the C4 Commander program only allows me to setup a Midi-out for the encoders, but no Midi-In and therefore i do not have feedback/bi-directional encoders. ![]() I can use this cable in Cubase and have working encoders. I abused this program with a Bome virtual cable. The C4 also comes with a software called C4 Commander, which is normally used primaly for controlling hardware synths. Cubase does not know, how to treat "2´s complement" encoders. This behaviour is useless in Cubase, as it does not offer any options for the encoders of a C4, even if they are the same, like the Vpots of a Mackie Control (shame on Steinberg). If i turn on the C4, the encoders behave like in your video (2´s complement example). Your program is the only tool, that can help me to solve my problem. ![]() While the Mackie Control is supported by Cubase, the Mackie C4 is sadly not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |