scook Posted May 7, 2019 Share Posted May 7, 2019 VeeSeeVST Rack, a free port of VCV Rack 0.6.1 to the VST2 format compiled to run as both an instrument and effect now works in CbB. It contains quite a few of the free modules written for VCV rack. The patch files are compatible with VCV rack. It a good way to test out this modular synth inside CbB. At least until the VCV v2.0 VST is released. To run in CbB currently it takes two downloads The latest version of the VeeSeeVST Rack package https://github.com/bsp2/releases/raw/master/vsvr/veeseevstrack_0_6_1_win64_bin-05May2019.7z and a hotfix for the dlls https://github.com/bsp2/releases/raw/master/vsvr/veeseevstrack_0_6_1_win64_bin-05May2019_cakewalk_hotfix-06May2019.7z After uncompressing the first file into the VST scan path. Overwrite the two dils by copying the contents of the second file into the vst2_bin folder. Update: the hotfix was rolled into the regular release https://github.com/bsp2/releases/raw/master/vsvr/veeseevstrack_0_6_1_win64_bin-07May2019.7z Update 2: another release today (bug fix for Frozen Wasteland BPM LFO) https://github.com/bsp2/releases/raw/master/vsvr/veeseevstrack_0_6_1_win64_bin-07May2019b.7z Update3: fixed problem with Fundamental LFO-1 and more modules added. https://github.com/bsp2/releases/raw/master/vsvr/veeseevstrack_0_6_1_win64_bin-19May2019.7z. I will probably not update this post with newer version. Check out the kvr thread or github for the most current release. The main thread for this software is https://www.kvraudio.com/forum/viewtopic.php?f=23&t=507216 Link to comment Share on other sites More sharing options...
scook Posted May 7, 2019 Author Share Posted May 7, 2019 CbB hotfix added to the regular release Link updated in OP Link to comment Share on other sites More sharing options...
Xoo Posted May 7, 2019 Share Posted May 7, 2019 Not here it doesn't work - VST scan hangs for ages on the _effect dll and never seems to complete its scan. Link to comment Share on other sites More sharing options...
scook Posted May 7, 2019 Author Share Posted May 7, 2019 It sounds like the problem another user reported on p39 of the KVR thread - the dlls were too many levels deep in the scan path. I placed the vst2_bin folder immediately under C:\Programs Files\Cakewalk\Vstplugins (although I renamed vst2_bin) Link to comment Share on other sites More sharing options...
Xoo Posted May 7, 2019 Share Posted May 7, 2019 That's what I used too (and I too renamed vst2_bin). I'll try on my other PC sometime tomorrow. Link to comment Share on other sites More sharing options...
shawker Posted May 8, 2019 Share Posted May 8, 2019 I just put vst2_bin as scook did and it worked great (didn't rename it). I inserted the instrument, loaded up a patch I did with VCVRack, and it actually recorded the audio without needing to route it to an aux track. Link to comment Share on other sites More sharing options...
Xoo Posted May 8, 2019 Share Posted May 8, 2019 (edited) I can get it working if in C:\VeeSeeVST but nowhere deeper so far (on 2 machines). Crashes VSTScan hard on my DAW, simply doesn't get scanned properly on my work machine. UPDATE: Confirmed on my DAW that any folder below C:\ (or, I assume, another root) crashes the VSTScan. C:\VeeSeeVST and it works fine. That inspires me with little confidence in the quality of the software, which is a pity as it's *FUN*. Edited May 8, 2019 by Kevin Perry Link to comment Share on other sites More sharing options...
scook Posted May 19, 2019 Author Share Posted May 19, 2019 The dev seems pretty responsive. I found a problem yesterday and posted about it on the KVR thread, Today the dev fixed the issue and posted links to new releases. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now