[POLL] which improvements would you like to see most in vcv?

Thanks Dave! also a possibility is to exchange between concerned modules via a (proprietary) protocol (based on 1ms pulses, for example, or by high-precision voltages to instruct other module, possible by VCV Rack, but not by real Eurorack hardware).

Excellent! :heart:

As I explain just above (by pulses, or by precise voltage, or both)… kind of communication protocol.

I’ve implemented (in FroeZe sequencer) the -10V as output for certain cases (then I’m using a “Polarity Switch” module - as free Open Source (Ohmer plugin) to route the +10V or -10V (inverted to +10) to different modules!

If the modules are within the same plugin, you have full code access between all of them. The “cables” could merely be a way to define who talks to whom.

I was assuming that such a direct access mechanism is what the Venom Bay modules use to teleport signals across your rack.

1 Like

Yes, you’re right!:+1:

Yes, exactly. I just feel like it would be good to have a graphical way of establishing and visualizing connections. Something more permanent than simply touching two modules together.

I have never tried this, but there must be way to trace cables to their other end and get a base class pointer for the connected module. If so, you could simply have a “Link” port on your modules and use normal Rack cables to establish connections between modules. Then you cast the pointer to your internal module class with dynamic casts and can access the modules directly.

1 Like

Yes, I actually do such tracing with the Venom Bypass module already. And I envision something similar with remote expanders.

I’ve done it both ways. But on Windows at least there’s a decent Broadcast Wave program called WaveAgent you can use to split the Broadcast Wav files that the Nysthi recorders generate.

I would really like the window opened by Host to not be on top of everything, even outside VCV Rack. It would also be nice if it always opened where you last saved it.

1 Like

I would like to see a VCV clone of industrial electronics’ Piston Honda oscillator. Hertz Donut and Kermit are also good options too, I don’t know how a Zorlon Cannon could be cloned but it’d make for great triggers and percussion…

More reliable zoom and/or UI scale, in particular when texts are displayed by using nvgText() from draw() / drawLayer() method. Texts may be perfectly centered @ 400% zoom, but looks badly centered when zoom is changed or reduced to default 100%).

Also, some users report large panels may disappear (become transparent) on certain machines (MacBook Pro in particular, Retina, resolution less than 1920x1080) while using important zoom factor + UI scale combo is applied.

Specific reproducible instances of those effects should be reported as bugs to VCV.

1 Like

About zoom + UI scale combo issues (large panels become transparent/hidden) on MacBook Retinas, already sent as bug report (by email to VCV support, but (too) recently).

1 Like

Just to shoot this across the bow again. 3 or 4 custom folders ( renamable) in the module browser. Big workflow benefits, please please.

3 Likes

Could be useful to have a tree view with modules as children of plugins.

3 Likes

I would like to have more polyphony channels. I have no idea if this is possible.

Is 16 a limit from the MIDI standard? I should really know this kind of thing, or at least invest the effort in a rudimentary web search.

Don’t need a web search. “Use the source, Luke” — Yoda

Rack/include/engine/port.hpp:

/** This is inspired by the number of MIDI channels. */
static const int PORT_MAX_CHANNELS = 16;

would Midi 2.0 have a greater channel count

edit: yes 256 channels (16x16)

1 Like

Ha, thanks! But…’inspired by the number of MIDI channels’ or limited by it?

Is there a technical reason why VCV couldn’t use more than the MIDI standard internally?

There isn’t really any technical reason why VCV couldn’t have more polyphony channels. The only thing stopping it from happening is that it would require recompilation of all plugins, as it’d be a massive breaking API change. Maybe better left for Rack 3…

There would likely also be some problems with a lot of plugins specifying the sizes of their internal arrays as 16 directly instead of using rack::engine::PORT_MAX_CHANNELS, so even with recompiling, many plugins would at best not work properly past 16 channels, or in a worse result, cause crashes.

2 Likes

I suppose some modules could possibly break. Many won’t.

Lot of plugins have varying limits that they set themselves. When I search the code of the plugins I happen to have cloned, I saw a variety of limits modules were setting themselves. I don’t recall any of them using the Rack #define. The issue with more channels is the performance cost of computing them, which is why modules limit them.

1 Like