On 2/23/06, MythTV <mythtv at cvs.mythtv.org> wrote:
> #1364: Transcoded material de-interlaced but shouldn't be
> -------------------------------+--------------------------------------------
> Reporter: mrvanes at gmail.com | Owner: ijr
> Type: defect | Status: new
> Priority: minor | Milestone: unknown
> Component: mythtv | Version: 0.19
> Severity: medium | Resolution:
> -------------------------------+--------------------------------------------
> Comment (by spin667 at mchsi.com):
>> How can you tell it's shown with de-interlacing (I'm sure it probably is
> as I don't think the frontend tries to detect if the material is
> interlaced or not)?
>> Also, just because something is transcoded doesn't mean de-interlacing was
> done. That's an option.
>> I play de-interlaced mpeg4/nuv recordings with mythtv all the time also
> using xvmc/bob and haven't noticed a problem. How is playback "broken"
> for you?
Sorry this wasn't clear, I thought that deinterlaced progressive video
looked the same everywhere. What I see is 2 frames above eachother
(both taking up half of the frame height) and one superimposed on top
of that (and a lot of flicker). That's why I thought it was
deinterlaced cause it looks like it sends 2 frames in the time of 1
and then 1 whole, sort of what happens with double frame rate bob I
thought? Plus, it disappears when I disable deinterlace. I haven't
experimented with other deinterlace types though.
Maybe it's of use to tell that I use via XvMC and I suspect my
deinterlacing is done in HW and that causes the problem?
Martin
--
if but was any useful, it would be a logic operator