Blackmagic Forum

I'm struggling with our H265 material from our Phantom 4 Pro also in the 4.01 update that should have hardware supported H265 as I understand.

Resolve can only playback in 7fps. Premiere is the only program I tried so far that actually can play the files back.
I'm thinking that the Titan X Maxwell cards do not fully support H265, but then why does it play in Premiere, maybe they use the CPU.

Windows 10
Davinci 4.01.008
Dual Titan X Maxwell cards.
Is anyone else experiencing anything similar?

/Andreas

i'm pretty sure it's not supported.

The Titan X Maxwell is a GM200 card, and h.265 decode is only supported on GM206 and later cards.

https://en.wikipedia.org/wiki/GeForce_900_series
https://developer.nvidia.com/nvidia-video-codec-sdk

Thanks Dan.
According to Nvidia H265 is supported on Titan X, but not all features of it, not B Splines for example which is maybe what DJI is using.
But yes, as we clearly see its not playing well so its probably not supported!
/Andreas

According to the chart in the link Dan provided encoding is not supported (the Titan X is GM200).

Thanks, I see well that comfirms my findings.
Currently we have 2xTitan X cards in our computer. I wonder how 1x Titan ti or 2 Titan Ti would compare to what we currently have. Could be worth upgrading just to be able to see our drone material without having to transcode.

/Andreas

I recommend a Proxy/Transcode workflow for all H.264 media when using Premiere Pro. Although I'm new to Resolve, given the nature of H.264, that advice still makes sense to me.

I think that would apply even more so to H.265.

Jim Simon wrote:I recommend a Proxy/Transcode workflow for all H.264 media when using Premiere Pro. Although I'm new to Resolve, given the nature of H.264, that advice still makes sense to me.

I think that would apply even more so to H.265.

The studio version of Resolve offloads decoding to the GPU. Unless you have source that's not supported by the Nvidia api, or you have a drastically under powered gpu, transcoding is no longer beneficial.

Dan Sherman wrote:The studio version of Resolve offloads decoding to the GPU.

In the past, that was never as "good" as when done on the CPU.

Leaving the color work for the GPU and using proxy/transcodes might still (forever?) be the best workflow with H.26x media, which just isn't well designed for editing.

Jim Simon wrote:

Dan Sherman wrote:The studio version of Resolve offloads decoding to the GPU.

In the past, that was never as "good" as when done on the CPU.

This is different to the old days, the Nvidea gpus now have special dedicated hardware specifically designed for decoding and encoding. its just as good as the cpu, and way faster.

Dan Sherman wrote:Nvidea gpus now have special dedicated hardware specifically designed for decoding and encoding. its just as good as the cpu, and way faster.

Interesting. I'd love to see some tests. Are you aware of any?

Jim Simon wrote:

Dan Sherman wrote:Nvidea gpus now have special dedicated hardware specifically designed for decoding and encoding. its just as good as the cpu, and way faster.

Interesting. I'd love to see some tests. Are you aware of any?

I've done some of my own last year, but not through the new DR workflow. I plan to get the studio version once it can be purchased without a dongle.

Dan Sherman wrote:

Jim Simon wrote:

Dan Sherman wrote:Nvidea gpus now have special dedicated hardware specifically designed for decoding and encoding. its just as good as the cpu, and way faster.

Interesting. I'd love to see some tests. Are you aware of any?

I've done some of my own last year, but not through the new DR workflow. I plan to get the studio version once it can be purchased without a dongle.

Ffmpeg for example will leverage the api if you configure it to do so.