Data Burn-In Does Not Follow Rendering Choices

Start a project in, say, Full HD (1920x1080)

Edit it, enable Data Burn-In with your logo in the lower right corner.

All is fine, the editing looks good.

Now go to deliver at a lesser quality -- for example, 720x480 NTSC DV to be streamed over the Internet (perhaps in addition to the 1920 version or perhaps not.)

Render it out and you will notice that the burn-in is at the same pixel density as it was at 1920x1080; it did not render down to the lesser-quality output, but everything else in the timeline did as expected. This means its wildly too large and out of place in the final product.

That's a problem because I often wish to edit in a given resolution but deliver in multiple ones, and I can't with one setup. I could set up Data Burn-Ins for each potential deliverable resolution however that is undesirable as well because I want to see during editing whether the logo or whatever it is might obscure something important and, if it does and the shot is already in the can then I need to go reconfigure/move it -- which means not moving one, it means moving all of the different format ones if I do it that way.

This seems like a bug in that if Data burn-in is set it should follow the scaling set for output resolution, but it does not unless I've missed something important in how to set this up.

Thanks!

I have seen this issue with titles as well: if you build the titles in UHD, they don't necessarily resize correctly when you flip the switch to HD. I just accept it as part of life and manually change and reposition them.

In a perfect world, if you were doing an even multiple, like going down by 1/2 (or by 1/4), you'd think it could do the internal math and just scale it all.