BUG - device lockup

[megamarkd]

If you really want to try 2.0 just make sure you backup your projects, just in case anything crazy happens. Otherwise you can always revert back to your stable version of the firmware that you're running now. I'm confident that there will be a quick fix for all these issues.
Peace.

Cheers for the reply and the gentle prod to move forward!  I know I want to, just last post about it breaking the machine really worries me....

Your user name is a palindrome!

[ben arturia]

Hi Guy,
I'm really sorry to hear about those issues.
I think that the bug comes from the previous firmware and not from the 2.0.
What you can try is :
- Back up all your project with the MidiControlCenter
- Reset you BeatStepPro to factory default.
=> Press PRST LINK/<</>>/LST STEP while booting the BSP
- Store your projects back

Please please let me know if it fix your problem.

[I grec]

Hi all,
Did you update your MCC?
When you perform the firmware update, the last MCC version is MANDATORY! Otherwise, your sequences are corrupted due to former MCC not knowing polyrhythm for instance.

Best,
Y.

[I grec]

Could different build date for the hardware make any difference to the firmware?

-> no.

[I grec]

One more thing, if you are in the case you did:

• No MCC update
• An update to FW v2.0.0.2
• Backup sequences into the MCC
• Reset factory
• Recall of your sequences from the MCC

You are going into troubles...
Please be sure perform the MCC update. Then do a reset factory. Then call back again your sequences from the last MCC.

Hope this help.

Y.

[ozmic]

I used the MCC and shut it down then restarted the BSP and got this (see video below) until I unplugged the USB cable from my macbookpro.
Then the BSP booted normally, but everything was wiped. But the drum map was the same as the one I set up earlier.

https://flic.kr/p/W6rFZY

I  just tried the same procedure again (although for ten minutes as opposed to an hour) and it functioned normally when rebooted.