Resolve 17 - Interlace not showing?

one more pic:

screenshot_4.png (254.23 KiB) Viewed 835 times

Just realized: joined at the forum exact 2 years ago

The settings are correct. Upper Field dominance is the one you need. You won't see any comb artifacts. Just go to the delivery page and check the Interlaced rendering -> Top Field first before hit render. You may want to enable 'Display a single field on video output' in the Ultrastidio settings, to see individual fields on the monitor.

Hi.
This subject is pretty much consolidated by now. As I wrote before, since transition from DR16 to DR17, the approach to interlaced processing has changed in Resolve.

DaVinci_Resolve_17_New_Features_Guide_p24.jpg (111.81 KiB) Viewed 801 times

It's no longer a question of whether you like it or not. It's a question of understanding it and having enough technical background to understand what an interlaced video signal consists of.
From my experience in many projects, if the settings are all consistent and we understand BMD's approach, all runs smoothly, from start to finish.
Two more hints:
Don't expect DR to behave exactly as other softwares do;
Choose a monitor you can trust, to display each video signal as it really is, i.e., interlaced/progressive/frame rates, etc. If you can't really see what's meant to be seen, you can never be sure of what you're doing.

While I agree that DR is handling interlaced footage quite nicely now, in particular with the 'neural' de-interlacer, there's one caveat left if you want to go back to interlace for the final output.
DR is not hindering you to edit on a field instead of a frame, since the timeline is progressive with full temporal resolution. The average viewer would hardly ever notice, but it might be rejected by QC.

Again, from my experience, never had any issues with QC.
With these settings, you have interlaced coming in, interlaced going out.

Project.png (107.88 KiB) Viewed 745 times

Clip_Attributes.png (108.41 KiB) Viewed 745 times

Deliver.png (215.64 KiB) Viewed 745 times

Furthermore, DR 18 manual clarifies the situations in which interlaced processing is mandatory to achieve a proper interlaced output.

DaVinci_Resolve_18_Manual_p125.jpg (414.24 KiB) Viewed 740 times

When working, you just have to understand that you have a 50 fields per second timeline, i.e. each time you press a key on your keyboard to move one frame forward, what you're really doing is moving one field forward.

Which means you MUST pay attention to the dots between the seconds and frames counter.

One dot, first field of each frame;

First_field.png (21.68 KiB) Viewed 740 times

Two dots, second field of each frame

Second_field.png (22.14 KiB) Viewed 740 times

That's what I mean. The information is there, but you must observe it.
Some other NLEs don't let you make a mistake here.

Of course, the alternative would be 'lying' to DR, treating the footage as progressive and output that.
Will be OK as long as you don't zoom or otherwise change the location of a single pixel.

Right Uli!
Let me ask your permission to use your own moto:
Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Also, speaking on how Resolve behaves in their own way, if you uncheck the Interlaced rendering checkbox on the Delivery page, the result will be rendered as full frame progressive with double framerate. Essentially it is deinterlacing the footage, outputting one frame for each field. Which is cool for doing mp4 previews.

Which is cool anyway, since without doing that, you'd loose half the temporal resolution.
Depending on the shutter speed (which is rarely taken much care about) it would look stuttery in 25 or 29.96p.

And, don't worry, Rui, I agree with you, since you are obviously aware of the issue.
Just trying to warn others. I've seen QC rejections when edits were in the wrong place.