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

Midi events uint offset #43

Merged
merged 8 commits into from
Feb 14, 2024

Conversation

swesterfeld
Copy link
Collaborator

As discussed in #26, midi events should not contain negative frame offsets. Here is a PR for that.

  • I didn't change AUDIO_BLOCK_MAX_RENDER_SIZE as I'm not sure if that depends on anything else (and 2048 is certainly enough for all use cases I can think of), but in principle we now support frame offsets up to 4095.
  • micro-timing information provided by the alsa driver is discarded now, but we can look into this once we really implement recording

Use unsigned data type for midi event offset, see issue tim-janik#26.

Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
…gned

Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
…gned

Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
…signed

Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
…ead)

Signed-off-by: Stefan Westerfeld <stefan@space.twc.de>
@tim-janik tim-janik merged commit 25c0f8a into tim-janik:trunk Feb 14, 2024
4 checks passed
@tim-janik
Copy link
Owner

Thanks.
Sadly the "Rebase and Merge" button of GH just rebases onto trunk, but does not add a dedicated merge commit, will have to push a separate "pr43/swesterfeld-midi-events-uint-offset" merge once the action run completed.

@swesterfeld swesterfeld deleted the midi-events-uint-offset branch February 14, 2024 10:00
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