I’m starting to play around with the new versions of Spectral Mesh and Auto_Waaave and so far I really like the new stuff, and motion recording is already very usable and is going to open up a ton of possibilities. I’ll post suggestions or potential bugs I encounter in this thread.
For starters, a few things about motion record:
- When motion record is on, the most recent recorded parameter doesn’t take effect until I adjust the next parameter. What this means is that the last parameter adjsuted with motion record on won’t actually have its motion played back.
-motion record on
-record some moves on the rotate fader. As I move it the rotation changes as expected, the recorded motion doesn’t play back.
-now record some moves on the Z displace. As soon as I start changing it, the recorded rotate motion begins to play. The recorded Z displace motion doesn’t play until I adjust another parameter.
-etc. etc. - the last parameter adjusted will never have its motion play back because it is waiting for another parameter to be adjusted.
The way you have it working now, when motion record is toggled off it freezes the parameters at their current value. I think it would be a lot more useful if turning off motion record allowed the recorded parameter changes to keep looping, so that it would be possible to record changes for some parameters, switch motion record off and make static adjustments, and repeat as needed. Static adjustments made to parameters that had motion recorded could act as offets or scaling factors for the recorded motion (both would be pretty interesting, I couldn’t say which would be better without trying them)
Using the existing Nanokontrol preset, the three MARKER buttons (G, H and I) don’t light at all when pressed. I think in general it would be better if they toggled between lit and unlit, but especially now that Spectral Mesh uses G/SET for toggling motion record - not having a visual indicator of whether it’s on or not is awkward. Easy enough to change myself with the editor, but unless there’s something I’m missing it should probably be part of the standard template.
That’s all so far, over all it all works really well and seems as stable as the previous versions. I won’t have a chance to mess with audio input in auto_waaave until tomorrow night at the soonest but I’m really excited to see how it interacts with motion record!