![]() ![]() A “powered” mixer becoming a unity mixer might be a little surprising, but on the other hand I’m not sure there’s a better bypass behavior for a mixer (since muting or picking a single input to pass on would be surprising as well). I’m guessing that processBypass() might not get overridden very often, but it’s very good (and very Rack-like) that it’s there. IDK if there are a ton of obvious use cases but I could imagine modules wanting to keep sync, consume control inputs, participate in expander relationships, etc. ![]() I assume that bypass conventions will be specified in the V2 API docs and may evolve from there. I think it means that a bypassed module can do anything it wants (including calling its own process() and thereby refusing to bypass). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |