Has anyone here ever made a frequency detector?

I'm honestly not sure.

 

I found these two links
https://serato.com/forum/discussion/242276
https://support.serato.com/hc/en-us/articles/234760828-Relative-Mode
Hope it helps you

 

I've got pitch tracking for both traktor and serato working, I'm still stuck on how to manage the phase comparison for forward and bacward.

How can I compare time in core and detect the phase alignment changes, I've messed with multiple combinations of compare modules and router triggers but none of them are doing the job right.

It's a situation where I know what I need to do, but I can't find the right configuration of modules to do it.

 

Is there a "Timer" module for core like there is in primary, I've been searching and can't find one.

So many modules to look through.

 

What's about e=m*c the Einstein formula. m is modulate and c is carrier. Like modulate a Block. Build a peak detector in front of Mod 1-4!

 

A timer? Every time a reset event happens, set an OBC value to zero. Every sample, add 1 to that value. Read the value, divide by the sample rate, and you have the number of seconds since the last reset event.

 

I've never really used obc connections before, I've got them counting properly but I can't seem to figure out how to do the reset event.

are there any examples of this type of function that you know of, I'm digging through the manual, but as usual the manual can be very general.

 

I'm counting reset events of a soundwave traveling at 2000hz that fluctuates between 5x speed and 0 speed.

 

Library > Control > Saw(up) LFO. Open it up and look at the Phase macro, taking note of the Rst input. Basically, you write the value you want to reset the counter to into the OBC.

Since the wave is ~2000 Hz, it may not actually be enough to simply reset the counter to zero. You'd need to use interpolation to figure out at what point in the sample the wave crossed zero. Linear interpolation (using the waveform sample amplitudes immediately before and after the crossing) might be enough.

 

I've come to another situation where I need to create a core level timer, but the issue is that I need the timer itself to create the reset event for something else.

As in an event enters the timer, it triggers a value of 1 to the output and then holds for 50ms, then outputs a zero to turn the next module off.

I need the exact behavior of the primary timer emulated in core and I just can't come up with a usable result at this point.

does anyone have any ideas?

 

there is a core macro flaoting around. its called 'hold'.
its made by michael hettrick and can be found in his west coast AD envelope and i have used it in AutoRiseAR.

 

Hopefully this will do..


the alternative, while also blocking init events :