Hi,
On 05.07.2011, at 10:48, alex wrote:
> What other techniques do live coders try and discard?
I tried out making a gui out of code and modyfying parameters and turning it into code again. It worked, but it's also very limiting. I discarded this idea, which was basically taking a piece of code (usually an array) and make out a button matrix or a bunch of sliders out of the values, then modyfy, and on close of that gui, replace the selected code with the new values. Kinf od like "wannabe FIELD" in SuperCollider. That reminds me I wanted to do a screencast with this idea...
We also tried with midi controllers, I used 8 rotary knobs as step sequencer, and some faders for filters and effect mixing. It was quite nice for reacting to the others in the ensamble (who also used any kind of controllers). But afterwards we saw we spent most of the time on the controllers and not coding that much, thus making the algorithmical development more steady and at some points totally abandoned. There was still a musical developement, trhough the controls, but once we started using them one sticks a little bit to it, in my opinion.
Same thing with prepared code. One you already have a scheme to follow and some sounds already "pre-coded" one might stay with those sounds and those patterns because they sound good, so the further coding is optimizing the precoded stuff instead of trying out new stuff.
Just my opinion, but I will surely keep practising both, blankslate, and with controllers or with prepared code. All setups have different usages and scenarios where they can be really productive, maybe also the code to gui to code approach... I guess I haven't discarded any possibility, but just stick it to the original setup... some snippets and a lot of time.
Cheers,
Juan
Received on Tue Jul 05 2011 - 09:11:19 BST