Kai-Jürgen Lietz

Thanks @abacab and @Kurre. I had a parallel discussion in the audiomodern forum. There is kind of a workaround. Though I would call it rather a tiptoe-around it. If you just click to put the chord into the sequencer and use a second click and hold to enlarge the chord-area Chordjam works in Cakewalk as intended and it will work for the session. But if you do it like I did, it is non-recoverable in the session. That being said, the combination of Chordjam and Cakewalk crashed once so hard that Cakewalk wouldn't recognize one of my MIDI keyboards anymore afterwards. It was a pain in the ### to make Cakewalk accept input from it again. 😮

@abacab Thanks! My bad, the option was set to hide VST2 if VST3 is available. Interesting though, Scaler's VST2 was still there. Anyway, in a short test VST2 showed the same (non-)result as VST3 😞

Thanks @abacab and @Kurre. I looked, but there is no VST2 version of that plugin in Cakewalk. Sounds strange, but maybe since VST2 is no longer officially supported by Steinberg there might be none.(?) Using Chordjam from inside Unify works like a charm. But that is to be expected since Unify's programming is highly efficient. I still have to find the plugin that doesn't work with it. So Unify is a good workaround for the time being. Thank you!

I just bought myself Chordjam from Audiomodern. So I might be wrong about this. But I tested it with another DAW and there everything worked fine so it is something in Cakewalk that makes the manual input in Chordjam sequencer not work in the Cakewalk. I realized this in my Livestream (in German language) but you can see that the interface does not behave like it should. Do not watch the whole episode! Just the few seconds after the starting points. The only reason I did not take the video down yet was for this post. And here you can see how it should behave (unfortunately in Ableton Live): Usually I do not have any problems in Cakewalk with my plugins. But since it works with other DAWs I thought People should know that Chordjam won't work in full capacity with our favorite DAW.

Hi all, I wouldn't change the preprogrammed DAWs in your M-Audio keyboard since you can load one into the preset editor as a template for example Bitwig and save it on the last position that is called "Custom" and you can call it whatever you want. 🙂 @Mike Maybe the presets are different because I updated the firmware? There was one when I bought my M-Audio and it was literally the first thing I did after setting it up. Have fun! Kai

It seems there are so many ways to set your keyboard up for controlling Cakewalk. I learnt from the posts in this thread but went a little different route (Mackie/HUI) when it did not work consistently for me. I made a YouTube video about my solution: Hope, this helps others to find their way through this.

Hi, after following this forum for the last year, I got my Oxygen Pro 61 temporarily working. But it was fickle. I had set up two ACT Controllers. One for the tracks and one for the Bus (like Master slider, etc.) Usually I had to activate the ACT Interfaces by righ-clicking on the colored strips in Console view. But sometimes it did not work. So I went another route today. I switched my keyboard to Logic and went for a Mackie controller and activated HUI. That was already quite impressive as the loop button worked as well as all sliders. But I really like to use the master slider and there seemed to be no way to control that. So I did the following. I read the presets from logic in the Oxygen preset editor, changed slider #9 to CC and send it to the last space in the DAW presets. I can access this mixed controller whenever I need, now. I call it "Cakewal". So I know what I must look for. After that I set up an ACT controller for the BUS. In options I had to disable the rotary controls, otherwise there was an unwanted influence of the slider to the panning of the master track. Anyway, everything works now as it is supposed to be. 🙂