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

Sync Hydra clock #243

Open
munshkr opened this issue Jan 19, 2024 · 3 comments
Open

Sync Hydra clock #243

munshkr opened this issue Jan 19, 2024 · 3 comments
Labels
enhancement New feature or request hydra Related to Hydra
Milestone

Comments

@munshkr
Copy link
Owner

munshkr commented Jan 19, 2024

I was thinking it'd be interesting to explore syncing Hydra internal clock (the time variable on HydraSynth). We could send this time variable on each evaluation and update the time variable on each peer that receives that evaluation message with the sent time value.

@munshkr munshkr added enhancement New feature or request hydra Related to Hydra labels Jan 19, 2024
@munshkr munshkr added this to the Version 1.1 milestone Jan 19, 2024
@munshkr munshkr moved this to Todo in Flok: Backlog Jan 19, 2024
@tmhglnd
Copy link
Contributor

tmhglnd commented Apr 20, 2024

Is a good idea, but with the downside that the animation might look interrupted because the time is all of a sudden reset to a different position. So smooth motion from oscillators and rotation is broken because of it. Maybe the resyncing should only happen when a new client enters the session, or when Hydra is hush()-ed.

@munshkr
Copy link
Owner Author

munshkr commented Apr 26, 2024

Is a good idea, but with the downside that the animation might look interrupted because the time is all of a sudden reset to a different position. So smooth motion from oscillators and rotation is broken because of it. Maybe the resyncing should only happen when a new client enters the session, or when Hydra is hush()-ed.

Hey! Yes, it's not as easy as I thought at first... I guess we'd need to only sync new clients by taking another client as reference. But things can go wrong anyway and drift, so it will never be perfect.

My motivation was mainly solving the use case of having two Hydra windows in the computer, one for rendering in another screen/projector for instance (there are some situations where you don't want to show the code for example, and it'd be great that both windows are synced).

@tmhglnd
Copy link
Contributor

tmhglnd commented Apr 26, 2024

I think it could make sense to just have a section in the Flok documentation explaining the option to re-sync hydra visuals amongst clients. If the .time variable is exposed as a global/window variable it can just be included in the code and run once before a performance starts to allow users to sync up manually if they prefer. I don't know what the variable is in Flok, but in Hydra it can be reset with hydraSynth.synth.time = 0 (in the past it was H.synth.time = 0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hydra Related to Hydra
Projects
Status: Todo
Development

No branches or pull requests

2 participants