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

Initial go using Rustler #1

Merged
merged 9 commits into from
Mar 7, 2022
Merged

Initial go using Rustler #1

merged 9 commits into from
Mar 7, 2022

Conversation

aef-
Copy link
Member

@aef- aef- commented Feb 10, 2022

No description provided.

@aef-
Copy link
Member Author

aef- commented Feb 10, 2022

Originally meant to do this using port drivers, but found the interface using Rust binding for JACK and Rustler to be much more pleasant to work with -- specifically, compiler checks for threads, which is required when interfacing with JACK, means my shoddy programming won't get too much in the way. That said, I don't know the full implications of using Rust JACK and need to understand how they're handling JACK's callback method. I get the feeling we're building threads upon threads and perhaps this is fine for our latency SLA at the moment, but it won't be in the distant future. This project will essentially be one layer above ExALSA, which makes sense seeing how JACK is a layer above ALSA. But that means we should probably offer ExALSA as an OTP server, which we already have.

@aef- aef- merged commit 4fad51e into main Mar 7, 2022
@aef- aef- deleted the aef-/initial-rustler-rc1 branch March 7, 2022 02:24
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.

1 participant