-
Notifications
You must be signed in to change notification settings - Fork 423
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
Add support for nested AudioMixers #4915
base: master
Are you sure you want to change the base?
Conversation
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.
Aside from the CI failure:
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 a few things I noticed from the diff of new changes.
@@ -96,9 +79,13 @@ protected void Remove(IAudioChannel channel, bool moveToParent) | |||
|
|||
#region IAudioChannel | |||
|
|||
public AudioMixer? Mixer { get; } | |||
public virtual AudioMixer? Mixer { get; set; } |
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 can see that this naming is used to match the IAudioChannel
interface, but mixer.Mixer = parent
reads pretty weird.
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.
Do you mean the part where it's named Mixer
? If so, I tend to agree but not sure of a better name... OutputTarget
maybe? but then if it's of type AudioMixer
, that's also weird, so...
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. Not sure on a solution yet.
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.
How about calling it Parent
/ParentMixer
and explicitly implement IAudioChannel.Mixer
to it:
public AudioMixer? Parent { get; set; }
AudioMixer? IAudioChannel.Mixer => Parent;
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 was going to suggest that but for some reason I thought it wouldn't work. I think it's an amicable solution.
…for MacOS 'popping' issue that is known to affect some hardware models when outputting at 32-bit
This functionality is a pre-requisite for applying processing to groupings of audio channels in Lazer, and affords the ability to chain mixers with different processing/effects.
Utilising this capability, a
GlobalMixer
has been added (whichTrackMixer
andSampleMixer
are now routed into). This will allow for monitoring of the final summed audio output and for any final audio processing to happen just prior to output.