Friday, January 22, 2016

Slightly More Gibberish

Among the various technical obstacles that I personally have encountered in Gibber is the lack of ability to publish my code to the server or retrieve other users' code via the search functionality on my computer. Nonetheless, I wanted to allow anyone who was interested the chance to explore, tweak, completely tear apart and reconstruct, or otherwise act on creative impulse with the Gibber code that I presented in class the other day. Note that this is a very small example--and not nearly as well documented--compared to the tutorials offered on the Gibber website.

Clock.bpm = 140

//Sub-bass
b = FM({index:15, cmRatio:1.0333})
 .note.seq( ['c1', ,'c1', ], [1/4,1/8,1/4,3/8])
 .fx.add( LPF(0.2) )
  .amp(0.5)
b2 = Synth({waveform:'Sine'})
 .note.seq( ['c2', ,'c2', ], [1/4,1/8,1/4,3/8])
 .fx.add( LPF(0.5) )
  .amp(0.9)

//Drums
d = XOX('xxxx')

e = XOX('..o.....', 1/4)
  .fx.add( Reverb(1) )
  .fx.add( Crush(10, 0.8))

c = XOX('**..*..*..*.**.*').fx.add( Delay(3/16) )
  .fx.add( Reverb(0.8) )

s = XOX('oo....oo........oo..oooo........', 1/16).amp(0.3)

a = Synth({ attack:ms(1000), maxVoices:4 })
 .chord.seq( ['c4min7'], 1 )
 .fx.add( LPF(0.4) )

a._


I also wanted to extend the offer of assisting anyone who is interested with installing Gibber locally on his/her computer. The process requires a small amount of knowledge on Git, command line, and node.js and allows you to use your computer's processor to run Gibber rather than limiting yourself to the processing bandwidth of your internet connection. For more computationally intensive tasks in Gibber--chordal synths, graphics, etc.--this is a must.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.