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

Macros #445

Open
cale-bradbury opened this issue Sep 28, 2024 · 4 comments
Open

Macros #445

cale-bradbury opened this issue Sep 28, 2024 · 4 comments

Comments

@cale-bradbury
Copy link
Contributor

cale-bradbury commented Sep 28, 2024

Opening this ticket up into an issue to share some thoughts on an extension of macros I really want to see.

I never used the float macros much in the og Hedron, but frequently wished to be able to create a Macro shot, ie; set a bunch of params to a specific value via a button.

This would pair well with an option to dump the entire state into a macro shot. Possibly with filtering, like just a particular sketch, or skipping values that are midi controlled.

This would also likely want the option to tween all the values, but that could come later.

@funwithtriangles
Copy link
Member

This is currently possible on the old hedron, but could be nicer.

  • create a macro with all your target params
  • add an anim to that macro (with 0 or more duration)
  • add a midi input to the anim trigger

I'm definitely open to other ways of achieving this, although it's nice to know that a mix of simpler features can achieve it

@cale-bradbury
Copy link
Contributor Author

cale-bradbury commented Sep 28, 2024

Ahh, its been awhile since I used it, thought it was just for tying multiple params to one, and was only floats.

Regardless, when it gets ported a helper(s) to dump the current state into the macro would be great

@funwithtriangles
Copy link
Member

I think we might be able to achieve macros using timelines. Scrubbing through a timeline is essentially the same as changing the value of a macro. We already have lots of things to solve with values not being synced with timelines and we had that problem with old Hedron and macros.

My suggestion is macros stay as a feature but under the hood they are basically just timelines configured in a specific way:

  • some specific duration
  • only two keyframes per param (beginning and end)
  • some specific conflict solving behaviour (e.g. lerp to target keyframe from start of movement)

When a macro is created it's really just a timeline with some isMacro flag so it is displayed differently (and in a different location). Perhaps we have a "convert to timeline" option if users want to have more control.

If we go down this route it's clear that the timeline feature should take priority over macros.

@funwithtriangles
Copy link
Member

Your multi shot macro idea doesn't quite fit well into the timeline thing, so that would almost certainly be handled differently. We could even consider naming it something else, or renaming macros.

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

2 participants