@DJ Philter > How many tracks would you say have got a point where the waveform stops like that? Have you tried re-analysing that one file? What is the filetype?
I was just playing around with Rekordbox DJ and noticed that one of my tracks froze when it reached the point of no wave form on the screen. Not sure what I did but I was playing around with various effects. Running the trial version on Windows 8.1 64-Bit. Please see attached image. Thank you.
Please sign in to leave a comment.
@DJ Philter > How many tracks would you say have got a point where the waveform stops like that? Have you tried re-analysing that one file? What is the filetype?
I would say 3 or 4 tracks until this happened. I know I had just opened Rekordbox DJ and was playing around with it for less than an hour and this happened. I just stopped playback and reloaded the track into the same deck and then it was fine. The file type is an MP3.
Kind of an odd glitch. I know when hitting the hot cue points on longer tracks like this one which is 7 minutes and 41 seconds, the waveform has to reload but maybe there is a glitch in with that? Some kind of memory leak? Not sure but just an idea. I know my computer isn't lacking in performance. Intel i7 with 12GB of RAM.
Here's an interesting thought about the image I posted, maybe it's something obvious but the original BPM of the track in deck 2 on the right is 121.99 but the original BPM of the track on the left in deck 1 is 74.02.
I had originally synced the left track, deck 1, to the track on the right, deck 2. I must have stopped playback of deck 2 at some point which made deck 1 the Master deck.
If the pitch range is set to + & - 6%, how was I even able to adjust the tempo down to 114.6 or 54.9%? Did I do something obvious to do that? Is this a or the possible bug that caused the audio wave form of the track in deck 2 to "lose" its wave form and then stop playing at the point shown in the image?
Just another idea for your team.
Thank you again.
I was playing around with my new DDJ-RZ on a MacBook Pro El Captian OS and had this same problem happen again. It happened with the same file but at a different location and hitting a different cue point fixes it but still kind of an odd problem. Maybe it is something with the file but could also be something else.