New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ossia-max ]Feature Request: [ossia.parameter] keeping its value when [ossia.model] changes its address #478
Comments
Is there any chance you look into this and/or make a decision if this behavior should become part of the specification? |
I won't object to this - however I don't know how complicated this is to implement. I guess @avilleret only knows |
well, I am very keen to see if I can implement ossia into SPARCK, but this feature is a prerequisite. without it it won't be possible. |
When this kind of case shows up in my own projects, when one particular feature isn't already there, and isn't completely obvious to implement either (maybe this one is, though, I have exactly 0 idea about this), my solution to make this happen is usually to find some budget on the said project, and to hire @avilleret to work upon it. Of course, this requires previous evaluation. |
You have a valid point. I am happy to dive into the code with some guidance. I have experience with Max C-externals, but none with your frameworks architecture. But before this can happen, a strategic decision has to be made by the framework architect. |
for the record, here is the patcher that have been posted on OSSIA forum :
I finally took the time to open it and understand what's wrong. This is indeed an ossia-max issue, not a libossia one. Concerning the issue itself, it a registering issue, when we change the [ossia.model] address, the parameter is not registered correctly. |
SPARCK is Max based, so I would use libossia through ossia-max. |
yes, so there's only stuff to change in ossia-max (and apparently in [ossia.model] I guess, probably around here) |
hey @maybites ! @avilleret began looking into this this morning on https://github.com/OSSIA/libossia/tree/ossia-max-fix - he said he would get back to it in 2 weeks or so... meanwhile, if you want to help to make this happen, you can try to compile this branch, since he couldn't test it (he only had a Linux machine, so no Max) |
Hi In file included from /Users/maybites/Arbeiten/02_code/library/ossia/libossia/OSSIA/ossia-max/src/ossia-max.cpp:7: |
hmm, if you started from an old clone you did a few months ago, you need to run |
sorry, I am at a loss here. I started afresh:
and followed the instructions from the wiki for building max on OSX. the result of
but then with
etc.. |
I made those changes blindly because I don't have OSX nor windows boxes under the hand for now.
I'll try to build it next week. |
hmm maybe the ossia-max code is not up-to-date. sadly I don't have access to a windows or a mac until sunday so I can't test until then either - will keep you posted |
the member 'raw' was removed from spdlog::details::log_msg last october in the following commit: gabime/spdlog@6355e98#diff-e467d3a37f5898269f0d711eb188e9bb could you verify against which commit of spdlog you are compiling? I tried to compile agains a commit before the removal of the member 'raw', but now its complaining
|
@maybites the issue here is that libossia have been updated to use latest spdlog code but not the ossia-max binding. |
@maybites I just pushed a fix, could you pull and try to build again (don't forget to revert spdlog to the version used in the repo, |
ok, the spdlog errors are gone, now there are these:
|
ossia-max build is now working again (and the ossia-max-fix branch have been merged into master) I'll look into that first |
I was able to compile as well, still have some compile warnings, but the externals seems to work. Really appreciate your efforts here. I assume you keep this thread updated on the above mentioned fixes. |
fixed with b21e0f5 |
this seems to be fixed now, but it was not tested extensively, in particular I didn't test with nested model. |
@avilleret I tested the latest master (d96537e) with this example and it still doesn't behave as I would expect: steps to reproduce:
pressing the bang confirms this. |
this is strange @maybites, I use the same example here and it works both in Mac OS VM and on Windows 10. |
I am pretty sure I have. the console shows: build SHA : d96537e |
This is very strange. I don't understand. Here is a video of what I got on my desktop MacOS machine. |
I compiled the latest: build SHA : 0c00d79 and tried both on Max8 and Max7 32 bit but it still doesn't work on my machine as on you video. can you provide me your compiled package? |
@maybites here is my build : https://framadrop.org/r/uv4LQsgJtU#Q9+SCf7hGlwTumwmuc9lHUYtEGsyC9iFlfNK4nQV9NU= |
@avilleret your package is not working on my machine either.. And I made pretty sure I use your code. very strange. I don't have a working theory at the moment. |
it seems to be working (I used the build from framadop above) Max 7.3.5 OS 10.14.2 |
@maybites do you have another computer under the hand to test on by any chance ? |
I just tried it on a pristine machine with osx 10.12.6 / Max 8.0.5 64bit with the same effect. |
Just tried @avilleret 's build with Max 8.0.4 (64 bit) on macOS 10.13.6 and the example by @maybites works fine (parameter does keep its value when model's name changes) |
@jln @avilleret this is all very strange. I just wanted to test it on windows, but it looks as if you haven't got a max-windows solution for libossia, yet. Is this correct? |
@maybites there is a ossia-max package for windows, both 32 and 64bit |
I am fearless but also very unsuccessful and unable to build max for win by myself (I was able to build up to the Visual Studio solution, but didn't progress any further than that). @avilleret your link doesn't contain a working max-package (at least I couldn't find it). there are some mxe-files, but they cause an error 126 inside max7 32bit. |
you're right there is something wrong with the packaging script... I'll upload my build asap |
here is my handmade Windows package @maybites |
still the same effect. Just to make sure we talk about the same thing, here another max patch with step by step description and the expected results:
|
I got the result described in the comment. Sorry for that... |
one thing to note : I can't save the patcher into a file and open it. |
OK, I got it: I always tested the following way:
when you do that you will see my experience I had so far. if you
it works. it also works when you load it as a maxpat. |
ha ok, so it seems there is still an initialization issue which is not related to this one |
@avilleret I can confirm, the issue seems to be resolved. But I haven't tested nested models and special parameters yet. |
Hi
Currently [ossia.parameter] is losing its value when [ossia.model] changes its address (see this topic)
I propose it should keep its value.
This is actually quite important, otherwise it is not possible to dynamically reassign addresses inside running patches without loosing the current parameters.
The text was updated successfully, but these errors were encountered: