Render issue in PD365

Forum Index » PowerDirector (previous versions)

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Solved by

Jan 27, 2021 06:51

I'm discovering following strange rendering issue in PD365. I have a 4k (3840x2160p50) project with 3840x2160p50 footage from my DJI Osmo Pocket. When I render this to AVC 2160p50 the output is indeed 3840x2160p50 but I discover that on the right side and on the bottom 2 pixels wide black borders have been added, or better said on the right side 2 pixel coloms are missing and on the bottom 2 lines are missing so the actual image becomes 3838x2158 in a 3840x2160 frame.
I discovered this difference when I put the 3840x2160 PD365 render into Handbrake, which automatically crops black borders. Recware: DJI Osmo Pocket, GoproHero7Black, PanasonicFZ300/HCX909, Sony PXW-X160.
Software: Vegaspro365+Vegasaur/PowerDirector365
Hardware: i910900k,32GB,GTX2080s, 1920x1200 display
Playware: Samsung Qled QE65Q6FN, Philips 55PFL7108

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Jan 27, 2021 10:25

Quote I'm discovering following strange rendering issue in PD365. I have a 4k (3840x2160p50) project with 3840x2160p50 footage from my DJI Osmo Pocket. When I render this to AVC 2160p50 the output is indeed 3840x2160p50 but I discover that on the right side and on the bottom 2 pixels wide black borders have been added, or better said on the right side 2 pixel coloms are missing and on the bottom 2 lines are missing so the actual image becomes 3838x2158 in a 3840x2160 frame.
I discovered this difference when I put the 3840x2160 PD365 render into Handbrake, which automatically crops black borders.

You'd probably have to supply a small clip to see if others have the same issue, maybe then CL would have a look if confirmed. I tried replicating by downloading a sample clip from the internet for that device but was only 25p at 3840 and I could not see the issue, nor could Handbrake.

It would also be helpful to know if you are doing CPU or GPU decoding and what type of encoding too as well as exact profile and container to try and replicate issue properly.

Jeff