Glen Dragon wrote:
Quoting john sturgeon <[EMAIL PROTECTED]>:
On 6/23/05, Doug Larrick <[EMAIL PROTECTED]> wrote:
Deinterlacing is clearly not working in these pictures. The stripes
are
so wide because something (probably your video card) is scaling the
pictures to a resolution less than
That stuff relates to the capture functions common to both PVR-250 and
PVR-350 -- it has the internal capacity to do simple spatial/temporal
filtering, but this shouldn't cause the effect described. (Especially
if it appears only on the amd64 machine -- same recorded video?)
Yep. All of these p
Hmm. looking at the guide, i found this:
Some people have run into issues with their cards generating a slight
inverse ghosted image off to the right of the main picture, myself
included. The recommended fix, which appears to be working for me, is
to set the DNR mode to 0 (mine was initially s
Quoting Ian Trider <[EMAIL PROTECTED]>:
This is different than the problem that I have with the bob deint. With
that the SD stuff will shimmer. I haven't seen a fix for that one
either. I believe that is also amd64 related.
I don't know about the main problem you describe in your message, bu
I've been seeing a problem for a while now, that has stumped me.
I see wierd horizontal striping every 1/2 an inch or so. There is a
jagged green area on the left (and covering parts of the picture). It
sort of makes the picture shimmer. It's semi-watchable if you can
ignore the effect (aka
Quoting David Kyle <[EMAIL PROTECTED]>:
Has anybody had success with 1.7 Ghz? The price difference between
1.7 and 2.0 is pretty big (about $200 from what I've found)... So it
would be nice to know if the extra .3 Ghz is necessary. I guess if
1.3 can do 720p, I'd imagine 1.7 could do 1024i. B
Quoting [EMAIL PROTECTED]:
Does anybody have any experience with Pentium M processors? I'm
thinking about getting an M based computer to use as a diskless
combination slave-backend/frontend. Any ideas as to how many Mhz
I'll need to accomplish this with SD MPEG4 software encoding? I
unders
Quoting Sasha Z <[EMAIL PROTECTED]>:
Oops. Does anyone know what the workaround is?
keybindings.cpp: In member function `void
KeyBindings::commitAction(const ActionIdentifier&)':
keybindings.cpp:192: error: 'class MythMainWindow' has no member named
'ClearKeylist'
Replace ClearKeylist with Cl
Quoting A JM <[EMAIL PROTECTED]>:
As far as hardware is concerned what are we talking about here? M/B,
ram, video, NIC? What's common for this type of setup?
Pretty much any hardware you want. Obviously you need to have enough
ram, since a swap partition isn't normally used. the NIC needs to
Quoting Mudit Wahal <[EMAIL PROTECTED]>:
S-out != HD Frontend
VGA-component converted -- add another $100 (AA 9A60)
Or get a nvidia card which has component out (similarly priced).
So, your cost is now $350 instead of 250.
Or if you have a DVI input on your HD tv, you can get a nvidia fx5200
Quoting Blammo <[EMAIL PROTECTED]>:
Very possible to put together an HD capable frontend for little $$.
$241+ shipping:
$75 CPU : http://www.newegg.com/Product/Product.asp?Item=N82E1681910341
$34 Heatsink : http://www.newegg.com/Product/Product.asp?Item=N82E16835106037
$50 Motherboard:
http:/
Quoting Greg Woods <[EMAIL PROTECTED]>:
I tried this, but it still does not work on my system. The 2.0 drivers
do work with the 2.6.10 kernel, but not 2.6.11.
What specifically is the problem? I know a number of people using them
with various 2.6.11 kernels. I've only had problems with a -mo
I'm successfully using the hd3000 with a 2.6.11 kernel. In two
machines, One with 2x HD3000s and another with 1x hd3000, and a pvr-350.
You need to use the v2.0 package from pchdtv.com and use the dvb
driver. Works like a charm. I don?t think that the old [atsc] driver
works well with the .11
13 matches
Mail list logo
