I'll spare you all from sending the full crash reports (Unless some kind soul can help to make sense of them?). I don't know how to read or understand Mac System diagnostic crash reports, but both reports for both crashes have similar errors. Yet, 2 weeks in a row, I've suffered a crash with Serato while performing live. ![]() Important to mention, I've stress tested Serato DJ while plugged into Serato Hardware for periods of 15 hours and up over the past week to see if I could replicate the problem. I plugged my cable into the other USB port on my computer, in the off chance that there was something wrong with the USB port. I restarted my computer, plugged back in my USB cable (again, a different cable than the one I used with the crash last week) and restarted serato, and thankfully, I was able to play for the final 2 hours without another crash happening. ![]() The 2 tracks that I was playing are not corrupt, and I have played them hundreds of times over the years. About 3 hours or so into my set, the music stopped out of nowhere, Serato froze and then shut down with another notification that it was forced to quit. While tonite I was using a different version of Serato DJ, and a different hardware connection (DDJ SX2, instead of Pioneer DJ DJM-900NXS2 Mixer), the circumstance was the same. Since last week, I decided I would downgrade to what some have said was a more stable version of Serato (2.4.6), and I cleaned out some hard drive space, changed USB cord, and was using different equipment (Pioneer DDJ SX2 Controller) Now, here is the info from my 2nd crash earlier tonite: Could anyone help to shed some light?! Thanks! I’ve submitted a crash log to serato, but still waiting to hear back from them. I’m at a loss as to what could’ve happened. Important to me mention, I worked at the same venue the following day, same computer, same equipment, same 2.5.5.83 and played a 3 hour set, and everything was fine. Has a crash happened for any of you on 2.5.5.83? Could this have just been a freak occurance? Should I revert to an older version? And which would be best? Could a wonky hub momentarily messing up cause Serato to force quit? Is it possible for analyzed files NOT flagged as corrupt to still be corrupt, even if you can’t duplicate the problem with them after the fact? The night that it happened, i was using the gear at the club, which was 2 CDJ-2000NXS2's and a Pioneer DJ DJM-900NXS2 Mixer, using HID mode connected to an Anker USB hub. I had a usb stick on hand that I quickly switched to while I unplugged the usb from my mac, restarted my comp, plugged usb in again, launched serato, and played for another 2 hours or so without a problem, albeit while walking on eggshells. I’ve since stress tested those files for hours trying to duplicate the problem, to no avail (I also have ZERO other corrupt files in library). The 2 files i was playing at the time were analyzed, not flagged as corrupt. ![]() I’ve been using Serato legit since 2007 and never once (aside from an old wonky computer i had) has serato actually crashed on me during a live gig, until this past sat.Īfter already playing for about 3-4 hours, all of a sudden the music stopped, no warning, serato screen was frozen, waveforms etc, then spinning beachball appeared followed by “serato quit due to unexpected error” or something like that. Last week with 2.5.5, and last nite with 2.4.6. I have suffered 2 Serato DJ Pro Crashes in 2 weeks while playing live.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |