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

投稿

8フォロワー フォローする
0
Avatar

CDJ-3000 Waveforms /Grid out of time / wrong place

This is a slightly confusing issue that im trying to track down so bear with me.

This has only started happening on recently analysed tracks, around the same time I installed firmware 1.06. Which makes it confusing.

On the PC two tracks (One new and one previously analysed) can be gridded and played using sync and be in time, and the grid over the waveform looks okay two.

Export and take the USB to the player, play the exact same two tracks and the new track needs manual adjustment to be in time. (See picture for amount of adjustment ). Picture is in time, both tracks are perfectly grided according to rekordbox on PC

This only happens when mixing an older analysed track with a new one, mixing two old or two new is fine

I have exported the same track from a fresh version of rekordbox on a new PC and same issue. So have to assume the player.

I know its no biggie, and can get in time by ear. But the second guessing myself as the grid is saying wrong is driving me nuts!

Filetype is mp3
Rekordbox 6 (Ill try RB5 and update ticket if different results)

Jack Daffron 回答済み

正式なコメント

Avatar

I'm going to close this topic as I would prefer users please create a new topic (each; please don't piggyback!) if you still have problems after updating to 1.11. Thanks.

Pulse
コメントアクション Permalink

投稿コメントは受け付けていません。

19件のコメント

0
Avatar

Manually adjusting the beatgrid on the CDJ while connected via prolink to Rekordbox, and then re-exporting to USB works fine. 

But then the same two tracks will be out when playing in Rekordbox on PC

Jack Daffron 0 票
コメントアクション Permalink
0
Avatar

If you export the accurately-gridded songs to the players and hit sync, even if the phase meter is not aligned, are the songs in sync?

Pulse 0 票
コメントアクション Permalink
0
Avatar

Hey, No sync will pull the songs out of time, and the grid into alignment. The players behave as if the grids are not in the right place

The problem seems to be that the audio and waveform/grid are out of alignment

Jack Daffron 0 票
コメントアクション Permalink
0
Avatar

I've gone through all of this with support;

Keiko (Pioneer DJ Global)

Nov 20, 2020, 12:51 GMT+9

Hello Greig,

Thank you for your reply.
CDJ-3000 engineers saw your reply and answered below. 

The issue that the stacking waveforms are still slightly off is caused by some slight delay of the LAN cable communication, which cannot be prevented due to small gaps in the communication timing. 
Greig Gaskill 0 票
コメントアクション Permalink
0
Avatar

@Jack > What I'm trying to ask is if you hit sync, is the audio aligned?

Pulse 0 票
コメントアクション Permalink
0
Avatar

Hey,

No, audio is not aligned when pressing sync.

In short the player behaves exactly as you expect if that track was not gridded properly.

If you adjust the grid on the player it all works fine on player, but is then out on Rekordbox. The following picture is from Rekordbox - on a track that I adjusted the grid on the player. The grid is now right on the player, but wrong in RB




Jack Daffron 0 票
コメントアクション Permalink
0
Avatar

precisely the same issues i reported, clearly something not right with the players and the pro dj link

PaulM72 0 票
コメントアクション Permalink
0
Avatar

Maybe I'm wrong, but this is very similar to the problem I encountered on the CDJ-2000 nexus. Some mp3 files in CDJ were decoded without taking into account the first mp3 frame. Because of this, the sound in CDJ did not match the grid and big waveform. Quantize and Sync works with offset ~26ms on these tracks. In RB these tracks play perfectly, the grids are perfect.

https://forums.pioneerdj.com/hc/en-us/community/posts/900001340886-CDJ-2000nxs-sync

Greeb-mail 0 票
コメントアクション Permalink
0
Avatar

I am having the same problem and it doesn't look like this has been solved. I have 2 CDJ 2000 NX2, and now 2 Brand New CDJ 3000s. Both 3000s sync just a bit behind, causing slight off beat sound, and I always have to then make a manual adjustment forward, creating a weird "extra step" that I have to warn other DJs about so they aren't counting on that sync button to work. Never had this problem hooking any other older pioneer player to my system before. 

Jimmy Gilland 0 票
コメントアクション Permalink
0
Avatar

@pulse - Is there any updates on this, this does not occur on any other players - only the 3000. So its not a legacy issue thats always been there at all

Thanks

Jack Daffron 0 票
コメントアクション Permalink
0
Avatar

As posted in another topic - our engineers and various testers have not been able to consistently reproduce this problem or find a cause, so they continue to investigate. If you have a video of this, we'd be happy to take a look. Also, if you have a song (or songs) where this can be reproduced at every playback, please email them over to me at forums@pioneerdj.com and I'll pass them to our engineers for review as well.

Pulse 0 票
コメントアクション Permalink
0
Avatar

@pulse sorry for the delay, Ive sent you an email with the video. and the tracks.

Judging by comments on a local FB group - this is a problem that is affecting everyone now

Jack Daffron 0 票
コメントアクション Permalink
0
Avatar

I have cdj3000s and can confirm Im getting the exact same issue on all 3 different cdj3000 setups I've played on (Mine, a gig I played at, and one of the radio stations here). I have also spoken to many other DJs who all experienced the same issue

Ruach Oosthuizen 0 票
コメントアクション Permalink
0
Avatar

Can we PLEASE get an update from PioneerDJ on this issue??

After reading several posts on the same exact issue, it's affecting all CDJ 3000 users for a long time now but I am see conflicting updates from PioneerDJ support (ie "our engineers cannot replicate the problem" or "we are still working on it but not a priority",....) and would like an update and clarify on this please.

...is this problem recognized as an issue by PioneerDJ and being worked on? Is it something that can be fixed with firmware updates?  

Chris 0 票
コメントアクション Permalink
0
Avatar

Anyone tried the new firmware that was released yesterday? 1.11

Greig Gaskill 0 票
コメントアクション Permalink
0
Avatar

Correction: this was fixed in V1.11 firmware just released yesterday lol, thank you! 

Chris 0 票
コメントアクション Permalink