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.

Sign up for GitHub

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

Jump to bottom

2024 chuckathon findings #13

Open

gewang opened this issue Oct 13, 2024 · 1 comment

Assignees

Member

gewang commented Oct 13, 2024

further investigations needed:

chuck SubInstance shred is still running after SubInstance is destroyed; note: audio is disconnected but otherwise shred is still executing in the VM; possible approach each SubInstance tracks shred ID to remove when it is destroyed
global dac replacements UGens need more cleanup: disconnect from blackhole; possible removal or recycle for future use

gewang assigned gewang, nshaheed and eitomurakami

nshaheed commented Oct 13, 2024 •

edited

Loading

have a set of available replacements dac ugens?

while the unique dac is in use it's not in the set
when the subinstance is destroyed, put the ugen in the set
on subinstance creation try to take from the set, if it's empty, create a new unique ugen

I don't think this needs to be a set - it could just be a stack

Are subinstance construction/destruction multithreaded? In that case we would need some data structure with atomic find/add/remove

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment