Skip to content

Conversation

@Philipp-M
Copy link
Contributor

Currently based on top of #28, which is the reason for the large amount of changes (last two commits are relevant, I'll rebase this onto master, when #28 is merged)

This adds fairly complete jack transport support (no sync yet though), based on the original jack_transport branch, as timebase master (maybe we should support this optionally in the future).

This means:

  • An additional thread, that listens for start/stop of jack transport (polls every 10 ms)
  • jack_set_timebase_callback, which updates the jack transport position, or sets the engine time to a new requested position (via engine.time = jack::TransportPosition::frame())

This is currently implemented via an Arc<Mutex<Engine>>. I originally wanted to use 2 channels (set and get time/metric_structure, but I think it's actually simpler to just use a Mutex around the engine instead.

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

Successfully merging this pull request may close these issues.

2 participants