Seems to me like you could use this too make it follow a tempo. 2 hz is 2 beats per second or 2 x 60 sec = 120 bpm. Pretty sure you can setup something that uses that math to detunw and lets you just move one slider/knob? maybe?
I tried your utility patch @rs2000 , but I am getting pulses instead of a continuous CV for BPM and the other parameters as well. That differentiator seems to be the main noise source:
Here it gets more bizarre: I read your response on my iPhone (15 pro max), and tried the module there - and it works. My two iPads (9th gen with latest iOS 17.x and Air 2 with 12.x) both show these strange pulses. And another observation: The frequency of the pulses changes with the Latency (buffer) setting: More buffer = lower pulse frequency. The Transport Time module produces the expected rising CV on all devices. I wonder if there is some kind of race condition in the patch that only affects slower devices. Or both of my iPads run corrupted Drambo installations.
Further checking: The module that behaves differently is indeed the differentiator: One pulse on the iPhone, pulse chain on the iPads. But it turns out that the actual source of the trouble is the Transport Time module. I put a HighPass filter between that module and an oscilloscope, and I can see ripple on the iPads, but not the iPhone. No wonder that this triggers the differentiator.
You need a HP filter and the Y scale on the scope to max in order to see the ripple. It’s tiny but enough to cause trouble with the differentiator in the start bit, and the BPM detector as well. Putting an envelope follower between the Transport Time and the following modules helps to reduce the problem but at the expense of latency and BPM CV accuracy.
It would be good to see if others have the same problem, or if I’m the only one. I might try to simply reinstall Drambo and see if that helps.
I think we can close this now: I just removed / reinstalled Drambo on my old iPad Air 2 and the problem is gone. This looks to me as if by accident the Drambo installations on both iPads got corrupted. I did a lot of playing around with Drambo over the past days, and had a performance involving both pads & Drambo on Saturday. The performance went well, but something must have caused the hikkup and corrupted the installation. Still very odd...
I've just checked on my iPad where it works, I can see such bursts too except that their amplitude is low enough to not affect the processing of the time signal negatively.
It turned out that both of my iPads had perfectly running Drambo installations, but that the ripple occurs when Ableton Link is enabled. And the ripple only appears in the Transport Time module, the sequencer clock output is fine. @rs2000 can you reproduce this? If yes, then I’m going to post a bug report about the Transport Time module in the issues category.
I just want to say that I'm categorically against beating oscillators or forcing one's will on them. Violence and intimidation is reprehensible in all its forms. You should all be ashamed of yourselves.
Comments
no
but you can take the beatings tempo and adjust your tempo to that (within given limits).
Seems to me like you could use this too make it follow a tempo. 2 hz is 2 beats per second or 2 x 60 sec = 120 bpm. Pretty sure you can setup something that uses that math to detunw and lets you just move one slider/knob? maybe?
Of course you can.
I'd recommend to get this utility patch first:
Then use the BPM signal to fine tune the second oscillator by modulating its pitch and adjust it to match the bpm changes.
with the tempo range I use (95 -180 bpm) thats 1,58 - 3hz
not enough detune for my taste 🤷🏻♂️
you can double the numbers, but than the beating is double speed to the tempo ...
whats the point of this exercise?
have a tempo ramp and let the beating slowdown/speed up along?
(that the beating isnt on time is what makes it interesting to listen to in the first place, IMHO 🤷🏻♂️)
The point is finding out if something I want to happen can be made to happen.
I tried your utility patch @rs2000 , but I am getting pulses instead of a continuous CV for BPM and the other parameters as well. That differentiator seems to be the main noise source:
Huh??
That's crazy. It works perfectly here, I just downloaded it from Patchstorage 😮
Could you please unfold all modules in the rack and add and connect an Oscilloscope to the output of the first "Transport Time" module?
Here it gets more bizarre: I read your response on my iPhone (15 pro max), and tried the module there - and it works. My two iPads (9th gen with latest iOS 17.x and Air 2 with 12.x) both show these strange pulses. And another observation: The frequency of the pulses changes with the Latency (buffer) setting: More buffer = lower pulse frequency. The Transport Time module produces the expected rising CV on all devices. I wonder if there is some kind of race condition in the patch that only affects slower devices. Or both of my iPads run corrupted Drambo installations.
Further checking: The module that behaves differently is indeed the differentiator: One pulse on the iPhone, pulse chain on the iPads. But it turns out that the actual source of the trouble is the Transport Time module. I put a HighPass filter between that module and an oscilloscope, and I can see ripple on the iPads, but not the iPhone. No wonder that this triggers the differentiator.
@catherder What exactly does the Oscilloscope show? A rising time signal with ripples overlaid?
You need a HP filter and the Y scale on the scope to max in order to see the ripple. It’s tiny but enough to cause trouble with the differentiator in the start bit, and the BPM detector as well. Putting an envelope follower between the Transport Time and the following modules helps to reduce the problem but at the expense of latency and BPM CV accuracy.
It would be good to see if others have the same problem, or if I’m the only one. I might try to simply reinstall Drambo and see if that helps.
I think we can close this now: I just removed / reinstalled Drambo on my old iPad Air 2 and the problem is gone. This looks to me as if by accident the Drambo installations on both iPads got corrupted. I did a lot of playing around with Drambo over the past days, and had a performance involving both pads & Drambo on Saturday. The performance went well, but something must have caused the hikkup and corrupted the installation. Still very odd...
😮 again. Weird.
I've just checked on my iPad where it works, I can see such bursts too except that their amplitude is low enough to not affect the processing of the time signal negatively.
It is strange. In the meantime I reinstalled Drambo on the iPad 9 as well and - problem gone!
It turned out that both of my iPads had perfectly running Drambo installations, but that the ripple occurs when Ableton Link is enabled. And the ripple only appears in the Transport Time module, the sequencer clock output is fine. @rs2000 can you reproduce this? If yes, then I’m going to post a bug report about the Transport Time module in the issues category.
I just want to say that I'm categorically against beating oscillators or forcing one's will on them. Violence and intimidation is reprehensible in all its forms. You should all be ashamed of yourselves.
Oh then you better stop playing synthesizers, enforced pitch happens to them all the time!
Hope your guitar strings are more forgiving.
They're feeling a bit stretched right now, but I'm not worried they're quite plucky.
😆
@rs2000 your irony detector doesn’t work 🤦🏻♂️