[mythtv-users] ivtv-0.1.9 and latest mythtv

Stuart Hodges mymythtv at twotails.org
Mon Jan 26 10:06:02 EST 2004


Hi,

	Thanks,

	I'm not getting these messages, so I guess its using the right driver.

	I'v played further.

	myth-0.13 works great with ivtv-0.1.9, I can change channels and watch live 
tv, all fine.

	With the latest CVS versions of Myth, on the screen where you choose a 
pre-recorded video to play it uses more cpu than 0.13 (around 45% to 20%). 
When I play one of the prerecorded video's. It still stays at 45%, on 0.13 
its down to 1%.

	The messages I get are:

mythfrontend
2004-01-26 09:18:40 mythfrontend version: 0.14.20040118-1 www.mythtv.org
2004-01-26 09:18:40 Enabled verbose msgs : important general
2004-01-26 09:18:41 Registering Internal as a media playback plugin.
2004-01-26 09:19:01 Connecting to backend server: 10.1.1.4:6543 (try 1 of 1)
Input #0, mpeg, from '/mythtv/input/1022_20040124215000_20040124223000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124215000_20040124223000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Error loading image file: 
/usr/local/share/mythtv/themes/default/1022_20040124210000_20040124213000.nuv.png
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124215000_20040124223000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Using the PVR-350 decoder/TV-out
2004-01-26 09:19:40 Changing from None to WatchingPreRecorded
IVTVFB_IOCTL_SET_ACTIVE_BUFFER: Success

*** The output stops after about 30seconds. This time the machine
*** did not lock escape put me back at the choose recording screen
*** I selected a recording to play again, but nothing came out. I 
*** rebooted to get output again.

2004-01-26 09:20:57 Changing from WatchingPreRecorded to None
2004-01-26 09:20:57 Changing from None to None
Input #0, mpeg, from '/mythtv/input/1022_20040124215000_20040124223000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Using the PVR-350 decoder/TV-out
2004-01-26 09:21:16 Changing from None to WatchingPreRecorded
2004-01-26 09:21:26 Changing from WatchingPreRecorded to None
2004-01-26 09:21:29 Changing from None to None
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
Input #0, mpeg, from '/mythtv/input/1022_20040124210000_20040124213000.nuv':
  Stream #0.0: Video: mpeg2video, 720x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s


	I'm going to play some more,

	Thanks,

		Stuart


On Sunday 25 January 2004 22:50, Brad Allen wrote:
> > 	I saw an earlier post about mythtv not using accelerated
> > drivers and checking you had the right ivtv version. I checked and I
> > am using 0.1.9. The only unusual thing I'm doing is starting
> > mythfrontend up xdisplaying back to another machine for control, but
> > using the PVR350 fb out.
>
> Check output of mythfrontend where it is running in the stderr &
> stdout where you first invoked it, and then you have then told it to
> play something.  If it fails and goes to fb, this is what it says:
>
>     {
>         if (vcap.version < 0x00000109)
>             cerr << "ivtv driver is version " << hex << vcap.version <<
>                 ", version " << hex <<  0x00000109 << " (or later) " <<
>                 "is required" << endl;
>         else if (vcap.capabilities & V4L2_CAP_VIDEO_OUTPUT)
>             ok = true;
>     }
>
> I think that means it will say "ivtv driver is version something,
> version 0.1.19 is required".  This happened to me after they said CVS
> was updated at IVTV, but when I got it, it hadn't been; CVS IVTV
> actually is slower to update than "CVS-LATEST" on IVTV's home page,
> and I downloaded CVS (I mean with "cvs" command), not "CVS-LATEST" (a
> tar file).  Anyway, then:
>
> Then it says:
>
> 2004-01-16 01:06:54 Changing from None to WatchingPreRecorded
> ***
> * Couldn't find Xv support, falling back to non-Xv mode.
> * MythTV performance will be much slower since color
> * conversion and scaling will be done in software.
> * Consider upgrading your video card or X server if
> * you would like better performance.
>
> ... and if you have a slow system it will say ...
>
> ***
> * Your system is not capable of displaying the
> * full framerate at 648x448 resolution.  Frames
> * will be skipped in order to keep the audio and
> * video in sync.
>
> [I deleted the output of the wrong version # problem.]
>
> Check this output first.  If you don't get that error message (about
> the IVTV version #), that's OK.  Since you didn't say you checked
> this, I think this isn't the problem, but I could be wrong; a lot of
> us have been trained through experience to ignore the substandard
> diagnostics of myth programs (they tend to report very little with
> little reference and at bad times; even the developers complain at you
> when you post their own diagnostic messages, because they don't think
> they're useful either (!), but somehow are clueless about realizing
> that they should be useful).  Every once in a while, something is
> printed there that's important.  Consider myth diagnostic messages to
> be like a freeway:  perhaps your wife is in one of those cars, but
> she's certainly not in the rest of them, and once you find her car, it
> might not be the right place to say hello to her anyway.



More information about the mythtv-users mailing list