Fit/scale to frame size glitch i've seen for years, still not fixed

[leod86781877]

Hello everyone,

I have seen this glitch so many times in my career, usually a good work around is to add like +0,1% scale but here is the problem:

Most recent exemple : I've shot a video with the GH5, some images 2160p24 and others 1080p180/60 (interpreted as 24) and I actually upscaled the 1080p footage to 4k with the Scale to frame size functionnality so I can render the whole thing at 4K. Problem is, if there's some 4K footage under the upscaled 1080p footage, there's a line of pixels all around that actually shows whats behind, i've seen this so many times, it also shows on the export, here's a zoomed screen shot of the problem (against a dark background to better see the problem).

Other widely encountered exemple: A lot of people add bars to their videos to give the wide cinescope feel (instead of making the timeline cinescope itself, which wouldn't allow you to warp stabilize in the main timeline), often times they use black bars png files that are not big enough, so they actually scale/fit to frame size and surprise surprise, it's not perfectly scaled and that line of pixel dancing (basically from the video behind the bars) is there all around, here's a zoomed screenshot (upper corner) i've just come across on a random youtube video:

So my question is, am I doing something wrong ? Am I missing something because clearly i'm not the only one, it has happened to me so many times and i've seen it almost as much. Maybe it's a glitch ?

You guys tell me Thanks a lot !

[Ann Bens]

Problem is, if there's some 4K footage under the upscaled 1080p footage, there's a line of pixels all around that actually shows whats behind,

I would remove the 4K footage....

[leod86781877]

This is a workaround, I have tons of workaround for this, and I could give you another situation where this won't cut it (I actually did in my second exemple). The problem is it doesn't work as it should and sometimes you don't realise until you've rendered the thing, and it's some time wasted, I wanted to know if it had happened to someone and if they had found a fix, or if adobe could chime in and confirm this is a known bug.

[Kevin-Monahan]

LeoD,

wanted to know if it had happened to someone and if they had found a fix, or if adobe could chime in and confirm this is a known bug.

That kind of thing doesn't usually happen on forums, as devs are usually not present. Please file this issue here: Premiere Pro: Hot (3766 ideas) – Adobe video & audio apps You'll get better feedback there.

Thanks,
Kevin