#42 midi track monitoring doesn't work

git_head
wont-fix
nobody
None
2015-02-01
2013-03-11
No

I am using Calf Fluidsynth plugin which when loaded with for example FluidR3 takes quite a lot of memory, so I set it up on a lone track (a bus of sorts) and all different instrument tracks are routed in it via an extra MIDI input and output buses (masterBus->midiTrack->fsOutBus->fsInBus->FSPlugin->_).
No matter what combination I try with monitor toggle on tracks, I can't have the same functionality as when I got a single track recieving my HW controller signals and has the synth plugin - it seems like the monitor toggle on tracks isn't the same functionality as the F6 Auto Monitor, which monitors MIDI too.
I'd be very happy if it was fixed soon, now I have to tediously move the plugin and set the Bank/Program after every move when I edit each track...

Discussion

  • Jiří Procházka

    Now I'm not sure if it is the calf fluidsynth problem, it is behaving very strangely now... I suppose I'll just drop it and use qsynth for now

     
  • Jiří Procházka

    With some more testing there is certainly something funky with the midi monitoring - with similar set up for drums with drumkv1 sampler plugin, I hear only the clips on the track which has the plugin itself and from the routed ones only when the plugin track has auto monitor on (is selected).
    Plase make it so normal monitor toggle also works like auto monitor, sending the midi...

     
  • Rui Nuno Capela

    Rui Nuno Capela - 2013-03-12

    please note,

    auto-monitor is a convenience that applies to one and only one track at a time, the current selected one.

    auto-monitor plays a very handy feature for live midi tracks only tough, as the midi channel filtering goes: all incoming events are automagically converted to the current track's channel.

    normal midi track monitor mode does not do any conversion, as midi events must match to their precise midi channel number (1-16), unless (midi track) is set to omni.

    auto-monitor does not apply to buses, it doesn't makes sense for buses anyway, cause there's no concept of "current bus" anyhow.

    cheers

     
    Last edit: Rui Nuno Capela 2013-03-12
  • Jiří Procházka

    Ok, when I set the synth track to omni and monitor on, it plays midi from tracks forwarded to it, so it seems to work, that channel stuff confused me. Thanks for clearing that up.

    With Calf Fluidsynth there is the problem that the program information of the routed tracks are not getting to the plugin (each routed track has its own program). Is there a way to "fix" it? Is it a qtractor issue or the plugin?

     
  • Rui Nuno Capela

    Rui Nuno Capela - 2013-03-12

    re. program information of the routed tracks are not getting to the plugin
    maybe you can try with fluidsynth-dssi instead and check if it behaves any better in that area.

    afaict. midi channel bank_select+program_change commands are transmitted to the corresponding midi output bus plugin chain, so all that should work on multi-timbral instrument plugins inserted on a midi output bus.

    sorry to tell, i don't know about calf-fluidsynth, whether it's supposed to work in a multi-channel environment and whether it recognizes midi bank+prog commands acordingly.

    cheers

     
    Last edit: Rui Nuno Capela 2013-03-12
  • Rui Nuno Capela

    Rui Nuno Capela - 2013-04-21
    • status: open --> pending
     
  • Rui Nuno Capela

    Rui Nuno Capela - 2013-05-06
    • status: pending --> wont-fix
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks