I’ve made some small syntax changes over the past few days. More importantly, I’ve dramatically cut down the CPU Gibber uses by implementing a much smarter sequencing algorithm. After viewing the original Gibber performance, which maxes out the CPU at the end, I decided to take another go at a performance using some of the same ideas but trying to make things move a little quicker.

I also performed a variation of this at a composition forum today at UCSB… the first Gibber public performance.

Here’s my first stab at a Gibber performance. There is a lot of low-frequency content that will not be heard on laptop speakers…