Reloop Terminal Mix 2 help (cracks and glitches)

Reloop Terminal Mix 2 help (cracks and glitches)

Hi all

this is a problem reported by several users of Terminal mix 2 and terminal mix 4.

tracks with cracks, and glitches, and sometimes slowing down

I’ve read all topics about this problem in reloop support forum (most of it with no answers or solutions), in serato forum, NI forum and other , and i’m afraid i wont get my problem solved, but nevertheless i will put my case here.

After some research about what should be my new controler, TM2 was the chosen one. It has all that i want and need.

I purchased it in the begining of the year here in portugal.

The first impressions were great, and i was very happy. The day after i received it i had a gig. Went there, and set up all the gear (it’s a place were i go regularly and the owner is a friend of mine) and started the check sound.

After some minutes playing with traktor the cracks and glitches started. We thought it was from the mixer or the amp or the cables, and we changed some conections but still no good. Tried serato, and the problem was the same.
I end up playing with the owners vestax controler with no problem.

Since then the problem remains, although i’ve tried everything to solve it. i’m going to describe what i did and the computers i tried the TM2 on (all of them with the requirements mencioned in reloop page for the terminal mix 2).

Laptop Toshiba satellite A300
Intel Core 2 Duo CPU T9550 2,66GHz
4Gb RAM
ATI Radeon 3650 - 2Gb dedicated
Windows 7 64bits

Desktop
Board - P5K SE/EPU
Intel core 2 Duo E8400 3GHz
4 Gb Ram
Nvidia Geforce 8600GT - 2Gb dedicated
Windows 7 64 bits

Mac book pro
Dont know the specs beacause it isn’t mine, but i tried it and the problem was the same

Software

Serato intro
Traktor Duo (updated)
Traktor pro (on the mac)
Serato 1.1 (on the Mac)

Tried to remove all old drivers, changed the usb power definitions (no wifi or bluetooth on), closed all background services, run latency checker (didn’t turn red pikes) and changed the latency with no results, created a windows user with minimum services running, and even tried a new instalation with Windows 7 32bits.
Did the firmware update to version 0.21

I decided i’m going to return it because has the warranty, and there’s nothing more to do (i think), but i don’t know if i will expect the TM2 repair/substitution or if i’m going to ask the money return and buy some other controler (i’ve read about some users that the replacement solved the problem, and others that not even the replacement solved it)

I don’t trust the TM2, and now i’m playing with a friend’s vestax, but i must solve the situation

any coments/sugestions?

P.s. sorry about my english errors

i use a TM 2 and have not noticed anything like this. odd that you’re getting the same thing in both traktor and serato.

  • try different traktor mappings?
  • faulty usb cables?
  • usb 3.0 ports (try using a powered usb 2.0 hub)?
  • software version?

just a few suggestions off the top of my head

I had the same issue with my new TM4; mine was caused by plugging into a USB hub rather than directly into my PC. It seems the hub itself introduces a slightly unacceptable amount of latency to the TM4; this ONLY occurs with the ASIO drivers, if you switch to WASAPI mode, it works fine - your latency is then 20ms, which is acceptable for non-scratch DJing. My ASIO is actually working fine though now at 8ms, going directly into a port on the mobo instead of a hub.

Also, try updating the firmware on the TM2; they released an update a little while ago which improves things slightly :slight_smile:

hey all
matrick i did try all of those things.
mdcdesign i have 0.21 firmware (the lat update) installed and i was not using a hub.

I posted all my issues in reloop support forum were the are some other guys with the same problem and with various pc and mac setups. Last week i received a email from a product manager of reloop that asked my serial number, and after i send him he answered me saying that reloop is going to replace my TM2 for a new one. :slight_smile:

Some guys also had their TM2 replaced and the problem was solved, so i supose there is really a problem with some TM2/TM4.