This project has moved. For the latest updates, please go here.
2

Closed

MCEBuddy breaking Ceton InfiniTV4 PCIe tunners

description

In the last few releases, my mce started complaining about unavailable tuners. It eventually got bad enough that none of the 4 Ceton tuner streams were working. Windows did not see the ceton tuners either. The only way to get the tuners working again was to reboot the system. I updated, windows, firmware, drivers etc. Then I started disabling software and low and behold stopping MCEBuddy stopped the tuner issue. When I start MCEBuddy it breaks. Very repeatable. I think this issue corresponds with the mcebuddy remote interface but I am not 100% on that.

Note* For those whom are not familiar, the ceton presents itself as a network device in windows
Closed Oct 25, 2012 at 6:41 PM by rboy1
UPnP not supported by Ceton drivers, Ceton working on a new driver set. Temp fix provided in 2.3.5 and also disabled UPnP or use new BETA drivers.

comments

rboy1 wrote Oct 5, 2012 at 2:29 PM

Try using 2.2.15 release, it does not support remote connection. Since you mention that ceton presents itself as a network device, I'm not sure what impact MCEBuddy should have but at the end of the day MCEBuddy is binding to network ports. It's a standard API should I'm confused, but it's a start to see what's causing the issue.

rboy1 wrote Oct 5, 2012 at 2:45 PM

Also in 2.3.1 try this, uncheck UPnP in the settings page and let me know if that helps.
UPnP works on remote network devices but also interacts with the firewall, wondering if that's creating an issue for the network device.

rboy1 wrote Oct 5, 2012 at 2:48 PM

See this link http://experts.windows.com/frms/windows_entertainment_and_connected_home/f/115/p/90940/475987.aspx#475987

Like it's a firewall issue since your card is setup as a network device. Try a few things on 2.3.1
  1. Disable or Enable UPnP
  2. Change the port MCEBuddy is using (click on the little icon next to the priority box) and use something else instead of 23323 (e.g. 11024)
  3. Disable the Windows Firewall - this should ideally fix your problem
This will help debug the issue atleast.

cheungkm wrote Oct 5, 2012 at 6:23 PM

I have tries disabling the upnp and that did not seem to fix the issue.

The windows firewall has been down the whole time.

I was not able to change the port an still be able to connect to the service.

2.2.15 has been running for a few hours with no issue.

Hope that helps. I am open to running other configurations.

Thanks,

rboy1 wrote Oct 5, 2012 at 8:25 PM

Okay if 2.2.15 is working fine, I need your help debug this. Please contact me directly and I'll create a special build for you that doesn't mess with the firewall or UPnP and lets see if that solves the problem.
I need to figure out what is causing the issue:
  1. Firewall API's
  2. UPnP API's
  3. Binding API's

rboy1 wrote Oct 11, 2012 at 8:30 PM

For those with CETON tuners, use this temporary solution for now:
  1. Download and install 2.3.2 (a clean install)
  2. Open Settings, uncheck Enable UPnP
  3. Click Start
  4. Reboot the computer
The UPnP appears to be interfering with the CETON tuners, and disabling it seems to fix the problem.
Let me know that works for now.

wrote Oct 13, 2012 at 3:01 PM

wrote Oct 13, 2012 at 3:02 PM

Ken62465 wrote Oct 15, 2012 at 1:59 PM

I know this is a couple weeks old but I have had countless issues with my Ceton InfiniTV card giving me "unavailable tuner" error messages inside WMC7 before I ever started using MCEBuddy. It was random and would happen a few times a day and go away after maybe 30 seconds. I finally started a support ticket with Ceton over the annoyance and they suggested to try the latest beta firmware as it's suppose to address these erros. Since it's install I've not had one issue with a tuner unavailable error. I've only been using MCEBuddy for a few days now and the errors have not come back with this new software in place either. I'd suggest using the Ceton diagnostic and on the update tab page check the "beta" version and install latest beta firmware. Ceton has been working on these exact issue pretty well. The card works far better now than when I installed it 8 months ago.

rboy1 wrote Oct 15, 2012 at 10:54 PM

That's great Ken, can you please post hte link (for the file) to the drivers for the CETON cards for other members to enjoy as well.

Thanks for posting this and resolving the issue.

Ken62465 wrote Oct 15, 2012 at 11:49 PM

It was not a link to the beta firmware, although I do believe Ceton does have a beta section on their site. Easiest means to acquire the latest beta firmware is right inside the Ceton diagnostics program itself. On the upgrade tab page is a check box option "include beta firmware". That makes it show up in the list and upgrade away! Thought the wife was going to make me get rid of the HTPC until this firmware came along, it was rather annoying loosing TV signal 3-4 times a day for 30 seconds with a tuner unavailable error.

Not saying it's the cure for all but I had these problems before I ever touched MCEBuddy and with latest Ceton beta firmware and now MCEBuddy added I still do not get these errors returning.

cheungkm wrote Oct 16, 2012 at 9:38 PM

Ken, thanks for the info on the beta firmware. I'm pretty sure it is not the problem here, since I've been running 2.2.15 for three days perfectly and 2.3.2 build, within an hour, causes all four tuners to fail until reboot.

rboy1 wrote Oct 17, 2012 at 1:02 AM

Kevin, I would suggest you try the new drivers. From the debugging so far it looks like when UPnP is disbabled it works fine.
When UPnP is enabled, MCEBuddy issues a broadcast request to find UPnP devices, it looks like the Ceton drivers are unable to process it and lock up.

I am skeptical this is an MCEBuddy issues since it's using standard .NET API's and Com API's. More likely than not it's a badly written driver downstream that's unable to respond to the API's. 2.2.15 does not have UPnP disovery API's in it so you're not facing the problem.
Also, if this were something specific to MCEBuddy, it would show up on other network adapters as well.

Wilky13 wrote Oct 20, 2012 at 3:03 AM

I've been pulling my hair out for 2 weeks now on why my Ceton is getting a "Tuners not available" errors! I did not realize it is because of MCEBuddy. I installed Flexraid about the same time I upgraded from 2.2.15. I am going to try and disable uPnP and see if that stops it. If not I am going to revert back to 2.2.15 and see if that helps.

wrote Oct 20, 2012 at 3:06 AM

rboy1 wrote Oct 20, 2012 at 4:44 AM

Also try the new BETA drivers, some users are reporting that it solves the issue.

cheungkm wrote Oct 20, 2012 at 6:18 AM

My current status after installing beta driver:

2.3.2 with UPnP hangs Ceton tuners
2.3.2 with out UPnP runs, but does not write converted output file
2.2.15 works perfectly

This is the same as before installing the beta driver

rboy1 wrote Oct 20, 2012 at 10:10 AM

Okay try 2.3.3 - I think it'll fix your problem. I've reverted back to the 2.2.15 style communication for local machines.

rboy1 wrote Oct 20, 2012 at 10:11 AM

Okay try 2.3.3 - I think it'll fix your problem. I've reverted back to the 2.2.15 style communication for local machines. Make sure UPnP is disabled (Ceton will be releasing an updated driver to fix that).

Wilky13 wrote Oct 20, 2012 at 4:56 PM

I've tried all different drivers for the Ceton. I am currently on the beta drivers. So far I have not had problems with 2.3.2 and unchecking uPnP.

Wilky13 wrote Oct 20, 2012 at 4:58 PM

Edit: no problems with the Ceton. I didn't run MCEBuddy last night, so not sure about the not writing output file thing.

Wilky13 wrote Oct 20, 2012 at 4:59 PM

Will try 2.3.3 Sunday night with uPnP unchecked.

rboy1 wrote Oct 25, 2012 at 3:57 AM

Try 2.3.5, it should be more stable. Also for Ceton tuners, I would keep UPnP unchecked until Ceton releases an update for your drivers. (some folks with the new BETA drivers are reporting success with UPnP also).

Ceton engineers are in touch with me and they're trying to figure out why their driver is not able to process the UPnP broadcast packets.

FYI - for those who want more technical details, UPnP COM API's are implemented by Microsoft, they send out 3 broadcast packets every 4 seconds for about a minute until all the devices are discovered (this is as per the UPnP specifications). Ceton is aware of this and is working on a fix.

wrote Oct 25, 2012 at 6:41 PM

wrote Feb 22, 2013 at 2:08 AM

wrote May 16, 2013 at 12:44 PM

CetonUser101 wrote Jun 27, 2014 at 1:24 AM

I installed MCEBuddy 2.3.15 and am running into the same problems described by other posters above. UPnP is disabled in the MCEBuddy settings by default. WMC cannot find the Ceton tuners until I uninstall MCEBuddy and reboot. Anyone found any solutions to this?

rboy1 wrote Jun 27, 2014 at 3:30 AM

Update your Ceton drivers. See the known issues thread

rboy1 wrote Jun 27, 2014 at 5:36 AM

also you may want to post in the discussion forum to get more resposnses

CetonUser101 wrote Jun 28, 2014 at 1:01 AM

Yes, I noticed the known issues thread and followed the instructions. I am running the latest beta drivers from Ceton (13.6.3.1088). There is also a beta firmware update. Since the Ceton Diagnostics Tool doesn't provide a way to undo a firmware update, I'd like to first hear from others having a similar problem. I will also follow your advice and post in the discussion forum.

BTW, I did not run into this issue with MCEBuddy 2.3.13. Does that provide any clues to the source of the problem?

rboy1 wrote Jun 28, 2014 at 3:55 AM

not really. the fundamental issue being mcebuddy really doesn't do anything to the Ceton ecosystem expect call some API's for UPnP and Firewalls. Try unchecking those options.