Skip to content
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

Improvements to state interpolation #1718

Open
aaronsantiago opened this issue Feb 17, 2025 · 0 comments
Open

Improvements to state interpolation #1718

aaronsantiago opened this issue Feb 17, 2025 · 0 comments

Comments

@aaronsantiago
Copy link

I see a lot of discussion on this in various places in the repo, though a lot of it is a bit difficult to understand for me b/c of how deep into the software the discussion gets (along with some of it being in French...)
#439
https://github.com/orgs/ossia/projects/44?pane=issue&itemId=71086967&issue=ossia%7Cscore%7C581
https://github.com/orgs/ossia/projects/44/views/1?pane=issue&itemId=71086982&issue=ossia%7Cscore%7C659

etc.

The issue I'm seeing now is--it's wildly difficult to create curves for many addresses at once. For example:

  1. Create a state
Image
  1. Create another state with different values (connected via interval)
Image
  1. Interpolate?
Image

All of a sudden, I've created quite a difficult scenario. If I want to modify the curves, I have to be careful:

  • The start and end values have to match the states that I've created, for each address. This could be MANY addresses potentially (imagine controlling a specific array of lights, or the position of a set of objects)
  • Each curve must be manually set up in a way that matches the others
  • I have to mentally keep track of which curves haven't been edited, and do so via a very specific menu (I know this is unrelated but this doesn't make sense to me)
    • Image

All this just to set it up once--if I ever want to change the curve behavior it would get QUITE unwieldy.

An idea that I had that maybe makes sense within the philosophy of Ossia was to try controlling the playhead of a disconnected interval:

Image

Given many such automations, this could get tedious. I'm not sure what the exact best way to do this would be, but my first thought is a process that does essentially exactly what I've done above but in a single window--and as the default action for "interpolate states". I believe this would create a massively improved artist experience when managing a mass of cues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant