Tuner conflict error
#1
I have a strange problem that I have never encountered before. I have installed a new analogue tuner avermedia mo39 usb hybrid atsc I only use s-video input on that card.

When I load XBMC there are times when the screen just freezes but xbmc is still functioning I can select a different channel but it doesn't show up. So I thought let me have a look what is happening in WMC.

On certain combination of channel changes I encounter a tuner conflict error when this happens if I close server.wmc it instantly tunes to that channel. At the time this happens there are no clients connected to server.wmc then I noticed something else that happens before tuner conflict error the channel before shows two rectangle boxes with an arrow.

Once that happens I cannot go back to the s-video channel as it always shows up video error and I need to restart the pc but before the restart I can watch dvb-t and dvb-s channels. I will try to disable the channel that shows s-video and see do I get this error again.

I have found a link below that has some discussion about it but no solution i will see are there up to date drivers.

http://experts.windows.com/frms/windows_...17849.aspx

I am very confused about this if there is a certain procedure that you want me to follow let me know and I will gladly do it.




I have attached a log but I think it is not very useful

http://pastebin.com/mrKk5ae8



Thanks
Reply
#2
(2013-12-22, 13:59)denz Wrote: I have a strange problem that I have never encountered before. I have installed a new analogue tuner avermedia mo39 usb hybrid atsc I only use s-video input on that card.

When I load XBMC there are times when the screen just freezes but xbmc is still functioning I can select a different channel but it doesn't show up. So I thought let me have a look what is happening in WMC.

On certain combination of channel changes I encounter a tuner conflict error when this happens if I close server.wmc it instantly tunes to that channel. At the time this happens there are no clients connected to server.wmc then I noticed something else that happens before tuner conflict error the channel before shows two rectangle boxes with an arrow.

Once that happens I cannot go back to the s-video channel as it always shows up video error and I need to restart the pc but before the restart I can watch dvb-t and dvb-s channels. I will try to disable the channel that shows s-video and see do I get this error again.

I have found a link below that has some discussion about it but no solution i will see are there up to date drivers.

http://experts.windows.com/frms/windows_...17849.aspx

I am very confused about this if there is a certain procedure that you want me to follow let me know and I will gladly do it.

I have attached a log but I think it is not very useful

http://pastebin.com/mrKk5ae8

Thanks

I don't know this tuner, but we have a known issue with hybrid tuners. The problem is one of the tuners is not completely released when the other is accessed. Its on my todo list to fix this particular tuner problem (I just need the hardware).

One thing you should try is to turn off ''pre-start' tuners in serverwmc (see Live TV tab). Restart serverwmc after you do that (you might even reboot for good measure). Then try again. You shouldn't have the trouble with serverwmc grabbing the tuner, with no client connected anymore. But you still may have trouble with lockup in xbmc if the second tuner is accessed.

The other not-so-nice workaround is to disable one of the tuners in wmc, preferable one you don't use that much (if possible).

We need to fix this.
Windows Media Center PVR addon (pvr.wmc) and server backend (ServerWMC)
http://bit.ly/serverwmc
Reply
#3
Thanks krustyreturns unticking pre-start did the trick. I did a lot of restarts and playing around the channels and it is working correctly.

The two rectangles icon means the channel is being watched on more than one screen. I still get that icon but at least this time no tuner conflict.
Reply

Logout Mark Read Team Forum Stats Members Help
Tuner conflict error0