LinuxMusicians

Happy holidays to you too and thank you for your tireless work improving Linux audio for us!

So JACK1 has more features than JACK2?

I never thought that JACK2 could be much better than what it already is. JACK2 nowadays makes me wonder how anyone who makes music on the computer can ever live without it.

This roadmap sounds interesting and exciting.

Thank you for your invaluable work, falkTX!

Thank you for your many labors, falkTX: I know from personal experience how much pain and effort goes into being the maintainer of multiple FLOSS projects.

Nice one falktx, your plan sounds very sensible.

I hope one day the version numbering can be addressed, from a layman's point of view it's always been puzzling why jack 1 and 2 both are 1.x.

JACK1 is at 0.125.0

Jack Winter wrote:JACK1 is at 0.125.0

oh well, yeah, that kind of reinforces my point, even more confusing then.

I had no idea you did all this, falkTX. I am so grateful for your work. If it wasn't for the projects you've built (and maintain) many of us would not be able to work effectively on Linux. Thank you.

Thank you and I wish you an excellent 2018!

is there anyone working on incorporating AVB into Jack. It is an open standard

superprick wrote:is there anyone working on incorporating AVB into Jack. It is an open standard

I think that AVB must be incorporated in the kernel.

superprick wrote:is there anyone working on incorporating AVB into Jack. It is an open standard

There was an attempt to add it it to kernel i believe but it has gone nowhere. I'd welcome this as my MOTU Ultralite AVB works really good through USB already. It would be icing on the cake.

@falktx thanks for the update and your never ending contributions to the Linux audio ecosystem! Really appreciated!
And enjoy the holidays!

Also really like it that finally there's a direction for JACK and like it even more that it is to bring them together.

falkTX wrote:This includes meta-data (JACK2 does have the API, but a non-functional one) and the new internal clients.

Does this mean integration of something like "a2jmidid" into JACK?
I'm interested in why this was done for JACK1. Never really understood why it was integrated into JACK1. Is it technically better to do it within JACK vs in a separate piece of software? And what does it offer over just directly making using of ALSA seq (or raw for that matter)?

A totally different question: Is OSC support something that you're considering (for some point in the future)?