On Tue, 2006-10-10 at 16:59 +0200, Dirk Meyer wrote:
> Jason Tackaberry wrote:
> > As an aside, there should be a generic open() function in kaa.popcorn
> > that will return a suitable player given the mrl.
> 
> But using kaa.popcorn.Player is the prefered way.

The Player constructor can accept an mrl, that'd be fine too.

> No, I don't think so. Xine can only guess. In mpeg files there is one
> bit 'progressive'. 1 == the stream is progressive, 0 == don't know (!)
> So some DVB-T channels in Germany always set this to 0, no matter what
> the content is. Xine will use the deinterlace if set to 0. And is it
> possible for xine to detect if deinterlacing is needed for real media?
> Quicktime? 

True, fair point.  xine can't detect progressive content, it can only
detect pulldown patterns.  Ideally, xine would be able to take any
content and detect whether it's progressive, telecined, or interlaced,
and do the right thing.  I've put this on my TODO.

You can set use_progressive_frame_flag=0 in the plugin, and it should
deinterlace any media, but unfortunately it won't leave progressive
content alone.

Ideally, the user shouldn't care at all about this stuff.  The player
should just figure it out.  Mplayer has no hope to do this, but it's
possible for xine, but will require some hacking.  I'm not sure about
gstreamer.


> Yes, but in that case you won't use kaa.popcorn as a generic
> player. If your filter on client side depend on the used player, it is
> not very generic.

No, but it might be nice to provide that ability.  I might want to add a
couple filters when I play back with mplayer that xine doesn't have.
Maybe I want to add a bit of noise to the video.  (Bad example, as I
ported the noise filter to xine :)).

> >         player.insert_video_filter('deinterlace', quality = 'high')
> >         player.append_video_filter('expand', osd = True, aspect = 4/3.0)
> >         player.set_video_out_device('xv')
> >         player.set_audio_out_device('alsa', passthrough = True)
> 
> That looks better to me. It is very similar to my idea, only that I
> used 
> 
> | set_property( DEINTERLACE, quality='high' )
> | set_property( VIDEO_OUT, 'xv', display=display )
> | set_property( AUDIO_OUT, 'alsa', passthrough = True )


Yeah, I'd prefer to have separate methods for audio/video filters and
audio/video devices.  Particularly for filters, because filters are
chained, and you should have the ability to move the filters around.  At
least at the API level.


> The problem with this could be different names for output. E.g. in
> mplayer I have mga for matrox and vidix working on fb. The x version
> is xvidix. On xine I don't have mga, vidix is X and the fb version is
> vidixfb. So we need to define some generic names. Or we can detect
> which version of vidix based on the display (X/FB). So it could be
> 
> | set_property( VIDEO_OUT, 'mga,vidix' )

Specifying multiple drivers in decreasing order of preference seems
sensible to me.  It's easy when there's overlap (xv, x11, directfb, fb),
but when there's not (dfbmga say), the sane thing for a player to do
that doesn't recognize or support that driver is to just ignore it.

> Some settings also depend on the content. You need different filters
> for playing NTCS files in the PAL world than the other way around. 

Which filters?

> But this is only needed for mplayer and we still lack the OSD support
> in it (hint, hint) ;)

Yeah, so little time.  You know, frankly, I'm comfortable requiring
people to patch mplayer for the time being.  As long as freevo works
out-of-the-box with one player, that's good enough as far as I'm
concerned.  And xine has dvd menus and superior deinterlacers anyway.
Plus we have much more control over xine.

Jason.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to