Ah - i think i might have found the cause?
In pad menu the last pad is default set to Slicer Loop 0.
Doesn't seem to be able to be changed though? Is this a bug?
Comment actions
Post
Follow
Slicer is always set to one beat behind when triggering on the fly - DDJ-1000
Hi,
If i trigger the slicer mode from my DDJ-1000 when a track is playing, it is always set to one beat behind, which means the 1st beat of the bar is always on the 2nd pad. Please can you help me solve this, or fix this with an update?
The only way it works is if i stop a track, and then press slicer - then it will play the 1st beat on the 1st pad.
The tracks are analysed and beatgrids are all correct.
Thanks
Marc
Post is closed for comments.
Date
Votes
9 comments
Is it possibly because you have quantizing enabled and it's waiting until the next beat before it engages?
Comment actions
No :( - tried with everything on / off (beat sync / quantise etc)
Should the slicer loop numbers start at 0 on the performance pads? Any other suggestions or fixes.
Comment actions
Ok - just tried again with a couple more tracks and now the pads lights are lagging out of time on playback. They are starting from the right pad this time though and they catch up, so can jam with them, but they arent synchronising to the one beat per step that they are set to. Seems to be something up on both accounts.
Comment actions
Any updates or thoughts pulse? Do you think these two errors could be something to do with the message that comes up in the last beta invitation when you open rekordbox? Be good to get some official insight and ideally a solution as slicer is pretty integral for my performance. Thanks
Comment actions
Can you record a video? I've not experienced this in my testing and nobody else seems to have posted about this problem either.
Can you also post your computer specs and the audio config within the rekordbox preferences?
Comment actions
Sorry for huge delay in reply Pulse - both times i came back the forum said it was down, and it seems to work as normal since last update so maybe thats fixed.
Have since had another issue though when hitting a cue point and slicer mode at the same time.
Normally was fine, but after a while, - hitting the cue point again (independently of slicer mode), would trigger slicer mode and jump to a different cue point! (the last hot cue i last triggered with slicer mode before the error)
Other deck was fine, reloading track and restarting ddj-1000 didn't solve it, only solution restart rekordbox.
Then later had another issue where hitting slicer mode on the same side - and would say there was a bpm out of range error, and not enable it. Reloading the track after loading a different track solved it.
All concerning things for using in a live situation though so hope an update could solve this
--- Since noting this down my macbook went down :( and now on windows machine. Havent tested this fully but was intermittent in the first place. If you could pass on my findings to the teams that would be great as was a definite occurence. My specs and audio config for both of the above was macbook pro 2011 16 gig ram, with pioneer DDJ 1000 as soundcard on latest version of rekordbox.
Cheers
Comment actions
This site sucks for one thing, but I'm having the same problems. My right deck is having the exact same problem. I use virtual dj too.
Comment actions
@Jason > Thanks for the compliments on the website! Maybe try removing the stored cookies for:
*.pioneerdj.com
*.zendesk.com
*.gigya.com
...and clear your cache.
If you're having the problem with Virtual DJ, you'll have to seek support on their site, as the DDJ-1000 is really a rekordbox controller.
Comment actions