Hello,
There is 2 new modules, SYNC3 & OSC3 that look interresting.
Will they be available for VCVRack?
Also a new video, GATESEQ walkthrough:
3 Likes
Yes they will. If you’re able to build from GitHub, early versions can be tested.
6 Likes
You guys are seriously awesome. Thank you so much!
Hello,
OSC3 video tour
https://starling.space/via/osc3/documentation
SYNC3 video tour
https://starling.space/via/sync3/documentation
Details of patches in the video description.
8 Likes
Really nice demos! Wish more manufacturers would do them like this.
1 Like
After a build hiccup that’s been fixed, the modules have been updated for Rack2. Along with that there’s an update for the v1 branch.
Github build only atm.
6 Likes
Trying to build the v2 branch…
fatal error: ‘atsr.hpp’ file not found
yup, just hit the exact same error, win10
CD into your local repo, do the following git log command, you should see this:
$ git log -1
commit 4eb8f2e902c16a6a9f8ba25031126eb541cff56c (HEAD -> v2, origin/v2)
Author: liquidcitymotors <liquidcitymotors@gmail.com>
Date: Tue Sep 28 19:10:49 2021 -0500
update submodule
If you don’t see HEAD -> v2 then you need to git checkout v2
Make sure the Via submodule is up to date:
$ cd Via && git log -1
commit 10a078083d8c37bac76a2794db51788947d84de9 (HEAD -> master, origin/master, origin/HEAD)
Author: liquidcitymotors <liquidcitymotors@gmail.com>
Date: Tue Sep 28 19:01:11 2021 -0500
update sync3 scale methods for rack
Look in Via\modules\inc [don’t CD there]
What files are there? If you don’t see that header file try git pull --ff-only
Then try a complete rebuild, CD back up a level to \Via-for-Rack first.
make clean
make -j4 dist
1 Like
Hmm, via is completely empty, that explains things and the ‘’‘git pull --ff-only’’’ didn’t fill it albeit updating some stuff. Still empty. That was after a new clone, switch branch to v2, then pull the header files, so no joy here. Alas, it is early days…
Sounds like you haven’t done git submodule update --init --recursive in the repo folder to download the submodule.
If you have a folder named Via in your local repo, delete it and try the above command.
this was my error too. doing that and everything was fine.
urhm, somehow it seems to want a public key that does not exist. Not sure why, I didn’t set anything from default and all other repos so far updated submodules just fine… That would explain the empty folder ideed, now how to tell it to forget that key and retry?
Cloning into '/home/Georg/Rack/plugins/Via-for-Rack/Via'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Never seen that before. I would start over with a clean repo. Follow the steps I gave in the posts above.
seems some github gremlins today as @flyingLow also hit this today, so I shall retry tomorrow to see if that works again. Too many weirs things with cloning from github today for my taste, but thanks for the willingness to help. Appreciated!
Sadly still same public key error, so no dice. And cannot find online how to make git forget whatever public key it’s using that doesn’t work anyhow…
here the same issue, on Win 10, it doesn’t build properly.
I tried all steps mentioned above.
also here on Linux
also here on Mac.