Gibber 2.0 roadmap


So I’ve gradually been moving towards a new version of Gibber, which I’m hoping to complete over the summer. I thought I’d post a bit about what will be in it, in case there is any early feedback, and kick off this new forum category that Alex kindly setup.

  1. A brand new audio engine. The main benefit is that it will run in a separate thread from other browser processes, making it easier to do audiovisual projects without stutters. But there are also nicer “virtual analog” filters (which make a huge difference in the sound quality) and other goodies. You can play a bit with it here.

  2. A brand new graphics engine. I wanted to do something that was different from other systems out there and encouraged different types of experimentation, and built a raymarching engine for this purpose. Although the end-user API will be much simpler when it’s integrated into Gibber, you can play with the underlying library as it currently stands here.

  3. Thanks to #1, code annotations / visualizations will be enabled by default. In prior versions of Gibber, you had to explicitly enable these; now that the audio runs in a separate thread I feel comfortable turning them on by default.

  4. Gibberwocky will be merged into Gibber. I hope to also make a Pd integration (in addition to existing Max / Live integrations). You’ll be able to sequence web audio / graphics / Live / Max / Pd / MIDI simultaneously using a single API with your choice of clocks.

  5. Use of Tidal mini-language for sequencing (in addition to the existing options). This is a bit dependent on a student finishing some work I started a while back but ideally you’ll be able to do things like:

    syn = Synth('acidBass')
    syn.note.tidal( '0 [2 [3 4]] 5(3,8)' )
    syn.cutoff.tidal( '[.1 .2 .5] .75' )
  1. Atom integration… and hopefully completing this will make it easier to integrate into other editors like VSCode.

There’s lots of other elements that I’m not listing, but if there’s something missing from the above list you think is critical to add please let me know! I’ll try to get alpha / beta versions up sooner rather than later; the last four or five performances I’ve given have been using an alpha version… just need to document some things first.



These Gibber 2.0 ideas sound very exciting: I look forward to trying this out when it’s all ready.

1 Like

Good l#rd you’re busy.

1 Like

I just have to drop by and say that Gibber 2.0 looks utterly amazing and I can’t wait to use it!

1 Like

You mean there’s going to be gibber in Atom? Looking forward to It!

For those who avoid social media, I’m still working on #4 (waaaaay harder than I thought) and haven’t started on #6 yet, but, lots of progress otherwise!