Mhm, no i did not. And I will immediately sir.
As I recall though, I have had the ADSR active in previous patches without gate.
Mhm, no i did not. And I will immediately sir.
As I recall though, I have had the ADSR active in previous patches without gate.
to the maximum also? What is LEVEL? I can not understand from the manual what level feedback and depth are.
Level is volume when set to 0 it is off. when set to max with the env on it will follow the ADSR. Feedback is the amount of self-feedback and Depth is the amount of FM.
I should have done more research on envelopes yesterday before posting. I will try better next time. Thank you for the buoy
What I have been thinking about is, the XOR creates an extra trigger when it recieves a trigger from OHM and clock simultainiously, but as I can understand according to the table
two triggers should lead to not trigger âŚ
It probably has to do with the sample delay between modules, the clock is going directly to the XOR but the Ohm is delayed by one sample and arrives late. Try to delay the direct clock with a module f.i. sum by ML.
Or Venom Thru
Hi @Hirretr808 have you tried this module:
Its super useful for clock divisions and Xor gates.
If you use more modules, every cable adds 1 sample delay as @Yeager said.
Or there might be situations where you want to be explicit that youâre accounting for sample delays, or need to handle multiple delays. Just remember that by inserting them youâre already adding a delay because of the added cables.
I still wish there was a way to calculate sample delay, I hate counting cables
Thatâs why the Bacon one is handy, itâs easy to adjust when you find you canât count, or if you change the patch
Like Inception when there is a dream within a dream.
Thanks for that tip. It is really handy!
The further left you drag on the red number the faster it scrolls, drag on the rightmost digit for tiniest adjustments. Works well once used to it.