Can't tune more than one frequency

Forums › Home Theatre (including HTPC and EPG Collector) › Can't tune more than one frequency - EPG Collector

bpbastos

12 posts

Geek

#152094 16-Sep-2014 03:51

Hello to all,

I'm trying to collect EPG from a DVB-C Brazilian provider but epg collector can only search one frequency at a time.

EPG Collector can tune the first frequency but every time it goes to the second, it raises the error "NO valid BDA tuner filter found".

I'm using Windows Server 2012 + Sundtek Media TV Pro III.

Any guidance will be welcome.

Thanks

1 | 2

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1129673 16-Sep-2014 09:54

Can you pot the EPG Collector log file?

If it's too big to post upload it somewhere and post a link.

MightyApe

You will find anything you want at MightyApe (affiliate link).

bpbastos

12 posts

Geek

#1130370 17-Sep-2014 01:10

SJB: Can you pot the EPG Collector log file?

If it's too big to post upload it somewhere and post a link.

Sure! http://pastebin.com/p9z5W1dX

Thank you

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1130491 17-Sep-2014 10:28

Can you try another run with BDA in the Trace box on the Diagnostics tab and upload the log again. It will show me in detail what's happening with the DirectShow filters.

One other thing. I think you have the format of the channel ID on the Output tab set to user channel number. That won't work with the version you have so you need to set it to Default (service ID).

The later version that I have may be able to generate user channel numbers, it depends on your broadcaster.

bpbastos

12 posts

Geek

#1131081 17-Sep-2014 22:23

SJB: Can you try another run with BDA in the Trace box on the Diagnostics tab and upload the log again. It will show me in detail what's happening with the DirectShow filters.

One other thing. I think you have the format of the channel ID on the Output tab set to user channel number. That won't work with the version you have so you need to set it to Default (service ID).

The later version that I have may be able to generate user channel numbers, it depends on your broadcaster.

Here it is : http://pastebin.com/tMxW4SEa

About the channel ID, I haven't changed the format to channel number it was setted as "Default (service ID)" but I've checked "Create an LNC tag containing the user channel number".

For this run I've unchecked the "Create an LNC tag containing the user channel number" checkbox.

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1131725 18-Sep-2014 19:25

It looks like your tuner driver may not like being released and then re-used very quickly (less than 1/10th second) so I am just trying a one second delay between release and re-use.

I'll PM you with a link to a version to try.

You are quite right about the channel ID. I should have said the LCN tag instead. That tag is of no use anyway unless you have some custom software to process the xmltv file.

bpbastos

12 posts

Geek

#1131895 19-Sep-2014 01:19

SJB: It looks like your tuner driver may not like being released and then re-used very quickly (less than 1/10th second) so I am just trying a one second delay between release and re-use.

I'll PM you with a link to a version to try.

You are quite right about the channel ID. I should have said the LCN tag instead. That tag is of no use anyway unless you have some custom software to process the xmltv file.

Thank you so much for your help SJB! Your software is awesome!

I'll test it and give you a feedback right after.

bpbastos

12 posts

Geek

#1131898 19-Sep-2014 01:57

SJB,

I did a run with the custom version you've sent me but the problem persist. Here is the log: http://pastebin.com/5VfxQwJE

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1131935 19-Sep-2014 08:25

Something has gone wrong there. That doesn't look like the right version. The log says it is 4.1 FP 10 and it should be 4.2 FP 0.

I downloaded it from the same place as you and after installing it did say 4.2 FP 0.

If you hover the mouse over the file DomainObjects.dll the file version should be 4.2.5373.28520.

bpbastos

12 posts

Geek

#1131946 19-Sep-2014 08:47

SJB: Something has gone wrong there. That doesn't look like the right version. The log says it is 4.1 FP 10 and it should be 4.2 FP 0.

I downloaded it from the same place as you and after installing it did say 4.2 FP 0.

If you hover the mouse over the file DomainObjects.dll the file version should be 4.2.5373.28520.

Sorry SJB it's my fault I've installed the .msi file and applied the fixpak.

Now, without the fixpak, the DomainObjects.dll shows 4.2.5373.28520 as version number but when I try to load my EPG Collector.ini it raises the follow exception https://imgur.com/XDuP8VI

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1132145 19-Sep-2014 14:14

Did you recreate your Brazil tuning file after installing 4.2?

If you didn't it will have been lost and if it's not there you get this error when you try and load an ini file that references it.

If you give me your Brazil cable tuning file I'll include it in the standard release.

bpbastos

12 posts

Geek

#1132432 19-Sep-2014 22:49

SJB: Did you recreate your Brazil tuning file after installing 4.2?

If you didn't it will have been lost and if it's not there you get this error when you try and load an ini file that references it.

If you give me your Brazil cable tuning file I'll include it in the standard release.

Oh, what a newbie I am.

Now with my tuning file in place i've made it run but ended with the same error "No valid BDA tuner filter found". http://pastebin.com/QkA4Se7d

I've pm'd you with my Brazil cable tuning file.

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1132485 20-Sep-2014 07:01

Can you try a run with 3 frequencies?

The delay between release and re-use didn't make any difference so I'm wondering if every attempt at re-use after the first run fails.

Thanks for the tuning file. I'll include it in the next release.

mm1352000

1149 posts

Uber Geek
Inactive user

#1132803 20-Sep-2014 17:44

Hi SJB

Hope you're well!
Odd problem.
Are you recreating everything from scratch? Graph, ROT entries, filters... everything?
I wonder if the problem occurs if the different frequencies are done via completely separate collections (ie. close and reopen EPG Centre, or new instance of EPGCollector.exe).

Best regards,
mm

SJB

2501 posts

Uber Geek

Trusted

Lifetime subscriber

#1133075 21-Sep-2014 11:28

Hi mm,

Good to hear from you again.

Yes it is a strange issue. Everything is disposed right down to the tuning space, tune request and locator before rebuilding a completely new graph. Don't use the ROT.

The error occurs on adding the tuner filter to the graph. Error code is of no use (8007001f - general error).

I'd assumed that separate runs worked but that would have been my next question.

I've also never heard of the tuner so being obscure the driver might have something strange in it like not being able to be instantiated a second time in the same process.

mm1352000

1149 posts

Uber Geek
Inactive user

#1133149 21-Sep-2014 15:03

SJB: Yes it is a strange issue. Everything is disposed right down to the tuning space, tune request and locator before rebuilding a completely new graph. Don't use the ROT.

The error occurs on adding the tuner filter to the graph. Error code is of no use (8007001f - general error).

I assume the same applies for any filter instances you might create during the tuner detection process?

SJB: I've also never heard of the tuner so being obscure the driver might have something strange in it like not being able to be instantiated a second time in the same process.

Likewise, and that was exactly the possibility that I was thinking of too.
I guess there are other possibilities too. For example, maybe there is:

some kind of interaction with software that comes with the tuner (driver [Empia] seems to come with something called emmon which runs in the system tray)
a weird USB related issue (not enough power, hub compatibility etc.)
some kind of interaction with the network provider (some tuners have weird network provider compatibility issues; some multi-mode tuners such as the HDHomeRun also change their internal node structure based on the network provider which is present in the graph)

1 | 2