I’m having this complicated and annoying bug that i’ve wasted a whole weekend on. Before I go to the trouble of trying to figure it out and then wording a post that people can understand, I could do with some clarification on the TSNS setting.
In a nutshell, am I using more DSP if I have TSNS cranked all the way to 127?
I imagine the TSNS setting to be like the sensitivity setting in ReCycle, is that correct?
Any knowledge given is appreciated!
Edit: I’ve discovered the cause of the bug now, TSNS is indeed related, I’ll have to file a support ticket.
I’m live sampling and playback and manipulating at the same time, with recorder trigs set to length 8. If timestretch is set to BEAT mode, the recorders randomly behave as if the length is set at 1. Switching timestretch mode to NORM instantly clears up the issue. Also the issue happens more frequently, the higher the TSNS setting. It may also be connected to RTRG and RTIM parameters
This only applies to live recorded material, of course using samples works fine
Ah I see, I haven’t really experimented with live recording so I don’t think I’m the best person to offer any advice but I suggest asking @sezare56, he seems pretty clued up!
No prob @sezare56, take the day off if you wish, you deserve a break, I’ll cover your shift!
TNTS adjusts the transient detection when TSTR is set to beat.
Has no effect on norm so that’s why it sounds fine there.
I usually leave it at default but have messed with it and noticed changes only to the sound of the timestretch and not the timing. Might be more dramatic with certain audio material, maybe when you increase it a lot it’s getting a wrong reading from your certain audio…
I would think just use norm or use beat and make adjustments to the TNTS setting until it sounds right, and then leave it there…
Hard to tell if it’s a bug or just with the transient detection so high it’s detecting too much subtle stuff and making a wrong reading?
There could easily be more going on. The way I have recorders set up with qrec and qpl, they always play back at the same bpm as the sequencer, so even though I have timestretch enabled it’s not used until I change the tempo. Maybe you are recording in a way things want to get timestretched immediately, if so is that intentional?
Sometimes it helps to rebuild the idea more simply in another bank with less tracks and trigs. Build the most simple example of what your after and adjust settings until it works reliably, then add more. When all the settings are dialed and the interactions understood, go back and readjust the pattern containing the main idea.
Cheers…
No worries guys, I’m treating it as a limitation but its not really a problem to use the NORM setting. I’m pretty sure its a bug though
The actual problem isn’t the TSNS, its that the recorder trigs randomly start behaving as if length is 1, switching away from BEAT mode instantly fixes it and high TSNS causes it to happen more often. I’m actually using a complex setup, live sampling the A4 and Volca Sample and also realtime manipulating the recordings.
Anyway, I filed a support ticket. Thanks for the input guys!
