ventosus

zynaddsubfx has a simple header with some macro definitions[1] and then just uses that [2] + tagging the port with the proper metadata [3]. [1] https://github.com/zynaddsubfx/zynaddsubfx/blob/master/src/Nio/jack_osc.h [2] https://github.com/zynaddsubfx/zynaddsubfx/blob/master/src/Nio/JackEngine.cpp#L320 [3] https://github.com/zynaddsubfx/zynaddsubfx/blob/master/src/Nio/JackEngine.cpp#L249

> @ventosus If the metadata things works properly, we can rely on our patchbays to warn from accidental port content mismatch. Now that JACK2 finally has metadata support, too, more...

@piagemesde If there's no new event structure, no a new port type, an additional header (e.g. jack/eventport.h) with some defines and typedefs like [1] would be enough, imho (e.g. just...

last time I checked, JACK OSC messages were not routed via either netjack1, netjack2 or both ? Needs some investigation, I guess...

> @ventosus Do we really need `JACK_METADATA_EVENT_TYPES` to be able to contain multiple values? This is quite a pain to process, honestly, and I don't really see the use (you...

> What do you mean by chat history messages? > The limited history sent by the MUC? No, messages from the SQLite log database.

I have the same problem, I don't need TLS and need to cross compile which fails currently. Is there a way to overwrite this in a parent projects Cargo.toml, maybe?

That should do the trick, indeed.

Please also allow to build without TLS support at all. This would make it much easier to cross compile for embedded devices (no need for openssl-sys) and lead to much...

Could this be extended to build without tls at all? I don't need tls in my project and it is a nuisance to cross build (`ring` dependency fails to cross...