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).
hi im sorry if theres an obvious answer somewhere that im missing … but im wondering: while using fixation, is it possible to set the playback length to match an incoming gate length??
my thought, while in style1, is to use the same gate source both into “play” and “clock” so when the signal is received at clock it will launch the playhead according to the expected behavior of style1 (indefinitely until next signal received). but since the signal is also present at play, am i correct in thinking that as long as the gate is high at that input playback will proceed, then once that signal ceases it will stop playback?? which is essentially setting the length of playback using that gate’s cycle??
the issue im running into is that the gate for “play” doesnt seem to be working as im expecting … documentation says it will set the state to “play” while a positive gate is active, but it doesnt seem to do that … it also isnt toggling the on/off state. am i misunderstanding this parameter?? or misusing it?
p.s. the documentation for the “play” parameter seems to be unfinished, it looks like it stops in the middle of a sentence!
p.p.s. love love love this memory system btw!!! such a cool unique way to play w samples
edit: ive found a workaround to accomplish what ive outlined above using umap + a gate delay, illustrated in this video:
im still a little confused about what the expected behavior of the PLAY cv jack is, as it seems to not have any influence at all over the button … at least as far as i can tell i could totally b missing something.
either way i love this little trick ive found, being able to dynamically adjust the size of the playback area is really neat & fun i really love this set of modules
What you expected to work (using the same gate signal for CLOCK and PLAY) is what I expected to work as well, but I can now confirm, it does not. And I confirm that, apparently, my attention, uhhh, drifted off while documenting the module.
I’m glad you puzzled out a workaround, but this is a clear logic error in Fixation. It’ll be fixed in the next release.
And since I’m here on this thread, I’ll mention that the next release will also include a new Memory module called Brainwash, allowing one to easily completely replace the Memory contents.
New Memory module, Brainwash, which can be told to record up to 60 seconds of audio
and then replace the contents of Memory when recording is completed.
Fixed bug in Fixation when CLOCK and PLAY input both receive triggers at the same moment. (thanks @idkreina!).
I should mention that Brainwash doesn’t feel complete to me yet, so I’m openly inviting people to make suggestions for how to make it more useful for kinds of music that benefit from it.
Question about Brainwash: how do you get the recorded audio back out of it? I see stereo input jacks but no output jacks. I even read the documentation. It mentions a memory but it’s not clear how to play back the memory contents. Clearly I am missing something!
There’s a separate module called Memory which holds the actual buffer to which you record stuff. Brainwash is an expander to Memory, and there are three others (Ruminate, Embellish and Fixation) which record and/or play back the stuff held in Memory. Also there’s Depict, which shows you a vertical waveform view of the Memory contents (and the positions of the various read/write heads.
Drop in a Memory + a Ruminate or two (the most typical playback head) + Depict (it’s really helpful) and one Brainwash and you’re off to the sound-on-sound looping races.
big thanks for this. very exciting release for live acts.
please please update the manual and publish hotkeys and info for it…
