The ability to customise keys on Speed Editor

I've been thinking about buying the Editor Keyboard for a long time. However, as it is only available as QWERTY and without a Windows key and without Pg Up and Pg Down, I decided in favour of the Speed Editor. However, after a lot of trial and error, I have put it away again.
Remapping would be sooo helpful to customise the SE to ones personal needs. It doesn't have to be everything. You could simply integrate the SE into the existing keyboard shortcut menu and allow existing shortcuts to be assigned to the 9 multicam keys. That would help a lot.

I think everyone here agrees with you but it looks like that this is a business decision for BMD as to whether allowing remapping is ok for them.

I think everyone here agrees with you but it looks like that this is a business decision for BMD as to whether allowing remapping is ok for them.

I can't really understand a business decision that costs them business. I happened to get the Speed Editor for free when I purchased Resolve Studio and having owned it for almost 3 years, I can safely say I would not have paid the extra $100 for this. The only thing I really use it for is the jog wheel, but a DAW controller with a jog wheel that I could also use in Reaper would have been a much better option for the money.

Is there really still no way to customize the Speed Editors keys-layout?!
So annoying to switch back and forth between two keyboards while having all the unused keys (in my workflow).

Especially when BM is making their money off of hardware products, I would think they want to make it as convenient to the user as possible so that it will be compelling.
Is the business decision to lead customers to buy the bigger, more capable Editors? Or is it to drive them to other manufacturers?

Is there any official statement regarding this topic?

Is there really still no way to customize the Speed Editors keys-layout?!
So annoying to switch back and forth between two keyboards while having all the unused keys (in my workflow).

Especially when BM is making their money off of hardware products, I would think they want to make it as convenient to the user as possible so that it will be compelling.
Is the business decision to lead customers to buy the bigger, more capable Editors? Or is it to drive them to other manufacturers?

Is there any official statement regarding this topic?

There are other people making Speed Editor type keyboards that are more flexible. They pop up on this thread occasionally. The problem is that BMD is likely to bring out a revised model that does have re-mapable keys, and leave the current purchasers high and dry. They did this with the first ATEM Mini.

+1 It is so crazy to me the Speed Editor can't have keys customized.

This is an on-going tragedy every... single... day.

What I want MOST OF ALL is "Ripple Trim to Beginning of Clip" and "Ripple Trim to End of Clip". It's crazy that instead you have to hit "Split"... then roll back a few frames with the Wheel.... then click "Ripple Delete". Those three actions could be ONE BUTTON PRESS. Just one! Imagine you are cutting through an hour of footage removing "ummms" and "ahhhs". The whole purpose of the Speed Editor is..... SPEED!

Please RECONSIDER this Blackmagic! Even if you don't wanna open it up at the Operating System level........ can't you make a configuration option inside of Resolve itself? (Just like the Keyboard Customization window.)

Please RECONSIDER this Blackmagic! Even if you don't wanna open it up at the Operating System level........ can't you make a configuration option inside of Resolve itself? (Just like the Keyboard Customization window.)

Exactly. All they need to do is remap the keys inside of Resolve just like they already do for the regular keyboard. They already have that system in place, just do that same thing for the Speed Editor.

With the price increase of the Speed Editor, I will certainly never recommend this unit anymore. It is now more expensive purchasing a Resolve Studio license and a separate DAW controller like the Behringer X Touch One, which has re-assignable buttons, a jog wheel, a motorized fader for audio, and can be used in other applications. With the Speed Editor being so tightly locked down, its severe limitations on the Edit page, you can't use it in any other editor, etc. I don't feel it's worth it anymore. It'd be better to get something else that's more flexible and more useful.

+1 it would be Wonderfull to remap the keys.
Already great to see that speed editor is more supported in V20, but remapping would actually make it useful.
Now I hardly use it, sometimes in the starting phase of some projects.

Please RECONSIDER this Blackmagic! Even if you don't wanna open it up at the Operating System level........ can't you make a configuration option inside of Resolve itself? (Just like the Keyboard Customization window.)

Exactly. All they need to do is remap the keys inside of Resolve just like they already do for the regular keyboard. They already have that system in place, just do that same thing for the Speed Editor.

With the price increase of the Speed Editor, I will certainly never recommend this unit anymore. It is now more expensive purchasing a Resolve Studio license and a separate DAW controller like the Behringer X Touch One, which has re-assignable buttons, a jog wheel, a motorized fader for audio, and can be used in other applications. With the Speed Editor being so tightly locked down, its severe limitations on the Edit page, you can't use it in any other editor, etc. I don't feel it's worth it anymore. It'd be better to get something else that's more flexible and more useful.

All Blackmagic need to do is actually read the posts on this forum. As far as I can see, the reason this has not been done could be due to:

Not knowing that people want this (i.e not visiting this forum occasionally)

Can’t be bothered to do what should be a simple software update

Plan on bringing out a new speed editor with this feature, thereby expecting everyone to scrap their existing unit and pay them more money

Whichever option it is, it does not reflect well on the company for continually ignoring users. This simply cannot be that hard.

If there is a good reason why this is not possible, at least come out and say it and stop ignoring us. If it is a cash issue, just charge an additional fee to add this function. It could be a paid upgrade. Not ideal but at least it would help.

This topic has been raised numerous times. BM, please start showing you care about user feedback.

All Blackmagic need to do is actually read the posts on this forum. As far as I can see, the reason this has not been done could be due to:

Not knowing that people want this (i.e not visiting this forum occasionally)

Can’t be bothered to do what should be a simple software update

Plan on bringing out a new speed editor with this feature, thereby expecting everyone to scrap their existing unit and pay them more money

Whichever option it is, it does not reflect well on the company for continually ignoring users. This simply cannot be that hard.

If there is a good reason why this is not possible, at least come out and say it and stop ignoring us. .

BMD clearly do read this forum as their support people respond on it.

The other two of your options are both likely.
BMD have before now listened to early adopters of hardware EG the original ATEM Mini and then brought out a new version of the hardware with no firmware updates for the original. They also dropped the price of the original and the new one was the same as the original price (from memory) This makes the original virtually worthless with no resale value.

The other thing is BMD have been known to not want to impliment things that people ask for that is in compeditors equipment. There seems to be a "not invented here" syndrom. This has also been mentoined by BMD staff at trade shows.

All that is needed is an addition to the Keyboard remapping in Resolve Studio that also remaps the SE. Problem solved.
Though I have a feeling BMD's answer will be a new SE with no firmware updates to the origional one.

My new theory is BlackMagic mistakenly thinks that opening up programmable keys will allow people to use the speed editor for other competitors’ software. Which A) I really don’t think would be a problem as their DaVinci Resolve is emerging as the best software on its own and B) they could probably still keep it locked in som way if they were so concerned.

But I guess it could be related to this. Just wish they would prioritize the benefits of their users over some fear of competition.

My new theory is BlackMagic mistakenly thinks that opening up programmable keys will allow people to use the speed editor for other competitors’ software. Which A) I really don’t think would be a problem as their DaVinci Resolve is emerging as the best software on its own and B) they could probably still keep it locked in som way if they were so concerned.

But I guess it could be related to this. Just wish they would prioritize the benefits of their users over some fear of competition.

There are already hacks out there to use the SE with other software.
There are already people making other programmable, and in some cases modular "Speed Editors" (see links above)
So the cat is already out of the bag.

AFAIK most people got the SE "free" with Resolve Studio (or vice versa) so I am not sure how many would now buy the SE on its own unless the keys are programmable (with in Resolve). I wouldn't

I think BMD are shooting themselves in the feet. One foot by not doing making the keys programmable and the other foot because (again) they seem to be ignoring the customers.

All Blackmagic need to do is actually read the posts on this forum. As far as I can see, the reason this has not been done could be due to:

Not knowing that people want this (i.e not visiting this forum occasionally)

Can’t be bothered to do what should be a simple software update

Plan on bringing out a new speed editor with this feature, thereby expecting everyone to scrap their existing unit and pay them more money

Whichever option it is, it does not reflect well on the company for continually ignoring users. This simply cannot be that hard.

If there is a good reason why this is not possible, at least come out and say it and stop ignoring us. .

BMD clearly do read this forum as their support people respond on it.

The other two of your options are both likely.
BMD have before now listened to early adopters of hardware EG the original ATEM Mini and then brought out a new version of the hardware with no firmware updates for the original. They also dropped the price of the original and the new one was the same as the original price (from memory) This makes the original virtually worthless with no resale value.

The other thing is BMD have been known to not want to impliment things that people ask for that is in compeditors equipment. There seems to be a "not invented here" syndrom. This has also been mentoined by BMD staff at trade shows.

All that is needed is an addition to the Keyboard remapping in Resolve Studio that also remaps the SE. Problem solved.
Though I have a feeling BMD's answer will be a new SE with no firmware updates to the origional one.

I am sure you are right.i am sure they do read these, I just can’t quite understand why the don’t address points like this.

I have found someone who produces devices which sit between a keyboard and pc, translating commands in real time. If have asked them if this could be used with a speed editor. Ideally you would program it for whatever keyboard short cuts you like. Alternatively, we could come up with 9 commands to replace the nine Cam buttons, which many of us never use. We could then simply produce nine corresponding labels for the keys.

Anyone interested? BM don’t seem interested in doing this so why not.

I am sure you are right.i am sure they do read these, I just can’t quite understand why the don’t address points like this.

Yes, Blackmagic does read the forum, but they don't respond to feature requests and they don't always respond to bugs either. In fact, on one of my threads reporting a bug with the mask input on the merge node in Fusion, instead of simply acknowledging and fixing the bug Blackmagic decided to edit my thread tittle to remove the word "BUG". This bug has still never been acknowledged nor fixed. Why does Blackmagic do this? Good question!

I am sure you are right.i am sure they do read these, I just can’t quite understand why the don’t address points like this.

Yes, Blackmagic does read the forum, but they don't respond to feature requests and they don't always respond to bugs either. In fact, on one of my threads reporting a bug with the mask input on the merge node in Fusion, instead of simply acknowledging and fixing the bug Blackmagic decided to edit my thread tittle to remove the word "BUG". This bug has still never been acknowledged nor fixed. Why does Blackmagic do this? Good question!

Then don't use the word "bug" the word we used in software development was "defect"

Then don't use the word "bug" the word we used in software development was "defect"

Oh come on, the word "bug" is the correct terminology to describe software defects. Do I really need to go here?

https://en.wikipedia.org/wiki/Software_bug
"A software bug is a design defect (bug) in computer software. A computer program with many or serious bugs may be described as buggy."

The software for helping developers find and fix bugs is literally called a "Debugger" (one of the top IDE's IntelliJ/Android Studio even has a "bug" icon in the toolbar to launch the debugger ). The software for monitoring/tracking reported software issues is called a "Bug Tracker". Some even have it built into the name of their product like Bugzilla.

I'm a programmer as well and the word "bug" is the correct term for what I described. There is absolutely no way Blackmagic removed the word bug from my title for this reason. But whatever their reason is (I'm sure they will never provide an answer) all they had to do was a simple, "Thank you, we've confirmed the problem. It has been added to our to-do list and we hope to get it fixed soon." That would have been a much more appropriate response than editing my title to remove the word bug. I reported the bug both in v19 (this is when they broke it as it used to work correctly in previous versions) and again in v20 (this is when they edited my title), but editing my title is the only action Blackmagic has taken on it. Editing my title to remove the word "bug" did not actually remove the bug, it is still there.

Why are simple things like this so difficult for Blackmagic? I don't get it!

Then don't use the word "bug" the word we used in software development was "defect"

Oh come on, the word "bug" is the correct terminology to describe software defects. Do I really need to go here?

If you ever worked on critical systems software you would know the term used is "defect".

BTW Wikipedia is not a credible source defining terms, especially if you have to go to court..

If you ever worked on critical systems software you would know the term used is "defect".

Can you name one IDE or other piece of development software that uses the term "Dedefecter" instead of "Debugger" for tracking down problems in code? Just curious...

This is from Microsoft's Visual Studio, which is the most widely used IDE.

https://learn.microsoft.com/en-us/visua ... ew=vs-2022
Overview of the Visual Studio debugger:
This topic introduces the debugger tools provided by Visual Studio. In the Visual Studio context, when you debug your app, it usually means that you are running the application with the debugger attached (that is, in debugger mode). When you do this, the debugger provides many ways to see what your code is doing while it runs

BTW Wikipedia is not a credible source defining terms, especially if you have to go to court..

LOL! I expected that was coming...

Is Oxford good enough for you?

https://www.oxfordlearnersdictionaries. ... lish/bug_1
bug: a fault in a machine, especially in a computer system or program
The software is full of bugs.
My computer's really slow at the moment—it must be some kind of bug.

So once again, the term I used is the correct term for what I described in my post. And to thoroughly beat this dead horse, even if there was a different term used by programmers/developers (bug is still used by developers by the way) and the word "bug" was only a colloquialism, this is an informal forum used by lots of people who are not programmers so layman terminology would still be used here regardless. This is a non-issue and I do not believe for a second that Blackmagic removed the word bug from my title for this reason.

This is a non-issue and I do not believe for a second that Blackmagic removed the word bug from my title for this reason.

I agree with that. However as I said on life critical systems the word used is defect.
Most "programmers" don't work at this level.

I agree with that. However as I said on life critical systems the word used is defect.

Ok, but we were talking about my bug report on the Resolve forum. You said not to use the word "bug", but my point is that was not the reason my title was edited. I used the correct term to report my bug. It's not just used colloquially, it is also used by developers and by the tools developers use to create software. And I still bet that the development tools used to create your critical systems also uses the term "Debugger" and not "Dedefecter".

And I still bet that the development tools used to create your critical systems also uses the term "Debugger" and not "Dedefecter".

Static Analyser
Dynamic Analyser
In Circuit Emulator

Just grabbed a few top Google results for "static analyzer definition"

- "Static analysis, or static code analysis, is best described as a method of debugging that is done by automatically examining the source code ..."
- "Static analysis, also called static code analysis, is a method of computer program debugging that is done by examining the code without executing the program."
- "Static analysis is the process of analyzing source code for the purpose of finding bugs and evaluating code quality without the need to execute it."

So again, no problem with using the word "bug"... it's fine.

Just grabbed a few top Google results for "static analyzer definition"

- "Static analysis, or static code analysis, is best described as a method of debugging that is done by automatically examining the source code ..."
- "Static analysis, also called static code analysis, is a method of computer program debugging that is done by examining the code without executing the program."
- "Static analysis is the process of analyzing source code for the purpose of finding bugs and evaluating code quality without the need to execute it."

So again, no problem with using the word "bug"... it's fine.

that is why you are just a programmer.

that is why you are just a programmer.

Wow, what a substantive response! You were the one who told me "don't use the word "bug" the word" on my bug report thread. I used the correct term "bug" for my thread and I backed up my usage of the word in multiple ways. You have yet to provide a single good reason for why my use of the term "bug" was a problem which warranted getting edited out by Blackmagic. For the last time (hopefully?), I used the correct word and this is a non-issue.

Why is this a discussion? And why say “that’s why you’re just a programmer?” This is neither substantive nor useful. C’mon.