Have a feature request or suggestion? Post your idea here!

Publicação

3 seguidores

CDJ-TOUR1/2000NXS2 USB Key woes

So I have come across a strange and serious issue with the CDJ-TOUR1 and CDJ-2000NXS2

Just to have a few things clear before we proceed.

All firmwares and rekordbox is up to date. USB Keys used are formatted FAT32

The USB Keys are Kingston Data Traveler G4 and G3 100 (both 64GB with read speeds of 80-130MB/s which don’t matter much as the CDJs are USB 2.0)

The following issues occur with all files.

The Issues do not occur with any other CDJ or XDJ device I have tested them all except the XDJ-1000MKII. (yes all of them)

These USB Keys have been used for the last 2 plus years with no issues on a weekly basis usually with CDJ-2000, CDJ-2000NXS, XDJ-1000, XDJ-700 and XDJ-RX

I have freshly formatted them and re-exported tracks and the issues still occur.

The issue:

1) When loading an MP3 on the TOUR1 it takes up to 5 seconds to load the track. The NXS2 loads almost instantly, in about a second. (this is not the main issues but thought I would mention it)

2) When loading and MP3 on the second deck while the First one is playing and you begin to play the track you just loaded, the first deck Gets Communication error and enters emergency loop. This error is completely reproducible every time. The same issue occurs with the NXS2 but after about 15Mins to an hour.

3) When in ProLink with a laptop via Ethernet no issue ever occurs. Everything work flawlessly (always with the same tracks from the same playlist)

4) This issues occurred less often with the older firmwares of the TOUR1 but also less often with the newer firmware of the NXS2.

5) When using a USB key that is set to Blue waveform instead of RGB the issue occurs later but still occurs.

There obviously seems to be some sort of issue reading the Keys.

Any input on this matter would be greatly appreciated.

Thanks :)

Mushin 1 de Maio de 2017 20:16

Publicação fechada para comentários.

Data Votos

8 comentários

Hey @Mushin, sorry this topic was somehow missed in my regular sweep through the forums. Glad to hear you're out rocking the TOUR1 system! Hopefully I can help you address these issues.

Are any of the tracks with which you've experienced these issues analysed after rekordbox v4.2.5?

What is the encoding type / bit / sample rate of the tracks you're using?

What kind of network hardware is being used to connect when you're not using the TOUR1 (as I expect when you are, that you're using the DJM as the network connector)?

Pulse 20 de Junho de 2017 17:35 0 votos

Hi Pulse,

I'm indeed rocking the TOUR1, or trying to lol. The issue however is not isolated to only the TOUR1. As I stated the NXS2 Kit also has the same issue.

It does it with all tracks, before and after 4.2.5

All Files are 44.1K 320kbps MP3s
I don't think it has anything to do with the files as the issue does not occur with ProLink, just USB keys.

Yes were using the Built in switch on the TOUR1 and with the NXS2 kit were using a NETGEAR GS 605NA switch

Thanks for looking into it! :)

Mushin 21 de Junho de 2017 16:07 0 votos

@Mushin > Thanks, just trying to obtain as much information before escalating this to our engineers for CDJ / rekordbox.

You mention you're using Kingston Data Traveler drives, have you used other USB drives and experienced a similar issue?

Pulse 21 de Junho de 2017 16:17 0 votos

Hey Pulse,

Sorry on the delays answering I never got an email notification that ou had responded and just noticed you had when I logged into the forum today.

Yes I have one other sony USB Key with the same issue.

I recently acquired a Kingston HyperX Savage 128GB 350mb/sec read speeds and no issues anymore.

However I have an older 32GB Kingston key that I have been using for over 5 years that doesn't even detect wen plugged into a NXS2/TOUR1 but if I plug it into a NXS or older runs with no problems.

I also had a acquaintance who had a smilier issue with a Corsair Survivor. They switched to the Kingston HyperX Savage like my new key and no issues.

This is very unfortunate as I really don't feel like replacing all my USB keys with savages. They are pretty pricey

Please let me know if there has been any updates. Thanks!

Mushin 27 de Setembro de 2017 16:07 0 votos

Glad to hear you got it resolved with a different USB drive, however I wouldn't personally recommend the HyperX drives as they have been found (through end-user speed tests online) to be VERRRRRY slow when it comes to small file transfers, which rekordbox tends to do a lot of (for waveform / cuepoint data). They are fantastically fast for large chunk data, but stumble under large numbers of small files.

Let me know how you make out with those drives.

Pulse 28 de Setembro de 2017 05:49 0 votos

Oops - forgot to mention that the Corsair Survivor drives are known to be problematic in reading on the XDJs, and possibly problematic on CDJs and other units, so we don't recommend them for use with Pioneer DJ products.

Pulse 28 de Setembro de 2017 05:50 0 votos

Even though the small file transfer of the HyperX Savage is a little slow (i feel VERRRRRY SLOW is a bit of an exaggeration IMO). I've had Zero issues with it.

Also I recently tested a Kingston Data Traveller 50 64GB with no issues.

Finally I wanted to let you know I had organized a large an event this past weekend where in the main room we had a TOUR1 Kit + NXS2 (DJM-TOUR1 + 2x CDJ-TOUR1 + 2x CDJ-2000NXS2) and it was a total shit show, many of the DJs who came to play had huge issues with there USB keys, the decks would go into emergency loop or half there tracks wouldn't load giving the error "the track had collapsed E-8302: CANNOT PLAY TRACK (3658)" There where some sandisk, Lexar, and others that I didn't see.

They informed me that those keys played perfectly on older CDJs. I ended up moving those DJs to the smaller room where we had an DJM-900NXS2 and a pair of XDJ-1000 where they had no issues, everything worked perfectly.

This is crazy! How can I run an event not knowing if the DJ's USB keys are going to work or not?

What changed with the new Players that is causing this issue?

It has to be resolved. Before you ask, The firmware where all up to date and the Keys were made with RekordBox 5. Funny enough both myself and another DJ had keys made with rekordbox 4.x and we hand no issue. The other DJs key was an old USB 2.0 32GB Lexar and mine was the 128GB HyperX Savage.

Any thoughts?

Mushin 14 de Novembro de 2017 19:46 0 votos

To be perfectly honest, I wish I knew the answer.

There are so many different USB drives out there, but the good news it there are only so many companies manufacturing the memory and control chips for them, so the variety isn't unlimited. But with most manufacturers opting to use inexpensive chips to keep the cost low for the consumer, they're more likely to come from a company whose manufacturing and QC tolerances are lower.

The same thing applies on the other end of that USB connection; the host controller. Pioneer DJ uses parts they've researched to fit their criteria and budget, and for the most part, these hosts (like the devices) are supposed to be universal and communicate within the USB standards. What we've found is that there are certain combinations (for example the Corsair Survivor series drives with the XDJ-1000) that absolutely do not play well together to the point I recommend users avoid them for Pioneer DJ products altogether, even if they work properly in other players. I used to have a USB2 version that worked great in CDJs, but since the issues with the XDJs, I've shelved it for DJ use and now use other brands.

It's entirely possible that a different USB host chip was spec'd for the TOUR1 system which is more sensitive to certain USB devices than previous CDJ models, or there was a generational update on the chip manufacturer's side, and that could result in changes to the specifications that Pioneer DJ's engineers didn't know about when selecting that component.

Unfortunately we can't test every combination of USB drive available with every product (although they do test a variety of them for compatibility), as some users have claimed that Corsair Survivor drives, when formatted to HFS+, worked fine, but FAT32 did not.

We always welcome feedback when there are issues with the products as there are sometimes changes that can be made to the firmware that correct them, but it can often be an impossible situation to nail down - from past experience, they have tested USB drives that have been reported problematic, only to have zero issues with the same make / model drive. Was there a running change made by the drive manufacturer and this was from a different set of internal hardware? Or was it just a faulty production batch? So many variables!

The more information you can provide as to the specifics of the situation, the better.

- USB drive make / model / capacity / format

- content of the drive / version of rekordbox used to export

- CDJ firmware / manufacture date

- whether the CDJs were linked and the error came from a linked player or directly from the host CDJ

- etc.

I know you might not have all that information available now, but for future reference, knowing those details would help our product teams isolate the issue to come up with potential fixes.

Pulse 15 de Novembro de 2017 00:17 0 votos