Hi all,
Currently using a pair of 2000NXS via link to a headless rekordbox. These decks are getting on a bit (they are actually sample units) and I'm thinking about upgrading them to a pair of NXS2.
A few things that bother me about the NXS and I was wondering if they were any better on the NXS2:
* Database performance. I find the NXS really slow via SD or USB unless using a really small database. Much better via Link, but even that lags sometimes.
* Unreliable link performance. When I was using straight deck to deck link I often got media file collapsed problems, needing a deck reboot to solve. This led me to originally using storage in each deck, making history a pain to manage (via merged playlists). When I switched to RB link these problems went away - I've only had this occur once since!
* History. Annoyingly RB logs my history perfectly (shows up under History in my browser as LINK HISTORY <DATE>) but the CDJs don't seem to be able to access it, always showing there being no histories at all. I'm sure it didn't used to be like this, but I can't remember when it started. Workaround is to convert history to playlist, but that's a PITA as it clutters up my playlists then when its got it's nice own area to live in!
* Search. This is probably the worst thing about the decks IMHO, the search is very restrictive. I don't seem to be able to cross-field search for example. A search for Loud Body wouldn't match Loud Luxury - Body for example.
Tempted for a complete change to the SC5000 too, but not entirely convinced - probably going to need to get some actual real hands on time there.
Thanks,
Scott
Post ist für Kommentare geschlossen.
I would definitely give the SC5000(M) a serious consideration before making the choice on the NX2. Don't try to look at what the NX2 can do compared to the SC5000 but look if the SC5000 meets your basic needs.
NAMM is at the end of January. There is speculation that Pioneer and Denon have some surprises up their sleeves.
Well I think I've had my mind made up for me - I attempted to put some of these questions to Pioneer without success :(
Well, considering you asked over the holiday break, it's unfortunate but it seems to have slipped through the cracks. If you are still looking for answers, I can certainly help you out.
I would definitely appreciate that :)
To answer your questions:
1) The response speed of a device connected to a CDJ is entirely dependent on the read/write performance of the device itself. Slower USB drives will be slower to load tracks (or scroll through them) than high-performance ones, regardless of the size of the library. Typically performance hits due to the library size only occur when you exceed 100,000 songs. The CDJ-2000NXS2 certainly does have a faster performance when performing the same actions in comparison with a NXS1, by virtue of newer and faster hardware.
2) It was entirely possible you had a bad ethernet cable, network hub/switch, a managed router, or ethernet jack causing packet drops. Alternatively, and my likely guess, points back to #1 - a low quality / slow USB device unable to keep up with delivering the data requested by the players, thus causing the errors.
3) It's been forever since I've even tried loading a LINK HISTORY from a player, so I'd have to fire them up myself to confirm.
4) Yes, the NXS2 does support cross-field search.
Thanks for the reply :)
1) I've tested this with multiple devices, including Samsung 850 EVO SSDs and Sandisk Ultra USB sticks. They work absolutely fine, but as the library gets larger it gets much, much slower. I actually found the slowdown to be around the 10k mark rather than 100k. My actual main media drive (that I'm using with RB via prolink) is a 4Tb Samsung 850. Obviously I'm expecting it to be slower directly connected to the CDJ since it's not USB3, but I do find it very slow, especially for searching. Since going prolink it's much better since the PC hardware is doing the work and simply sending the display information to the CDJ.
2) I'm using the same switch, network cables and drive I was before, just with the addition of a little BRIX PC connected into the same switch running RB. It'd actually be awesome if RB had an 'auto link' option, because the only reason I need a monitor/remote desktop for it is to click that button in RB! From some searching I'm not the only person who has experienced this, with others resorting as I did initially to the drive-in-each-player method.
3) Like I say, the history records fine via prolink, I just can't see any of the history playlists that are visible in the RB browser from the CDJ itself. Might actually be a deal-breaker for me as it really bugs me!
4) Thanks. Shame it can't be implemented for the NXS too, especially via prolink since it'll be offloading the actual search.
Regards,
Scott
Scott,
1) The CDJ-2000NXS2 is certainly faster at managing larger databases than earlier models due to a larger / faster memory in the unit.
2) Sorry, I'm not clear on whether you're saying you had the link issues when serving the files from your BRIX computer or direct connection?
4) The searching when linked may be slightly different than when direct from USB (again, I'd have to get the units out to confirm), due to the fact there is an expectation that you have a computer running rekordbox which would serve as the quicker / easier way to browse your library and find the songs vs. using the CDJ interface exclusively.
Thanks for the replies :)
Unfortunately it looks like I'm going to be leaving the Pioneer/Rekordbox ecosystem.
I created a support ticket on the 2nd Jan regarding the outstanding technical issues I'm experiencing - in particular the history issue.
I've still not had an actual answer to that ticket. Whoever read it misunderstood both my setup and question and despite my expanding on it with more information and it's now been marked as solved.
As Pulse was unable to help with the history issue I'm having I've raised another ticket with more detail but sadly I don't hold out much hope.
Thankfully I have an RZX to sell too that will help fund the change :)
@MrScott > I understand your frustration and I've raised that ticket with our support staff, I'm not sure why they hadn't replied yet (and see that they merged the two tickets you created together into one, which was why the first was closed).
I've been out of town for a trade show since our last conversation so I hadn't had the opportunity to test your issue re: the history logging, but I should be able to get you that information in the next week if you're still interested.
If you could that would be appreciated :)
OK, I have my answers from support and thought I'd share them here for anyone who is after this info in the future.
History: Inaccessible via prodjlink with Rekordbox, and has always been this way. Seems like a strange decision to me, but apparently I'm the only person to ever ask for it, so perhaps I'm the strange one ;)
Cross-field search: Apparently no CDJ/XDJ supports cross-field searching. I'm not entirely sure I agree with the reasoning, but at least I know what I've got to work with now.
Thankfully I may have a solution to all of the above problems - I've written an app that reads an exported rekordbox database and simulates Rekordbox to the CDJs. Still a lot of work to go, but hopefully this means I'll be able to control the exact information displayed. If I can get it to work, it may just be my perfect solution :)
Just found this:
https://forums.pioneerdj.com/hc/en-us/community/posts/203069849-Rekordbox-CDJ-not-showing-History
The post from roberto milani 3 years ago is exactly what I'm experiencing with the history, so I feel a little less strange now!