Timeline resolution render warning

This isn't really a big deal, but I noticed that when working on an old project (probably created in Resolve 16), when I try to render 4k, I always get the warning about timeline resolution being lower than the render resolution. I have of course changed the timeline resolution to 4k, and it does render 4k as it should, but the warning still appears.

I tried creating a new project in 17 (latest beta as of now), and this issue does not appear, so I'm guessing it has something to do with the project being migrated from an older version. As I said, not really a problem, just a very minor annoyance, so I'm mentioning it here just as a notice.

[Shrinivas Ramani]

Øyvind

You want to check if:
a. the timeline reflects project settigns or uses custom settings (explained below)
b. the resolution you changed was in the project settings.

A timeline by default reflects project settings, but can be customised.

From File menu, or the gear icon in the bottom right, you can invoke the Project settings dialog. Changes made here affect how the project's default timelines behave, and what values new timelines will start with. The timeline resolution values here are part of this behavior.

You can right click a timeline in the media pool and open Timeline settings to see what they are. Project-reflected timelines show the project values, but disables changes till you switch to using custom settings. Subsequent changes made here will change the values only for that timeline - including the aforementioned timeline resolution field.

If you had used a custom HD timeline and changed the project settings afterwards, the custom timeline will not be changed.

Regards
Shrinivas

@Shrinivas Ramani:
That was very helpful, and even if I can't remember that I have ever used custom settings for the timeline (in any project), it turns out that for this project I actually had custom settings for the timeline (being the reason for the warning). Could this by any chance have happened during project migration? If not, then I must have unintentionally done it myself, and Resolve is completely innocent.

Anyways, I learned something, so thanks again!