Pulse Width works after calibration, gets limited range after reboot

Started by joachip, July 21, 2025, 01:29:10 PM

5 Replies 19,312 Views

joachip

*
Commerce
Posts: 10
Logged
I calibrated my new TEO-5, and after rebooting the pulse width of the square waveform cannot go all the way up to complete silence like it's been able to the whole first week I was using it. Now I regret calibrating.

Fortunately I've found a work-around: After turning on the synth, run calibration again. This will unlock the full range of the pulse width until you power it off.

I know that the original SEM module only had a limited pulse width range (cannot go to silence), so I was really happy to see that the TEO-5 doesn't have this limitation.

But losing that ability every time you power it off seems like a bug to me. My friend who also has a TEO-5 has the same issue.

Odd thing: I was using the synth for a week before I calibrated. All this time the pulse width had full range.

I've updated the firmware to 1.1.0.4, but this did not help. I've attached two examples. "Full Range" is the beheavior I prefer, and this is how it behaved the first week... until i calibrated.

joachip

*
Commerce
Posts: 10
Logged
Oh that's odd. This morning I turned it on, and now the pulsewidth has the full range - without running any calibration. Nice.

But that means it's not quite as easy to reproduce as I first thought.

kpatz

**
Jr. Member
Posts: 166
Logged
Could it be patch related?  If the mod matrix is offsetting the pulse width that could be a factor.  Next time the issue occurs, try initializing the patch (Basic Program) and see if that makes a difference.
OB-6 module, Take 5, TEO-5, plus many other synths.

joachip

*
Commerce
Posts: 10
Logged
In order to avoid mistakes, I made a very simple patch called "Pulse width" which I've been using to test this. Every time I turned on the synth, I check if I have full range or not.

This same patch has been giving me different results before the firmware upgrade (and once after). But for now it seems the problem has gone away. I'll report back if I suddenly see a limited range on my test patch again.

SprunkiRetake

*
Commerce
Posts: 3
Logged
Quote from: joachip on July 31, 2025, 09:24:44 AM
In order to avoid mistakes, I made a very simple patch called "Pulse width" which I've been using to test this. Every time I turned on the synth, I check if I have full range or not.

This same patch has been giving me different results before the firmware upgrade (and once after). But for now it seems the problem has gone away. I'll report back if I suddenly see a limited range on my test patch again. fnf
Hi, can I have a look at your patch? I'd love to see how it works!

joachip

*
Commerce
Posts: 10
Logged
It's just a straight up square wave oscillator, and then I've used the mod matrix to control the pulsewidth. Set it to...

Source = ModWheel
Amount = +123
Destination = Osc All PW