2012-10-12, 08:14
@gfisher:
Yes, what you describe could be caused by deinterlacing. Windows with fglrx cards does another deinterlacing algorithm, something like temporal / spatial. fglrx on linux only uses bob, this always causes artefacts on the last lines.
But - the screenshot linked in this bugreport indicates another issue. It seems that they did not cut the h264 frames correctly and left over some 8 pixels. If you look at the osx-quartz-1088.diff this is what they actuall do - cutting any frames (1088 -> 1080) by changing the output size.
This is iirc also done in Eden, since fernetmenta implemented cropping a long time ago.
Could you make a screenshot yourself of this issue running xbmc?
Just to be sure - could you post a mediainfo of such a file?
Yes, what you describe could be caused by deinterlacing. Windows with fglrx cards does another deinterlacing algorithm, something like temporal / spatial. fglrx on linux only uses bob, this always causes artefacts on the last lines.
But - the screenshot linked in this bugreport indicates another issue. It seems that they did not cut the h264 frames correctly and left over some 8 pixels. If you look at the osx-quartz-1088.diff this is what they actuall do - cutting any frames (1088 -> 1080) by changing the output size.
This is iirc also done in Eden, since fernetmenta implemented cropping a long time ago.
Could you make a screenshot yourself of this issue running xbmc?
Just to be sure - could you post a mediainfo of such a file?