|
Hi Fredrik
Hm, I still think we need a AudienceBoredomLimiter.
I love that you call this synth your ugly beast, as opposed to for instance these... (which are evidently elegant)
I swear I hear some Miles Davis influence sneaking (back?) into your music. Ok, this may be far fetched, but tell me if I am wrong. If I'm right it's sort of nice that a trumpet player makes a trumpet free Miles Davis tribute.
Keep up the good work! (Better tired, drunk and going somewhere than the opposite!)
Greetings from Copenhagen Martin
Den 01/05/2009 kl. 10.55 skrev Fredrik Olofsson: hi peter, i believe in learn by doing. after a few amp= 100 during my sc years, i don't have such a big problem with crazy amplitudes anymore. i've just learned to avoid them.
other things best learnt the hard way... to not code infinite loops to not blow up filters to not bore the audience
and i don't see other [automatic/better/safer] ways around these problems than just practice practice practice. _f
1 maj 2009 kl. 10.11 skrev Peter O'Doherty: There's a lot of interesting material here. I'm looking forward to studying it in my own livecoding practice. On a slight tangent, I was wondering what safeguards you and other livecoders use to avoid nasty, potentially ear-splitting sounds when livecoding. This also occurred to me when watching Marije's Greyhound video especially considering the fact she was using headphones. I realise that, for some, part of the aesthetic of livecoding is the potential to crash the system and everything that that might entail sonically, but accidentally setting a mul of 100 when you meant 00.1, for example, when wearing headphones simply isn't amusing! (Without headphones it can also be something of a shock for other passengers too!) Frederik, I don't see any limiters in your "pact" code or other controls for keeping the amplitude within a certain level. Do you have any strategies for managing this? Of course this doesn't apply only to livecoding. How do people generally deal with this when writing code? Regards, Peter Thank you! There's a lot to study here, and so far (day 3) I like what I'm hearing. For me it's easier to handle them in one big plaintext file, and I've attached it if anyone's interested.
Congratulations on sticking to your pact; I'll check out your counterpart's work next! I'd be interested to hear about self-imposed limits anyone else uses to boost productivity -- I fully understand the feeling of having so many options available in sc that it's easy to get sidetracked.
micromoog
On Thu, Apr 30, 2009 at 1:05 PM, Fredrik Olofsson <f@xxxxxxxxxxxxxxxxxxx <mailto:f@xxxxxxxxxxxxxxxxxxx>> wrote:
dear all,
for april i did 1hour-per-day coding practice. the results can be
found here...
http://www.fredrikolofsson.com/f0blog/?q=node/357
to run the code you'll need to first send the redMond synthdef to
the server.
sorry for music quality - varies a lot and most pieces are
quite embarrassing. but they are all coded from scratch during
the 1h time limit, and i restrain myself to silly restrictions: to
only use one [albeit massive] synthdef, patterns+pdefs, and no
randomness allowed. another excuse is that i often was tired,
drunk or on the train going somewhere.
i don't know how you others get things done, but for me these
restrictions really helps. as well as getting faster at coding by
rewriting the same structures over and over, it does produce a lot
of music material that could be the foundation for a few real tracks.
comments welcome.
_f
#|
fredrikolofsson.com klippav.org musicalfieldsforever.com |#
|