I won’t claim to have watched it all, but I have clicked around and watched several sections. You’ve done a great job here and it must have been a lot of work. Beautifully presented and very clear. Chapeau!
Merci beaucoup, Nik!
Yes, it was, but mostly because I’m new to recording tutorials, and editing in DaVinci…
I hope it helps the community 
how to connect vca rack with studio one in windows
Hi, do you have the pro/vst version?
i have installed the open source version
hello 
You’ll need the VST to run inside studio one. Consider purchasing it because it works really well in Studio One.
i really don’t have money right now to buy this i will buy but right now i am broke
do u have any solution for the opensource .
No, sorry. Before I bought pro, I’d record stems out of VCV rack and import them into Studio One for post processing. But as for Midi input and output, Im not sure. There is Loopmidi, but I have no experience with it.
loopmidi is not working
btw thanks for ur quick response
I’m still kinda new to vcv rack. I keep having an issue where adding a new module will cause existing modules to reposition themselves erratically. Do I need to be holding a key while adding a new module to prevent this from happening? Here’s a video showing what I’m experiencing.
https://www.youtube.com/watch?v=mIASKEP0Hog
Yeager, that worked. I thought I already tried that setting with no change in outcome. I was mistaken. Thanks!
Hello! I have a Rack Pro newbie question for you all.
I just got Pro and am experiencing successive crashes with it when:
-
Running VCV Pro running as a plugin
-
Instantiated within an Ableton Live (12 Suite) set
-
if I attempt one of the following, in which case crashes occur every time:
-
Use DAW-instantiated VCV Pro plugin to open a patch created using VCV Free
-
Use DAW-instantiated VCV Pro plugin to open a patch created using VCV Free but then opened in VCV Pro standalone, and saving the patch again,
-
Or when using “import selection” of designated modules from the same patch as 2) above - the one I opened in Pro standalone, and saved as a selection there. In this case I can see the modules load, and Live then crashes. In the previous 2 scenarios, Live just crashes right away.
-
When I launch the VCV Standalone after one of these crashes, standalone returns an alert that the problem could be with one of the modules, and I suppose that could certainly be the case.
But my patches are not all that complex compared with some I have seen, me being a beginner and all.
Not being able to use my the VCV Free patches I created up til now isn’t really a deal-breaker, I can simply just move on from here since Pro is working fine as long as I don’t ask it to “revive to the past.”
But it would be nice to be have the option to call upon my old patches without making screenshots from the standalone and then slogging thru the swamp of re-building from scratch.
Also, I’m not sure if opening the old patches in the DAW plugin environment is something that in general really ought to work, and that some kind of problem in my system or something I’m doing wrong in general is indicated.
Simply instantiating VCV Pro in Live and building patches “from scratch,” Pro seems to be otherwise stable running as a DAW Plugin in Live 12 Suite.
I have already set up a template of grouped Instrument, MIDI & audio output tracks for Pro instances in Live, and that’s working great. It really saves time over setting up the same basic modules I will use time and time again.
Hope all this isn’t too tedious, and thanks!
Sorry you’re experiencing these issues! Could you contact us at VCV Support so we can look into it? Along with your system information, please include (as attachments) the log.txt files after the crashes and the .vcv or .vcvs files you were trying to open at the time.
Resolved, with many thanks to Eric.
For those who might benefit: conflicting audio output modules appear to have caused the crashes. My existing standalone patches of course had an Audio module in them, while the Ableton Live template into which I was hoping to load my existing patches had another one as well.
It seems that I can use my old patches if I first open them in standalone and delete the audio module there before trying to open the patch in the DAW plugin.
OK!