Open thomasgeissl opened 8 years ago
Hi Thomas, I think there's no need to. everything has an input and an output. if you happen to connect something to the input of a generator nothing will happen as it wont be using it, and nothing will break or crash. In the case of a more daw like setup it means that a gui or some kind of interfase will be needed, hence subclassing the ofxSoundObject class, and in this new class it could you can add flags to allow to connect to the input or not. I like the extreme simplicity of this class yet how much you can expand over it. Adding more stuff to the base class might be a constraint rather tan a benefit and I would leave to the other programmers the choice to add whatever they might need or like to add. Thanks for your enthusiams! I'd really like to see whatever you are using this addon for. take care!
Hey Roy, sorry for the late response. I forgot to submit. I get your point about simplicity and I also prefer thin base classes than rich base classes. However, in my opinion, it would be cleaner if we differentiate between generators and effects. This garantees a semantically correct dsp chain.
I am doing some tests for a democratic dj session. Angularjs frontend, oF backend. And for other projects, I am trying to get away from max or pd and do everything within oF.
Best Thomas
I wonder if there shouldn't be separate base classes for instruments/generators and effects. Generators are the first element in the dsp chain and do not have inputs. This would reduce semantic programming errors and user errors at run time, if there is dynamic daw-like patching. What was the intention to have only the ofxSoundObject base calss?