Deinterlacing

Forums › Home Theatre (including HTPC and EPG Collector) › Deinterlacing

PerfectV

33 posts

Geek
+1 received by user: 1

ID Verified

#115155 15-Mar-2013 15:31

I have a HTPC box that I've just rebuilt from Windows 8 to 7 to get around some ACamd issues. Specs are -

i3
8gb ram
GT 640 2gb

I use XBMC 12 with Argus TV as the TV back end (because I couldn't get MediaPortal to behave when doing more than a single stream). All pushed to a Panasonic 60" plasma.

For some reason my picture looks weird on deinterlaced content, like the sharpness has been turned up to 11 since the rebuild. I've tried all the different settings etc.

I was wondering if I could somehow hand the deinterlacing duties off to my TV, possibly by setting my default XBMC res to 1080i so the TV picks it up as such. Does anyone think this will work? Will it make it wig out if I then watch progressive stuff?

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#782606 16-Mar-2013 10:03

What codec are you using and how do you have your video settings configured?

Deinterlacing on a PC will always be vastly superior than the cheap deinterlacer on a TV.

1080p

1332 posts

Uber Geek
+1 received by user: 152
Inactive user

#782622 16-Mar-2013 10:50

Yep, this will all depend on the CODECs you're using.

PerfectV

33 posts

Geek
+1 received by user: 1

ID Verified

#785345 22-Mar-2013 10:20

I think I've discovered that it's refresh rate of all things. Windows is set to 60Hz and it seems to force XBMC to push it out at that. I changed the setting "sync to display" or whatever it is and it seems to fix it, until I watch something from my collection when it gets really jumpy until i turn that setting off, then it plays fine at 60Hz. If I turn the setting on again it'll drop it to 24Hz for the first video I watch, then same story if I play another file after it. They don't play well at 50Hz, which is where Sky Sports plays well.

Guessing it's a XBMC thing that has come about with one of the updates as I never had the issue with RC3.