Speed Editor Troubleshooting R17b9 Windows

Hello!,

I can see my Speed Editor connected in Resolve Preferences, as well as the Control Panels application.

The jog wheel is not doing anything and the console does not light up.

please see youtube video below:

viewtopic.php?f=21&t=125567

Speed Editor will not connect to Bluetooth if it is plugged in with USB C. The other thing to mention is that all previous versions of Resolve must be uninstalled before installing any version after Beta 5. I would uninstall all Resolve version including panels. Then install Resolve 17 beta 9( latest version ) and see if it then all works.

And for first run (I think) the Speed Editor needs to be USB connected to Resolve for a few hours / overnight to charge the battery. After that I've found it can be charged on a phone charger etc. separately but mine needed the computer for the first one.

PS It works best on Bluetooth 5 too. Stronger signal, better range, less latency. I just bought a decent BT 5 dongle

Thanks everyone, I'll post in the R17 beta forum next time.

I uninstalled Resolve, and Re-Installed as the per the comment about a clean installation. Still no luck, same results.

Any luck yet? I have the exact same problem.

Tried a fresh install of beta 9, as well as beta 8. Also tried installing beta 9 on a PC that hadn't run Resolve before, but the Speed Editor behaves the same.

Currently have an email out to BM support.

I did another installation of R17b9 and... the Speed Editor works!

Not sure exactly what needed to be done.

I had my wired network unplugged during the installation, that was the only change in my setup. Perhaps that was a component required to get the wireless connection to work.

Anyways, I am happy.

Man, I wish the fix was that simple for me. I have now fresh installed 17beta9 multiple times, and tested multiple computers. I tried disconnecting my network connections first, but that didn't seem to make any difference. I even checked any Bluetooth device within range to make sure a rogue device hadn't managed to pair with the SE and block input to the connected PC.

There's really nothing else you can think of that was different the time that it finally worked? I am not thrilled about paying shipping fees to RMA a device that worked for just a few days before it died.