-
Notifications
You must be signed in to change notification settings - Fork 13
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
Arrangement mode support #39
Comments
Since this is pretty much a whole new feature, would you take a pull request for it? I might be interested in developing it myself. I've got plenty experience in all technologies involved. |
Hey, This sounds interesting, but using formulas in the arrangement view would require keeping track of more than the selected clip. How would you refer to other clips? I guess you could use some kind of naming scheme where you refer to clips by a special name? Feel free to try implementing something like this, I'd be very curious to see what you come up with! |
Any clip that has been selected before has an id, not only the currently selected clip. If you're starting a new project this should come with minimal hassle, because each new (or pasted or duplicated) clip will have been selected once. Only when you move multiple clips at the same time in arrangement view they apparently lose their ids, until they've been selected again. It's far from ideal. The "Alias Clips" project has a "blink" feature which blinks the color of the tracked clips, I could add something similar to check which clips we're still tracking. As for naming, I would simply not give arrangement clips a name. They start with "=" and they get their data from the session view. In any case, I'll give it a shot |
Great, let me know how it goes! |
@VulumeCode Did you get anywhere with this? |
I haven't forgotten about it, but free time has been scarce. I'm wrapping up another Max project and then I'll get to it. |
It appears that since Live 11 it is possible to observe all arrangement clips as well with arrangement_clips. That should make implementing this feature a bit easier. Are you okay with losing Live 10.1 support? |
That's great news! I've just started looking into Live 11 as well, and since the existing calls I use for populating clips and so on are now deprecated I am thinking of maintaining two mutateful connectors: one for Live 10 and earlier, and one for Live 11. This also means that I can implement MPE support, which is planned. However, I'm currently in the midst of redoing all logic related to how clips and formulas are sent between Live and mutateful, so it would be a good idea to wait until this revamp is completed before starting on this. The new handling will be much more robust wrt having large chains of clips which depend on or reference each other. This was previously done in JS-code inside the mutateful-connector, but I'm removing all logic of this sort on the JS side and replacing it with a more robust system in the mutateful app itself. This will handle things like circular references properly, as well as clips being moved around and various other things which break down in the current version. This transition is about 80% complete at present, I can let you know when this is done and we could discuss some possibilities for how to best implement arrangement support. |
As seen in http://jgarcia.hungry.jp/project/alias-clips/ it is possible to track and update arrangement clips as well, provided they've been selected before and you don't move them in groups.
I don't know the details but I started implementing until I've found both your projects so I figured this much. You can observe the selected clip and keep track of it by id, even though they don't have a canonical path (though strangely they have a track as canonical parent).
The text was updated successfully, but these errors were encountered: