Hello, noob to vcvrack (about a year), first time posting here, but not a noob to synthesis or computer music technology. Hello to everyone!
I did try searching the community, asked support (email), however, I am not finding anything even close to helping me decipher why I get this “random” annoying issue loading a patch that should not be happening.
The problem? When loading a patch, I receive an “audio-stutter noise.” A loud burst of ugliness lasting a couple seconds, it is not DC, but it’s a loud nasty sound that generally scares the crap out of me and screams through my monitors or headphones.
Crazy thing is, it doesn’t happen on every patch, nor does this happen on the same one patch.
I save presets, ALL presets, with mixer bus mains muted and sequence / clocks not running. I have use the mindmeld mixer, I’ve used bogaudio mixers along with a few others too, depending on my needs and application. I generally use my default ASIO device drivers, but I also have used JackAudio and ASIO LinkPro. Come to think of it, using Jack and the skJack modules I don’t recall this issue - then again, it sidesteps the vcv audio module.
Which brings me to this thought… What seems to be consistent is I am using the vcv audio-8 vcv audio-16 when I have the problem. I’ve run the LinkPro driver along with using stoermelder ‘s Audio-64, I can’t recall this happening on his module.
To be fair to all, I say I can’t recall, because it only rears it’s ugly head when I forget to turn down the mains on my audio interface before loading a patch.
I should not have to do this. Before I load another patch, I go to my audio interface’s software and lower/mute the level, load the patch, then up levels.
I have other music app configurations on my system that this never happens. I am using the same audio interface and the default asio drivers for that interface. For example: Abelton, Reaper, Max8, audiomulch, Plogue Bidule… I can push my system and squeeze every ounce I can out of it…my buffer size at 256, sampling rate 48khz, I am running sadly in a Windows 10 (64x) environment.
I can be running all the above listed apps in a massive routing midi/audio complexity nightmare, including using my iPad Pro, and it all works well. I make music and I have had no issues. I share this point to give a snapshot, a glimpse how I have my windows 10 laptop running and what it can handle with all of those apps … concurrently running.
I only get this issue running vcvrack as a stand-alone app. I am running the latest v1.16. IF I remember to pull down my audio interface’s mains, obviously it’s not apparent. The clock is not running and I mute the module’s mixer that’s wired/cabled directly to the vcv audio module…
If the mixer is muted, if the clock isn’t starting at startup …
… where is this coming from and why is this allowed to happen? I don’t even know where to look. To me, even if a module is auto-running at start up, but the mixer main bus is muted, it should not allow for a “leak,” nor should, by default I would think at load, the vcv audio out modules burst out this “audio-noise” at startup… if everything behind it in the signal chain is muted, nothing is running(ostensibly) - but yet it bursts out during a load - this is really odd true? - it is not healthy for my nerves nor particular great for my studio monitors.
any ideas where’s this coming from ??
I much appreciate your help and guidance Gary