Considering Pro, A Question: Pro as a DAW Plugin and Project Tempo

VCV Rack
1

Hello!

My apologies for the ignorance that’s inspiring this inquiry.

When Pro runs as a DAW plugin, is it “locked” to the project tempo, or can a clock module that one instantiates in that circumstance provide a separate tempo of its own?

It isn’t clear to me from the manual whether or not the MIDI > CV module creates the connection between a DAW’s project tempo and VCV as running as a plugin (as well as the other kinds of connectivity it offers) or if VCV simply “sees” the host tempo and conforms to it.

My thinking was, well, maybe if you want something kinda free-flowing within your DAW project, you “simply don’t plug it in” (MIDI > CV – CLK, I mean).

Can VCV (Pro, natch) run as a DAW plugin, but not necessarily synced to the project’s definition of time?

Other plugins that I use DO sync to the overall project tempo as a matter of course – indeed, it can be quite tricky if not impossible to free them of that. But it would be great if VCV could function either as a synced element, or in free-’n’-easy fashion based on the need at hand.

Thanks!

2

Nope, it doesn’t automatically lock to DAW tempo, you need to use a clock module like Clocked and use the MIDI-CV module to sync the BPM. So you can choose to run it completely un-synced if that’s what you want to do.

3

If you run it free from DAW Sync keep in mind that it will keep running if you stop transport in your DAW so it will play endlessly unless you do patch the MIDI>CV or a similar module to stop (& reset) your free running LFOs/Clocks or vca mute the signal(s).

4

no, you are the one that connects the DAW tempo into your Rack instance, so you can run a different “free” tempo inside your plugin