The love and care you put into all your modules is obvious. The old visuals certainly were gorgeous, and I am sure you had to think long and hard before you abandoned all that meticulous design work for something simpler and easier to maintain. That must have been a very difficult decision to sacrifice your previous artwork. With your consistent attention to detail, I implicitly trust you made the best decision for you, and thus the best for the collection long term.
6 Likes
this sounds great. onward and upward
Bret Your modules are nice from the first moment in version 1. The theme is uncertainty, everything moves faster than we can assimilate these days…it happens to me with the modules that are a full state of being what they are; I don’t touch modules if I don’t like their interface, fortunately the best ones have that translation of being visually full and close to eurorack or something that starts from a piece of hardware and it is disconcerting to see that sometimes the change does not translate into preserving that state of fullness. The graphical textures of the modules resembling patina and age are nice and let one believe that one is closer to that analog that inspires the code. I know that for many people it doesn’t matter how a module looks, what matters to them is how it sounds, if it’s in tune, if its aliasing levels are right etc…but VCV is as visual as it is musical and that gravitates. So is that balance between a code that translates well the clone of reality or goes beyond it and also looks like the real thing, for me at least, yes. I know there is an ethic and I understand your reasons against the simplicity of the code in order to have an easy and fluid evolution, it is desirable. As such, the dark mode could be chosen independently of the VCV interface. This would be very desirable. Choice of texture or simple smooth skin. I know it is work on your time and there is no hurry just to let you know an idea. Thanks for your answer and your great work.
Vladimir, thanks so much for your thoughtful response. Let me think about the texture a bit. Perhaps I can find another way to implement it (or something close) that will work on all platforms. 
I know exactly what you mean about using modules who’s design provides the musician with a type of romanticism. I think that the recent synthesizers.com modules do that very effectively.
I’ll see what I can do. 
2 Likes
A totally random note on the Digital Programmer: the context menu still contains the old keyboard info for shifting the sequence with the arrow keys which isn’t functional (now functioning with shift + mouse drag instead). The Digital Programmer XP version has the up to date info for the updated shifting feature
1 Like
Sorry for the late reply. Thanks for the heads up. I’ll try to get this fixed for the next release.
1 Like
Would anyone have a moment to build a mac distribution package from this branch? GitHub - clone45/voxglitch at vectorRotation
It contains a few modules that I’m throwing together for @zakforrest.
Cheers,
Bret
1 Like
Its already on GitHub just add the action to build all platforms?
check thy github for the mac-arm64 build of the vectorRotation branch
1 Like
wrong reply button?
thanks for the help everyone!! 
is it available yet, or still missing a fix?
fractalgee posted it here for you :
1 Like
Thank you everyone! Wow, you all are amazing. Sorry, I do need to fix that github Action. I didn’t set that up and haven’t delved into getting it updated.
2 Likes