Events of the form event::MouseButton) have been renamed to MouseButtonEvent, etc. If you’ve started porting your code to the v1 API, you can rename them with
perl -pi -e 's/event::(\w+)/$1Event/g' src/*
Dev builds:
https://vcvrack.com/downloads/Rack-1.dev.3eb0426-lin.zip
https://vcvrack.com/downloads/Rack-1.dev.3eb0426-mac.dmg
https://vcvrack.com/downloads/Rack-1.dev.3eb0426-win.zip
Make sure your Rack user directory is backed up and removed before running dev builds.
Post bug reports on https://github.com/VCVRack/Rack/issues
4 Likes
Dependencies have been updated. As always, to make sure your dependencies are up to date, run
git submodule sync
git submodule update
cd dep
make -j8
To really make sure, run make clean before make, which will rebuild all dependencies (15-60 minutes).
Thanks for the info Andrew.
What about the status of Fundamental plugins about polyphony?
The following plugins still need cleanup, optimization, and polyphony:
- VCO
- VCO2
- VCF
- LFO
- LFO2
- Delay
- ADSR
- Unity
- Scope
- SEQ3
1 Like
Just out of curiosity how is polyphony going to work with Scope? One cable in and 16(?) channels of waves?
N blue (or pink) lines will be drawn.
1 Like
Make sure there is enough space between knobs and ports to put your thumbs between them.
= breath of fresh air, thanks Andrew!
1 Like
I think that even though the platform is open and everyone is free to design modules as they wish, we should collectively strive to have the best layouts and follow the best standards in our modules, such that it reflects positively on any random new user opening Rack for the first time.
A very inspiring example of this was yesterday in the FB group where two people contributed an improved svg for a new module created by someone else.
In the same vein, I can’t help but remember when I saw Deadmau5 streaming his first steps with VCV Rack a while back, and thinking that any un-polished modules that he opened would reflect negatively on his experience. And I am including myself in this, since if I recall correctly, he didn’t get a single note out of my PhraseSeq16, which was quite revealing to me…
4 Likes
Couldn’t agree more best practise coupled with standards would be extremely beneficial for everyone.
Very nice, any suggestions for handling text in the panels?
not much to it, object to path
I was thinking about clarity issues, such as colour, size, fonts, positioning (above/below), avoiding blurring etc.
plus any workflow normals: if you’ve got a lot of labels and want to change them, it’s quite hard if you’ve only got the path - you have to delete and recreate them, remembering position/font/exact size etc.
we’ve all got our own solutions, of course. just wondering if there were any official recommendations for the platform.
Suppose it boils down to your own workflow. Regarding the path I always keep a backup copy of the text before object to path in the .svg until its about to get uploaded.
Just a note that I successfully ported the ESeries E340 VCO to v1 today, just for fun (no distribution). I wanted to learn about what’s going on at the code level in a v1 module, it was a neat learning experience.
1 Like
It would be great it this were in the readme. I’m not a git dummy, but updating sub-modules isn’t something I do that often…
1 Like
Updating dependencies may require different actions depending on the change, so I’ll announce it here each time.
The most general method is to wipe the Rack directory and start over. Particular changes are of course less destructive than that.
1 Like
Added zooming with Ctrl+scroll wheel (Cmd+scroll wheel on Mac). Zooming is very smooth now and is guaranteed not to lag the screen.
19 Likes
Yay! This is really useful.