Closed KennethWhite closed 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This still remains an issue, simply fighting the Stale Bot.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
My apologies for sucha late response @KennethWhite will the PR #493 fix this? if so let me know so I can close this issue.
Unfortunately the changes in #493 do not fix this issue here. I had spent some time digging to see what was causing this but never tracked down the exact cause.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Playback rendering frames at incorrect dimensions
When using the library we noticed a video with dimensions 204x360 (WxH) was having its frames displayed at 200x360. Debugging through pertinent areas like
VideoComponent.MaterializeFrame()
orVideoRenderer
shows the dimensions on the frames and bitmaps being generated are 204x360 as expected, snoop shows the image in the model as 204x360, but the actual on-screen physical pixel dimension is 200x360.We also tested this against the sample WPF application, VLC, and FFplay. In the sample app the resolution appears to be scaled up, but the video plays back at 400x720 as opposed to an expected 408x720 (17/30 aspect ratio). In comparison when played through FFplay and VLC we see the video rendered at the correct dimensions 204x360.
This is reproducible by trimming down other video files to the same dimensions.
Issue Categories
Version Information
Steps to Reproduce
Unosquare.FFME.Windows.Sample player
Expected Results
VLC Media Player
FFplay Media Player
Command line ffplay
Version information
Example invocation