I have successfully installed a pvr-250 and winfast 2000 tuner card in the same box.

The pvr-250 is my primary card and the Winfast is my secondary.
When I use PIP the Winfast 2000 display in the upper left hand corner of the screen.

When I toggle out of PIP live TV freezes, and a dialog is presented stating that I have lost connection to the backend.

The following is in the mythtvbackend.log.

Any suggestions?
Thanks,
MIke G.
open: Device or resource busy
2004-05-18 21:52:50 Could not open audio device: /dev/dsp
2004-05-18 21:52:50 Changing from None to WatchingLiveTV
Unknown video codec
Please go into the TV Settings, Recording Profiles and
setup the four 'Software Encoders' profiles.
Assuming RTjpeg for now.
Unknown audio codec
audio volume set to '65535'
2004-05-18 21:52:58 Changing from WatchingLiveTV to None
2004-05-18 21:52:59 Changing from WatchingLiveTV to None

have you done what it said and setup the recording profiles?

I setup the 'Software Encoders' profile and the problem still persists.

The following is from the backend log. It is slightly different from the original log message that I posted.

I believe that the error has something to do with the sound capture of my sound card. The Winfast 2000 sound gets captured from the line in.

Any suggestions?
Thanks,
Mike G.
2004-05-18 22:43:18 adding: mythtv as a remote ringbuffer
open: Device or resource busy
2004-05-18 22:43:18 Could not open audio device: /dev/dsp
2004-05-18 22:43:18 Changing from None to WatchingLiveTV
audio volume set to '65535'
2004-05-18 22:43:23 Changing from WatchingLiveTV to None

Ok I think I know why I am having this problem I just don't know how to solve it.

I can view TV/audio with my pvr-250 fine.
I switch to the WinFast capture card <Y>
I can view TV/audio with the Winfast2000 fine.
When I switch back to the pvr-250 the TV.audio for the pvr-250 is fine but I also hear the audio from the Winfast2000 which I have just switched from.

When I use PiP the Winfast is not giving up the audio therefore the pvr-250 hangs.

This must be a configuration error either in mythtv-setup or modules.config.
Both cards are setup for /dev/dsp.
I also tried the Winfast with /dev/dsp1 and still had the same results.

I have also upgraded the bttv driver.

Any suggestions?

Thanks,
Mike G.

Have you searched or posted to the MythTV mailing list?

_________________
cesman

When the source is open, the possibilities are endless!

well I don't think the /dev/dsp is the problem, because even though the pvr250 is setup for /dev/dsp it never really uses the device. It muxes the audio in with the video stream in hardware.

and I'm not really sure why you are having the problem. I have a leadtek and pvr250, and pip works just fine for me. I've never tried the Y to switch cards though.

Xsecrets,
What version of the ivtv drivers are you using?

Thanks,
Mike G.

the ones that came with R4v2

Xsecrets,
Which tuner is your primary tuner?

Thanks,
Mike G.

The pvr250 of course.

it is not /dev/video0. for some reason I could not get it to detect the pvr first no matter what I did, but doesn't seem to bother anything. I just set it up first in the database.

Xsecrets,
So far I can't seem to detect any differences so I have a couple of more questions.

1. It sounds like you started with r4v2 have you upgraded since and how, "Auto Upgrade" or apt-get

2. what are you running for v4l? I am running v4l2.
3. what are you running for bttv? I am running 9.15.


Thanks,
Mike G.

mythtv@mythtv:~ $ dmesg | grep v4l
ivtv: Registered v4l2 device, minor 0
ivtv: Registered v4l2 device, minor 32
ivtv: Registered v4l2 device, minor 224


mythtv@mythtv:~ $ dmesg | grep bttv
tuner: tv aard core driver (bttv, saa7134, ...) instead.
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 01:08.0, irq: 5, latency: 32, mmio: 0xdc000000
bttv0: detected: Leadtek WinFast TV 2000 [card=34], PCI subsystem ID is 107d:6606
bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00bf7707 [init]
tuner: tv aard core driver (bttv, saa7134, ...) instead.
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: registered device video1
bttv0: registered device vbi1
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: PLL can sleep, using XTAL (28636363).

well I started on R4 then reinstalled with R4V2 then I reinstalled again with R4V3, but the wireless drivers suck in the new kernel, and I was getting hit with the red bug from the new bttv v4l2 so I did an autoupgrade to downgrade back to R4V2 and that's what I'm running now. R4V2 with the tv_grab_na_dd fix. so I am using v4l not sure what the version of bttv is, but certainly not the newest.

Ok, all I can think of doing now is to downgrade from v4l2 to v4l.

I was going to do this by updating the kernel to pchdtv. Will I have problems with a pvr-250 and winfast 2000 if I upgrade the kernel to pchdtv?

There is a statement in the README thas says that ivtv and pcHDTV current don't work together.

Please advise.
Thanks,
Mike G.

You shouldn't have any issue as you aren't using the two cards together(ivtv and pcHDTV).

_________________
cesman

When the source is open, the possibilities are endless!

one other thing to make sure you are not using xvmc. pip does not ever work with xvmc.