-
i found a reproducible hang!
dependencies:
- please grab the latest test server from the slack (0.4.2.3), it includes a build of commit 648c86cf6692213a56415cb822572d0b37e14b73 from oscqueryhtml. …
mrRay updated
6 years ago
-
we need
https://github.com/OSSIA/libossia/blob/master/CMake/ossiaConfig.cmake.in
cf https://cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-a-package-configuration-file
then…
-
As I proposed as a part of the (now-closed) #11:
The proposed syntax could IMHO be more readable if using explicit names instead of numbers for the ACCESS query
I have no strong opinion about what …
bltzr updated
6 years ago
-
the title more or less says it all
that's, of course, when the one we try to instantiate has non-default ports
to reproduce:
- run an ossia app with default ports (e.g. Max's OSSIA overview)
-…
bltzr updated
6 years ago
-
after spending some time with @jcelerier working on libossia's OSCQuery compatibility, here are two things I noticed:
- some apps (notably @lov 's Mitti and @mattbeghin 's MadMapper, and @mrRay 's …
bltzr updated
6 years ago
-
-
The proposal mentions WebSockets could be useful to push out notification to the clients, so I did a little research on this topic, and as I found WebSockets is probably not the way to go, because:
- …
-
as mentioned in #386
brackets are still missing for single values in the OSCQuery JSON:
from my ossia-cpp app:
"size" : {
"ACCESS" : 3,
"FULL_PATH" : "\/renderer\/size",
…
bltzr updated
6 years ago
-
Hello,
I think that there is a small problem in the third example :
```
http://ip:port/foo?VALUE
{
"VALUE": [
0.5
]
}
```
How is the server expected to answer if the para…
-
as defined in the specs @
https://github.com/Vidvox/OSCQueryProposal/blame/master/README.md#L93
> **UNIT** If provided, the value stored with this string is always an array- this array contains …
bltzr updated
6 years ago