A ambient performance that mostly consists of sampling and layering the output of Gibber on top of itself repeatedly.

This is a recreation of a performance I did at a bar last week in downtown Santa Barbara. It uses the Gibber monosynth a bunch and has some granulation at the end. It also has a few mistakes, most notably at the start of the trumpet part.

What was especially nice about this performance (as opposed to previous ones) is that I didn’t have to worry about CPU usage at all, thanks to the new custom-written audio backend for Gibber. Even with screen capture software running (which takes quite a bit of CPU) there weren’t any glitches.

Here is my latest performance recording; the new Gibber default script is based on tweaks to this performance. It makes extensive use of Karplus-Strong and lots of flanging. It also shows the new verbose constructor syntax for objects, where you can pass any parameter to the constructor by name. There’s still a few objects I have to implement this for…

I’m feeling reasonably confident that this is how the Gibber syntax is going to look, and thus, getting closer to removing the “Beta” label and publicizing Gibber. Please let me know if you have feeedback!

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…

This post starts my official announcement of Gibber, a new browser-based, live coding platform. My goal for Gibber is to create a super simple syntax for musical live coding performances that can also be an educational tool. I think there are some pretty interesting selling points for a browser-based implementation, such as automatic updates and easy networking. The browser provides a lot of affordances and I’m looking forward to exploring interactivity in the context of live coding.

Here’s a screenshot, primarily to provide a small amount of color to this blog entry. Please try out Gibber and be in touch in the forum!