"Failed to open the device" Cannot SYNC

[ricvdb]

"Failed to open the device" / "Firmware update Error - Failed to open the device"

I'm getting these messages when I try to sync or update the firmware in MCC (as described in the stickied post).

It seems MCC recognises when the device is connected, but I can't sync or update firmware.

Any ideas?!

[teceem]

Do you have any other program running when this happens?

[ricvdb]

Nope, nothing!

[theotrst]

same to me.

(OSX 10.9.2 / Mavericks)

my beatstep when is plugged/unplugged to computer does not turn on the left side PADs (to enter in the firmware update mode).
I try to remove the device from "Audio MIDI Setup" as suggested, but in the MCC did not work (the sync and the update of firmware).

any help?
thanks

[alterationx10]

I am having the same issue. It works fine on my Macbook Pro, but not on my iMac (both running OSX 10.9.2).

[theotrst]

just a question for those who can correctly connect Beatstep to MCC:

when beatstep is plugged, does it turn on the left-side LEDs?

(mine doesn't. And I succeeded to go into this "update-mode" holding START/STOP buttons when is plugged)
Anyway I continue to have the communication problem: no update, no syncronization.

I asked to technical support... they suggested:

If you encounter any connection problem with your computer and your Hardware. Start by following those steps:
Reboot your computer
Try another usb port / preferably on the back panel of the computer
Try another usb cable
Try another Computer/OS


 
any suggestion?

thanks

[theotrst]

I succeeded! I had problem with USB socket,...here the my procedure:

(for my MacBook Pro (OSX 10.9.2) one USB socket did not recognize the BS and names in the "Audio MIDI Setup" the device as "Device MIDI/USB". The other one works fine (for me) and 'see' the BS device as "Beatstep Updater").

-plug the BS (holding START/STOP buttons).
-open MCC and "Audio MIDI Setup":
1) go to MCC and click button for Firmware Revision. MCC asks to locate firmware file, then it asks for unplug.
2) unplug the BS.
3) go to "Audio MIDI Setup" and remove the device named "Beatstep Updater"
4) go back to MCC, plug the BS (holding START/STOP buttons).
5) it works and you can sync.

thanks Dav1d.
 

[xmota]

Same problem here. I have tried several USB ports and hubs on my Mac Pro, no success

[A.C.]

Unfortunately I'm on MacOS 10.6.8 and MCC is not supported.

I've tried to set it up on a Mac Book Pro under 10.7.4 but MCC didn't recognize the BeatStep. It was shown listed as many other Arturia devices but didn't show as connected. MIDI window did show the BeatStep so usb connection was working right I guess.

I'll update to Mavericks in a week or so, and cross my fingers...But there seems to be too many problems to us Mac users

[Jerome Arturia]

A.C.:

If you encounter any connection problem with your computer and your Hardware. Start by following those steps:

Reboot your computer
Try another usb port / preferably on the back panel of the computer
Try another usb cable
Try another Computer/OS (if possible)

Best,

J.

[aaxon]

I'm getting the "Failed to open device" message too.  The problem persists after reboot, changing cable, and changing USB port.  I able to read midi messages sent by the BeatStep hardware on the same computer with Max6, so the basic hardware is working.

The MIDI Control Center software shows the BeatStep connected, but does not synch with it, update it, or reprogram it.

Computer is a mid-2012 MacbookPro with OS X 10.9.2, Intel Core i7, 8GB ram.

[theotrst]

@AAXON:
how is it labelled in the Audio MIDI Setup?

[jeffreyjames]

I was pulling my hair out about this. Oddly going to vew>midi console made it work. No idea why.

[gabriel chicoine]

I'm also having the "Failed to open device" syncing issue. I'm running a 2013 Mac Mini (quadcore i7) with OS X 10.9.2. Audio MIDI Setup doesn't find the device in any USB ports. I've tried all of the methods suggested in this forum (excluding trying a different computer, which is a total cop-out, guys). Different ports, rebooting, trying to reinstall the firmware (which also doesn't work, by the way). Please help!!

I understand this is a new product and there will be some connectivity issues that need to be sorted out, but it's very frustrating to get a new piece of gear and have to spend several hours troubleshooting before even getting to use it. Especially since I've been waiting months for this thing to come out since the original launch date in March. 

[sendhelp]

yup. no dice