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

Weird multi-channel issue when modifying m_num_ins and m_num_outs as in a multichannel chugin #290

Open
nshaheed opened this issue May 8, 2023 · 0 comments
Labels

Comments

@nshaheed
Copy link
Contributor

nshaheed commented May 8, 2023

This is a weird one that I don't fully understand. Mostly just writing this down so I don't forget.

I was messing with dynamically setting the input and output channels for my Rave chugin. Basically, when the chugin loads the model file it sets the number of input and output channels based off of whether it's doing forward/encode/decode.

This looks something like this in the cpp:

Chuck_UGen* m_self; // the chuck ugen pointer I'm storing in my Rave helper class

m_self->m_num_ins = m_in_dim;
m_self->m_num_outs = m_out_dim;
m_self->m_multi_chan_size = m_in_dim > m_out_dim ? m_in_dim: m_out_dim;

However if I do that, then run the following code:

adc => Rave r => dac;
r.model(me.dir() + "rave_chafe_data_rt.ts");

1::eon => now;

not only can you hear the output of rave, but the adc is just getting passed through to the dac directly (setting the gain of Rave to 0 doesn't change this at all so it's just stepping over it somehow)

@nshaheed nshaheed added the bug label May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant