I've been using kerneldeint as a preprocessing filter since MythTV 0.14. So
all video stored on disk is deinterlaced, but only at 25fps (PAL). This is
needed for the S-Video output of the Asus Pundit.
Now using MythTV 0.16 I'd like to switch to bobdeint to up new recording to
50fps for
: [mythtv-users] Bobdeint is only for playback?
I've been using kerneldeint as a preprocessing filter since
MythTV 0.14. So
all video stored on disk is deinterlaced, but only at 25fps
(PAL). This is
needed for the S-Video output of the Asus Pundit.
Now using MythTV 0.16 I'd like to switch
Op zaterdag 22 januari 2005 12:07, schreef William:
AFAIF deinterlacing is only done to the screen. The file is not altered so
your file is stored interlaced.
Yes, in the bobdeint case, but no in general. All the deinterlace filters
combine two consecutive frames in one so they halve the FPS
Henk Poley wrote:
Like I said Is it possible to edit my existing nuv files so Myth knows it's
deinterlaced already (aka. no guesses)?
I can't answer this question, but my guess is no. The heuristics you
noticed in NuppelVideoPlayer are basically always used, AFAICT; if it's
read from the stream,
Op zaterdag 22 januari 2005 14:52, schreef Doug Larrick:
Henk Poley wrote:
Like I said Is it possible to edit my existing nuv files so Myth knows
it's deinterlaced already (aka. no guesses)?
I can't answer this question, but my guess is no. The heuristics you
noticed in NuppelVideoPlayer
Henk Poley wrote:
Exactly what should be read from the stream that says this is already
deinterlaced (or this is progressive scan if you like)?
Sorry, I don't know. Anybody? You might try mplayer to see if it
detects a difference, and if so, how it reads it. You might have to
search online to
