DR16.1.2 playback scaling issue

DR16.1.2 playback scaling issue

Computer Mac Pro 2013 8 core, 32 memory, two D-700 GPU cards, two thunderbolt monitors.

Timeline setting HD 1920 x 1018

Source footage 4k Arri log

Playing timeline or source image in GUI viewers or hero monitor video is zoomed into HD area of 4k frame.

Is there a new setting to click?

thanks,
Jim

I did some more testing.

Input scaling appears to not work. Set to: Scale entire image to fit.

Computer monitor system:
Hero monitor Sony HD PVM 250 connected by BM UltraStudio Mini
Second Hero Sony HD PVM monitor connected by Video Clean Feed

What works...when with 4k UHD source footage

Project settings > Master Settings >Timeline setting 3840 x 2160 UHD When the "timeline resolution matches the source resolution at UHD" video plays scaled correct from source play and timeline. Image is scaled correct in GUI viewers and Video Clean Feed

To correct Ultrastudio hero image
Project settings >Image Scaling > Output scaling: uncheck match time scaling > set Output HD

Anyone else find workarounds?
I rarely finish 4k but originate in 4k for HD timeline.

Thanks,
Jim

What is your Project Settings --> Image Scaling, Input Scaling, Mismatched Resolution Files? And Output Scaling, Mismatched Resolution Files? My (default) values for both of these is "Scale entire image to fit".

Suggest posting a screen capture of the entire Image Scaling panel of Project Settings, maybe someone can help.

The video link shows the issue.



Thanks,

I've confirmed this anomaly with Arri UHD footage, from the LF. No idea what's causing it. It's not seen with UHD footage from other cameras, in the same project with the same preferences.

This is one for BMD....

Is it ProRes or ARRIRAW that's the issue? (Or both?)

Is it ProRes or ARRIRAW that's the issue? (Or both?)


You have found the conflict!! This Arri ProRes footage is from an old project that worked in past Resolve versions.... if did find other UHD footage including BM and it scales correct.

Now what do I do to correct?

thanks,

OK.

It's certain the clips are set to Project in their Scaling? That's not been overridden in Clip Attributes or via Inspector?

Only scaling in the project. I did try a zoom in the inspector but still the issue.

Footage is Arri Log. I'm going to record a clip with the Amira without log for a test, stand by.

As reported by John, Arri UHD has issue.

I do not have raw license. Different flavors of Arri ProRes did not make a difference, HQ, 4444 in UHD. Stepping down to 3.2k (3200 x 1800) works well.

As I stated in earlier post I do have a workaround in setting the timeline to UHD but would prefer setting a HD timeline as it allows me to zoom in the inspector.

Jim, I'm having the exact same issue after installing 16.1.2.
Anything at 3200x1800 plays as expected. UHD does the scaling thing.

Thanks for the workaround, but I'm sure you will agree we need a fix for this fast.

Try going into Preferences>User>Playback Settings and choose Manual with Optimize Sizing unchecked.

Thanks Jim!..... found this on a different post. It appears that the new Resolve has issue with AMD GPU for certain situations.


Try going into Preferences>User>Playback Settings and choose Manual with Optimize Sizing unchecked.


The advise fixed my issue.

Try going into Preferences>User>Playback Settings and choose Manual with Optimize Sizing unchecked.

Did not work for me. But thanks for suggestion.

[edit] Set to Disable however did work for me.
I'm on Nvidia BTW so not just an AMD issue

Sorry, got it wrong. From Rohit:

For now, just disable the following option (until the issue is fixed)
Top Menu 'DaVinci Resolve' -> Preferences -> 'User' tab -> Playback Settings -> Set 'Performance Mode' to manual -> un-check 'Optimized Decode Quality'
You don't need to restart Resolve for this to take effect.

This worked for me...

Ok, yes, that works for me as well.
Manual>Optimized Image Processing (only)
Thank you

THANKS. I thought I was going craaaazy. Both on Linux and. on the Mac..

Thank You guys! this issue left me scratching my head, I had a job on which this happened and the DP was also wondering what was going on, pretty embarrassing. Anyways I was trying everything to fix this before my next job, its the weekend BMD support is closed and I work Monday morning. I lost hope until I saw this. This works. Hopefully BMD addresses this in their next update.