that was a couple of weeks ago, so it is a very recent rekordbuddy version. i import less a dozen new tracks every week so it's not a big deal to do it twice, and my long term dream & vision is to ditch traktor. basically i keep traktor for when i have to play at small parties or at friends where I don't have/dont want to lug around the cdjs.

If you already have the tracks in your rekordbox library then rekord buddy won't change the beatgrids. I did around 250 new tracks at the weekend and they were identical when brought into rekordbox.

You can sync the other way too, does both.

So you dont actually import tracks into rekordbox, or how does this method work to get rbuddy to change the beatgrids?

You import into rekordbox but the beatgrid info is set by traktor. It's imported over by rekord buddy converting the traktor nml database and writing it to the rekordbox XML file.

If you've got the traktor ipad app you can use that to check/set your grids, set hot cues etc and sync with traktor and then quickly port it over to rekordbox. It's much easier to do/use than it sounds. It's everything that rekordbox and the iOS app should have been.

@ Phil, i don't misunerstand the problem at all. The master is part of the whole sync thing, the whole way the decks and mixer work together. But hey, you say its all working fine and tickedy boo and theres no reason to return the units or demand action, ..... so everyone thats moaning about problems ..... you all must be mistaken ....... NOT. Phil are you sure you don't have shares in Pioneer? lol

i'll try again with the car analogy .... If you bought a turbo charged car and the turbo failed to kick in .... but the car still drove fine .... would you think the car was fit for purpose and worked as advertised ...... NO!!!!!!

to try and argue the point, whilst at the same time saying you use two different programs to do the job that the Pioneer ones SHOULD be doing is ridiculous to say the least. 

Using traktor soft to do what RB it's supposed to do i found it little bit ridiculous. anyway two things any of those works fine...

No mr green, the problem is not a problem with sync. The master not switching decks automatically is completely independent of the sync function, it's actually used in non sync mode to help determine the musical key of the next track.

I'm not saying everything is working fine, it isn't. I'm not defending pioneer either, they need to pull their fingers out and fix these few annoying bugs.

Save your car analogies for when you speak to Anne Robinson mate, she might be interested in them, I'm not.

I'm sorry but sync on these units is not ok - anyone who's worked with Serato or Traktor for more than 5 minutes can tell you this.  People continue to talk past each other on these forums regarding this issue and it's driving me banana sandwich.  Yes, I understand many lazy people will analyze their libraries in RB, not adjust the grids, hit sync and expect beatmatching to be spot on - then when they double clap and trainwreck they come on the forums and say 'sync doesn't work'.  That is not why sync doesn't work.  There are two issues at play here that shouldn't be coupled or confused; beatgrids and sync.  Regardless of how crappy your beatgrids are, sync has one job and that is to keep beatgrids from multiple tracks (however poorly mapped) in line with one another.  How a beatgrid is laid out on a track has no bearing on sync's job to align those grids; if your grids are off, sync will expose them because the underlying tracks won't match up when the grids are snapped.  In a simple example, let's say you're double clapping when you sync two 4-beat loops, is sync not working or are beatmaps off?  Let's say we go manually adjust the beatgrid, try again and you're perfectly beatmatched - THAT'S a beatgrid issue.  NOW, keep that loop going and after a few dozen times, you start double clapping...THAT'S a sync issue.  For the record, this scenario can be easily reproduced on the nexus decks as they are today.  I will say that in general, the way sync currently functions is tolerable in its MOST BASIC applications, however when combined with other features such as active loops, tempo adjustments, hot cues, etc, there are times it fails to snap the grids and keep them in lockstep.  Just because a particular feature works for you in your application DOES NOT mean it isn't faulty in other applications that you don't happen to encounter because you have a different style of mixing.  Out of respect for people who RTFM and are struggling with faulty features and deserve to have them addressed by Pioneer, please don't dismiss them by broadcasting generalities like 'sync works fine'.    

I fully understand your issues fox, but this all sounds like the grids are not correct. Sync is nothing without a bang on grid and it is pretty difficult to get the grids right in rekordbox. Ive tried to help you in other threads and couldn't reproduce your issues. As I have said before, send me a couple of tracks you have sync/active loop issues with and I'll try to see if I can see what's up.

@Phil, now you're just coming across as an a**hole .... stand alone and pretend these decks are fine or fit for purpose ....... no one is standing with you.

Give it a rest. At what point do I ever say that the decks are fine? I don't because that isn't the case. Don't try and twist things around.

So phil for rekordbuddy to actually work properly( and adjust the beatgrids of tracks in rb) you need to start a new collection and reimport everything? Otherwise it wont work (with an existing collection) as it doesnt adjust the beatgrid?

if the beatgrids are correct the sync will be correct. that's my experience.

where the sync of the nexus is vastly inferior to traktor is when you start jumping around the track. if i sync two tracks in tractor (..ok i give up to the autocorrect of the imac let it write tractor and stop nagging me!), even manually by nudging the timecode vinyl and not activating the sync lock, the two tracks will stay in sync when i push for instance fast forward or the cue, hot cue buttons. with the nexus sync it doesn't happen, when i push a hot cue or fast forward it will jump out of sync.

so yes we can say that the sync works, but it's not worth 2000 euro a piece compared to the cost of a copy of tractor scratch/serato (or even mixxx that is free, open source, supports timecode and has auto beatmatching), an audio interface and timecode cds or records.

@phil rekordbuddy: the tracks i imported into rb from traktor where not yet existing in the rb library. i tried rekordbuddy to see if it could simplify my workflow and it does not do it. 

@sergio amado: yes using traktor to beatgrid for rekordbox makes no sense and it is stupid, i agree. the point is that many of us still keep two libraries of music, one in traktor/serato/etc. and one in rekordbox. suppose you have to play in a club where there are only two turntables,the only way to play your digital music is to go via tractor/serato/mixxx/whatever software either with dvs or with some type of controller and an audio interface plugged into the mixer.

Wow... Let me just say, WOW...

144 comments on a FW?!? if u guys wanna be heard - post on pioneers Facebook page or some newspapers homepage, why are u shouting here???

If anybody have seen my posts before, I had some problems with the FW and was one of the haters... But serious, come on guys, pioneer can't dj for u????

I hope pioneer fix the nexus but leave Gavin and pulse alone, go to some media that care?!?!

A last word is - pioneer, please don't get into this mess agin!

Thank u!

That's correct cdjbasile, it's a limitation of the rekordbox database that won't allow merging. I've been testing it with new tracks so its not been an issue. I've got another few hundred tracks that I'm going to test it on soon and if it works as well as last time, I'll do my whole collection.

@ Julia "when i push for instance fast forward or the cue, hot cue buttons. with the nexus sync it doesn't happen, when i push a hot cue or fast forward it will jump out of sync."

The fast forward buttons in traktor do quantised beat jumps (set in traktor prefs) which are designed to stay in time. On the nexus they just scrub forwards or backwards and aren't part of the sync feature. Hotcues shouldn't jump out of sync though.

Sorry guys but i have to say this: PIoneer we dont care about the damn sync-master-whatever issue. FIX THE DAMN UI.

i'm with tasos, Screw the sync crap for now, it should be fixed "if" there is an issue but get to the bottom of the other issues first that are more important, Speed the UI up a lot and make searching capabilities through tablets possible like all other comapnies are doing, you're falling behind and people are starting to get fed up

Blimey we have been busy, I do agree people need to be careful when claiming sync doesn't work and its the decks fault. Bottom line the software powering the beat grid plays an intrinsic part and it needs to be adjusted properly to have any chance to sync. As Phil says the RB grids are just very difficult to get bang on sometimes. Tracks starting with strings and no beat as an example can be problematic.
Having used ableton which has a level of complexity and the easy traktor systems I know what I'm doing but it still isn't where it needs to be.
I'm really interested in trying the Traktor beat grid import route though I'll be giving that a try but that just goes to illustrate how substandard the RB software is and just how preposterous it is to have to do that when paying £30000 for the hardware the software driving it should be so much better !!

Yeah guys let's all argue about what fixes should take priority!  Your time would be better spent adjusting your beatgrids because no one is listening.  You guys win, forget sync, fix the UI first Pioneer.  100% of nothing is nothing...

WOW ...

I guess im not the only one that is totally F888 off with the current state of affairs - Good to see so many others are passionate about how PIONEER have FAILED so far with the Nexus

I agree - I think we should think of taking this further, in the UK under the SALES OF GOOD ACT 1979, the purchased item, must by "fit for purpose"

The CDJ 2000 NEXUS - is currently unfit for purpose, though one grain of comort might have been thrown, does the ". "Fixed a rare issue where playback from other media would not start, stop or be selected when a large USB device (e.g. 20,000 tracks) is disconnected." - Mean that the disappearing file issue has been sorted ...

I again Djed to a packed club on Tuesday night - THE NEXUS LET ME DOWN !! My files went Awol - and the folders appeared EMPTY .

DOES 1.13 SORT THIS ?! im on 1.10, and will NOT chance changing unless others have given it the seel of approval.

1.10 - is ok, but COME ON PIONEER ... WE HAVE SPENT £3000 on these players ... taking the mickey is an understatement

Reasing all these problems makes me thank my instinct i knew was going to happen worse when mk3 to 2000 was launched ...

Imo first time i buy professional cdjs from pioneer my next set up will be either from denn r gtting back to vinyls with timecode

Hi guys ,

I'm still on version 1.06 should I stay or should I go to 1.13 ? 

well I cannot give it 100% approval to say to update yet till I use it live Saturday night. I have been testing it a lot when I can, Letting the players just autoplay hours at a time and I don't see any slowing down but again, the real test is saturday when i am actually loading and using cues, loops, etc.....

I would however still like them to speed up the time it takes to go from the waveform view back to the tracks view, when linked to RB on my laptop, the tracks appear instantly but when using a usb drive, it takes a second or 2 for them to appear and the sort is then always wrong on the main deck

More than 150 replies. And not a single word from Pioneer.
Doesn't this say it all?

So still no useful updates. But about the SYNC problem ok the master switch not changing back can be annoying but I can live a while longer without it. I had a good play around with sync and it works perfect on some tracks even with active loops. Then other tracks can be a train wreck.  Personally I think it goes back to rekordbox and inaccurate beat grids. Rekordbox really needs to be improved especially the beat grids than changing them manually if this was done then things would start to improve along with faster firmware updates. 

Attention all users...

This update addresses several bugs and does not change any existing features, nor does it add any. As such, there should be no concern over negative impact after the update to 1.13.

From reading the comments in this thread, most of the complaints are about the change made in ver. 1.10 (unexpected switching of Master Player and Slave Player when using Slip Scratch or Slip Pause during SYNC). This change was made for preventing the issue of the tempo changing unintentionally while using the sync feature on only one of two players. 

This improvement has triggered complaints that usability was lowered for those who do not use the SYNC feature at all, notably those using the automatic switch of Master/Slave feature not for sync purpose but simply for the phase meter and traffic light functions. If the SYNC feature is not used in either player, the bug fixed in ver. 1.10 does not occur even if this change is reversed.

Your feedback is always taken into consideration and improvements and changes are made as necessary and as soon as possible.

Thanks again for your patience.