Speed editor not working after 17.2.2 update

After updating to 17.2.2 there was a notification to update the Speed Editor. After this update, the speed editor does no longer respond. LED lights are off. Connected via USB on Windows 10. Resolve Studio.
Any way to fix this? Roll back to the previous firmware?

....same here on my Mac mini M1....

I updated the firmware of the editor, made a reset, but does not function....
then, suddenly, it runs, but too much lag, not usable......
much more bad as before.....

Blackmagic, you have to do much homework. ..

HG

Just updated to Studio 17.2.2, and updated the Speed Editor. Both are working as they should, with the Speed Editor immediately connecting via Bluetooth.

Mine didn't work via Bluetooth before the update and it doesn't now. It seems to be working ok over usb, though. iMac (Retina 5K, 27-inch, 2019)

By me it's the same only via USB but not under Bluetooth.

delete the SE in the bluetooth preferences and connect it again

You were right! After deleting it, I got this message box, which didn't show up on first try, and now it works:

Screen Shot 2021-07-01 at 18.50.29.png (178.77 KiB) Viewed 9382 times

Still not working for me with 17.2.2 and its accompanying SE firmware update. Windows says the SE is connected and displays the correct battery level. Upon starting Resolve the SNAP and JOG keys illuminate but Resolve doesn't respond to any keys nor the dial. This has been the case since 17.2. I've tried all the usual stuff (re-pairing, restarting, etc) but to no effect. The USB connection does work as before.

It's annoying that the SE had been working perfectly via Bluetooth for several months up until the exact time I updated to 17.2 and 1.3. This leads me to believe it's a Resolve issue rather than a Windows one.

Before the 17.2.2 update, Resolve would not connect via BT to the the Speed Editor. It seemed to continually try to connect and this slowed Resolve down to where it was unusable. I had to connect to the SE via USB to be able to use DR. After the update (both DR and SE) it wouldn't connect until I deleted the SE in the BT section of Windows Settings and re-paired it. Now it seems (knock on wood) to be working correctly. It doesn't wake up when I start DR, but striking a key or two seems to wake it and after that it works smoothly -- so far (I've been fooled before).

Before I had to make sure I touched keys on Speed Editor before launching Resolve other wise it would not work, Now Speed Editor LED do not light up when Resolve is launched but touching keys brings it to life. That is fine with me. So improvement.

[Dwaine Maggart]

It seems some people don't install the Control Panel code when they install a new Resolve version.

If you've installed 17.2.2, make sure the Control Panels version is 1.6.1.

It should be 1.6 for 17.2.1.

You should not have 1.3 installed with current Resolve code.

[Peter Chamberlain]

And for those with previous BT issues, un-pair the old connection and then make a new BT pair

You should not have 1.3 installed with current Resolve code.

By this do you mean: Speed Editor firmware version 1.3 does not work properly with Resolve versions prior to 17.2.2? Or does "1.3" refer to the version of Control Panel?

[Dwaine Maggart]

1.3 was referring to the DaVinci Control Panels Setup app version.

The Speed Editor software version in the DaVinci Control Panels Setup app version 1.6.1 (for 17.2.2) is 1.4.

So if you have installed Resolve 17.2.2, you hopefully have DaVinci Control Panels Setup app version 1.6.1. And if you connect the Speed Editor, it should prompt to update, and after the update, the Speed Editor should have software version 1.4.

And as Peter noted, if the Speed Editor is Bluetooth connected, you should remove the current pairing connection and re-pair the panel after the 1.4. update.

Hello People

Please refer this below link for reference

viewtopic.php?f=21&t=143923

Hope this may help you

Works great here.

After starting the latest DR update you'll get a pop up warning that there is an update, click ok to start the Control Panels Setup. The SE will need to be connected with a USB cable to do the upgrade, at least it did on my system. It will update the firmware, after that I restarted Resolve and everything worked perfectly.

Thor

Still not working for me with 17.2.2 and its accompanying SE firmware update. Windows says the SE is connected and displays the correct battery level. Upon starting Resolve the SNAP and JOG keys illuminate but Resolve doesn't respond to any keys nor the dial. This has been the case since 17.2. I've tried all the usual stuff (re-pairing, restarting, etc) but to no effect. The USB connection does work as before.

UPDATE:
It's working now. I completely removed my Bluetooth devices and drivers in Windows and restarted the PC. I then re-installed Bluetooth and re-paired the SE, etc.

Have subsequently turned the PC off and on a couple of times and reloaded Resolve. So far so good.

Unfortunately I am also experiencing very laggy response after updating on MacBook Pro M1.

The speed editor connects fine - but there is sometimes a delay of a second after stopping spinning the search dial.

I've paired and unpaired it, and reset it to factory settings...

All works as expected via USB.

To date SE appears now to be working on my pc

I just removed the Speed Editor from my list of Bluetooth devices, ran the 17.2.2 installation, ran the Blackmagic Control Panels app with the Speed Editor connected via USB, updated the Speed Editor to firmware version 1.4, and re-paired the Speed Editor with Windows. It all works great.

For those that are still having issues, I've seen numerous posts now where flaky behaviour has been attributed to a poor radio frequency link between the keyboard and the system, and has been fixed by attaching a WiFi antenna to the motherboard (some of which apparently use that antenna for Bluetooth as well), by adding a Bluetooth USB dongle to the system, or by moving an existing Bluetooth dongle from a rear USB port to a front port that's in closer proximity to the keyboard.

So if you're on the latest Resolve version (17.2.2) and the latest Speed Editor firmware (1.4) and are still having issues, I urge you to look into the possibility of a poor RF connection. You could try moving the Speed Editor as close as possible to wherever you think the Bluetooth antenna is on your system and see if that improves the behaviour. Or you could spend $20.00 and buy a Bluetooth dongle to plug into whatever port is physically closest to the keyboard.

Also note that your system needs Bluetooth 4 or later capability. I'm using a Bluetooth 5 dongle plugged into a USB port that's pretty close to line-of-site to the Speed Editor keyboard over a distance of about 5 feet, and it's working great.

yes, Bluetooth doesn’t work well when there is no direct ‘view’ between computer/antenna and device. I can see this with all Bluetooth devices. For example, remote control for a 8-bulb set of Aputure B7c bulbs shows connection errors for every bulb that is not visible from the controller, which restricts the remote control considerably. Something that Aputure (and all other developers for that matter) do not communicate at all. In their manuals and promo videos everything works smoothly. In real life things are very different concerning Bluetooth connectivity. Not visible devices may work when there is reflective environment, but in nature they immediately lose connection. Something to bear in mind.

I’m sure a poor Bluetooth connection can cause problems.

Unfortunately, this doesn’t explain why the laggy performance only started after updating to the latest version. It was working fine before…

Working fine here on my M1 Mini.

I unpaired the SE before running the update to 17.2.2. I then made sure battery was charged fully on the SE, and paired it with M1 before launching Resolve.

The SE lights came on immediately when Resolve launched, and is performing perfectly - no lagging etc.

After previously stating it seem to work fine today on first Start SE did not light up. It was a case of pressing buttons before launching again. I had previously disconnected and re paired in bluetooth

After previously stating it seem to work fine today on first Start SE did not light up. It was a case of pressing buttons before launching again. I had previously disconnected and re paired in bluetooth

The keyboard turns itself off to conserve battery power if it's inactive for a while. Pressing one of the buttons turns it back on again.

The latest 17.2.2 update seems to solve the problem where you forgot to press one of the keyboard buttons before launching Resolve, in former versions it wouldn't connect and you'd have to start/stop Resolve to get it to work, With 17.2.2 you can push one of the buttons to turn on the keyboard even if Resolve is already running - it will detect and use it as you'd expect.

I Stated its on First start-up of the day therefore a period of inactivity doesn't apply
Therefore IMHO it shouldn't need that wakeup but it does

I Stated its on First start-up of the day therefore a period of inactivity doesn't apply
Therefore IMHO it shouldn't need that wakeup but it does

I would assume that the first startup of the day follows a long overnight period of non-use, during which the keyboard would power itself down. Booting the system doesn't magically wake the keyboard up when it's powered down, hence the need to press one of the keys to wake it up.

I'm speaking to Bluetooth use, of course. This wouldn't apply for USB-connected keyboards.

I agree the change now is that it is not necessary to press keys before launching Resolve. It will wake up fine with Resolve running. So that is fine with me.

Hi Ron
For the first 2 days it did that for me and returned to its old ways
I understand its clever enough to power down after a period of activity but next day it should be clever enough to realise somebody started resolve again wake up ?

Hi Ron
For the first 2 days it did that for me and but thereafter returned to its old ways
I understand its clever enough to power down after a period of inactivity but next day it should be clever enough to realise somebody started resolve again wake up ?

When the keyboard is powered down and not connected via USB it's "dead" - it's not aware of anything going on, including whatever is happening on your computer system. It's not like, say, a smart phone which is actually still running programs even when the screen is off (and using up the battery as it does so). When the keyboard has gone to sleep the only way to wake it up is to hit a key. I just experimented with mine, it didn't seem to respond to the jog dial or to the "In" key - I normally hit the "Stop/Play" bar to wake it up.

If the keyboard seemed before to wake up automatically first thing in the morning it may be that you just happened to accidentally brush against a key before you started to use it.

I agree Sean. When it shuts off nothing is running so neither the PC can see the Speed Editor and the Speed editor cannot see the PC. It is my belief that once you touch a key the Speed Editor powers up, powers its Bluetooth circuits and then can see and be seen. Not sure how long it stays powered up after Resolve is shut down but seems to be less than 3 hours in my tests. Certainly overnight it is off. It would be nice to have the option of shutting down or leaving running ( and of course draining the battery ). I am happy with it shutting down now that it will work by touching keys after Resolve is launched. Having to touch keys before launching Resolve was a big problem.

Here's my experience:

BUG REPORT: Speed Editor Bluetooth Issues after 17.2.2 Update

macOS Big Sur 11.4
Apple Mac Mini M1
DR Studio 17.2.2
SE 1.4

Issue: Everything but the Jog Wheel works. Prior to the update I was on 17.2.1 and everything worked perfectly.

I’ve tried everything I can find in the threads on this topic and nothing works to fix this issue permanently. Whenever I launch DR and press a key on the SE the buttons light up. The moment I use the scroll wheel, nothing happens.

The only workaround is to (1) quit DR, (2) “remove” the device in Big Sur’s bluetooth settings, (3) reconnect it, and (4) re-launch DR. The problem is that it happens every time I launch DR!

This is not a long term solution. BlackMagic, please fix this issue!

I can only relate my experience with Windows. I have only had a non working jog wheel once. Restarting the computer cured it and I haven't seen it since. I'm more inclined to blame the computer rather than Resolve for this and other Bluetooth connection issues that may arise.

When you updated to 17.2.2 did you install the updated Control Panels software as well?

...Whenever I launch DR and press a key on the SE the buttons light up. The moment I use the scroll wheel, nothing happens.

I have only had a non working jog wheel once. Restarting the computer cured it and I haven't seen it since.

Yeah, if you haven't yet rebooted the computer I would certainly try that. I've seen the odd weird behaviour in Resolve that a reboot cleared up. Just one reboot fixed it, it wasn't as if I had to reboot my computer every time I used Resolve.

When you updated to 17.2.2 did you install the updated Control Panels software as well?

I took the firmware update for the Speed Editor if that's what you mean. I updated DR, then when I launched it, it asked to update the Speed Editor firmware.

Yeah, if you haven't yet rebooted the computer I would certainly try that. I've seen the odd weird behaviour in Resolve that a reboot cleared up. Just one reboot fixed it, it wasn't as if I had to reboot my computer every time I used Resolve.

I've rebooted and seen it after the reboot too. It's weird that when I see it, the buttons work but the jog wheel doesn't. I'm hoping someone at BM is reading this thread and will eventually find the software bug. I think it's something with BM software because prior to the update to 17.2.2 and the SE update, everything worked and I never saw any issues.

The only time I've seen the jog dial to be unresponsive is when I have some sort of intensive effect applied to a clip (such as change the clip speed with "Optical Flow / Speed Warp" retiming applied). But that wasn't really a jog dial issue, rather a response time one. But it feels like the dial isn't working and by the time you go for the mouse or keyboard the response finally happens and makes you wonder why the heck the jog dial didn't do anything.

Ron, not the Speed Editor firmware update, the DaVinci Resolve Control Panels section of the Resolve installer. For 17.2.2 make sure it is version 1.6.1.0.

Possibly a faulty Speed Editor or cable. Try talking to the place where you purchased it about a replacement.

[Peter Chamberlain]

It's outside of store warranty. It was also working perfectly fine for months right up until the 17.2.2 update, so I have no reason to believe the hardware is defective. Rather that there is most likely some sort of conflict on a software level.

Can you connect a USB cable and using the DaVinci Control Panels Setup app, see the SE?
if so, what software version is shown as loaded?

it looks like you have a Mac and PC,, is the SE not working via USB on both?

Is 17.2.2 installed?
Did you update the DaVinci Control Panels Setup app during the 17.2.2 install?

One idea is to install 17.2.0, with the matching DaVinci Control Panels Setup app.
check then the connection to the SE.

Publish here your NFO and resolve generated logs as per the FAQs if you have no success.

My Speed Editor is also lagging with 17.2.2 and my Mac Mini M1. Everything was fine before the update and firmware upgrade, but now the dial is lagging. I can't precisely scroll or jog anymore.

I've removed the controller from the BT device list and paired it again but no luck. The control panel is up to date. When I connect the Speed Editor via USB-C, everything is fine again.

You may need to play with the orientation and position of the mini. I've seen problems with other BT devices too.

Anyone have a resolution to this? I am still struggling with this issue.

Anyone have a resolution to this? I am still struggling with this issue.

I am still struggling with this too. I'm now on DR 17.3.1 build 5. What a pain! I'm going to try to uninstall just the control panel and reinstall it but I'm not sure how to do that just yet. We really need some support on this!

[Dwaine Maggart]

With both USB and Bluetooth connections? Or just one or the other?

Bluetooth

[Dwaine Maggart]

What OS?

Have you tried connecting via USB to see if that works, and that it has the current software loaded?

Is there a downside to just keeping it wired? Will I damage the battery?

Thanks

[Dwaine Maggart]

Not at all. If you keep it USB connected, you won't have to worry about keeping the battery charged.

Perfect. Thank you