C13.0.50 AI Knob issues

[jordikt]

AI knob issues:

1. AI knob in unlocked mode is not updating its cc midi value when the mouse pointer hovers different faders or knobs

2. AI knob in locked mode looses the link to the locked parameter if I click another parameter or if I select another track

[Martin.Jirsak]

Hi,

@jordikt

AI knob in unlocked mode is not updating its cc midi value when the mouse pointer hovers different faders or knobs

What exactly do you mean? Could you describe a use case, how to replicate this?

@jordikt

AI knob in locked mode looses the link to the locked parameter if I click another parameter or if I select another track

How do you use AI Knob? Do you use it with a MIDI Remote script (did you write your own script, or did you create one with the Mapping Assistant)? Or do you use any real AI Knob from Steinberg/Yamaha (CC121, CMC AI)?

[LluisV]

Take a look on this message.

PreSonus FaderPort 2 (2018) midi remote script

I’m sorry but I cannot do more tests because I rolled back (Nuendo). With Faderport, I toggle the shift key and then the fader should get the value of the knob under mouse. With 13.0.50 the fader sometimes reads the value under mouse, sometimes not. Edit: I reinstalled 13.0.50 and recorded what is happening. With 13.0.41 when I move the mouse over any knob the fader gets the value and I can set it. With 13.0.50 the fader do not get the value of the knob but I can set it, but starting from a…

If you have an issue like this, you will need to roll back to 13.0.41

[jordikt]

I am using AI knob since Cubase 12.

It’s configured via Midi Remote using the mapping assistant.

AI knob dial is linked to midi channel 16 cc 0.
AI knob locked/unlocked is linked to midi channel 16 note 0.

I don’t use a real AI knob from Steinberg/Yamaha. I use a hardware knob that sends/receives ch16 cc0 when is rotated and a button that sends/receives ch16 note0 when it’s pressed.

USE CASE of “AI knob in unlocked mode is not updating its cc midi value when the mouse pointer hovers different faders or knobs”

Previoulsy, i.e. in Cubase 12, every time the mouse pointer was hovering a parameter that can be controlled by the AI knob, Cubase sent a midi message like ch16 cc0 value xx , being the value xx the position of the parameter.

As example, if the mouse pointer was hovering a fader at the top, Cubase sent ch16 cc0 value127. After that, if the mouse pointer moved to a centered panorama, Cubase sent ch16 cc0 value 63. And so on.

What I am experiencing now is that Cubase is not sending any midi message when the mouse pointer moves along different parameters.

If I want that Cubase sends the midi message, I have to click in the parameter.

As example, if I click a fader of the mixconsole, the midi message is sent.

But i.e. I can’t get any midi message from a panorama slider in the mixconsole. If I click the panorama of channel 1 in the mixconsole, Cubase is not sending nothing.

A detailed example:
Let’s say I have two channels in the mixconsole, and both channels are panned left at 100%. I move my mouse pointer to hover the panorama of the first channel, and using the AI knob I set the panorama to right at 100%. Then I move the mouse pointer to hover the panorama of the second channel. I rotate a little bit the AI knob to the right. The pan of this second channel will go from panned 100% left to panned 100% right (roughly).

USE CASE of " AI knob in locked mode looses the link to the locked parameter if I click another parameter or if I select another track"

Let’s say I hover the fader of the first channel of the mixconsole, and I press the button to lock the AI knob to that fader.

I can move the mouse pointer anywhere and the AI knob seems to work fine, as everytime I rotate the AI knob the fader of channel 1 moves accordingly, no matter where the mouse pointer is.

But if I select another track that is not the first channel, the AI knob locked stops working and doesn’t do nothing.

Furthermore, if I click the fader of the second channel, the locked AI knob changes its link and then it is locked to the fader of the channel 2.

Previously, when I locked the AI knob to a parameter, this link was never broken in any circumstance, except if I unlock it or I close the project or quit the app.

[jordikt]

@LluisV

If you have an issue like this, you will need to roll back to 13.0.41

Gracies @LluisV , this is the issue I am experiencing.

It seems AI knob has been broken in 13.0.50. Hope Steinberg can fix it in the next release.

@Martin.Jirsak do you know if this issue is a known issue for fixing in next release?

[m.c]

Just to be clear, your midi remote setups are now properly handling the AI knob when you run CB12? Or you recall that it used to work in CB12?

[m.c]

Yeah, just replicated this here too. Just by hovering, the next host value takes the value of the previous one. One needs to actually click on the area of the new host value for the AI knob to take this new value and treat it properly.

[jordikt]

@m.c

Just to be clear, your midi remote setups are now properly handling the AI knob when you run CB12? Or you recall that it used to work in CB12?

If I run C12.0.70, my AI knob works perfectly and if I run C13.0.50 it works bad, with the same midi remote setup. Check the link posted by @LluisV previously, it seems that the last release has broken the AI knob.

[m.c]

@jordikt

Check the link

As I’ve mentioned in my previous post I did replicate the issue, thank you.

[jordikt]

@m.c are you able to replicate also the lock issue?

[Martin.Jirsak]

Hi,

@jordikt

• AI knob in unlocked mode is not updating its cc midi value when the mouse pointer hovers different faders or knobs
• AI knob in locked mode looses the link to the locked parameter if I click another parameter or if I select another track

I can reproduce both of them. Reported to Steinberg. Thank you.