hmmm, do you make the add_protocol call happening in the io_context thread ?
(with e.g. some post(...)) method
I'm doing some contract work rn, looking at it this weekend
the
push_value that triggers the exception in this case happens in the same thread as the io_context poll, but no longer with the mutex lock so add/remove protocol could be happening in parallel
Hey there!
There is no 1.2.5 build for ossia-max, which notably prevents users from using a version with some bugs fixed (in this case ossia/libossia#710)
Would anyone be able to make one?
not 1.2.5 but more recent
hi folks ! i've been busy with a project for the last couple weeks, will get back on track here soon.
for anyone interested: automatic media object generation (max/pd external, audio plug-ins, python bindings, etc...) just from a C++ class: https://github.com/celtera/avendish
for anyone interested: automatic media object generation (max/pd external, audio plug-ins, python bindings, etc...) just from a C++ class: https://github.com/celtera/avendish
Namely, is there a way to have parameters which are not stored in a preset?
There is another reason for you, @avilleret to stay out on the room: apparently Max’s SDK has been updated https://github.com/Cycling74/max-sdk/blob/main/README-8.2-update.md
which means that, at some point we’ll need to update ossia-max so it can run natively on M1s in Max 8.2
I am trying to nudge the developer of AudioOverOsc (https://git.iem.at/cm/aoo) to create a Max version (there are already pd-externals available). I know there are similarities between the two apps, but how hard is it really to write something like libossia and then make it work for both? Obviously it is doable, and are there some guidelines one could share? things to look out for?
There are some frameworks for developing stuff from scratch for both Max and pd but one needs to do it from the start AFAIK
is libossia's implementation for pd and max developed by the same person?
would love to hear what you think would be the best
@maybites yes I developed both ossia-max and ossia-pd, @jcelerier made a great talk last week about some tools he made to help developer to make cross environment development (that is to say : write the binding code only once, then the core of the object is shared between pd and max)
this is not how ossia-pd and ossia-max are build, and I don't know yet if this tool might be easily used to port AudioOverOSC to Max
btw AudioOverOsc sounds like a dirty hack to me
it works quite well, though.