Topic: MIDI routing to a VST Effect

Viewing 11 posts - 1 through 11 (of 11 total)
  • #1072
    pj geerlings
    Participant

    After reading (and participating in) this thread I think I may have misunderstood where Podium development is at the moment …

    I have a suite of three plugs: NuBiPlus/VFX/Spinner – both NuBiPlus (an instrument) and Spinner (and effect insert) need MIDI data to perform properly from a “live” keyboard.

    Before registering Podium I was able to create a track with NuBiPlus – I didn’t try to use a keyboard and I didn’t even think to add VFX & Spinner as effects.

    So now I wonder: Is it even possible to add MIDI-driven effects to a track currently?

    peace,
    pj

    #8461
    Zynewave
    Keymaster

    Yes, you can automate both instrument and effect plugins with MIDI parameters. What is not supported yet, is routing MIDI output from one plugin to another. This means that plugins whose main function is to output MIDI to drive other sound generating plugins are not usable with Podium currently.

    #8462
    pj geerlings
    Participant

    @Zynewave wrote:

    Yes, you can automate both instrument and effect plugins with MIDI parameters. What is not supported yet, is routing MIDI output from one plugin to another. This means that plugins whose main function is to output MIDI to drive other sound generating plugins are not usable with Podium currently.

    I may be confused here but I thought that automating parameters on a track is different than using MIDI CC#s from external hardware to control track parameters.

    Specifically I need to use MIDI CC #1 from a keyboard to control the speed of Spinner’s rotors and at the same time use the MIDI Note On/Off messages to “run” NuBiPlus.

    Is this routing already available in Podium?

    thanks,
    pj

    #8463
    Zynewave
    Keymaster

    Specifically I need to use MIDI CC #1 from a keyboard to control the speed of Spinner’s rotors and at the same time use the MIDI Note On/Off messages to “run” NuBiPlus.

    Is this routing already available in Podium?

    Can you set your keyboard up so that CC#1 and the note on/offs output on different MIDI channels?

    #8465
    pj geerlings
    Participant

    @Zynewave wrote:

    Specifically I need to use MIDI CC #1 from a keyboard to control the speed of Spinner’s rotors and at the same time use the MIDI Note On/Off messages to “run” NuBiPlus.

    Is this routing already available in Podium?

    Can you set your keyboard up so that CC#1 and the note on/offs output on different MIDI channels?

    My test keyboards are pretty basic so I think not…
    I could be wrong, however

    #8467
    Zynewave
    Keymaster

    I’ll check my code tomorrow, to see if I can come up with a solution. I may have to do a small modification to the MIDI input mapping handling.

    #8471
    Zynewave
    Keymaster

    I guess what you are looking for is a way to assign the same MIDI input (your keyboard) to both NuBiPlus and Spinner. Podium restricts a MIDI input object to only be assigned on one track, to avoid confusion, and to make it easy to drag the mapping from track to track without having to unassign it from the old track. A solution for you would be to create a second MIDI input object mapped to the same MIDI input. You can then assign MIDI1 to Spinner and MIDI2 to NuBiPlus. In effect you duplicate the MIDI input from your keyboard into the two MIDI input objects. As a consequence, both Spinner and NuBiPlus receives the notes and CC#1 messages. This may be undesirable if NuBiPlus reacts to CC#1 or Spinner reacts to note messages.

    Will this setup do what you want to achieve?

    Currently Podium does not allow two MIDI input objects mapped to the same MIDI input, but I can remove this restriction.

    #8472
    pj geerlings
    Participant

    @Zynewave wrote:

    I guess what you are looking for is a way to assign the same MIDI input (your keyboard) to both NuBiPlus and Spinner. Podium restricts a MIDI input object to only be assigned on one track, to avoid confusion, and to make it easy to drag the mapping from track to track without having to unassign it from the old track. A solution for you would be to create a second MIDI input object mapped to the same MIDI input. You can then assign MIDI1 to Spinner and MIDI2 to NuBiPlus. In effect you duplicate the MIDI input from your keyboard into the two MIDI input objects. As a consequence, both Spinner and NuBiPlus receives the notes and CC#1 messages. This may be undesirable if NuBiPlus reacts to CC#1 or Spinner reacts to note messages.

    Will this setup do what you want to achieve? …

    I think it just might!

    thanks,
    pj

    #8475
    Zynewave
    Keymaster

    I think it just might!

    Good. I’ve already made the modifications. Podium 1.76 is just released.

    Hints:
    Locate your MIDI input mapping in the devices panel on the project start page. Right-click and use the “New copy…” command. Give it a proper name and press OK. You now have two MIDI inputs in the track inspector input panel. Assign one on the track with NuBiPlus and the other on the track with Spinner. I hope that works.

    #8935
    koalaboy
    Participant

    Forgive my asking, and I may be being silly here because I’m at work, and can’t fully test this, but…

    Couldn’t the same thing be achieved by adding a group track ‘above’ the two VST tracks, and just assigning the single midi input to that ? I’m probably missing something obvious.

    Thanks,

    Michael.
    (Just trying to get behind the thinking)

    #8936
    Zynewave
    Keymaster

    Couldn’t the same thing be achieved by adding a group track ‘above’ the two VST tracks, and just assigning the single midi input to that ?

    It won’t work, although I can understand why you think this could be a solution. However: everything flows upwards in the hierarchy. So a MIDI input assigned to a parent group track will only flow upwards to the nearest device mapping, and it will not flow downwards to any child devices.

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave