Runs in the browser (well, Chrome and Opera) and should talk with any MIDI hardware or DAWs; no plugins or closed-source software required. Please let me know if you have a chance to try it out! - Charlie
I was about to post a plea for help when I got things working. (Take-away: a quick video demonstrating setup would be super handy.) Anyway, I have some exploring to do but will chime in when I get somewhere.
Hmmm… if you’re talking about the calls to Gibber.log() in the Patterns tutorial, those print to the console in the browser (make sure you’ve got the console open in the gibberwocky sidebar). But it’s a great idea to have them print in the Max console as well, as the gibberwocky console is often not open… I’ll have to look into that. - Charlie
i’m so excited about Gibberwocky in Max/M4L! all the videos are very engaging and i’m glad the response has been so warm on the c74 site. q: is there a way to trigger the M4L version at quantizations smaller than 1 bar?
Ah yes that wasn’t a very clear question, though an excellent response! I just meant that it seems the M4L device is tied to run sequences on the 1, rather than being able to trigger a sequence on the 2, 3 or 4th beat of a bar.
e.g. if i execute a line of 1/512 notes, the sequencer seems to wait for the transport to hit beat 1 before playing the sequence. i was wondering if there was a way to tighten this so that i could change and trigger the code halfway through a bar, rather than wait for the 1 of the new bar.
I was having trouble with the first section of Tutorial 1: Basic Messaging. In particular, this section says it should appear on the Max console:
// Let's start by sending the following message 'synth1 1'. Connect the left
// most outlet of the gibberwocky object in Max to a print object, and then
// run the following three lines code and look at the console in Max:
synth1 = namespace('synth1')
synth1( 1 )
synth1( 'test' )
The message doesn’t appear on either console for me. I have “Show All Messages” mode on for the Max Console.
The log you mention in the Patterns tutorial works perfectly for me. One note: the Max Console is mentioned specifically in tutorial 1, while in tutorial 4 the Gibber Console is simply called “the console”. Since this is the first time it is introduced in the tutorial, it would be helpful to distinguish the two more clearly for new users. I kept checking the Max Console in tutorial 4 before realizing that the Gibber Console existed.
Hmmm… that’s really strange. That should definitely work without any problems! And the other note / sequencing stuff is OK? You get the “gibberwocky is ready to burble.” message in the gibberwocky console? Are there any errors in the browser’s developer console?
Agreed about the need to differentiate “console” in the Patterns tutorial. And I still think it would be cool to just print to both consoles for any call to Gibber.log()…
Anyways, let me know if you learn anything else about this bug, I can’t figure out how this could be happening if other gibberwocky features work.