Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

Mozaic CC number converter

Hi all,
Does anyone know how I can convert a series of incoming midi CC numbers using Mozaic?
I have two midi keyboards that both have different transport CC parameters numbers, but I would like both keyboards to operate the transport controls in Cubasis 3 iOS ie,
my Nektar sends CC106 for PLAY, my Novation sends CC115, Cubasis responds to the Nektar but not Novation. I want to change:
112 to 103
113 to 104
115 to 106
116 to 102
117 to 107
Any help will be very much appreciated.

Comments

  • wimwim
    edited June 10

    You can do this without coding with the very handy mfxConvert app. Just send the midi to it and it to the destination. Engage Learn and press a button. On the TO panel, set the CC number. Repeat for each button. Disengage Learn and test. If there are any mistakes, just relearn that button. Once working, save as a preset for future use.

    However, here is some Mozaic code:

    @Description
    Convert transport controls from Novation CCs to Nektar CCs
    @End
    
    @OnMidiCC
      if MIDIByte2 = 112
        byte2 = 103
      elseif MIDIByte2 = 113
        byte2 = 104
      elseif MIDIByte2 = 115
        byte2 = 106
      elseif MIDIByte2 = 116
        byte2 = 102
      elseif MIDIByte2 = 117
        byte2 = 107
      else
        byte2 = MIDIByte2
      endif
      
      SendMIDICC MIDIChannel,byte2,MIDIByte3
    @End
    
    @OnMidiInput
      // Pass messages other than CC's thru unchanged
      if MIDICommand <> 0xB0
        SendMIDIThru
      endif
    @End
    
    @OnSysex
      // Pass Sysex thru
      SendSysexThru
    @End
    

    Just for fun, here it is in Streambyter code:

    # Convert transport controls from Novation CCs to Nektar CCs
    BX 70 = XX 67
    BX 71 = XX 68
    BX 73 = XX 6A
    BX 74 = XX 66
    BX 75 = XX 6B
    
  • @wim said:
    You can do this without coding with the very handy mfxConvert app. Just send the midi to it and it to the destination. Engage Learn and press a button. On the TO panel, set the CC number. Repeat for each button. Disengage Learn and test. If there are any mistakes, just relearn that button. Once working, save as a preset for future use.

    However, here is some Mozaic code:

    @Description
    Convert transport controls from Novation CCs to Nektar CCs
    @End
    
    @OnMidiCC
      if MIDIByte2 = 112
        byte2 = 103
      elseif MIDIByte2 = 113
        byte2 = 104
      elseif MIDIByte2 = 115
        byte2 = 106
      elseif MIDIByte2 = 116
        byte2 = 102
      elseif MIDIByte2 = 117
        byte2 = 107
      else
        byte2 = MIDIByte2
      endif
      
      SendMIDICC MIDIChannel,byte2,MIDIByte3
    @End
    
    @OnMidiInput
      // Pass messages other than CC's thru unchanged
      if MIDICommand <> 0xB0
        SendMIDIThru
      endif
    @End
    
    @OnSysex
      // Pass Sysex thru
      SendSysexThru
    @End
    

    Just for fun, here it is in Streambyter code:

    # Convert transport controls from Novation CCs to Nektar CCs
    BX 70 = XX 67
    BX 71 = XX 68
    BX 73 = XX 6A
    BX 74 = XX 66
    BX 75 = XX 6B
    

    Thanks for your fast response to my question, very much appreciated.
    I first copied and pasted the above script into Mozaic and called it up in Cubasis 3 as a Midi Effect, nothing happened, so I purchased the mfx Convert app and entered all the relevant details and selected Controller as event type but still the transport buttons on my Novation won’t operate Cubasis. The App Store states that mfx Convert is AUv3, so how do I get the converted midi controller numbers to operate Cubasis transport? I have Midi Wrench running and that normally acts as a link but it only shows me the original Novation CC numbers before conversion. I closed Midi Wrench but still nothing.
    Is there any chance you could point me in the right direction
    Thanks in advance

  • wimwim
    edited June 11

    @rapidfire said:

    @wim said:
    You can do this without coding with the very handy mfxConvert app. Just send the midi to it and it to the destination. Engage Learn and press a button. On the TO panel, set the CC number. Repeat for each button. Disengage Learn and test. If there are any mistakes, just relearn that button. Once working, save as a preset for future use.

    However, here is some Mozaic code:

    @Description
    Convert transport controls from Novation CCs to Nektar CCs
    @End
    
    @OnMidiCC
      if MIDIByte2 = 112
        byte2 = 103
      elseif MIDIByte2 = 113
        byte2 = 104
      elseif MIDIByte2 = 115
        byte2 = 106
      elseif MIDIByte2 = 116
        byte2 = 102
      elseif MIDIByte2 = 117
        byte2 = 107
      else
        byte2 = MIDIByte2
      endif
      
      SendMIDICC MIDIChannel,byte2,MIDIByte3
    @End
    
    @OnMidiInput
      // Pass messages other than CC's thru unchanged
      if MIDICommand <> 0xB0
        SendMIDIThru
      endif
    @End
    
    @OnSysex
      // Pass Sysex thru
      SendSysexThru
    @End
    

    Just for fun, here it is in Streambyter code:

    # Convert transport controls from Novation CCs to Nektar CCs
    BX 70 = XX 67
    BX 71 = XX 68
    BX 73 = XX 6A
    BX 74 = XX 66
    BX 75 = XX 6B
    

    Thanks for your fast response to my question, very much appreciated.
    I first copied and pasted the above script into Mozaic and called it up in Cubasis 3 as a Midi Effect, nothing happened, so I purchased the mfx Convert app and entered all the relevant details and selected Controller as event type but still the transport buttons on my Novation won’t operate Cubasis. The App Store states that mfx Convert is AUv3, so how do I get the converted midi controller numbers to operate Cubasis transport? I have Midi Wrench running and that normally acts as a link but it only shows me the original Novation CC numbers before conversion. I closed Midi Wrench but still nothing.
    Is there any chance you could point me in the right direction
    Thanks in advance

    You're going to have to do the conversion before the midi hits Cubasis. Nothing generated from within Cubasis is routed to the transport controls. You may need something that can accept the midi then route it to cubasis. Do you have any other hosts such as Audiobus or AUM to work with?

    But first ... have you tried just using Midi Learn for the transport controls in Cubasis? I'm able to map anything I like to them using MIDI Learn. Go to Setup > Midi > MIDI Learn, then tap each control. If midi learn won't work, then it would be useful to see the midi wrench output for at least one of the controls from the Pacer and from the Novation.

  • @wim said:

    @rapidfire said:

    @wim said:
    You can do this without coding with the very handy mfxConvert app. Just send the midi to it and it to the destination. Engage Learn and press a button. On the TO panel, set the CC number. Repeat for each button. Disengage Learn and test. If there are any mistakes, just relearn that button. Once working, save as a preset for future use.

    However, here is some Mozaic code:

    @Description
    Convert transport controls from Novation CCs to Nektar CCs
    @End
    
    @OnMidiCC
      if MIDIByte2 = 112
        byte2 = 103
      elseif MIDIByte2 = 113
        byte2 = 104
      elseif MIDIByte2 = 115
        byte2 = 106
      elseif MIDIByte2 = 116
        byte2 = 102
      elseif MIDIByte2 = 117
        byte2 = 107
      else
        byte2 = MIDIByte2
      endif
      
      SendMIDICC MIDIChannel,byte2,MIDIByte3
    @End
    
    @OnMidiInput
      // Pass messages other than CC's thru unchanged
      if MIDICommand <> 0xB0
        SendMIDIThru
      endif
    @End
    
    @OnSysex
      // Pass Sysex thru
      SendSysexThru
    @End
    

    Just for fun, here it is in Streambyter code:

    # Convert transport controls from Novation CCs to Nektar CCs
    BX 70 = XX 67
    BX 71 = XX 68
    BX 73 = XX 6A
    BX 74 = XX 66
    BX 75 = XX 6B
    

    Thanks for your fast response to my question, very much appreciated.
    I first copied and pasted the above script into Mozaic and called it up in Cubasis 3 as a Midi Effect, nothing happened, so I purchased the mfx Convert app and entered all the relevant details and selected Controller as event type but still the transport buttons on my Novation won’t operate Cubasis. The App Store states that mfx Convert is AUv3, so how do I get the converted midi controller numbers to operate Cubasis transport? I have Midi Wrench running and that normally acts as a link but it only shows me the original Novation CC numbers before conversion. I closed Midi Wrench but still nothing.
    Is there any chance you could point me in the right direction
    Thanks in advance

    You're going to have to do the conversion before the midi hits Cubasis. Nothing generated from within Cubasis is routed to the transport controls. You may need something that can accept the midi then route it to cubasis. Do you have any other hosts such as Audiobus or AUM to work with?

    But first ... have you tried just using Midi Learn for the transport controls in Cubasis? I'm able to map anything I like to them using MIDI Learn. Go to Setup > Midi > MIDI Learn, then tap each control. If midi learn won't work, then it would be useful to see the midi wrench output for at least one of the controls from the Pacer and from the Novation.

    Ah….. I never thought of that, I do have AUM and I will try and set it up with mfxconvert.
    I a midi learn it no problem, but then I can’t use the Nektar transport, that’s why I want both keyboards to be able to operate Cubasis. I will let you know how I get on.
    Thank you 🍻

  • @wim said:

    @rapidfire said:

    @wim said:
    You can do this without coding with the very handy mfxConvert app. Just send the midi to it and it to the destination. Engage Learn and press a button. On the TO panel, set the CC number. Repeat for each button. Disengage Learn and test. If there are any mistakes, just relearn that button. Once working, save as a preset for future use.

    However, here is some Mozaic code:

    @Description
    Convert transport controls from Novation CCs to Nektar CCs
    @End
    
    @OnMidiCC
      if MIDIByte2 = 112
        byte2 = 103
      elseif MIDIByte2 = 113
        byte2 = 104
      elseif MIDIByte2 = 115
        byte2 = 106
      elseif MIDIByte2 = 116
        byte2 = 102
      elseif MIDIByte2 = 117
        byte2 = 107
      else
        byte2 = MIDIByte2
      endif
      
      SendMIDICC MIDIChannel,byte2,MIDIByte3
    @End
    
    @OnMidiInput
      // Pass messages other than CC's thru unchanged
      if MIDICommand <> 0xB0
        SendMIDIThru
      endif
    @End
    
    @OnSysex
      // Pass Sysex thru
      SendSysexThru
    @End
    

    Just for fun, here it is in Streambyter code:

    # Convert transport controls from Novation CCs to Nektar CCs
    BX 70 = XX 67
    BX 71 = XX 68
    BX 73 = XX 6A
    BX 74 = XX 66
    BX 75 = XX 6B
    

    Thanks for your fast response to my question, very much appreciated.
    I first copied and pasted the above script into Mozaic and called it up in Cubasis 3 as a Midi Effect, nothing happened, so I purchased the mfx Convert app and entered all the relevant details and selected Controller as event type but still the transport buttons on my Novation won’t operate Cubasis. The App Store states that mfx Convert is AUv3, so how do I get the converted midi controller numbers to operate Cubasis transport? I have Midi Wrench running and that normally acts as a link but it only shows me the original Novation CC numbers before conversion. I closed Midi Wrench but still nothing.
    Is there any chance you could point me in the right direction
    Thanks in advance

    You're going to have to do the conversion before the midi hits Cubasis. Nothing generated from within Cubasis is routed to the transport controls. You may need something that can accept the midi then route it to cubasis. Do you have any other hosts such as Audiobus or AUM to work with?

    But first ... have you tried just using Midi Learn for the transport controls in Cubasis? I'm able to map anything I like to them using MIDI Learn. Go to Setup > Midi > MIDI Learn, then tap each control. If midi learn won't work, then it would be useful to see the midi wrench output for at least one of the controls from the Pacer and from the Novation.

    Hi wim,
    I’ve spent the last couple of days trying to figure a way of routing my Novation into mfxConvert into AUM and finally into Cubasis, but it still won’t work 😢 I set up the mfxConvert easily but I just can’t get it into Cubasis, please see attached photo, maybe you can spot the mistake.

  • Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

  • @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

  • @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

  • @espiegel123 said:

    @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

    The only way I found is to perform a Midi Learn in Cubasis using Novation after it passes through mfx and AUM, there has been no conversion at all even though mfx shows the FROM and TO CC numbers are correct. It seems like I’m flogging a dead horse here!

  • @rapidfire said:

    @espiegel123 said:

    @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

    The only way I found is to perform a Midi Learn in Cubasis using Novation after it passes through mfx and AUM, there has been no conversion at all even though mfx shows the FROM and TO CC numbers are correct. It seems like I’m flogging a dead horse here!

    Download a a midimonitor AU such as ShowMidi. Load it into AUM. Use it to see if mfxConvert is receiving the midi you expect from the Novation. If it is, send the mfxconvert output to the midimonitor to see if it is sending out what you expect.

  • @espiegel123 said:

    @rapidfire said:

    @espiegel123 said:

    @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

    The only way I found is to perform a Midi Learn in Cubasis using Novation after it passes through mfx and AUM, there has been no conversion at all even though mfx shows the FROM and TO CC numbers are correct. It seems like I’m flogging a dead horse here!

    Download a a midimonitor AU such as ShowMidi. Load it into AUM. Use it to see if mfxConvert is receiving the midi you expect from the Novation. If it is, send the mfxconvert output to the midimonitor to see if it is sending out what you expect.

    Thanks for your help, I have downloaded ShowMidi and it shows the converted CC numbers correctly but they still don’t operate Cubasis transport?
    Here is my AUM routing map. I had to set up mfx in one Midi Input in AUM and then set up FhowMidi in a second Midi Input, but they are both displayed on the routing screen below:

  • @rapidfire said:

    @espiegel123 said:

    @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

    The only way I found is to perform a Midi Learn in Cubasis using Novation after it passes through mfx and AUM, there has been no conversion at all even though mfx shows the FROM and TO CC numbers are correct. It seems like I’m flogging a dead horse here!

    It sounds like Cubasis is just receiving the Novation messages from Core MIDI. It is not looking at the Cubasis Virtual MIDI port at all. You might be able to change this in the Cubasis MIDI settings.

  • @uncledave said:

    @rapidfire said:

    @espiegel123 said:

    @rapidfire said:

    @uncledave said:
    Hi. You need to route mfxConvert directly to Cubasis. The AUM Source is an output that another app can listen to. The AUM Destination is an input that other apps can send to. They are not connected. In Cubasis, you will use the Cubasis Virtual MIDI input, not AUM (which would be the AUM Source).

    Hi uncledave,
    Thanks for your reply.
    I have attached a photo of AUM with a new routing map as per your suggestion, maybe I have got it wrong but my Novation Impulse transport still won’t operate Cubasis.
    You can see the Novation enters at point [E] and is directed into mfx at point [3].
    mfx sends midi from point [B] into Cubasis at point [5].
    The orange line under B, C & E indicates a midi signal. There is no orange line under [F] even though it is shown as Impulse Midi In.

    If I have made a mistake and you can see it from my photo, please could you indicate a new path using the Letter to Number method in my above description.
    I have discovered I have Midi Learn presets for both keyboards in settings, but I would still like to merge them together and operate Cubasis transport using either mfxConvert or Mozaic if it is possible.
    Thanks in advance.
    Mike.

    Ps, my mother introduced me to an uncle Dave when I was a small lad……but that’s another story 🤣

    Have you used a MIDI monitor to confirm that you are receiving the MIDI you expect on the port you have connected to?

    The only way I found is to perform a Midi Learn in Cubasis using Novation after it passes through mfx and AUM, there has been no conversion at all even though mfx shows the FROM and TO CC numbers are correct. It seems like I’m flogging a dead horse here!

    It sounds like Cubasis is just receiving the Novation messages from Core MIDI. It is not looking at the Cubasis Virtual MIDI port at all. You might be able to change this in the Cubasis MIDI settings.

    Been right through the settings but not found any way of changing MIDI in or outputs.
    Oh well, it was worth a try.
    I want to thank all those that offered help, very much appreciated 🍻

  • wimwim
    edited June 15

    Hey, sorry @rapidfire - I was off camping with no internet the past week. I see that the conversation has confirmed what I was afraid of. I believe Cubasis is listening to the hardware directly and that you can’t make it not do that, unfortunately. Some apps are like that.

  • @wim said:
    Hey, sorry @rapidfire - I was off camping with no internet the past week. I see that the conversation has confirmed what I was afraid of. I believe Cubasis is listening to the hardware directly and that you can’t make it not do that, unfortunately. Some apps are like that.

    Absolutely no problem, I hope you had a good camping holiday, I understand your internet issues having experienced it myself a few weeks ago whilst we were in our caravan with only 3G poor phone signal for a hotspot, the old dial up internet was faster!
    It’s no big issue with not being able to convert transport CC#s, at least I can use either keyboard using Midi Learn presets for the transport.
    Thanks 🍻

  • What about using Midifire ? I don't have Cubasis but Midifire handles coremidi, and can advertise virtual ports.
    I can test it for you but I don't know if midi learn is available in cubasis LE

  • @Etienne said:
    What about using Midifire ? I don't have Cubasis but Midifire handles coremidi, and can advertise virtual ports.
    I can test it for you but I don't know if midi learn is available in cubasis LE

    That's not likely to be any different from AUM, which also advertises virtual ports. The problem is that Cubasis does not listen to virtual ports, at least for its own control functions.

  • wimwim
    edited June 15

    @Etienne said:
    What about using Midifire ? I don't have Cubasis but Midifire handles coremidi, and can advertise virtual ports.
    I can test it for you but I don't know if midi learn is available in cubasis LE

    I think what @uncledave says is correct.
    Midi learn is available in Cubasis under midi settings if you want to test, but I don't think it'll work. The problem is whatever does the midi message translation has to sit between Cubasis and the hardware, but Cubasis listens directly to the hardware. I have Midi Fire, so I'll test later today out of curiosity anyway.

  • @rapidfire @uncledave @wim

    I did a quick test (downloading Cubasis LE was the longest part lol) and it's working. I assigned the buttons to CC0 through midifire.
    (crappy video for a crappy phone, sorry)

  • @Etienne said:
    @rapidfire @uncledave @wim

    I did a quick test (downloading Cubasis LE was the longest part lol) and it's working. I assigned the buttons to CC0 through midifire.
    (crappy video for a crappy phone, sorry)

    I’m not really sure what you mean by assigning buttons to CC0?, I tried to read what was going on in the video but alas my eyes won’t focus sharp enough.
    Are you saying you have successfully managed to operate the Cubasis PLAY button using two different transport controllers using midifire? My one keyboard Play button transmits CC106, the second keyboard Play button transmits CC115, are you saying both these CC numbers will operate Cubasis by using midifire? I ask because I don’t want to buy apps that won’t do the job.

  • @rapidfire said:

    @Etienne said:
    @rapidfire @uncledave @wim

    I did a quick test (downloading Cubasis LE was the longest part lol) and it's working. I assigned the buttons to CC0 through midifire.
    (crappy video for a crappy phone, sorry)

    I’m not really sure what you mean by assigning buttons to CC0?, I tried to read what was going on in the video but alas my eyes won’t focus sharp enough.
    Are you saying you have successfully managed to operate the Cubasis PLAY button using two different transport controllers using midifire? My one keyboard Play button transmits CC106, the second keyboard Play button transmits CC115, are you saying both these CC numbers will operate Cubasis by using midifire? I ask because I don’t want to buy apps that won’t do the job.

    Yes, it works.
    CC0 was arbitrary, it could've been anything between 0 and 127.
    Correct, I midi assigned the 2 different buttons to Cubasis PLAY button. You can use the streambyter lines provided by @wim to your corresponding CCs :

    Convert transport controls from Novation CCs to Nektar CCs

    BX 70 = XX 67 #112 to 103 (70 hexadecimal = 112 in decimal)
    BX 71 = XX 68 #113 to 104
    BX 73 = XX 6A #115 to 106
    BX 74 = XX 66 #116 to 102
    BX 75 = XX 6B #117 to 107

    Inside Midifire, add your 2 controllers as inputs, connect them to a streambyter module, choose the output as Cubasis (must be open beforehand), midilearn the things you want inside Cubasis.

    Maybe some other apps can do this as well, but I only have this one. Before buying, I'd wait for the approval of the gurus though.

  • If it can learn from MIDI Fire, it should work from AUM, too.

  • @espiegel123 said:
    If it can learn from MIDI Fire, it should work from AUM, too.

    Yeh, that one has me puzzled too.

Sign In or Register to comment.