-
When score is running in background, there is a latency on OSC that slowly increase.
No issue with OSCQuery protocol (doesn't try other one) but command received from ipad are responding slower and …
-
Using score v3.0.0-a18, created Midi input device cannot be edited. Steps to reproduce:
- From the D-E: Add device
- Select Midi input (leave 'create whole tree' unticked)
- Right-click on the M…
-
open ossia.device.maxhelp
expose osquery
open Score : the device is not visible in device explorer (oscquery)
expose osc seems to work fine.
-
With minuit protocole, we should be able to have several devices talking to i-score on the same udp port (default 13579).
And maybe the udp port could be hardcoded… as it is for art-net for exemple (6…
reno- updated
3 years ago
-
After installing the Quark in SC 3.10.4 and following the provided guide
https://github.com/ossia/ossia-sclang/blob/1d2913c18d6ffc1279751ee8bab312e80441022a/HelpSource/Guides/OssiaReference.schelp#…
-
this score crashes on load, throwing the following error
LLVM ERROR: IO failure on output stream: Bad file descriptor
[Walking_02.4.zip](https://github.com/ossia/score/files/6124132/Walking_02.4.z…
-
I've got a failing test case here:
https://github.com/Cycling74/libossia/tree/xnor/mirror-update
Basically, my understanding of the oscquery protocol is that an update to the device should get sen…
-
When Tick policy (under Preferences -> Execution) is set to score-accurate and playback is started, Score crashes immediately. Tested on OS X 10.11.6 with Score 2.0.0-a4.
-
**Environment**
- OS: MacOS 10.15.5
- Version: 1.7.4
**Describe the bug**
I believe Chataigne is not using the `OSC_PORT` from OSCQuery's `HOST_INFO` object. See `HOST_INFO` in the protocol [h…
-
When an ossia.device is exposed to osc with « expose osc / oscquery » it will output received osc messages that do not match any existing parameter prepended with « osc »
This is a very useful featur…