All great ideas, but the open ended nature of VCV means sometimes people will be fully engaged with VCV as a developer and sometimes their journey will take them elsewhere and their designs may get left behind. But we have many many engaged designers that keep beautiful stuff working, sometimes you will have to let something fun go that isn’t going to update.
Yes, i understand that changes can be drastically, for bring something inportant new. But (as i understand it) always can be done something like “bridge” in code for backward compatibility. (Incl. enabling optionally, if this will somehow interfere with new engine work). I believe it’s just a matter of desire\time (and coding level of course).
It is up to each developer to keep up their own modules unless they pass them onto other developers.
sum module limiting output voltage would be nice
just put a Rescale module after it
1 Like
Currently, VST3 is still not saving parameters in DAW, whereas VST, Clap, and AU are fine.
1 Like
Arrow-key navigation in preset menus.
1 Like
[quote=“Squinky, post:151, topic:19785”]chopper is an underappreciated module ;-0 [/quote]
“Chopper. For when regular tremolo is too subtle.”
Which is a jokey slogan but it describes how I use it most of the time.
1 Like
Yes this is right too, or even can say, this is optimal (less headaches) situation for VCV dev. And can even say that it is quite bearable for the user too, in the case when paid modules (was) not a much. But when there were already much more premium stuff (including bundles like ALM, with 50$ cost), then in my opinion the situation changes somewhat. It’s about the same as if Reason users lost all their purchased (and free) rack devices in the Reason shop every time a new version of the program was released. With waiting for each of dev’s to rewrite code. In my opinion, this would reduce the desire not only to buy modules, but also for developers to make them.
It’s a great stance, but VCV has succeeded because it doesn’t force any developer into any action they are uninterested in or blocks them from designing a unique game changer module either. The pressure is all from the desire to create in this space, and the money involved for almost every individual designer is honestly very little compensation for the outlay in time and skill set. This “come and play at your leisure” is part of the appeal, people come and people go and modules fall in and out of favor over stretches of time. Being in contact with designers thru this community and the discord and even making a GitHub account to make bug reports and feature requests is the best way to connect and get a feeling for the designer’s long term plans.
It is a great community that is constantly expanding and growing on user and developer side. The longer you hang the more it grows on you, it is unique among synth software models and gets mad respect in a larger Eurorack community that generally is software averse. VCV will surprise you and delight you and frustrate you, but always engage your creative urge. I wish every collection stayed whole forever but it does not always happen.
10 Likes
I want to clarify that i am Very pleased with what VCV is capable of in its current state, it is really impressed me (actually this is one of the reasons why i stated such concerns above. Whereas if i found VCV to be something ordinary, i would simply pass by).
Additionally, can noted that my wroted above in no way contradicts (nor incompatibility) the mentioned factor of not forcing module developers to do what they do not interesting. Since my appeal is all about hypothetical addition\modification on the host side only.
Well controversial. When there is sure that work will stays afloat \ compatible, it i assume contributes to desire to create further. As well as desire of user to pay for it (including this confidence can contribute to pay more than a little, up to normal compensation).
But of course, I also can allow that by not fully understanding the technical nuances of this undercurrent, and in some sense shifting the problem onto shoulders of host dev, I may be misprioritizing. Ok in any case, it’s without insist, just thoughts on the topic, + judging by reactions (or lack of), seems my idea of “compatibility” exhausted.
so, some new improvement came to mind today. I noticed how my capability to imagine what a new module can be used for (if it’s anymore complex than say a straightforward vcf), is somewhat limited these days. so I figured it would be very welcome and helpful to have the creativity module in one’s brain boosted by 3-10 suggestions for actual use. I think a module designer knows best what his module is capable of, why not share some of his ideas in the manual? I have seen cv funk do this already, which was very nice to see, then I tried hetrik phasor splitter and thought what the heck. how and where is this useful? it’s neat and I see what it does, but where might I use this?
2 Likes
Maybe a dedicated shortcut-key to the “Import selection” menu option.
4 Likes
Second that!
Perhaps sometimes. But as a plugin developer it is extremely satisfying to see creative people come up with use cases you never dreamed of. Thanks @Omri for your many videos!
Yes, I too appreciate seeing interesting use cases in a manual. Some VCV Free modules have a Tips section in the documentation. I thought the older Fundamental manual had more suggested uses, but it was very incomplete, with many modules not documented at all. At least now all the modules are documented, and they generally do a good job explaining concepts, which I very much appreciate.
Documenting use cases is a tremendous amount of work to be placed on top of all the work that goes into making the module, and then documenting all the features. This is especially true when a plugin is developed and documented by a single individual, and released for free. Documenting interesting applications for the features takes a lot of time and energy that is typically in short supply at that stage of development. I often want to do this, but I usually run out of steam. There are a few Venom exceptions where I go the extra mile - Shaped VCA being one example with a use case section in the manual.
4 Likes
Two things:
-
Grids instead of lists for module browser filters, I spend way too much time scrolling the brand list, even on a huge 4K display. Bonus point for adjustable font size.
-
Dark panels for the remaining VCV premium modules that don’t have them yet.
And yes, I’ve asked, over years, which in hindsight was a total waste of time (so far, fingers remain vaguely crossed that this might happen eventually).
1 Like
Here are a couple scope improvements that would be nice:
-
An extra, extra, extra large, super wide version.
-
Zoomable.
-
Variable line thickness.
-
Option for grid lines.
-
Bpm aware. Would be nice to input a clock as well as a trigger. The trigger would still be used for sync but the clock could be used to zoom the width of the display based on beat/bar subdivisions as well as determine the spacing for the grid lines.
BTW why at least not to add scrollbar element for vendor’ list. Seems it will be faster than by mouse wheel.
2 Likes