ossia score auto-connects to the JACK system output. Is there some way to disable that behaviour?

Describe the feature
A simple text box in the button editor to be used to write and store notes for future button editing. This would be especially helpful for buttons with more extensive action sequences. Possibly even an option for notes on each individual action?

Is this platform dependent (windows, mac, ..)?
nope

**If documentation is required to implement, do you know where to

TODO

• code linting
• menu/dropdown/switch: unify values parsing
• meta infos in session files
• example sessions
• scripting documentation
• general documentation
• missing properties descriptions
• sliders design choices names
• improve property help modal
• pasted widget position is not always predictable (optional)
• editor keyboard s

It seems like the only reasonable way to get a command-line/terminal program in a usable state onto people's Macs is with Homebrew. I don't really know how Homebrew works internally, though the tool build script I made for orca will check to see if ncurses and portmidi have been installed via Homebrew.

It would be nice if someone could help create a Homebrew thingy (formula? cask? uhh) so tha

I'm working with SLIPSerial and after I have decoded the packet I can't quickly parse it into an osc message, though all the methods are there to do it easily.

Would make this handy library even handier!

I tried running the documentation generator and the following error occurred:

PHP Warning:  preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home/joe/git/xrnx/Xtra/HtmlGen/api_to_html.php on line 152

And it spit out .html pages with no documentation.

I have PHPv7 on my machine. I've never touched PHP code before, so I looked at their docs and

At the main page for the this repo, there's no README, and hence no text after the file listing. What's missing is:

A brief explanation of what the app does. I don't mean how to operate it, but a summary of functionality as well as explaining things that are not present when such might reasonably be expected (e..g, if it does video, what about stills on command). Also does one need to have

If I'm understanding correctly from hypebeast/go-osc#10 and the following code:

https://github.com/hypebeast/go-osc/blob/85fee7fed6921d46ac6261a794ddab814db86888/osc/osc.go#L124-L128

wildcards in addresses are not supported.

If the wildcard addressing feature is not implemented, it should not be listed under "Features". It could be listed under a "Feature TODO" s

In order to make OSCMessage an immutable object (all fields final), while still having a comfortable way to create messages, we could simply use the builder pattern, like in OSCPortInBuilder.java

This is related to the concurrency issue #4.

in the documentation, there is :

auto dom = ossia::net::init_domain(ossia::val_type::INT);
ossia::net::set_values(dom, {-1, 1, 2, 3, 5, 10});
ossia::net::set_domain(node, dom);

but it seems that domain functions have been move from ossia::net to ossia namespace.
maybe others also need check

The aboce should be :

auto dom = ossia::init_domain(ossia::val_type::I

It took me a while to even figure out exactly how to install and load everything.

Now I've got freeliner up and running but due to all the keyboard shortcuts it's quite hard to figure out how to make any progress in making a visual.

It would greatly help to have either a written step by step guide or a screencast with someone instructing on how to make your first visuals. A Hello World for f