[SOLVED] Rmx1000 problems
Hi, im getting this message trying to link my rmx to my laptop any help on this would be awesome.
The Rmx1000 is already being used with a different apllication. Data cannot be transferred until the midi device is released.
Post is closed for comments.
Can't find help? Search our Support Site or alternatively, reach out to our Support agents
Suggestion- if you're running a 32-bit version of a DAW only use the 32-bit plug-in... my issue was running ableton 8.2.2 and had the 64-bit version of the plug-in and my CPU would jump to 90% just by touching the RMX1000. Once I switched the plug-in back to the 32bit version it worked well. Also update all your drivers in Win7 cause there was one crucial update that made everything work released from Microsoft in November.
I'm still getting this error message! I have followed all the instructions but still no joy!
Had the device since sept and starting to give up hope! Without being able to loa my own samples into the device I'm not getting the full value of the product!
Gav, I'm still getting the error!!!
Let me know if I need to provide you some info.
I'm running win 7 x64 , no other programs are running ( checked the services and task manager)
Hope this gets solved!!
@maDJam > Thanks for the tip.
Users - please give the 32bit plugin a shot if you are having a problem with the plugin.
@TheOne > Asking the engineers to follow-up.
@DAN > Have you made sure the firmware and software are up-to-date?
I am still having this problem. I use windows 7 64bit ...any help would be appreciated
Update: I tried to connected first to my laptop and i got the error message " The Rmx1000 is already being used with a different apllication. Data cannot be transferred until the midi device is released. " So I then tried to connect it to my desktop which is also windows 7 and still got the same error. Please help someone! I am unable to change the parameters in the software until i clear this error. I am unable to sync.
@Elmer > Try disconnecting the unit from your laptop, shutting down your computer (not hibernate or sleep, a full shutdown) and then start up your computer again. This should work as a temporary work around.
37 comments