thanks! there seem to be still several things i need to work on, but the plugin is definitely getting closer and closer to being finished.
I have mainly been playing wit Turbulence. Self patching it, gating and modulating at audiorates. Using the ADSR env output (and/or the noise or a wave output) to modulate inputs (including V/Oct). Even gating it at audiorates. Minor detail reported, where it intermittently/temporary fell silent at some very short ADSR settings (skipping some external 60 BPM gates). But hey, I guess it was never really meant to be modulated/gated at audiorates.
Also tried to run Cascade at audiorates (Befaco Rampage style), but the envelopes are not fast enough for that. The attack/release minimum duration is 0.01 ms (10ms). Not really an issue. Because as a ‘normal’ modulation source Cascade is pretty versatile.
Anyway…neither crashed or failed to respond.
Win10Pro x64.
1 Like
thanks for sharing and for posting the issue. i replied to your issue because i’m having trouble reproducing it on my own.
I’ll see if I can reproduce it and add the patch to the issue in Github.
Update: I can reproduce it. See .vcv patchfile in issue #6 (Github, NullPath).
1 Like
that patch seems to work fine on my end. could you reply to the issue with the specific build number of the plugin you’re using? i shared a screenshot showing where to find it.
From copy/pasted json: “version”: “2.0.0-bf523fa”,
damn. that’s the same version. i was hoping maybe i was just using a slightly newer version where i’d inadvertently solved the problem, but no such luck 
i still can’t reproduce the issue on my end, but i’ll keep looking into it.
Update: There’s a pattern. 30 times working fine, then skipping 10. Weird. At 120 BPM TRIGGERS from JW Clock.
Just tried and noticed: different patterns at different BPM. So…it’s TRIGGER related. And yes, I use a TRIGGER to GATE input. This suggests it’s some combination of small pulsewidth of the GATE signal and the BPM.
1 Like
thanks for the extra details. will keep trying to figure it out, but it’s definitely harder not being able to even reproduce the issue on my own system.
Further troubleshooting/analysis of this weird phenomenon. Reducing variables. Putting VCV Gates in between to control the pulse width. Stripping all modulation, just triggering the gate, I get skipping with very short pulses to the gate input. It’s a mystery.
thanks again. i don’t want to clog up this thread with bug hunting, so i’ll keep it to the github issue from now on. 
new build available: Release Release 2.0.0-6986405 · alefnull/NullPath · GitHub.
includes some small bug fixes and addresses some inconsistencies between some of the modules’ initial menu settings.
also, a new minor feature added to Entangle: a right click menu to enable “trigger mode”, which turns the ‘mode’, ‘entropy’, and ‘channels’ CV inputs into trigger inputs. by default, in this mode, a trigger to each of the CV inputs will cycle sequentially through their respective options. there is also an included optional “random mode” which does what it says. each trigger will simply randomize the ‘mode’, ‘entropy’, or ‘channels’ parameters.
also also, a really cool change made by @Patheros to the way Entangle displays its connections - try enabling the ‘crossfade’ option in the menu, and increasing the fade duration a bit, then giving the module a clock signal, and watch the magic unfold!
EDIT: does not include a fix for the issue @kwurqx was describing. that will take some time to solve.
1 Like
That would be a good issue to solve with unit tests. clocking and triggering logic can be pretty difficult to test in the final product.
we did manage to discover, just before they went to sleep, that the difference in our environments was sample rate. they were running at 48 Khz, i was running at 96 Khz. when i switched to 48 Khz, i immediately noticed the same issue. so it’s a starting point, at least.
or you could write unit tests.
i heard you the first time, thanks for the advice.
1 Like
oh, sorry. couldn’t tell from your response. good luck!
Ah…great news. Sort of. At least we have a cause. It was getting way to late yesterday to actually test at different samplerates. But I reasoned that this might effect timing and therefore triggering with different pulsewidths.
Update: I’ll check the new build later today (might be solved)
Update: Solved!
2 Likes
new build available: Release Release 2.0.0-c8dfbc7 · alefnull/NullPath · GitHub
includes the following added to Turbulence, based on a user request.
- added CV inputs and attenuators for the 3 individual wave levels, as well as the final mix output level.
- added CV inputs for the ADSR controls.
EDIT: i should note, it was pointed out to me after some changes i made that they will likely break old patches that include Turbulence.
5 Likes
initial manual for Entangle has been added to the repo’s README.