I was watching your description of a clock signal as a square wave, my nerd meters pinging, sending me into "well, actually" mode. Then you finished the discussion by pointing out how the leading edge is what really matters, and systems returned to normal. ❤
Really enjoyed this little series, very informative and I think I'll be getting a Tides in the future. But also thanks for the clock signal info, it's really helpful to know that just the leading edge is important. 👍
2 completely different modules. tides is fantastic, i got it couple of dyas ago and this guy does simply the best tutorials...bar none! but pams is a must in every system. i have 2!!!
I was just thinking about getting an extra clock divider when I thought, “I bet my Tides can do this. I’d better check.” Thank you for this series. So clutch!👏
Great video! I have a question about how you were describing clocks though. The video suggests that clocks have to have a short rise time on the leading edge to register with other modules. I was under the impression that the majority of eurorack modules use a comparator circuit so that any oscillation can be used as a clock as long as the leading edge goes above a specific voltage. Do you know which scenario most modules follow? Also 120/60 = 2 not 0.5 :P
Modules, particularly digital ones, will use different technique to recognize triggers and measure the duration between them. A lot of modern modules will recognize any signal that crosses 0v, going from negative to positive, as being a "trigger", but not every module does this the same. Some digital modules keep a limited "look back" history that only holds a certain amount of time, which might exclude triggers that don't abruptly rise or fall. By making your clocks a rising edge, they have the highest chance to work correctly with every module. You are correct in that it's not absolutely required for every module that they be a rising edge, more so that it ends up being the most compatible by doing it that way. You can test it out with your own modules by patching a slow sine wave LFO to the clock input and seeing what it does (also interesting is to pass audio rate stuff and see what it does lol). And, yeah, as soon as you hit "record", it's amazing how unclear doing math on the spot becomes. :)
@@ferrycollider cool, thanks for the response! Sometimes it is confusing what will or won’t work with eurorack because the manuals are not that great. I am more used to working with clocks, trigger, scopes, etc in a science research setting where the electronic equipment is documented with every tiny detail. Also when the record button has been hit ones mouth has a mind of its own and cannot be controlled
For what reason you use the Quadrax after the Tides? I thought the tides is not only outputting gate triggers, but envelopes like triangle or such by itself?
120 / 60 = 0.5 so it's 2Hz ... Well... no. 120/60 = 2 (Hz) But what you really wanted to do is : 60/120 = 0.5s per cycle Hertz is s^-1 so : (60/120)^-1 = 0.5^-1 = 1/0.5 = 2Hz Which is the same thing as 60/120 TL;DR : bpm/60 = second per cycle ; 60/bpm = Hertz (aka : cycle per second) PS : Tides v2 is
Yeah, I think he was confused, wrote 120/60 but thought 120)60 (sorry, that's as close to a long division symbol as I can make on a keyboard, hehe). Also, your TL;DR is incorrect. bpm/60 means seconds is in the denominator, so it's cycles per second, aka Hz. 60/bpm is seconds per cycle.
