Shortcut to start playback in Cinema Viewer

It would be great to be able to configure a single stroke shortcut to bring up the Cinema Viewer mode and immediately start playback.

Also, in Cinema Viewer mode the up and down arrow keys should serve to jump back and forth between edit points just like in all other modes.

With a second monitor and using Video Clean Feed playback is one keystroke, the up and down arrows work, and a full screen picture is displayed for all of Resolves pages. The Cinema viewer is just that, a viewer.

Video Clean Feed on the Edit Page.jpg (323.06 KiB) Viewed 990 times

Video Clean Feed on the Color Page.jpg (367.17 KiB) Viewed 989 times

With a second monitor and using Video Clean Feed playback is one keystroke, the up and down arrows work, and a full screen picture is displayed for all of Resolves pages. The Cinema viewer is just that, a viewer.

Thanks, Charles. I do have a permanent Clean Feed, but onto a smaller 4k monitor, so I still find myself using the Cinema Viewer quite frequently.

The requested feature would also benefit single monitor setups as well as on-the-go laptop use.

The larger issue is should there be a way that Resolve acts EXACTLY the same keyboard-wise whether or not the screen is being used to display just a picture feed (i.e. using Cinema Viewer).

This is extensively discussed in viewtopic.php?f=21&t=163480

Charles - suggesting extra hardware is fine as a workaround but hardware is not an easy workaround and is unreasonable for a whole class of users: those using laptops where they actually travel rather than just editing in one place.

I don't look on having a second monitor as a work around, more as a practicality.
However, if I have Resolve single screen and open the timeline Cinema viewer, not only do the JKL keys work, but the up and down arrow keys do as well. The only thing you haven't got is playback starting automatically.

...but the up and down arrow keys do as well....

Thanks for insisting here, Charles! There seems to be a quirk in the interface in that it depends on where you last clicked before calling up the Cinema Viewer. The (only) way to make the up and down arrow keys work inside CV appears to be by first clicking inside the Viewer area. Not ideal, because I always need it from within the timeline, but definitely a valuable workaround for now (hopefully). I also miss being able to enable/disable the selected clips inside CV.

I realize there have been forum debates on the logic of the UI, but in case of the Cinema Viewer from within Edit, I can see no benefit in the way it currently behaves, particularly since CV does behave as expected from within the Color page (not only regarding said arrow keys, but also enabling/disabling nodes, etc.), regardless of where the user last clicked.

Regarding this post's subject line, it would be great to hear if anyone else might welcome a "Play in Cinema Viewer" shortcut.

That is a strange quirk as here switching from the Edit page to CV the up and down arrows work straight away with no other action needed. They also switch between clips in the Color page.

That is a strange quirk as here switching from the Edit page to CV the up and down arrows work straight away with no other action needed. They also switch between clips in the Color page.

Thanks again, Charles. So if you mouse-click in the timeline to set the playline somewhere and then immediately open the CV you are able to jump back and forth between edits? Using the up and down arrows?

I was basing my answer on what happens when I open a project. The action seems to be inconsistent with it sometimes working and sometimes not. To not have to use the mouse to click on the viewer double click the Q key before opening CV.

in Cinema Viewer mode the up and down arrow keys should...

viewtopic.php?f=33&t=120056

Thanks, Charles! I may decide to set up an AutoHotkey macro to rattle off "QQ - CTRL+F - K"

And thanks, Jim! Good to know I'm not alone on the Cinema Viewer's shortcut behavior (should have searched the forum more thoroughly).

I still hope this post's main request (subject line) might find support as well.