"New Update Available!" message results in music playback stopping and ignore option does nothing!

Engine DJ Hardware Media Players
,
1

Did an event up on Mt. Hood this weekend that went really well. Lots of Rekordbox DJs that put their USB sticks in, chose “updated database”, and then were impressed that all their playlists/hotcues got imported. Everyone was impressed with the SC5000 decks and loved playing on them instead of Pioneer. There really were no issues…

Except one issue… THREE TIMES the decks popped up an “A new firmware is available” and just stopped playing music during the message. One of the decks just froze and wouldn’t respond after showing the message. Apparently clicking the “ignore” option, does not actually make it be ignored either as it prompted twice more!

Anyway, it’d be great if InMusic could make it so that there is no interruption in playing when providing these messages, or at a minimum make it so the “ignore” button actually disables the messages completely. We had to stop playing on the decks and do the updates to make sure we felt safe playing the rest of the event.

PS - We went from version 1.6.1 to 2.3.2 (we kept waiting for another 1.x release) so maybe this is fixed already…

2

I’ve only ever had that pop up after initially powering up the prime 2, are you sure there wasn’t a blip in the power supply to the units that caused it to reboot, or lose power momentarily?

1 Like
3

Absolutely sure that they did not lose power plus when they lose power they always tell you and give you a few seconds before they shut down

1 Like
4

Fair play, sounds like a proper issue. Hopefully someone who owns them can chime in with a workaround/solution.

5

Hi @sovamind - Glad to hear your event went well and sorry to hear of the update issue.

To confirm, the firmware update dialog should never interrupt the audio stream in normal conditions. When you experienced this, were your SC5000 units running v1.6.0?

6

I believe they were both running 1.6.3.

7

1.6.2 was the last version prior to 2.0, so maybe that was the version?

We have made several improvements to OTA updates including the update dialog since 1.6.2, so it is likely this could have been fixed already, but we will keep our eyes open for the issue.

Hopefully you won’t encounter the behavior with the latest firmware, but please keep us posted if you do.

8

Must have been 1.6.2 then as we updated to the last version of the 1.x code but were waiting for the 2.x code to be more deployed / stable. Now we are on the latest so hopefully this issue is fixed and won’t come back.