Hi, just recently got my Tete and loving it so far apart from some issues.
I’ll document 2 different issues I’ve had:
Right now as I sit at my modular the looper in combo mode seems to have gone a bit weird…
Using combo mode, external clock, euclid-fader-fader-LFO, all set to LOOP
An hour or so ago it was working fine, I just came back to it to have another play.
It didn’t seem to want to record, I messed around with the clock, turing play on and off etc. I have eventually (at least I think I have, it might have been my original loop) managed to record a loop but it appears only the 1st pad is being recorded, none of the other pads seem to have done anything.
Even though I hear pitch changes from the loop to my oscillator neither the display or the pads are changing as the loop plays. If I move the pads they work as expected but nothing can be recorded. The progress bar on the loop doesn’t move either.
Loopy also doesn’t work - no effect in the loop or the display.
Overdubbing doesn’t seem to work at all on any pad.
I haven’t restarted it yet, but switching into different modes and back doesn’t make any difference.
Same configuration as above.
This was some days ago… I was using the tete normally then started to try out different clock speeds, CV’s etc. After messing around with various things I got the main display back but noticed the 4th pad (LFO) wasn’t displaying anything, it looked like a line at the top instead of a waveform. It was working as an LFO though, I could hear its effect. Moving the pad changed the speed but didn’t change the display at all.
I appreciate that was a bit of a mouthful, sorry.
The only thing in common with these issues are both using external clock and both happened sometime after the screensaver had been on. It might not affect it but could be worth some investigation.
And a couple of questions:
The looper can be made to start when an external clock starts by pressing the play button twice before the clock input (fast flash) but it doesn’t stop when the clock stops. Will there be a way to do this in future?
The loop itself doesn’t seem to reset when using the reset input and using external clock. I have a reset coming out of another sequencer so the clock and reset are sent at the same time. Perhaps this is connected to the question above? Again, is this something that can be added in the future.