Connecting `VCO-1` `TRI` to `CAPTRUE` crashes Rack

[dschiller]

Repro

• Load VCO-1
• Load Tiny Tricks Wavetable Oscillator 1.5.0
• Connect VCO-1 TRI to CAPTURE
• Change VCO-1 FREQ

  Actual

• Crashes Rack 1.1.6

  Expected

• FREQ can be changed

log.txt

[thomassidor]

Hi @dschiller

I've just tried to recreate the issue, but without success.

Just to understand correctly: Are you taking the TRI output and patching it to the capture input right below the button (see attached screenshot) ? This trigger input is for triggering the caputre of a new wavetable - but to capture a proper wavetable something needs to be connected to the wave inputs as well.

So with this patch you're creating a new wavetable at audio rate. Might be what you are going for, just wanted to point that out.

So I can debug a bit further I'd like some more details:

• The sample rate you've set VCV Rack to
• The thread priority it's set to (both are in the Engine menu in VCV Rack)
• Also operating system and exact version
• Hardware specs of your system

[dschiller]

Hey Thomas,

thanks for your comment. I updated the repro steps.

Repro

• Load VCO-1
• Load Tiny Tricks Wavetable Oscillator 1.5.0
• Connect VCO-1 TRI to CAPTURE
• Change VCO-1 FREQ
• Connect VCO-1 SAW to INPUT

Actual

• Crashes Rack 1.1.6

Expected

• FREQ can be changed / Input can get connected
• Sometimes it crashes on changing FREQ and sometimes it crashes while connecting to INPUT

Debug Details

• Sample rates engine is at 192 kHz
• Threads at 2
• macOS Catalina 10.15.7 / Windows 10
• Mac: 2 GHz Quad Core i5, 16GB 3733 MHz LPDDR4X, SSD 500GB
• Windows: 2.7 GHz Quad Core i7, 32GB DDR4, SSD 4TB

[thomassidor]

Hi Dirk

Thanks for the update. I was able to recreate it with the increased sample rate (the default in VCV is 44.1k).

Will have to reestablish the build environment on my computer before I can work on a fix.

A temporary workaround is to reduce the sample rate. I could get it to work with 48k at max though.

All the best, Thomas