Frame Errors on 25fps to 50fps Conversion XAVC Export

Hey Folks. Since v17 of Resolve Studio we have a strange problem: for broadcasting purpose we have to convert our 25fps ProRes4444XQ P3D65 PQ master to 50fps XAVC 100 CBR Rec2100 HLG.
Everything was cool in v16. Creating a 50fps project and dropping the 25fps file into the timeline. Frames were duplicated (no interpolation), playback was fine. But since v17 the rendered files are corrupted. There are wrong frames in the export regarding their temporal position.
Source is like frame 1, 2, 3, 4, 5, 6, ... (25fps) and the destination should be 1, 1, 2, 2, 3, 3, 4, 4, 5, 5, ... (50fps). But randomly it is like 1, 1, 2, 1, 3, 3, 4, 2, 5, 5, ...

This is not fixed in the latest version. Could someone reproduce this behaviour?

I'm having the same problem with XAVC in Resolve 17 and I'm just rendering 30p (no frame conversion) to intermediate files for use in another program. Worked perfectly in Resolve 16 which I just recently upgraded from. My solution has been to switch to Cineform for intermediate work but I do hope they fix this bug as XAVC is a nice codec.

I tested at HD resolution, but it came out fine.

Studio 17.1.1 for Windows.

I tested at HD resolution, but it came out fine.

Studio 17.1.1 for Windows.

Strange. Because it seems Marc is using Windows too. I am on MacOS 10.15. Which frame rate did you use @Jim?

Thank you for your feedback!

It's probably some AVC encoder issues (and those are not necessarily same between OSes).

The clip I tested was 25p, timeline was set to 50p.

Nothing was interlaced.

Try the MainConcept exporter. They are focused on broadcast formats: https://www.mainconcept.com/products/pl ... s/bmd.html

Could be a solution @Uli, but I would prefer a bug fix. Btw, there was no reaction from the BM support team on this issue yet

Have you reported to support? This is users forum not support. Don’t assume that if you write about some problem here BM will fix it.
You need to send support ticket and provide all needed info including Resolve log, OSX version, drivers version etc.
Your initial post is way not enough detailed to analyse it.

I wrote an email via https://www.blackmagicdesign.com/support/contact/email.

BMD was not able to reproduce the problem. And me neither at the time I was in contact with the support team
But today I had the same issue again using the latest version of Resolve. Now I am back at the beginning and have no clue how to solve this problem on v17..

Maybe that's the reason? I am doing some test right now..

Resolve Update 17.2.2:

• Addressed dropped frames rendering some clips to slow network disks.

Seems to be fixed. But now I have several crashes on rendering. Rendering to local NVMe storage seems to solve the crashes. So maybe "rendering to slow network disks" results in crshes now?