[mythtv-users] Nehemiah Performance
and
hons at rcn.com
Wed Sep 3 23:20:19 EDT 2003
I choose the settings as I thought they would improve the performance
if I decreased the amount of data so therefore the bitrate, and I got
the dnr settings from the list as a way to improve the handling of
motion...
It doesn't seem to have worked ... ;-)
anders
On Wednesday, September 3, 2003, at 08:20 PM, rwk at americom.com wrote:
>> I'll have a look at what my xfree86config says after switching back to
>> 2.4.20-8
>> What are your ivtv settings?
>
> Since I haven't done anything (other than below) to set them I must be
> using mostly defaults. What do you do, set them with test_ioctl in
> your
> rc.local?
>
> I do run: test_ioctl --set-codec-params=dnr_mode=0,dnr_temporal=0
> in rc.local because it seems to minimize ghosting and mythbackend sets
> the height and width dynamically.
>
> Did you come up with yours by trial and error? I.e., should I expect
> better performance with your settings than the defaults?
>
> Here is the result I get from running: test_ioctl -a
>
> ioctl: IVTV_IOC_G_CODEC
> Codec parameters
> aspect : 2
> audio : 0x00e9
> bframes : 3
> bitrate : 8000000
> bitrate_peak: 16000000
> dnr_mode : 3
> dnr_spatial : 0
> dnr_temporal: 0
> dnr_type : 0
> framerate : 0
> framespergop: 15
> gop_closure : 0
> pulldown : 0
> stream_type : 0
> ioctl: VIDIOC_G_FMT
> Type : Video Capture
> Width : 480
> Height : 480
> ioctl: VIDIOC_QUERYCAP
> Driver name : ivtv
> Card type : Vanilla iTVC15 card
> Bus info : 0
> Driver version: 1
> Capabilities : 0x01030001
> ioctl: VIDIOC_ENUMINPUT
> Name : Composite 0
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : Composite 1
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : Composite 2
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : Composite 3
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : Tuner 0
> Type : 0x00000001
> Audioset: 0x00000000
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : Composite 4
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : S-Video 0
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : S-Video 1
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : S-Video 2
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> Name : S-Video 3
> Type : 0x00000002
> Audioset: 0x00000001
> Tuner : 0x00000000
> Standard: 0x00003000 ( NTSC )
> Status : 0
> ioctl: VIDIOC_G_INPUT
> Input = 4
> ioctl: VIDIOC_G_FREQUENCY
> Frequency = 3188
> ioctl: VIDIOC_ENUMSTD
> ID : 0x00003000
> Name : NTSC
> Frame period: 1001/30000
> Frame lines : 525
> ID : 0x000000FF
> Name : PAL
> Frame period: 1/25
> Frame lines : 625
> ID : 0x007F0000
> Name : SECAM
> Frame period: 1/25
> Frame lines : 625
> ioctl: VIDIOC_G_STD
> Standard = 0x00003000
>
>> Mine are:
>> bitrate 4000000
>> bitrate_peak 6000000
>> aspect 1
>> dnr_mode=3
>> dnr_spatial=2
>> dnr_temporal=4
>> dnr_type=0
>> height 480
>> width 480
>>
>> The odd thing is that mythtv sounds and looks fine using vesa just
>> when
>> I boot and for a while, but as a test I ran it over night, last night
>> and this morning it was not at all smooth.... as aI mentioned it was
>> sputtering on both video and audio even if I chage channel. It would
>> also seem to be in slowmotion this morning and from that I imagine
>> either the processor busy or the myth slowmotion features has engaged,
>> but as I couldn't switch it off it probably the processor....
>>
>> Any thoughts
>>
>> anders
>>
>> On Wednesday, September 3, 2003, at 03:57 PM, rwk at americom.com wrote:
>>
>>> If you find any optimizations, I would like to see them...
>>>
>>> Dick
>>>
>>> #####################################################################
>>> ##
>>> #
>>> # Config for EPIA-M TV-out
>>> #
>>>
>>> Section "ServerLayout"
>>>
>>> #
>>> Identifier "Anaconda Configured"
>>> Screen 0 "Screen0" 0 0
>>> InputDevice "Mouse0" "CorePointer"
>>> InputDevice "Keyboard0" "CoreKeyboard"
>>> EndSection
>>>
>>> Section "Files"
>>>
>>> # The location of the RGB database. Note, this is the name of the
>>> # file minus the extension (like ".txt" or ".db"). There is normally
>>> # no need to change the default.
>>> # Multiple FontPath entries are allowed (they are concatenated
>>> together)
>>> # By default, Red Hat 6.0 and later now use a font server independent
>>> of
>>> # the X server to render fonts.
>>> #FontPath "unix/:7100"
>>> RgbPath "/usr/X11R6/lib/X11/rgb"
>>> FontPath "/usr/X11R6/lib/X11/fonts/misc"
>>> EndSection
>>>
>>> Section "Module"
>>> Load "extmod"
>>> Load "glx"
>>> EndSection
>>>
>>> Section "ServerFlags"
>>>
>>> # added these few options in. cb
>>> Option "allowmouseopenfail"
>>> Option "blank time" "0"
>>> Option "standby time" "0"
>>> Option "suspend time" "0"
>>> Option "off time" "0"
>>> EndSection
>>>
>>> Section "InputDevice"
>>>
>>> # Option "AutoRepeat" "500 5"
>>> # when using XQUEUE, comment out the above line, and uncomment the
>>> # following line
>>> # Option "Protocol" "Xqueue"
>>> # Specify which keyboard LEDs can be user-controlled (eg, with
>>> xset(1))
>>> # Option "XkbDisable"
>>> # To customise the XKB settings to suit your keyboard, modify the
>>> # lines below (which are the defaults). For example, for a non-U.S.
>>> # keyboard, you will probably want to use:
>>> # Option "XkbModel" "pc102"
>>> # If you have a US Microsoft Natural keyboard, you can use:
>>> # Option "XkbModel" "microsoft"
>>> #
>>> # Then to change the language, change the Layout setting.
>>> # For example, a german layout can be obtained with:
>>> # Option "XkbLayout" "de"
>>> # or:
>>> # Option "XkbLayout" "de"
>>> # Option "XkbVariant" "nodeadkeys"
>>> #
>>> # If you'd like to switch the positions of your capslock and
>>> # control keys, use:
>>> # Option "XkbOptions" "ctrl:swapcaps"
>>> #Option "XkbOptions" ""
>>> Identifier "Keyboard0"
>>> Driver "kbd"
>>> Option "Xleds" "1 2 3"
>>> # To disable the XKEYBOARD extension, uncomment XkbDisable.
>>> Option "XkbRules" "xfree86"
>>> Option "XkbModel" "pc105"
>>> Option "XkbLayout" "us"
>>> #Option "XkbVariant" ""
>>> EndSection
>>>
>>> Section "InputDevice"
>>> Identifier "Mouse0"
>>> Driver "mouse"
>>> Option "Protocol" "IMPS/2"
>>> Option "Device" "/dev/psaux"
>>> Option "ZAxisMapping" "4 5"
>>> Option "Emulate3Buttons" "no"
>>> EndSection
>>>
>>> Section "Monitor"
>>> Identifier "Monitor0"
>>> VendorName "Monitor Vendor"
>>> ModelName "Monitor Model"
>>> HorizSync 30.0 - 60.0
>>> VertRefresh 50.0 - 125.0
>>> ModeLine "720x480" 26.7 720 736 808 896 480 481 484 497
>>> ModeLine "720x576" 32.7 720 744 816 912 576 577 580 597
>>> ModeLine "848x480" 31.5 848 864 952 1056 480 481 484 497
>>> ModeLine "856x480" 31.7 856 872 960 1064 480 481 484 497
>>> ModeLine "1024x512" 41.3 1024 1056 1160 1296 512 513 516 531
>>> ModeLine "1280x768" 80.1 1280 1344 1480 1680 768 769 772 795
>>> ModeLine "1440x1050" 126.2 1440 1536 1688 1936 1050 1051 1054
>>> 1087
>>> ModeLine "720x480" 34.9 720 752 824 928 480 481 484 502
>>> ModeLine "720x576" 42.6 720 760 832 944 576 577 580 602
>>> ModeLine "848x480" 41.0 848 880 968 1088 480 481 484 502
>>> ModeLine "856x480" 41.3 856 888 976 1096 480 481 484 502
>>> ModeLine "1024x512" 53.3 1024 1072 1176 1328 512 513 516 535
>>> ModeLine "1280x768" 103.0 1280 1360 1496 1712 768 769 772 802
>>> ModeLine "1440x1050" 160.0 1440 1536 1696 1952 1050 1051 1054
>>> 1096
>>> ModeLine "1280x768" 118.5 1280 1368 1504 1728 768 769 772 807
>>> ModeLine "1440x1050" 184.5 1440 1544 1704 1968 1050 1051 1054
>>> 1103
>>> ModeLine "848x480" 47.4 848 888 976 1104 480 481 484 505
>>> Option "dpms"
>>> #Refresh Rate 60Hz
>>> EndSection
>>>
>>> Section "Device"
>>> Identifier "VESA driver (generic)"
>>> Driver "via"
>>> VendorName "VESA driver (generic)"
>>> BoardName "VESA driver (generic)"
>>> Option "TVType" "NTSC"
>>> Option "TVOutput" "S-Video"
>>> EndSection
>>>
>>> Section "Screen"
>>> Identifier "Screen0"
>>> Device "VESA driver (generic)"
>>> Monitor "Monitor0"
>>> DefaultDepth 24
>>> SubSection "Display"
>>> Depth 24
>>> Modes "1024x768" "720x480" "640x480" "800x600"
>>> EndSubSection
>>> EndSection
>>>
>>> Section "DRI"
>>> Mode 0666
>>> EndSection
>>>
>>>> I'm using a monitor at the moment, but will switch to tv as soon as
>>>> I
>>>> get it reasonably working so I'd love to see your XF86Config as I
>>>> have
>>>> my serious doubt the one I use.. no matter how much I tweak the ivtv
>>>> settings my video is sputtering and not at all smooth... even at
>>>> 480x480 using the vesa driver.
>>>> When I use the via driver I get the ui corruption in the list views
>>>> and
>>>> weather etc as mentioned by Tako.
>>>> rgds
>>>> anders
>>>>
>>>> On Wednesday, September 3, 2003, at 12:27 AM, rwk at americom.com
>>>> wrote:
>>>>
>>>>>> I now have myth more or less working and the first report was
>>>>>> vastly
>>>>>> optimistic.
>>>>>> Mplayer still looks great with full size and stream, but the video
>>>>>> in
>>>>>> myth has to be much smaller *480x480) for my m10k to handle it!!
>>>>>>
>>>>>> My screen graphics is also completely screwed up. Screens don't
>>>>>> redraw
>>>>>> and some graphics don't show up or move when a button is
>>>>>> pressed...etc.
>>>>>> Might be the video driver, but it's pretty wiesrd and I have no
>>>>>> idea
>>>>>> how to fix it. I'm going to try to switch to another video drivers
>>>>>> (vesa generic), but if some one have a suggestions or
>>>>>> recommendation
>>>>>> for my rh9-epiam10k system I'd greatly appreciate it.
>>>>>
>>>>> Are you using a TV or a VGA monitor? I use a TV (i.e., the EPIA's
>>>>> S-video out) and have no problems. If you use TV-out I will be
>>>>> happy
>>>>> to
>>>>> send you my XF86config file (or post it if anyone else wants to see
>>>>> it).
>>>>>
>>>>> BTW, I found the drivers (on viaarena) you mentioned below to use
>>>>> the
>>>>> on-board MPEG decoder but I haven't yet installed them. I too am
>>>>> unable
>>>>> to run above 480x480 with the M10k decoding with software. If the
>>>>> drivers work, I expect to be able to decode 720x480 with virtually
>>>>> no
>>>>> CPU usage. This will free up the CPU to do things like
>>>>> transcoding.
>>>>> Both encoding and decoding will be done in hardware, encoding on
>>>>> the
>>>>> pvr-250 and decoding on the m10k broad. It ought to be very cool
>>>>> if
>>>>> it
>>>>> works.
>>>>>
>>>>> Has anyone else out there gotten this to work (under RH9)? The
>>>>> epia-m
>>>>> on-board mpeg decoder, that is...
>>>>>
>>>>> Dick
>>>>>
>>>>>> thanks
>>>>>> anders
>>>>>>
>>>>>>
>>>>>> Sorry about the confusion.
>>>>>> On Friday, August 29, 2003, at 09:02 AM, and wrote:
>>>>>>
>>>>>>> I haven't fully installed mythtv 0.11 yet (using atrms from
>>>>>>> berlin
>>>>>>> and
>>>>>>> I can't get the lirc to install/compile), but tried it out with
>>>>>>> mplayer and there was absolutely smooth video.
>>>>>>>
>>>>>>> I also originally tried on debian with the regular cvs
>>>>>>> xfree86-4.3
>>>>>>> drivers and had to settle for the via (with lots of mpeg and
>>>>>>> other
>>>>>>> undeclared and other errors) and had to settle for lower rez and
>>>>>>> birate, but even then I had bad sound unless I timeshifted the
>>>>>>> content
>>>>>>> a little...The xfree drivers are still a little buggy acording to
>>>>>>> vias
>>>>>>> opensource reprasentative and only provides 2d accl with out the
>>>>>>> mpeg
>>>>>>> stuff.
>>>>>>>
>>>>>>> Too bad the binary drivers are not available for debian. I'm
>>>>>>> having
>>>>>>> a
>>>>>>> hard time adjusting to redhat world... ;-)
>>>>>>>
>>>>>>> rgds
>>>>>>> anedrs
>>>>>>>
>>>>>>> On Friday, August 29, 2003, at 02:34 AM, Tako Schotanus wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> You got 16m/8m at 720x480 running with Myth Live TV?
>>>>>>>> That would be seriously cool because I'm currently using
>>>>>>>> something
>>>>>>>> like
>>>>>>>> 5m/4m at 460x576 to get stutter free video.
>>>>>>>>
>>>>>>>> But I'm not using those binary drivers you mention but the
>>>>>>>> drivers
>>>>>>>> that
>>>>>>>> came with the CVS version of XFree86 some months ago.
>>>>>>>>
>>>>>>>> Did you have to do anything special to get those drivers to
>>>>>>>> work?
>>>>>>>> (Recompile X like I had to do for example) The reason I ask is
>>>>>>>> that
>>>>>>>> previous binary drivers I had encountered all seemed to use
>>>>>>>> functionality/API from X that was not included in the standard
>>>>>>>> RedHat
>>>>>>>> 9
>>>>>>>> version.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -Tako
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: mythtv-users-bounces at mythtv.org
>>>>>>>>> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of and
>>>>>>>>> Sent: vrijdag 29 augustus 2003 9:12
>>>>>>>>> To: Discussion about mythtv
>>>>>>>>> Subject: Re: [mythtv-users] Nehemiah Performance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Are you using redhat 9?
>>>>>>>>> If you are, there are binary video and accl mpeg drivers
>>>>>>>>> available
>>>>>>>>> at
>>>>>>>>> viaarena.com that really helps. I've been playing around with
>>>>>>>>> it today
>>>>>>>>> and even with the 16m/8m stream at 720x480 from my pvr250 I
>>>>>>>>> didn't see
>>>>>>>>> any problems.
>>>>>>>>> I used to be running debian where there are no binary drivers
>>>>>>>>> avaliable
>>>>>>>>> for the cle266 and could therefore not take advantage of the
>>>>>>>>> hardware
>>>>>>>>> accl....at least that is what I think is making the big
>>>>>>>>> difference
>>>>>>>>> on
>>>>>>>>> my m10k.
>>>>>>>>>
>>>>>>>>> anders
>>>>>>>>>
>>>>>>>>> On Thursday, August 28, 2003, at 09:21 PM, rwk at americom.com
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Just to see if I could tell the difference, I set my record
>>>>>>>>> resolution
>>>>>>>>>> from 480x480 to 720x480. However, when I started watching I
>>>>>>>>>> was
>>>>>>>>>> surprised to find that my 1Gh Nehemiah EPIA processor
>>>>>>>>> couldn't handle
>>>>>>>>>> it. It sputtered every few seconds.
>>>>>>>>>>
>>>>>>>>>> I ran a top from another machine and indeed observed that
>>>>>>>>> mythfrontend
>>>>>>>>>> was using 99% of the cpu.
>>>>>>>>>>
>>>>>>>>>> My EPIA machine is connected to a TV through the onboard
>>>>>>>>> S-Video out.
>>>>>>>>>>
>>>>>>>>>> As a comparison I tried the same thing on my Athlon 2200+
>>>>>>>>> running a ATI
>>>>>>>>>> Technologies Inc Radeon VE QY video card. I was again
>>>>>>>>> surprised to see
>>>>>>>>>> that mythfrontend was using less than 0.1% of the CPU and X
>>>>>>>>> was using
>>>>>>>>>> about 10%. Needless to say it plays without missing a beat.
>>>>>>>>>>
>>>>>>>>>> What is it about the EPIA (hardware or drivers) which makes it
>>>>>>>>>> soooo
>>>>>>>>>> much slower than the Athlon system? The difference is CPU
>>>>>>>>> power is not
>>>>>>>>>> enough to explain it. Is it the video drivers?
>>>>>>>>>>
>>>>>>>>>> And why is all the processing in mythfrontend on the EPIA
>>>>>>>>> box, and in X
>>>>>>>>>> on the Athlon?
>>>>>>>>>>
>>>>>>>>>> Thanks for any and all opinions!
>>>>>>>>>>
>>>>>>>>>> Dick
>>>>>>>>>> _______________________________________________
>>>>>>>>>> mythtv-users mailing list
>>>>>>>>>> mythtv-users at mythtv.org
>>>>>>>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> mythtv-users mailing list
>>>>>>>> mythtv-users at mythtv.org
>>>>>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> mythtv-users mailing list
>>>>>>> mythtv-users at mythtv.org
>>>>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>>>
>>>>>>
>>>>>> --===============1859116010==
>>>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>>>> MIME-Version: 1.0
>>>>>> Content-Transfer-Encoding: quoted-printable
>>>>>> Content-Disposition: inline
>>>>>>
>>>>>> _______________________________________________
>>>>>> mythtv-users mailing list
>>>>>> mythtv-users at mythtv.org
>>>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>>>
>>>>>> --===============1859116010==--
>>>>>>
>>>>> _______________________________________________
>>>>> mythtv-users mailing list
>>>>> mythtv-users at mythtv.org
>>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>
>>>>
>>>> --===============1970015050==
>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>> MIME-Version: 1.0
>>>> Content-Transfer-Encoding: quoted-printable
>>>> Content-Disposition: inline
>>>>
>>>> _______________________________________________
>>>> mythtv-users mailing list
>>>> mythtv-users at mythtv.org
>>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>>
>>>> --===============1970015050==--
>>>>
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>>
>> --===============2120135991==
>> Content-Type: text/plain; charset="iso-8859-1"
>> MIME-Version: 1.0
>> Content-Transfer-Encoding: quoted-printable
>> Content-Disposition: inline
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>> --===============2120135991==--
>>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
More information about the mythtv-users
mailing list