Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MIDI connection lost after freewheel was used #80

Open
prokoudine opened this issue Nov 30, 2014 · 1 comment
Open

MIDI connection lost after freewheel was used #80

prokoudine opened this issue Nov 30, 2014 · 1 comment

Comments

@prokoudine
Copy link

  1. Start JACK with Raw MIDI driver.
  2. Connect MIDI keyboard to a JACK MIDI port (e.g. a Pianoteq's one)
  3. '$ jack_freewheel y', MIDI signal stops reaching the port as expected
  4. '$ jack_freewheel n', MIDI transmission never restored, not quite expected.

Originally this was discovered after exporting a session in Ardour 3 with a Pianoteq plugin on a track.

@7890
Copy link
Contributor

7890 commented Mar 15, 2019

Point 3) is confusing.
The following setup: jack_midiseq emitting midi events captured by jack_midi_dump, then start freewheeling -> both midiseq and dump still do the job but at higher "speed". After stopping freewheeling, everything is back to normal.
I wonder if it makes a difference whether it's midiseq or a midi keyboard. If you'd press the keyboard while freewheeling, why would it not inject the midi event? If the keyboard should be inoperable during freewheeling, it is possibly something the application should take care off (if we're talking virtual keyboard GUI). However maybe this was misunderstood.
@prokoudine Can you test this scenario again with current version of JACK and if it's still an issue, please make a compact case that is easy to reproduce with detailed information. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants