Tracker stems, when exported to the SD and dropped into Pro Tools or a similar DAW run at an ever so slightly faster tempo than the DAW (100 BPM > 100.71BPM…I think) It is quite frustrating to have to figure out the dead on exact tempo and correct it as ever so-slight drift between the metronome and tracker stems occurs within about 30 seconds.
Reproduction Steps
Using Pro Tools in this case:
Create a track, remember the tempo.
Export the song stems, or pattern stems, it applies to both. Disconnect SD when complete.
Plug SD into PC
Pull .wav files from the /export folder.
Drop them into daw of choice, set the tempo to the tempo set on the polyend.
Hi @pingapong64 , thank you for reporting this bug. We are sorry you’re experiencing issues while using our product. We will do our best to resolve it and notify you when it’s ready.
Hi I encountered the same issue on my tracker + (and it’s also the same on my original tracker) :
software : 1.0.3 build 1138
When I’m exporting song stems or pattern stems the frequency is weirdly 44117Hz instead of 44100Hz. (I opened the files in adobe audition).
and It can create slight shifts when you try to sync the tracker + stems and stems from another daw / synth …
to reproduce :
File / Export / pattern stems export and just check the sample rate of the wave files in an audio software.
That would explain it then, wowzers!
If that sample rate affects all Trackers across the board, then 100 BPM would be 100.0385487528345 BPM… unless I did maths wrong. I’ll do some testing with my machine.
I have had a similar experience yesterday. i have recorded a song from Tracker OG into Ableton at 130 bpm. once recorded the song had ca. 130.07 bpm. I had to warp the file to make it fit tight to the grid for editing.
Just to be sure: This should only be a problem if you record or bounce things out with the trackers’ internal clock right? I’m asking, because I plan to use an external MIDI-clock (which is clocked via audio from the DAW) for getting things into the box on grid.
So how do we ensure timing is correct, record into external DAW and clock to that?
Edit if my research is correct the only way currently is to record audio then warp to grid in DAW
That was my idea, yes. Like record in realtime into a DAW with some external clock, be it from the DAW or a dedicated clock. Didn’t try it, yet, though. I just was thinking, that this, in theory, should work.
Trackers can’t keep time, I have the tracker as master to an SP404 mk2, the 404’s bpm counter flickers by full bpms around the set bpm on the tracker above and below what it’s supposed to be. If you set the tracker at 140bpm you’ll see the bpm counter on your slave device change between 139 to 141 but not stay at 140bpm.
That’s why your exports are all off the set bpm.
I tried the DAW clock it didn’t seem to make much difference, seems easier to just export stems and warp. Ableton seems to handle this easiest in my research
How old are the trackers now? They haven’t fixed what is an integral function of any sequencer, being able to stay in time.
Makes you wonder doesn’t it?
If that’s the case, it’s “just” Midi jitter which can be coped with in part by using a better clock source. If not, it must be something else, which would be worse (I guess).
This bug was submitted 0.5 year ago, i dont know why they don’t fix such instead of dumping new products with more bugs……its like a Monty Python movie…
