Speed Editor Support for DR16???

So I scoured the BMD website, looked for a manual to DL and eventually found my answer on a third-party website.

So the neat little Speed Editor ONLY works on beta software? BUT, if you move to the beta software forget about any support if you run into any problems! I've been stung on that when 16 was in beta working on a project I ran into a problem and support refused to troubleshoot the issue. Instead, they requested I thoroughly document the issue and post it on here. In the meantime, I had to restart the project in v15 from scratch. So no, I won't be moving a current project to a beta version again, thanks.

So now I have this cool little piece of hardware that is essentially a paperweight until 17 comes out of beta which could be months for all we know.

So my questions are the following:

1. Who thought this was a good idea?

2. Why wasn't there a bump to 16.2.8 to provide support for the new editor KB?

3. Why wasn't there a notice included in or on the box stating v17 support ONLY?

For crying out loud, DR v16 was included with the purchase which you can't even use it with!!

AND, It just dawned on me that the full editor keyboard works in v16 so why does the speed editor not?

Back to work....

PS Ordered list items on here don't work.

Does no one else want to see the speed editor in v16?

I watched the introduction on all the new items on the You tube video and it clearly stated to me the Speed Editor was only for 17 and also for the CUT page. Grant spent a lot of time demonstrating and talking about it. I am happy with 17 so I have no interest in it working on 16 as that for me has gone to the past.

Seems reasonable to conclude that 16 would need an update for the Speed Editor to work.

To my thinking, it makes a lot more sense to devote those programming resources to pushing 17 towards Gold than to spend them on updating 16.

Yes. You wait until 17 is out of beta. BMD clearly considers the Speed Editor to be part of the 17 beta process, so that’s why they’ve made it available before the17 GM.

Part of the responsibility of running a beta is accepting that you may/will have problems with the software, and taking the time to thoroughly document and submit those issues to BMD so that they can investigate and fix the issue. If you can’t (or don’t want to) do that, then the beta is not intended for you.

Why is this so difficult to understand?

Also, the reason Resolve 16 was “included with the purchase” is because you need an activation key to run the Studio version of 17beta.

ok, wow. I was hoping for a little more understanding about releasing a product that doesn't work with currently released software. I was really interested in hearing from those that shared my view that this should have been released with v16 support from the get-go. I certainly didn't invite others to try and point out that I'm supposedly stupid for "not getting it".

As SkierEvans pointed out. There was one reference to being supported only in v17beta. Nowhere else was this referenced or clearly spelled out. So if you missed that 2 seconds somewhere in the 2-hour live stream where it was said, there was no other way to know this. IMO, this is not sufficient to inform a customer base.

@Mel Matsuoka - This is not a question of whether I want to work with beta software. That's beside the point. The point is this piece of hardware only works with beta software. That's like selling an electric car before the batteries are widely released and if you do buy those batteries, your car may explode. [But if it does explode, do jot down anything you saw when it happened so we can stop that from happening to other people.] Some kind of notice should have been added to ether the box, as in a sticker; or a notice put in the box clearly stating v17beta support only. That's all.

Maybe I don't know for sure but it seems to me that the speed editor is simply half of the editor keyboard. Other online reviewers have said the same. That editor keyboard already works with v16. The software and key mapping are already there. There's really no deep development to be done. Now if you were to ask me which is more important, speed editor in v16 or once and for all fixing the beyond horrendous keyframe and easing support in Resolve. I'd jump on keyframes and easing control in a heartbeat.

PS. I just re-watched the speed editor section of the stream and it was said ZERO times that it was supported only in v17beta. If I just missed it (again, which is my point) please point out at which point in the stream it was said.

you can try to open 17, see if this works then try to downgrade to 16 ans see if this works.

I agree with Jim to cut to the chase and only work on 17 onward from now on...