2.0.15 release is out this morning. Here are my release notes:
Memory gained access to the file system:
Memory can now load .WAV files into itself, replacing the entire contents of the Memory and resizing it.
Memory can save .WAV files as well.
Since file operations can take a widely varying amount of time, Memory sends out a trigger when those operations complete.
You can load and save files from the menu, or you can use BASICally to send Tipsy text messages to Memory to tell it to load or save a file.
Since surprising things can happen when loading or saving files, instead of silently failing,
when you have the LOG output of Memory cabled to a TEXTn input on a TTY module, you can read the log of what happened on the TTY.
Fade on Move - affects the behavior when the slider or SET moves the position of the head.
If checked (the default), the L&R outputs will be silent until the position stops changing. If not checked, then the playback will continue as it’s being moved.
See example video.
Use Speed as V/Oct - affects how the SPEED is interpreted. When unchecked (the default),
the sum of the SPEED input and control is how many samples the playhead moves forward per sample emitted, so 1 is normal speed, .5 is half-speed. When checked, this sum will be interpreted the way that V/Oct is interpreted in most modules. See example video.
When the sliders on Ruminate and Embellish are released, they now resume normal operation more quickly.
Put a big “T” behind ports only input or output Tispy text messages. Put a less solid “T”
on the BASICally OUTn ports, to suggest that they can emit both Tipsy and regular values.
Can you explain a bit more what you are imagining?
My understanding is that a Clock signal is series of short trigger pulses to the beat. What are you imagining would happen whenever a trigger is seen to the CLOCK input?
Memory, when loading a file, now smooths the ending and beginning to ensure there is
no sudden “click” when looping from beginning to end (or vice versa).
Made the text windows on Fermata, BASICally, and TTY more efficient on the UI thread. This won’t affect the measured performance of these modules, but you may see slightly higher FPS numbers when using these modules.
Added string variables and arrays to BASICally:
A variable name that ends with a “$” (e.g., a$, foo$, mod_name$) can only hold a string
(i.e., a series of printable characters) instead of a number.
An array whose name ends in a “$” (e.g., bar$, names$[3]) can only hold an array of strings.
These changes are only really useful when using print() to send text messages to other modules. See docs for details.
After working on this, I was hoping to take a breather on VCV modules and do other things for while…but then a really compelling idea came to me, and it’s pretty fun. I’ll make videos on the YouTube channel when I have something to show.
@StochasticTelegraph
Venn is out! big thanks for this. very exciting release for live acts.
please please update the manual and publish hotkeys and info for it…
And that promised video is now published, this one about how one might use Venn to generate MIDI and what moving the Point at audio rate does (in this case, make drones).