search

ValleyAudio / ValleyRackFree

Modules for VCV Rack
Other
176 stars 24 forks source link

Bug: Interzone output constant -10V #88

Open rsmus7 opened 1 year ago

rsmus7 commented 1 year ago

I've made a patch with interzone, that played fine, now when I reload the patch it overdrive the channel input of mixmaster to infinite, tho it shows -10V on the output of interzone. when I stop the clock interzone still puts out -10V. Tho the gate is stoped (low). I would say there is a bug in interzone. I can provide the patch if that would help.

ValleyAudio commented 1 year ago

@rsmus7 Can you send me a very basic patch that reliably reproduces this bug, and the technical specs (Platform, OS, and Rack version) of your setup please?

ValleyAudio commented 1 year ago

@rsmus7 Can you send me a very basic patch that reliably reproduces this bug, and the technical specs (Platform, OS, and Rack version) of your setup please?

rsmus7 commented 1 year ago

Hi Dale I tried to make a very small patch, only with Valley and Fundamental modules, when I load this patch interzone either immediately outputs -10V or waits maybe 30 seconds to break the output. You can compare it to the WT VCO on the second channel of the mixer, just to show, that interzone is working and the sound driver too.

I'm on Win11 on a HP laptop with Ryzen 5 4600h cpu and Nvidia 1650 GTX gpu, with the latest VCV Pro 2.2.3 version, using the FL Studio ASIO driver.

(I needed to zip the patch to upload it) 2023_02_22_interzone_bug_01.zip

jonnners commented 3 months ago

Wondering if this went anywhere. I've got the same problem.

I can add additional info, that the individual VCO outputs all work fine, as does the output from the mixer. The filter output, however, puts out nanV, and the VCA output is -10V.

In my case, Win10 on Intel i7-580, 16GB RAM. NVIDIA 1030, ASIO driver for Yamaha Steinberg UR22 (I've tried other drivers, WASAPI etc, no difference). Rack 2.4.1

Completely repeatable with a minimum patch.

image

ValleyAudio commented 2 months ago

Hi @jonnners, does this issue go away if you move any of the controls in the Filter section? If so, which ones?

This type of issue is usually caused by a "divide by 0" situation, which may be occurring in my code. I did try to trace it at the time it was first brought to my attention, but I was having no luck reproducing this issue.

Also, does this happen randomly or consistently, like every time you insert Interzone?

jonnners commented 2 months ago

Hi @ValleyAudio /Dale, I've been a way a few days and just seen this. I'll have a play around and get back to you with what I find. Love a bit of diagnostic testing!

jonnners commented 2 months ago

Hi @ValleyAudio /Dale, OK, got a little for you to go on. 1) With a clean set up, I can load Interzone and play a sequence through it fine. I can alter the Mixer, the VCA Envelope etc. As you pointed out, the issue is the filter. If I don't touch it, it works fine. 2) I can increase the V/Oct filter modulation, no problem. 3) I increased the LFO modulation about 40% and it overloaded (NaNV - and whenever it does this I have to reload a clean Interzone, nothing recovers it) 4) I can increase just the Envelope modulation and it's fine, but when I switch it to the inverted envelope and set a sharp delay, it pops out again (NaNV) 4) Lowering the Cutoff Frequency drops it out. Resonance variation is fine. HPF Cutoff is fine.

Hope this helps.

bl-nero commented 1 month ago

I came here looking for "nanV"; I have a similar problem, but with Dexter: almost every time I try to use it, after a certain dose of knob fiddling, it enters a state where there's a NaN value on the output — and nothing helps, short of reverting to the saved state.

I will file a separate issue for this if I find some more concrete reproduction steps.