Problemwith multi-port device port assignement

Hi,

I’m currently having problems setting up a multi-port device in Nuendo 12.0.30. Looks like a bug to me but I may be wrong.

So my plan is to use 3 MIDI ports to control 24 tracks in Nuendo. Each port should handle 8 tracks on channels 1-8.

Here’s a bit of code reproducing the issue:

var midiInput = [
    deviceDriver.mPorts.makeMidiInput('MB_In_2'),
    deviceDriver.mPorts.makeMidiInput('MB_In_3'),
    deviceDriver.mPorts.makeMidiInput('MB_In_4'),
]

var midiOutput = [
    deviceDriver.mPorts.makeMidiOutput('MB_Out_2'),
    deviceDriver.mPorts.makeMidiOutput('MB_Out_3'),
    deviceDriver.mPorts.makeMidiOutput('MB_Out_4'),
]

var fader1 = surface.makeFader(0,0, 2,2)
fader1.mSurfaceValue.mMidiBinding.setInputPort(midiInput[0])
                                .setOutputPort(midiOutput[0])
                                .bindToControlChange14BitNRPN(0,1)
                                .setValueRange(0,2000)

var channel1 = hostMixerBankZone.makeMixerBankChannel()

mainPage.makeValueBinding(fader1.mSurfaceValue, channel1.mValue.mVolume)

var fader9 = surface.makeFader(2,0, 2,2)
fader9.mSurfaceValue.mMidiBinding.setInputPort(midiInput[1])
                                .setOutputPort(midiOutput[1])
                                .bindToControlChange14BitNRPN(0,1)
                                .setValueRange(0,2000)

var channel2 = hostMixerBankZone.makeMixerBankChannel()

mainPage.makeValueBinding(fader9.mSurfaceValue, channel2.mValue.mVolume)

Now fader 1 on port 0 controls both tracks although feedback works as intended
This is the same for fader 2 on port 1

I’ve mad sure that nothing else was happening midi-wise, so no unintended feedback…

Is there something I’m doing wrong? Or is this really a bug?

I’m running on W10, attached is the full script to reproduce the bug.

ToTo_Bug_MultiDevice.zip (1000 Bytes)

Thanks!

Hi!

It seems this bug as been fixed in v12.0.50!

All is working on my side now.

Thanks Steinberg!

Thomas

1 Like