Sdkovacs wrote:
>> DVR:~ # mplayer -vo x11 /tmp/test_capture.mpg
>> MPlayer 1.0rc1-4.1.1 (C) 2000-2006 MPlayer Team
>> CPU: AMD Athlon(tm) Processor (Family: 6, Model: 6, Stepping: 2)
>> CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
>> Compiled with runtime CPU detection.
>> Can't open joystick device /dev/input/js0: No such file or directory
>> Can't init input joystick
>> mplayer: could not connect to socket
>> mplayer: No such file or directory
>> Failed to open LIRC support. You will not be able to use your
>> remote control.
>>
>> Playing /tmp/test_capture.mpg.
>> MPEG-PS file format detected.
>> VIDEO: MPEG2 720x480 (aspect 2) 29.970 fps 8000.0 kbps (1000.0 kbyte/s)
>> Xlib: extension "XFree86-VidModeExtension" missing on display ":20.0".
>>
>
> Mr. Moodyjunk,
>
> Are you running the mplayer command on the system console or are you
> SSHed into your mythbox? Mplayer is not outputting to screen :0 which
> leads me to believe you are not on the console.
>
> I noticed this from your post:
>
> Xlib: extension "XFree86-VidModeExtension" missing on display ":20.0".
>
>
> So try the mplayer command from the physical display.
>
I am actually VNC'd (SSH under the covers I believe) into the box
without any keyboard/mouse/display physically attached. I connected a
physical display and indeed get video on the display via mplayer,
proving that the video is being captured correctly. Thanks for that
pointer.
However, my goal is to view recordings via MythTV on a television
using PVR-350 TV Out. I get sound, but not picture on the TV when
issuing:
ivtvfbctl /dev/fb1 --globalalpha=off --localalpha=on
(fails with "IVTVFB_IOCTL_GET_STATE failed" as above)
dd if=/dev/video0 of=/dev/video16 bs=64k
I suspect the problem is the ivtvfbctl failure, but the ivtvfbctl help
doesn't describe what the globalalpha and localalpha parms are trying
to do, nor what the IVTVFB_IOCTL_GET_STATE failure means.
Also, the instructions I'm following say to issue
/usr/lib/ivtv/ptune-ui.pl, but that file is not found. I don't know
if the two problems are related.
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
