No announcement yet.

Shuttle Pro V2 and DaVinci Resolve 16

  • Filter
  • Time
  • Show
Clear All
new posts

  • Shuttle Pro V2 and DaVinci Resolve 16

    As I'm a small 'one man band' user I'm not sure I'll be able to spring for the Resolve keyboard when it's launched in August as a grand is a fair bit out of my budget.

    I'm on the verge of moving over from PremierePro for a lot of reasons, but the new 'cut' page was just up my street.

    So, I thought I'd fire up my Contour ShuttlePro V2 jog shuttle controller (that works flawlessly in Premiere) and see if I could map some buttons to the superb new features in the Cut page of Resolve 16.

    Sadly though it seems BM must have blocked use of this device as even with specialist or global settings it just does not work. I'm pretty disappointed, and it's definitely a barrier to moving over as the shuttle is a superb piece of low-cost kit.

    Does anyone have any workarounds, or confirmation that there's no way of using this inside Resolve 16?

    I'm on latest software, and have tried Countour's latest settings download.


  • #2
    That would suck if functions were actually blocked, and how would that work in that the device just remaps keyboard controls. Hopefully it's just a beta glitch.


    • #3
      works fine for me.... i have one attached to my home machine, but i have Artist Color and Transport at home as well, so no need for the Contour anymore

      they have a default Resolve mapping for both shuttle and mini on their site somewhere, but it's so easy to roll yer own with their software that i just did it myself, works very well


      • #4
        I'm on Resolve 15.3 and using the Shuttle Contour V2 with it with no issues. I have all the buttons and jogger mapped. I hope it will work with 16 when it comes out. I'm not on 16 and don't usually upgrade until it is GA.


        • #5

          Seems to be an extensions problem on the iMac, or High Sierra. Works fine on MacBookPro with Mojave.

          Might just have to bump the iMac up to Mojave and see if that solves anything.


          • #6
            no issues on w10 + v16.0.b1