That explains why I couldn’t get scenes to work. Figured I was missing something. Even when the modules are not complete they’re still great.
Another update.
It’s over two months now and I haven’t heard anything from VCV support. You can be sure I have a pretty solid opinion about that, but this been a public forum I will keep it to myself.
In the meantime I’m considering dropping support for the VST for all mapping modules (MIDI-CAT, CV-MAP, microMAP etc.), meaning these modules won’t be available in the VST. But I haven’t decided yet.
9 Likes
NOOOOOOOOOOOOO!!!
Ok I am going to SPAM them now every day. We need your modules.
I dropped them an email at support. Not sure if we all do that, it will help the process, but at least we can show them the support for your modules is huge.
4 Likes
It’s really sad to hear that.
Really sorry to hear that Ben.
Please don’t drop support for the mapping modules, instead do push the update to the library, maybe that might make it more of an issue for VCV to speed up support for the plugin?
I too will send en email to support, for what it’s worth.
edit: (sent)
2 Likes
Likewise. Considering the magic Stoermelder has bought to VCV the lack of support is very disappointing.
4 Likes
@pgatt you guys need to sort this out pronto, Ben’s modules are insanely useful and losing them over VCV’s red tape would be a crime.
Shame hearing this. The way the Frequency Domain v2 submission was handled by the VCV staff (at least four weeks of total silence, even when the developer tried to contact them multiple times just to hear something from them) was so bad I thought it was an outlier; and now, it’s not very nice hearing that this is the usual way things go, Stoermelder waiting for two months to hear anything back. Ghosting this much on the developers who provide this environment with the most interesting and inspiring modules is obviously a bad idea in the long run.
1 Like
@Vortico can you help here?
Ben, imho it would be a great loss if your modules aren’t available in the VST
For my part, i’m currently switching back to V1 of VCV because i simply cannot compose / arrange without using Stoermelder modules wich are an integrated part of my setup. I really hope support will sort it out soon.
1 Like
No need, development builds are available and work fine here in 2.0.6 standalone (at least the ones I habitually use do). The main problems manifest when rack (pro) is run as a VST.
3 Likes
This is Andrew’s response to me begging on my knees to help out Ben haha.
@stoermelder see below, are you waiting on a follow up? Or no response to the VST questions you have?
Thank you for letting us know! We responded to Benjamin’s ticket on January 3, 15 hours after his support request on January 2. We have a responsive support team and are available most days to answer user, customer, developer questions and requests. Let me know if you need anything else or have any other questions.
Andrew Belt
Thanks but i already downloaded this release.
I’m using 8face and transit modules for snapshots in the standalone version but as soon as i try to reload my patches (with this modules connected to my DAW via the MIDI CC > CV) i systematically get a crash seemingly related to the Stoermelder plugins. Knowing that they’re not still present in the library, i supposed it was related to issues that support haven’t fixed yet.
That said, i would be glad and gratefull if someone knowing this problem had eventually found a solution.
I got the same clarrification in mail just now, so maybe something got lost in communication between support and @stoermelder Ben? But at least it is now getting more attention, could you try again Ben?
That’s exactly what Ben was saying. Help with the VST. I do have it running in VST as well, but especially the Transit and 8Face modules are the ones that need a VST solution.
That is correct, I got a response on January 3rd:
Hi Ben,
Thanks for the bug report/feature request. We are looking into it and hope we can have a solution for you soon.
Paul Gatt
VCV https://vcvrack.com/
Point is, there’s no advantage to switching back to v1. Stoermelder works fine in v2 standalone, just not in the v2 VST.
But there is no VST at all for v1, so there is nothing to be gained by switching back to it.
2 Likes
Sure i’m aware the problem is not related to the VST version wich i don’t use.
Glad to hear everything is fine with the standalone version but my issue is reproducible and tested on two different computers. I will investigate more and eventually ask for @stoermelder on github.