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

Publicação

3 seguidores Seguir
0
Avatar

Hardware/Software Audible "Loop/Cue Freeze"

Hi Everyone,

For starters, my setup:
MBP Retina (Mid-2014), i7, 16GB RAM
2 x XDJ 1000 paired with DJM900 NXS.
RekordBox 3.2.2

I've placed the Pioneer Technical Q&A at the the foot of this post.

After about two hours of playing without issue, a track would reach the end point of the song (about 30 seconds out) and then suddenly the track would become "locked." Specifically, playing seems to become stuck in a loop that is shortened to the point where it becomes audible noise (analogous to a high-speed LFO). As you can imagine, the sound isn't pleasant. Once this occurs, I can move the platter and see a reaction with the wave form, but the playhead remains in place (as does the sound). Attempting to exit the loop yields no results. Even stranger, I can see on the wave form a "C" for the hot cue and a bright right triangle. What's strange is that I haven't set these cue point either live or pre-DJ set in RekordBox. Even more strange–this has occurred with several tracks, all of which are quite healthy (i.e. not corrupt, torrented, low kbps, etc.).

I've tried to emulate the behavior in order to replicate the problem, but unfortunately it's too unpredictable. I've narrowed it down to the fact that it occurs about 1.5 to 2 hours of consecutive playing. Furthermore, I'm not able to replicate this behavior in HID when using Traktor, so I think there's something going on with regards to the hardware/software communication between my XDJ's and Rekordbox.

Has anyone experienced something similar? Is this something that was addressed/corrected in RekordBox 4 (full disclosure, while I've been using RB4 in private, I have yet to use it in a performance setting as I typically wait a couple months before doing so, as is best-practice). Or am I just crazy? :-)

Regardless, I was able to carry-on and playoff the mishaps, though ideally I would prefer to not have to deal with them–my fear being the noise that occurs when the "freeze" happens is could potential zap my lovely audio system.

Cheers.

0) Have you read the "READ ME FIRST" thread in its entirety AND TRIED THE SOLUTIONS THERE before posting: No, it's too long and don't really need help OR Yes, I swear it!
Yup!
1) Operating System: OS X 10.x, Windows 10 / 8.1 / 8 / 7 (Note that Windows XP and Vista are NOT SUPPORTED)
OSX Yosemite (up-to-date)
2) OS Type: 64bit / 32bit
64
3) rekordbox version: (if rekordbox can run, post the version and revision number found under Help > About)
3.2.2
4) Using LINK: No / Yes
Yes
4b) LINK Connection method: DJM2000/nexus or make/model of network hardware + wired / wireless
Wired via Pioneer recommended ethernet hub. XDJ-1000/DJM900NXS
LINK Hardware:D-Link 5-Port 10/100 Unmanaged Desktop Switch (DES-1005E)
4c) Using with CDJs: No / Yes (if yes, list them and their firmware version)
XDJ-1000, DJM900-NXS (both up-to-date firmware)
5) Source Hard drive / Flash drive / SD card file system: FAT16 / FAT32 / NTFS / HFS+ / exFAT
RB via laptop
5b) Connection type: USB3.0 / USB2.0 / USB 1.1 / FireWire / Thunderbolt / Network Share / Other (please specify)
Hub: Thunderbolt to ethernet. DJ gear CAT5 to Hub.
5c) Does the device have multiple partitions: No / Yes / Unsure
No
5d) If it's a flash drive, is it a U3 device: No / Yes / Unsure
NA
5e) With what utility did you format the device: OS X, Windows, HP USB Formatting Utility, Other
NA
6) Export Hard drive / Flash drive / SD card file system: FAT16 / FAT32 / NTFS / HFS+ / exFAT
NA
6b) Connection type: USB3.0 / USB2.0 / USB 1.1 / FireWire / Thunderbolt / Network Share / Other (please specify)
NA
6c) Does the device have multiple partitions: No / Yes / Unsure
NA
6d) If it's a flash drive, is it a U3 device: No Yes Unsure
NA
6e) With what utility did you format the device: OSX, Windows, HP USB Formatting Utility, Other
NA
7) Have you scanned your files for errors: No / Yes
Yes
7b) Have you scanned your drive for errors: No / Yes
Yes
8) Is rekordbox crashing at all: No / Yes
No
8a) If crashing, is it resulting in: an error message OR a crash log OR both (DO NOT POST YOUR CRASH LOG UNLESS REQUESTED!)
NA
8b) If not crashing, are there any error messages: No / Yes
No
9) Are you able to repeat / reproduce the problem: No / Yes
Sort of. I can narrow down when it occurs, but cannot isolate an exact order of operations (see notes in above post)
9a) If yes, can you do it consistently: No / Yes
It's happened that past three weeks at weekend gigs, but again, it occurs between 1.5 and 2 hours of consecutive playing and occurs during random tracks.
10) Does the problem occur with one specific song: No / Yes
No
10a) If yes, please post a link to it:
11) Any other notes regarding your setup only:
My computer is clean and well maintained. I'm a huge tech-nerd so don't sugarcoat anything when discussion things with me. :-)
12) Provide as much detail of the issue here:
See above post.

lostnthesound

Publicação fechada para comentários.

11 comentários

0
Avatar

CORRECTION: First paragraph:
"...a "C" for the hot cue and a bright RIGHT triangle..." should read "a "C" for the hot cue and a bright RED triangle..." Couldn't find an "edit post" button. :-)

lostnthesound 0 votos
Ações de comentário Permalink
0
Avatar

So just to clarify, this is only over the link when using XDJs after 90-120 minutes of use, using the thunderbolt connector (Apple brand?) and a network switch (not a router?)

And when those cue marks are noticed, if you load the track another time, do they still exist or does it only seem to appear after the glitch occurs?

Does it still occur with rekordbox 4.x?

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

Hey @Pulse, thanks for the quick follow-up!

  1. Correct, only over the link when using the XDJs after ~90-120 minutes. Yes, Apple brand thunderbolt to Female Ethernet and yes, a network switch.

  2. That's another strange thing–next time I load the track the phantom cue points are no longer present. They seem to only occur when the error occurs and they're always listed as hot cue "C."

  3. Admittedly, I've been using RB4 primarily on my testing laptop and the longest session I've had with it has been an hour, max. I'll have a little bonding session and put it through a two hour mix to see if I can make the problem happen again.

lostnthesound 0 votos
Ações de comentário Permalink
0
Avatar

If you could test it with RB4, this may be one of those things that if it doesn't happen in the new software, the likelihood of them going back to v3 and addressing an old bug are slim to none.

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

Which is completely understandable. To add, if I manage to get through 2 hours of RB4 without issue, I'm quite certain it's a safe bet that it's "road ready." :) I'll report back. Thanks again @Pulse.

lostnthesound 0 votos
Ações de comentário Permalink
0
Avatar

I had exactly this problem as well a few times now. Sometimes after a few minutes of practice, sometimes after about an hour.
I am using Windows 10 , Core i7, 16 GB Ram, and a Pioneer DDJ SX2.

Gerd Bauersfeld 0 votos
Ações de comentário Permalink
0
Avatar

I have to add that I am using RB 4.01.

Gerd Bauersfeld 0 votos
Ações de comentário Permalink
0
Avatar

Unfortunately, even after upgrading to RB4, I'm going to use another program to rescan my music collection in order to see if I missed anything. I have yet to find a pattern, rhyme or reason as to what could be causing this, so I'm admittedly not much help to Pioneer engineers. If my new scan comes up with anything I'll be sure to report back.

lostnthesound 0 votos
Ações de comentário Permalink
0
Avatar

@Pulse I may have resolved the issue. I've been on Firmware 1.04–I hadn't received any emails/alerts that 1.05 had arrived. I took note of a specific note in the changelog:
"Ver.1.04 (17 February, 2015 Update)
Fixed a freeze issue when loading a track where a comment is
added to a memory cue in rekordbox 3.1."

I have a theory that this is the freeze I'm experiencing, but perhaps it's resolved in 1.05. I'm going to update and give it shot.

lostnthesound 0 votos
Ações de comentário Permalink
0
Avatar

Let me know if that issue persists with 1.05 as well. Thanks!

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

@Pulse Just wanted to provide an update.

I was able to identify the problem: if the user created an "auto-loop" in the cue list (the red loop icon) that was placed within the last :45 seconds of the track AND entered a name for said auto-loop, this would cause the "freeze." While the Firmware (1.05) prevented this from occurring with any new tracks, tracks that still had the auto-loop prior to the firmware update were still at risk. To resolve, I simply viewed the mini-waveforms in the Rekordbox browser to identify waveforms with the red arrow (indicating an auto-loop) present. I then simply loaded the respective track and deleted the auto-loop from the cue list. Since doing this I've had zero issues (knocks on wood).

Cheers.

lostnthesound 0 votos
Ações de comentário Permalink