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

Import a2jmidi internal client from JACK1 #360

Open
falkTX opened this issue Aug 8, 2018 · 6 comments
Open

Import a2jmidi internal client from JACK1 #360

falkTX opened this issue Aug 8, 2018 · 6 comments
Labels
feature migration Add missing bits to jack2 from jack1 for equal set of tools and features

Comments

@falkTX
Copy link
Member

falkTX commented Aug 8, 2018

No description provided.

@falkTX falkTX added the feature label Aug 8, 2018
@falkTX falkTX added this to the feature-parity milestone Aug 8, 2018
@7890 7890 added the migration Add missing bits to jack2 from jack1 for equal set of tools and features label Jan 16, 2019
@Jacalz
Copy link

Jacalz commented Sep 8, 2019

I would really appreciate this being put in to JACK2. 👍

@Jacalz
Copy link

Jacalz commented Sep 8, 2019

Any news on when this will be done?

@falkTX
Copy link
Member Author

falkTX commented Sep 8, 2019

I need to do some fixes on meta data stuff, so 1.9.13 can be released.
Incorporating the jack1 internal clients comes right after that.

@Jacalz
Copy link

Jacalz commented Sep 8, 2019

Wonderful! Thanks for the information. I’m looking forward to this since my MIDI keyboard only exposes itself using ALSA_midi and the internal client of a2jmidi in JACK1 saves me a bunch of hassle...

@niclashoyer
Copy link

👍

@dingodoppelt
Copy link

I'd really love to see this feature, too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature migration Add missing bits to jack2 from jack1 for equal set of tools and features
Projects
None yet
Development

No branches or pull requests

5 participants