I’ve been loving my Live 4 since I got it about a year ago. But about a month ago (possibly after the latest fw update), it started rebooting automatically overnight.
I usually keep the unit on for extended period of time (2-3 days at a time, when I work on prep ahead of a gig), and most mornings I find the prompt asking to load my DJ settings, and whether I want to load the Rekordbox library from the SD card. I’ve only ever seen this prompts upon reboot, or inserting an SD/USB into the unit.
Yesterday afternoon I loaded a track and played on Continue mode, which went on automatically well into the night. However this morning the unit looked like it had rebooted judging by the prensence of those 2 prompts again (and not playing).
I would hate for this to happen at a gig. Is there a log file or other way to see what may be causing this condition?
And should it not only restart while on standby? In my test, it seemed to have rebooted while playing (albeit I wasn’t there to witness), I had it playing with Continue mode on, on a long playlist. Looking at the history this morning, it had only played a third of the playlist tracks before rebooting.
This type of device is not designed to stay on 24/7, so it’s never a good idea to leave it on non-stop anyway. You risk premature wear of the internal components.
I guess this is caused by the latest update, since there already were people reporting device crashing and rebooting during some time in specific undetermined conditions
I edited my post to clarify what i meant by keeping the unit on. It’s not on for months on end. But I do keep it on when I work on gig prep over multiple days to not lose where I’m at in the flow.
I’ll also add that I’m less concerned about the unit rebooting on its own, than the timing of that reboot being in the midst of a set. That would be a huge problem!
Hope someone can help me identify a way to look at log files. There may be some hint of what may be the reason, even if it’s to say all-normal system reboot (if that’s indeed expected behavior, although I never had this issue before the last update).
I think 4.2 is the earliest you can do without rebuilding your database on your desktop.
I went back to 4.0 on mine and I hadn’t backed up my library so I had to do a full new import from Serato and start again. Currently repairing grids and setting my cue marker on the first downbeat as I DJ. Luckily I don’t use quantise so it’s not a massive deal if they are misaligned etc,
Downgraded to 4.2 yesterday and the problem is gone. Not a single crash in the last 24hours. Prior to the downgrade, I was experiencing reboots multiple times a day.
Thanks y’all for your guidance! And I hope Denon DJ fixes this problem in their next release!