[Bluemusic-devel] More Mixer Musings
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2006-02-27 23:17:45
|
Hi All, I'm posting this on the dev list as it's more implementation oriented. I am thinking that effects should generate as UDO's, and for the editor you choose number of inputs and outputs (1 or more for each), and those values are going to come in hardcoded ain1, ain2, etc. and output as aout1, aout2, depending on num inputs/outputs set. For coding an effect, you only have to implement the code and not worry about the UDO details. I was beginning to think also that UDO's would have something like: opcode echo ain1, ain2, [list of values set from interface] xin ...code... xout aout1, aout2 endop So that we can reuse UDO's and send in parameters from the interface, but I think it could be a headache and that there won't be *THAT* many effects, and even if there were many, it wouldn't affect parsing too much. I am thinking that all effects though will be given autoassigned names with the original name added as a comment to the output, something like: opcode bMixerEffect0 ; mixer effect: echo ... endop this is to avoid collision of effects names, and may play a part later if we arm parameters for automation. Just thought I'd throw this out there to see if this sounds good or not. I'm going to go ahead with this design when I start working later tonight and can change later if other solutions or issues are presented. Thanks! steven |