-
Notifications
You must be signed in to change notification settings - Fork 9
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
Change channel/synth configuration methods #93
Conversation
core/src/channel_group/mod.rs
Outdated
config.audio_params, | ||
channel_pool.clone(), | ||
)); | ||
channel_events_cache.push(Vec::new()); | ||
sample_cache_vecs.push(Vec::new()); | ||
} | ||
|
||
if config.channel_count >= 16 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for later, but should we make this optional in the future? Just a config flag or something if it's not too messy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean we could, although the user always will have the option to send a config event to channel 10 to make it standard if they wish.
One idea would also be to manage the channel count with a type or something
enum SynthFormat {
// Will create 16 channels, with 10 being drums
Midi,
// Probably other formats here? Idk what else there is
// Will create the amount of channels without setting any to drums
// so the user can do it themselves
Custom { channels: u32 }.
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that works
ChannelConfigEvent
SynthEvent
to useChannelEvent
instead of audio of config so it is a bit more verbose and configurableI haven't benchmarked this yet