CableCARD tuner support for MediaPortal 1 (4 Viewers)

[breese]

I would like to say thank you for the info and I have made some progress. Once my schedules direct plugin went to work, I got a lot of named channels. Other side of that is they came marked as Channel not mapped to card. It appears my provider might be sending these out as analoge.

On a whim I installed your updated code for the cablecards. While I did try it against my card (knowing it would prob fail), when I changed the menu to Clear QAM Cable and the lower one to QAM Alt Standard (the same one that has been working to a degree), all scans failed.
While doing all my testing, I leave the Hauppauge Digital Signal Quality screen open. While your new code is running, I see a lot of Green SNR 40 but get Nothing found.

The reasion I am passing this on to you is because it appears the code you are writing is going to replace the current code and seeing it breaks the one that works, you might need to add that to the list of tests needing to be done. If I can help in any way (I am not a programmer, but I do testing in my I.T. job), just let me know.

 

[Tsaukpaetra]

Other side of that is they came marked as Channel not mapped to card. It appears my provider might be sending these out as analoge.

This is indeed what happens, as the plugin adds the anticipated channels, but MP can't map them, as it's not talking to the cablecard device correctly. And no, as far as I can tell, (at least my) cablecard device doesn't necessarily tune to Analog channels, as the whole idea of the cablecard is to be allowed access to digitally encrypted transmissions from the cable company.

all scans failed.

Again, expected due to MP not communicating with the cablecard device correctly. The fact that your device is responding to MP's attempts to tune is a good thing, because the underlying commands to try to do so are indeed working, but we're speaking chinese to a french-man.

it breaks the one that works

Curious, as you mention that you weren't able to get anything working as yet before trying the new mod....

 

[breese]

With 1.3.0 Final I only get one pull down menu allowing me to choose the different QAM choices.
When I installed your code, the upper pull down activated. There are 3 choices for it. As I expected 2 of them failed. But when I went to QAM Cable (I think that was the name.. Not on the box right now), the lower menu again allowed me to choose the different QAM choices.
Problem is, these QAM's now all fail. When I go back to the 1.3.0 Final code, I get full scans with the Standard and Alt Standard.

So, if your new code should allow the older QAM choices and work (like it currently does) then there is a bug in your new code.

 

[Tsaukpaetra]

your new code

It's not my code, but I do have a vested interest in getting it working. I think you're off the point though, as cablecard tuners DON'T TUNE QAM as MP tries to tell it to. MP As it is in the trunk doesn't really know anything about cablecard tuners, other than the fact that they appear as ATSC devices (which is why QAM tuning options are present, as that's how you're supposed to talk to normal tuners). With the new code, MP gets a little more intelligent insomuch as how it talks to the cablecard, but since it was a work in progress (and in reality, a completely new card type should be defined), the coders that were making these efforts decided to just modify/tweak the code that MP was already trying to use so that it wasn't a total rewrite of the command engine for the card.
If you notice, the thread is tagged Work In Progress, so only if you are trying to get a CableCard device working should you even be interested in this topic.
Furthermore, if you get full scans (you haven't told us whether the scans actually find channels, odd), why are you trying this mod? I can't imagine why anyone would try something that was meant for a specific purpose on a setup that was (apparently?) working correctly.

 

[breese]

Thanks for the time.
I guess I was wrong in assuming that after weeks of searching this web site and google that what I was reading in this thread might lead me to a fix.
I can get channels listed in 1.3.0 Final with a direct connect to my WOW Cable provider.
I am however getting all kinds of mixed results.
One of them is the QAM scan giving me analog results and its not even connected (I will figure that one out).
After getting the response yesterday (that helped a little) I just thought I might try and be the Nice Guy and see what this new code does or does not do.
Low and behold to my surprise, the same QAM scans I was going with the 1.3.0 Final were still an available function… Cool… I tried it.
When it failed I once again thought I would tell someone.. Who knew….
Fyi… There are tons of unanswered QAM messages on this board. Just glad I asked here yesterday and got 1 more link to an answer I did not have before.

 

[Lyfesaver74]

Tuning mode needs to be set to ATSC Digital terrestrial. When that is selected the QAM option is greyed out.

 

[hello_joe]

I would like to say thank you for the info and I have made some progress. Once my schedules direct plugin went to work, I got a lot of named channels. Other side of that is they came marked as Channel not mapped to card. It appears my provider might be sending these out as analoge.

As @Tsaukpaetra said, SD creates channel placeholders for all the channels that it expects you to have access to (based on the lineup you select). Where it can't link to real channel tuning details, that is what happens. As I recall, there are options in the SD plugin that allow you to turn off creation of these channels, or only create digital channels. What kind of tuner do you have? If it is a hybrid one, you'd use the analog side of the tuner for analog cable channels. That is a completely different scan section.
http://wiki.team-mediaportal.com/1_...ver_Configuration/02_TV_Servers/5_Scan_Analog

On a whim I installed your updated code for the cablecards. While I did try it against my card (knowing it would prob fail), when I changed the menu to Clear QAM Cable and the lower one to QAM Alt Standard (the same one that has been working to a degree), all scans failed.

While doing all my testing, I leave the Hauppauge Digital Signal Quality screen open. While your new code is running, I see a lot of Green SNR 40 but get Nothing found.

@Lyfesaver74: that sounds like a bug you should report to your friend. And do you know if your friend has a regular clear QAM or ATSC tuner to test with?

...but MP can't map them, as it's not talking to the cablecard device correctly.

Have I missed something here? I don't think breese has a CableCARD tuner. breese, can you confirm.

And no, as far as I can tell, (at least my) cablecard device doesn't necessarily tune to Analog channels, as the whole idea of the cablecard is to be allowed access to digitally encrypted transmissions from the cable company.

The CableCARD is completely separate to the tuners. Primes, Cetons and DCR-2650s only have cable tuners. They can't tune analog or ATSC over-the-air digital. That's not to say a CableCARD + analog + ATSC supporting tuner couldn't be made. Just that the current products don't support it.

all scans failed.

Again, expected due to MP not communicating with the cablecard device correctly. The fact that your device is responding to MP's attempts to tune is a good thing, because the underlying commands to try to do so are indeed working, but we're speaking chinese to a french-man.

Again, I don't think breese has a CableCARD tuner (unless I missed something). I think breese is right. The patch shouldn't break support for normal clear QAM and ATSC tuners. If it does that is clearly a bug. Also, keep in mind that clear QAM is cable TV too; same type of signal as what your Ceton tuner is receiving. "CableCARD tuner" is a misleading term; the tuner is a QAM tuner that has a CableCARD subsystem attached. The CableCARD allows the board to decrypt cable channels where necessary. So what I'm trying to say is that underneath it all, clear QAM and CableCARD tuners aren't totally different.

With 1.3.0 Final I only get one pull down menu allowing me to choose the different QAM choices.

When I installed your code, the upper pull down activated. There are 3 choices for it. As I expected 2 of them failed. But when I went to QAM Cable (I think that was the name.. Not on the box right now), the lower menu again allowed me to choose the different QAM choices.

Problem is, these QAM's now all fail. When I go back to the 1.3.0 Final code, I get full scans with the Standard and Alt Standard.



So, if your new code should allow the older QAM choices and work (like it currently does) then there is a bug in your new code.

Agreed.
The new field is a replacement for the tick box at the top of the standard scanning screen. The ATSC option is like having the tickbox ticked; the QAM option is like having it unticked. The additional option is for CableCARD only. Or at least that is the way I read it. Existing ATSC and clear QAM tuners should continue to work with the other two options.

I guess I was wrong in assuming that after weeks of searching this web site and google that what I was reading in this thread might lead me to a fix.

I can get channels listed in 1.3.0 Final with a direct connect to my WOW Cable provider.

I am however getting all kinds of mixed results.

Did you try increasing the SDT scan time as suggested?
To truly test MP's scanning abilities, don't use SchedulesDirect to load in your channels. I suspect it will just confuse things further.
I suggest find out which QAM standard you're meant to use (call your provider if necessary), then stick with it.

One of them is the QAM scan giving me analog results and its not even connected (I will figure that one out).

Everything depends on the PSIP that your provider puts into the signal. If the PSIP lists analog channels then I guess it is possible that analog channels would be "found". However I don't think they'd be tunable.

After getting the response yesterday (that helped a little) I just thought I might try and be the Nice Guy and see what this new code does or does not do.

Low and behold to my surprise, the same QAM scans I was going with the 1.3.0 Final were still an available function… Cool… I tried it.

When it failed I once again thought I would tell someone.. Who knew….

Fyi… There are tons of unanswered QAM messages on this board. Just glad I asked here yesterday and got 1 more link to an answer I did not have before.

You're right - there are tons of confusing messages. I'm happy to try and help if I can. I've made some more suggestions above - hope they help. Keep asking. If necessary we can move to another thread.

 

[Lyfesaver74]

Yes, Joe.... an ATI HD 750 TV USB Hybrid Tuner (http://www.amd.com/us/products/pctv/tv-theater/Pages/tv-theater.aspx) is available to my friend.

 

[hello_joe]

Yes, Joe.... an ATI HD 750 TV USB Hybrid Tuner (http://www.amd.com/us/products/pctv/tv-theater/Pages/tv-theater.aspx) is available to my friend.

Excellent
Might want to let him/her know about what @breese said and see if he can look into it.

 

[breese]

This server has a Haupp hvr-1600 Dual - 1 digital (finctional on the WOW Cable line) - 1 Analog (not connected)
I have increased the SDT up to 90 seconds just to be safe.
I will stop and clear the Schedules Direct - I was unaware of that issue to talk about.
I am going to move my topics over to the MP1 General from here on out. If there is something you would like tested or a log, let me know. I will be more than happy to assist in any way I can.
Now if I can just find info on the XDM files. I cannot understand the Frequencies listed in them.
Thanks again...