Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Sep 1997 14:51:45 -0700
From:      Amancio Hasty <hasty@rah.star-gate.com>
To:        Randall Hopper <rhh@ct.picker.com>
Cc:        multimedia@freebsd.org
Subject:   Re: [video] fxtv feedback 
Message-ID:  <199709132151.OAA00472@rah.star-gate.com>
In-Reply-To: Your message of "Sat, 13 Sep 1997 16:10:12 EDT." <19970913161012.57800@ct.picker.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
>From The Desk Of Randall Hopper :
> 
> --liOOAslEiF7prFVr
> Content-Type: text/plain; charset=us-ascii
> 
> Amancio Hasty:
>  |I would like if fxtv had accelerators for punching the channel number 
>  |for instance if I placed the cursor in the display window if I  key in
>  |12 <enter>, fxtv tunes to channel 12. Right now the channel input
>  |is a little awkward. 
> 
> In leui of this feature (for now), you may find videoWin translations like
> these useful:
>    <Key>F1          : TVSetChannel( 3 ) \n\
>    <Key>F2          : TVSetChannel( 5 ) \n\
>    <Key>F3          : TVSetChannel( 8 ) \n\
>    ...
>    <Key>F9          : TVSetChannel( 61 ) \n\
> 
> This meets my needs, since I don't have cable.  But your suggestion is a
> good one for folks with satellite and/or cable.  Consider it on the list.
> 
>  |When changing resolutions please check the error return status also try 
>  |to change the width in increments of 4 and the height in increments of 2.
> 
> All ioctl returns are already being checked, and fxtv ensures that
> capture width and height are both multiples of 2, since that's the
> condition that's checked for in the SETGEO ioctl.  Did you mistype when you
> said "4" for width?
> 
>  |1. Try to use yuv for mpeg encoding it should speed up video capture and
>  |   mpeg encoding also it should not be hard to implement given
>  |   all the work that has gone into fxtv to support video capture.
> 
> Had this on the list from your previous request.  Don't have it very high
> though since RGB does everything I need.  Wouldn't really save capture
> bandwidth since, if you're running in 15- or 16-bit, RGB16 capture is being
> used.  Probably would speed up image save and encoding though; don't have a
> feel for how much since I've never tried it.  It's on the list.

You save about 1/3 in bandwith and I have on my list of things
to do to have the X server support yuv directly which will be
nice for scaling to 1024x768.

Given that the mpeg encoder operates on yuv data and not RGB you will
save processing time . The question is what percentage of 
of the mpeg encoding is currently being taken by converting 
rgb to yuv and then encoding. The other factor involved is the
size of the data files so if processing time is not significant
storage capacity is important.


>  |2. It would be nice if fxtv sports a better look and feel
>  |   and a widget to change the gamma and contrast.
> 
> Better look and feel?  Need more detail here.

I think that gimp has a nice looking graphical interface .

> Gamma and contrast -- have you tried Input->Appearance?  You got sliders
> for these guys.  Admittedly I need to implement the text field key-ins
> sometime.  Been on my list.

gimp, sane (a scsi scanner package), and xv provide a gamma curve.


>  |3.  design a cool icon for fxtv -- we all want to show off fxtv 8)

> 
> <PLUG ALERT> Speaking of showing off TV in FreeBSD, here's a snap of my
> desktop with that icon and TV in action:
> 
> http://multiverse.com/~rhh/rhh_desktop.jpg
> </PLUG ALERT>
> 

I like the contents of your desktop it gives me the feeling of 
serious programming going on over there 8)

We can adopt your icon by default. Ideally , it will be nice
to pick from a list of icons (thats a hint to the list to get
involved 8) )


	Happy fxtv user,
	Amancio





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709132151.OAA00472>