I have been posting for over a year now about issues I'm having with my CDJ 2000's, DJM 2000 and Rekordbox either freezing up when you load a track or tracks just stopping during playback and they players needing to be power cycled in order to correct this. At one point it was decided that renaming the Pioneer Artwork folder would solve this issue until it was fixed by the engineers. This worked until I updated to Mac OS 10.8 at that point the issue returned even with the artwork folder name change. I was told by Pioneer that OS 10.8 was not supported and I would have to wait.
I have now waited over 5 months and decided to update all firmware and RB software to the most current version and bring the artwork folder back. I would hope that the engineers would have fixed that obvious bug that was discovered almost a year ago. So I played on Saturday night for 3 hrs and both players STOPPED for 3 sec and then would play for 3sec and then stop again! I would like to point out that the players did not do this at the same time it would happen to one deck and then a bit later to the other in no particular order. This happened a total of 3 TIMES! I finally put in a cd and changed once again the "Artwork" folder to "Artwork-temp" so it would not be recognized by RB. The last 45min of my set was ok but I have no idea at this point if the artwork folder had anything to with the issue or not?
IS THIS EVER GOING TO BE FIXED? Am I the only one that is having this issue?
Post ist für Kommentare geschlossen.
this thing happend to me also after updating from 2.0.1 to 2.0.2 and 2.0.3 on ml 10.8.2. the biggest mistake is updating a thing that's works like i have done. try to first open rekordbox and after that plug the network cable. sometimes it crush ml and i have to force it to shut down (i keep the power button pressed ).
@Dustin > I'm very sorry to hear you had issues - particularly in a live audio environment. Did you happen to make note of any particular tracks this issue happened with?
@Dustin > Any update for us?
I wish I had a solution to update you with. Unfortunately what I have found is that I cannot have the artwork folder showing and certain files will sometimes cause this issue and sometimes they won't? I took the three track that caused the crash and played them over and over for about 45 min and had no issues so I gave up on that. What I do if this happens during a gig is quickly turn of the deck that is starting to freeze up and turn it back on if I have enough time I wait for it to link up again and keep going, if i'm crunched for time I load a song off the backup cd that is in both decks and keep the music going. I wish I had more to report. Any news on your end when they can get this as solid as other programs like serato? I play once a week downstairs at my other club that has two 1200's and a serato box and have never had this issue with any files.
@Dustin > I believe the next rb update does include a fix for handling artwork issues.
Thank you Gavin, that will be great! Unfortunately on Saturday night I had another start and stop issue during playback with the song that was playing live. It has been some time since that has happened. Usually the song i'm cueing starts to mess up and I have learned to just immediately power down the player that is having the issue and reboot it. Doing that will fix the problem on the malfunctioning deck and keep the playing deck from crashing. Saturday night unfortunately the deck that was playing just out of the blue started to fail. I cut to the other deck (luckily I had a track cued) and powered down the failing deck. This should have had nothing to do with the artwork since the art work folder was renamed "Artwork-Temp" and not being seen by RB. I will attach the track that malfunctioned. It is an older track and I'm not sure of it's origins. I do want to add that I have played it before with no issues and have never had an issue with it on Serato. It would be great if RB could analyze and highlight files that have issues with playback. I would rather have to replace tracks than have failures like this in the future. Again thanks for the update!