Early concerns, great fun

Tracker
1

Hello tracker community :slight_smile:

I purchased a tracker mini 2 months ago, and used it quite extensively since.

Here are some concerns I have with it, and I would love to hear if some other users had something similar and how to get away with it.

Seems like I have an issue with some samples when trying to import them. They get super-staurated or maybe bitcrushed when previewing and importing, but if I open them from my computer they are totally fine. Also some times opening a folder crashes the device, but only on some specific folders. Those open also fine when connected to a PC.

Another one is that the tracker isn’t recognized as an audio pilot by my PC (Windows 10, latest version) so I can’t use it to sample or to bounce tracks. Did I missed a driver to install or something else ? On my Mac it’s working perfectly fine.

And the last one is that when exporting from the tracker mini itself, I get a slight clock issue (exporting at 134 bpm, then importing in Ableton Live at 134bpm and I get a quarter note gap after 45 seconds of audio). At 1st I thought about a 44.1khz to 48khz issue, but that’s not it.

I made a quick research and didn’t saw anyone else with those issues.

I’m using a tracker mini with the latest stable 2.1 OS

Looks like I’m grumpying, but actually I love using this device, it totally changed the way I produced and I tend to use it even more.

Thanks a lot <3

1 Like
2

Hey @Whim_Therapy, welcome to Backstage! It‘s good to have you :hugs:.

What sample- and bit-rate are they? If they are not 44100hz 16-bit, the tracker will convert them on load. Which might be what is causing issues here?

I‘d be curious to hear what format they are in and if you got a sample to upload, i‘d love to investigate that as well.

Are there large number of samples in those folders? Or long filenames? Special characters in the filenames?

There are no specific Windows drivers. It should just be a general audio device using Microsoft Drivers. You could try updating/removing those drivers when you have the Tracker connected - using the Device Manager.

The exported tracks or stems are not exactly 44100hz, which is most likely what is causing the issue. Make sure in Ableton that it is not trying to stretch the audiofiles. That should resolve the issue. Not sure what that option is called in Ableton, but i know it‘s there somewhere :laughing:

3

Hello @Sandroid and thanks a lot for the fast answer :slight_smile:

What sample- and bit-rate are they? If they are not 44100hz 16-bit, the tracker will convert them on load. Which might be what is causing issues here?

I‘d be curious to hear what format they are in and if you got a sample to upload, i‘d love to investigate that as well.

I think it’s indeed a conversion issue, I just uploaded 2 files here from the same sample pack : kDrive

The 1st one is having issues when imported, but the 2nd is working perfectly. They are both at a different sample rate so this might be one of the keys to the answer.

Are there large number of samples in those folders? Or long filenames? Special characters in the filenames?

Nothing much actually, it’s all like “kick” “clap” “one shots” adding up to around 400 samples over 15 folders. but everytime I try to open the main folder containing all those subfolders, I get stuck on the “loading files list” window.

There are no specific Windows drivers. It should just be a general audio device using Microsoft Drivers. You could try updating/removing those drivers when you have the Tracker connected - using the Device Manager.

I just tried this out, removed the “Tracker Mini Audio” and “Tracker Mini MIDI” from the device manager, unplugged the TM, restarted my PC and replugged the TM, and I still get the same issue even if the device shows up correctly in the device manager. Weird.

The exported tracks or stems are not exactly 44100hz, which is most likely what is causing the issue. Make sure in Ableton that it is not trying to stretch the audiofiles. That should resolve the issue. Not sure what that option is called in Ableton, but i know it‘s there somewhere :laughing:

Ha yes ! Just read this 44.117 hz thing ! It explains everything :slight_smile: I guess the best workaround right now for me is bouncing the multitrack in realtime on my mac and then transfer the Ableton project to my PC.

EDIT : I just did it, and ended up with something strange. I got the same misplacement, which aligned pretty much correctly when adjusting the tempo in Ableton to 134.23 bpm (on the TM it is 134) I don’t really understand why because I bounced in real time. Is the bpm on the tracker slightly off ?

Thanks once again for your time, it’s very helpful :slight_smile:

1 Like
4

If you haven’t already, try recording the audio out of Tracker headphone jack into ableton and let me know your results with this

5

Hey !

If you haven’t already, try recording the audio out of Tracker headphone jack into ableton and let me know your results with this

So I just tried to record directly from the line out of the PT into Ableton Live, and I have the same weird issue ! So i tried with 2 other projects, one at 90BPM and one at 100.

The 90 one got perfectly aligned, but the 100 got the same issue, less accentuated than the 134 one.

How weird is that ? Does anybody experienced something similar ?

I can share the projects with you all if it’s helpful.

Cheers and massive thanks !