Delay Sync to MIDI Clock


#14

Thanks so much for posting this. Some questions:

1) What is Note 40 doing? From what I can tell it is a manual trigger of the LFO wave. I suppose this would allow you to sequence the note from an external control to have more complex control over the LFO timing?

2) What is Note 39 doing? Again, similar to the LFO, does this allow for manual triggering / sequencing of the delay?

3) How are you controlling clock divisions to control the LFO and delay in relationship to the tempo... for 1/4 notes, 1/8 notes, 1/16 notes, 1/8 triplets, 1/16 triplets, etc?

4) Any chance you might share the file to get someone started?

Thanks!


#15
  1. note 40 controls the rate of the LFO as an integer multiple of the host rate. The gate retriggers the LFO
  2. note 39 controls the division of the base timing based on the host rate.
  3. see point 1. Also, to get other divisions use an integer-control, followed by a "reciprocal" (math, float) followed by a div64 (divide by 64) and multiply this with the frequency to divide it by a given division.
    You could also very well use a multiplexer to select between standard divisions using the velocity.
  4. When I got a nice "total" subpatch that you can use to sync multiple LFO's and delay easily, I'll upload it

#16

Thanks so much!

I have seen some posts around here talking about how to make the Axoloti more accessible to many more people. The generosity of the community members is very helpful. "Total" subpatches like you are mentioning will go a long way towards getting more people comfortable with using the Axoloti for their musical adventures. I suppose being able to easily navigate objects and sub patches within the software will be important as well.

I am very happy to have jumped in to the Axoloti after it sitting by my computer unused for a while as I didn't really know where to start. I'm grateful for everyone's help.


Clock tapping patch
#17

for me it just looks so much like synthedit that it is very easy to go around and think of solutions if a function is "missing".
I guess I'll need to build a whole bunch of subpatches myself to regain all the functions I used in synthedit.


#18

SirSickSik, I remember your name from Synthedit forums. Great to know that you're around and getting in to Axoloti!


#19

@SirSickSik your sync engine looks nice, would you mind posting the patch?


Cpwitz Contributions
#20

hmm, trying to, but I can't seem to locate the subpatch with windows explorer.. it just doesn't show up in the map somehow.. not even if I save as a normal patch..

wow, seriously... trying everything here.. it just won't show up..?!? I'm afraid you'll have to do with the picture...
Though, you'll need to extra divide the delaytime with 3 and multiply with 4 when the clock is coming in at 24 frame rate

oh... FINALLY!
Though then again.. first tried it with a new post, then thought, let's just add it to the former one and closed the loading screen. When I opened the former post and tried to add the file... it was gone again?!? Though, luckily, it was able to re-save the file and show up again (no mention of any overwriting existing files...?!?)
midi clock sync example2.axp (19.1 KB)


#21

Thanks for sharing and thanks for the effort! Maybe the problems you describe are problems of the unfinished test release?

I'm trying out your patch but I'm a bit unsure how to set it up.
I set the delay write to 682ms and choose low rate accordingly at "Low<>High Rate". I connected the blue output that goes to delay read disp to delay read with a conv/interp. To which value should I set the knob at the delay read object? right now it's not syncing and changing delay time only introduces a little glitch but doesn't really change much.

Edit: Generally speaking I'm a bit confused as to how the delay read works. It seems as if the red inlet is only for modulating the pitch, whereas the knob chooses the delay length by choosing the lenghth of window within the sample recorded by delay write.


#22

I would appreciate if you would put an delay into your patch,
so noobs like me could comprehend how to apply your patch to a delay...


#23

I figured it out. No it's time to experiment with subdivisions and filters+saturation in the feedback loop :smile:

midi clock sync example delay.axp (21.7 KB)


#24

Hi there,

I just sketched up something that might be related,it's pretty close to a tap-tempo-object.
what it does roughly,is start counting and then setting a saw-LFO to the corresponding speed.

taptempo_4.axp (4.5 KB)


#25

Sound interesting but somehow I can't download it...
"The page you requested doesn't exist or is private."


#26

should be working now...


#27

Yes it works, thanks! This is great for manually tapping in tempo but I don't know if it's usable for a syncengine. A synceninge should rather have a continous input so that it can react to tempo changes, your object stops once you tap in a new tempo. Maybe it would be more usefull if the lfo wouldn't stop when tapping in a new tempo?


#28

your right..
I think it makes sense to keep this more modular,to suit different needs.
so I cooked up some more stuff,most of all a 'k2f' object that converts integer
k-rate ticks to something like HZ,to be fed into a 'lfo/saw lin' object...

so here's the new patch,it contains a bunch of custom objects that I already uploaded to the
community library (you need 1.08 and up to run it)
I also did a signal-rate saw-lfo called 'phasor' to be used in conjunction with the 'k2f' - object.

taptempo_7.axp (5.1 KB)


Cpwitz Contributions
#29

This looks terrific, thank you very much vor sharing! Gonna try this for syncing delays later.

Just an Idea, I don't know if you're up for that but it would be awesome to have a midi clock object that could be set by tap tempo too. This would open up for a lot of great use cases, setting tempo with the length of the first loop you make or just generally speaking keeping several elements and other gear more coherent and setting the tempo in more intuitive way.

P.S. I'm implementing your patch now for Sidechain compression like pumping that is independant of tempo, so thanks again for opening it more up and making it available here :smile:


#30

I patched this Tap delay, it works well...but isnt this too simple?
taptempo_7delay.axp (6.2 KB)


#31

@SirSickSik
I thought the timer object output was in 'number of k-rate samples' rather than ms. Are you sure your maths is correct?


#32

I translated from samplerate to ms with the 48000->"reciprocal module"
though as I found later on, this should have been the krate.
BUT!
I've written some dedicated modules to do the maths here and just uploaded these to the community library.
1- a clock to "basic timing" converter for delays and LFO's (though for this, my own multishape LFO should be used as this actually responds to actual 1v/hz input.
2. ratio module to quickly set divisions of base tempo (first multiply the float values, then use a mult64 behind it to scale it back to.
3. actual 1v/hz LFO. Has sine, triangle,saw, ramp and squarewave and I'm going add some more features later on, like a dedicated pwm for each waveform)

search in the library under "SirSickSik"

I've also just released three dynamics modules:
-limiter
-compressor
-transient designer
order of use for mastering purposes: compressor->transient designer->limiter


#33

Ah, then I was just thrown off by the annotations.

Because that's definitely not right. :slight_smile: