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

non-realtime buffer manipulation commands #1151

Open
catfact opened this issue Jul 3, 2020 · 4 comments
Open

non-realtime buffer manipulation commands #1151

catfact opened this issue Jul 3, 2020 · 4 comments
Assignees

Comments

@catfact
Copy link
Collaborator

@catfact catfact commented Jul 3, 2020

things like "copy/mix" would be useful additions to buffer "clear, read, write" &c. functionally very straightforward.

additions required for glue layers:

on the crone/c++ side:

(note that for this we don't need to add to Commands enum because there is no work to do on the audio thread.)

and then on the lua/matron/C side:

@tehn
Copy link
Member

@tehn tehn commented Nov 2, 2020

@catfact did you have additional commands you wanted added? or did @csboling cover this?

@catfact
Copy link
Collaborator Author

@catfact catfact commented Nov 2, 2020

i can imagine plenty of other things, but this is not a priority. i like it as a "good first issue" to encourage potential contributors to get their feet wet with the audio cpp code in a non-realtime environment. if you're trying to purge the issue list of non-bugs, then i guess close it by all means. i have no personal desires here.

@tehn
Copy link
Member

@tehn tehn commented Nov 2, 2020

i agree it's a good first issue!

i was suggesting that if we were to indicate a few NRT processes we wanted it'd be a better first issue.

ie, NRT gain changes? or normalization?

not trying to simply purge the list of non-bugs... just making an attempt to establish a more focused roadmap

@catfact
Copy link
Collaborator Author

@catfact catfact commented Nov 2, 2020

gain change and normalization would be obvious ones that have been explicitly mentioned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants