Input Transformer data off-by-one

Cubase
,
1

An issue that I reported and was fixed in Cubase 13 is now occurring in Cubase 15.

I’m creating a MIDI input transformer to handle the conversion for MIDI CC relative values from a Novation SL MKIII to the values expected by Arturia V-Collection for relative rotary control movement.

I’m checking for the valid range for CW and CCW motion and changing Value 2 to the expected values respectively.

The problem is that any write to Value 2 appears to be off-by-one. Both values 0 and 1 result in a 0 being inserted in the MIDI Value 2, while Value 2 > 1 writes (value - 1).

Add, subtract, and set exact, all appear to have this problem.

In my case, I am using a Track Input Transformer. I suspect Project Transformer would show the same problem.

Again, this was fixed in Cubase 13 after I reported it there.

2

Hi Dave,
can you please post a screenshot of the Transformer’s settings? Thanks.

3
  1. Capture of MIDI controller CW and CCW with no transformer.

image
image941×484 27.8 KB

  1. Input Transformer and MIDI capture (incorrect)

image
image884×685 26.4 KB

image
image882×683 26 KB

image
image943×483 31.2 KB

Please note that the value being written is not the same as the MIDI Value 2.

4

Please note that the result Value 2 has the same issue(s) if the value is the result of Add or Subtract, as well as setting the exact value.

5

Thanks for posting all the necessary screenshots. Makes it easy to set up the same on my Cubase.
You must be using a preset from before C13 or C14? The term “value 2” has been replaced by a less generic and rather context sensitive term. In this case it would be “main value”.

grafik
grafik520×100 1.92 KB

If you change the entry in the action list from Value 2 to Main Value the issue will disappear. That’s the quick fix to get you going right away.

Still, the old preset should be working as well. Maybe we can get Steinberg to see your report.

6

That’s helpful! However, there is still an issue:

If I store the created transformers as presets, the values get altered incorrectly.

Here’s the input transformer BEFORE saving the presets:

image
image881×680 14.4 KB

Now, let’s see what happens when I save this as a preset:

image
image879×686 33.2 KB

Note that all I did was save the preset and the values are all changed.

So…Setting up the transformer as you suggested gives the correct result. However, attempting to save as a preset results in the incorrect values.

7

Merde. This is the bug found in the Logical Editor. Let’s hope they’ll fix it soon.

8

Loaded 15.0.21 and tested.

If I redefine the transformer configuration per the new values, this appears to now be fixed.

Having said that, using the original presets from earlier versions still show the one-off problem I originally reported.

I only have two presets to define, so not a show-stopper, but confusing absent knowledge of the changes to the naming convention. Interestingly, the old presets appear to show up if used, but the behavior is not as expected (one-off originally reported).

The save and restore of the transformer presets appear to be fixed, once the needed corrections are done.

9

Maybe the hotfix update was already finished when you reported this issue and thus it couldn’t be fixed in time.
Let’s hope it’ll get addressed in a next maintenance release.