JonH

Taken a while to get round to (broken Deluge + busy job!) but here's the updated CUG (DRAFT) for Version 3.0

The original idea was to try and capture all button pressing & knob twiddling combos - plus a few other useful bits of info. Not trying to cover all items in the manual.

Am sure a few commands are wrong, no longer valid (have tried to remove and update old ones where possible) or missing. Please drop me a message here or on facebook "Deluge Users" Group with the command reference (eg, WF03) and I'll try and get it fixed up.

I am happy to share source files from draw.io (free web-based tool) if people want them. I'll add another post here once out of draft but URL link below will remain the same I hope.

https://www.dropbox.com/s/lwx9mq6xuh7qcst/Community User Guide 3.0 DRAFT.pdf?dl=0

Taken a while due to other commitments but version 3.0 now out of draft and ready for release. A dozen or so corrections/clarifications since the draft version and a few new items added too for Parameters, FM ratios and more.

https://www.dropbox.com/s/kmajdnvspd1oj1u/Community User Guide 3.0.pdf?dl=0

Hi - yes exactly that. So use line in port on Deluge to receive the audio clock (which is by far the most stable way for PC/DAW to send clock) and then when pressing play on Deluge it waits until the first beat of a bar from audio to send upstream devices midi and CV/Gate start/clock. Note, at moment when Deluge is midi clock slave, the Deluge does not forward clock signal out of Gate ports (CV port 3) but it does send a Run signal (CV port 4). Not sure why this is, but Ian acknowledged andbsaid would be a good candidate to fix in open source dev if possible.