Gliss Dev Diaries: Record and Waveshape Mode

These videos show the current state of the Gliss firmware and each focus on a specific mode. Please note that we are actively working on the firmware for Gliss with a group of beta testers and everything is subject to change. We welcome any feedback you have.
Help bring Gliss into the world and be one of the first to get this module by backing us on Crowd Supply: www.crowdsupply.com/augmented...

[@kbowman0016]

Hello- I believe you mentioned that there were going to be tutorial videos on this now that it has been released- is there an ETA for them?

[@BelaPlatform]

Hey! Yes, we have recorded all the material are now in the process of editing it together. Hopefully we should be done in a couple of weeks if not before.

[@kbowman0016]

@@BelaPlatform -Thanks for the update! Will they be posted here, or is there another channel I should be following?

[@stephenspackman5573]

Excellent! The scrubbable gesture is specifically something I need. Backed! (These things can't daisychain, so that a single “gesture” syncs across multiple devices, can they? Maybe a request for the next hardware version, if not!) In oscillator mode, does the CV input work as a multiplier of the recorded gesture length, or does it track V/oct with the full gesture treated as one cycle? These are both useful.

[@oromoiluig]

In both frequency (i.e.: input is V/oct) and "waveshaper" (i.e.: input is phase) input modes, the gesture is stored in a wavetable (currently 1024 points, could be more). So it's V/oct with the full gesture treated as one cycle. > These things can't daisychain, so that a single “gesture” syncs across multiple devices, can they? Would that be desirable? We are trying to figure out what would be use cases for synchronising across devices. How would you use this in this case?

[@stephenspackman5573]

@@oromoiluig Originally I was thinking in terms of stored gestures with different natural lengths, so that synchronised and unsynchronised playback would mean slightly different things, but that may be a confused idea anyway, since it's probably as easy and more flexible to work two devices with two fingers. If you're _actively_ looking for ideas that would work better with coupled devices, though, a multiwaveshape mode in which you could morph between waveshaper waveforms across four channels of output (using the left Gliss for morph and the right Gliss for phase) might be awesome. Though again, it would probably be adequate to have the input CV perform one of these and have the other be manual, and then it could be purely local. (I'm thinking about scene transition and timbre transition duties, specifically.) I hope I'm not wasting your time; I'm going to keep thinking ;).