Terratec Cinergy T2 HD Stick DVB-T/T2 not recognized (1 Viewer)

BioEgo

MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy
    Hi all,
    I've recently bought a Terratec Cinergy T2 HD Stick DVB-T/T2 USB tuner (specs here [PDF] http://www.terratec.it/prodotti/tv/Cinergy_T2_Stick/caratteristiche.pdf) but unfortunately I'm not able to tune any channel in MePo (1.10.0 Final). The tuner works fine with its own software (DVBViewer Terratec Edition).

    This stick is based on eMPIA USB 28179 (the same used in the PCTV292e), and should be recognized as two different tuners (DVB-T and DVB-T2): that's true in DVBViewer but TVServer only shows one (DVB-T2). Trying to scan for channels works but since there are no T2 broadcast in my area at the moment nothing is found.
    When using DVBViewer I'm able to tune using the DVB-T one and it finds 400+ channels.

    I also tried to install ARGUS TV 2.3: it seems to correctly find both components but it recognizes the T2 part as a DVB-C card (not really surprising since in the .inf file the DVB-T2 part is referred to as BDATunerC): when scanning with the DVB-T component it skims rapidly through all the frequencies and no result is given (I doubt it even tries to tune, it's definitely too fast). A similar behavior is also found in TVServer if I set the card provider to Dvbt instead than Generic.

    I tried looking at the logs and I found the following part which might be a good lead in finding whats wrong:

    Code:
    [2015-03-24 21:00:53,193] [Log    ] [TVService] [INFO ] - Detected new digital BDA tuner device CINERGY T2 Stick HD DVB-T2 Tuner @device:pnp:\\?\usb#vid_eb1a&pid_8179#0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{b50b8116-da24-4f97-80d1-00451702c5f7}
    [2015-03-24 21:00:53,208] [Log    ] [TVService] [DEBUG] -   check type with MS NP
    [2015-03-24 21:00:53,240] [Log    ] [TVService] [DEBUG] -   network type count = 1
    [2015-03-24 21:00:53,255] [Log    ] [TVService] [DEBUG] -   network type 0 = 216c62df-6d7f-4e9a-8571-05f14edb766a
    [2015-03-24 21:00:53,271] [Log    ] [TVService] [INFO ] -   tuner type = DvbT
    [2015-03-24 21:00:53,271] [Log    ] [TVService] [INFO ] - Controller: add device CINERGY T2 Stick HD DVB-T2 Tuner @device:pnp:\\?\usb#vid_eb1a&pid_8179#0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{b50b8116-da24-4f97-80d1-00451702c5f7}
    [2015-03-24 21:00:53,287] [Log    ] [TVService] [DEBUG] - Controller: creating standard handler
    [2015-03-24 21:00:53,302] [Log    ] [TVService] [DEBUG] - Controller: current timeshifting folder is "C:\ProgramData\Team MediaPortal\MediaPortal TV Server\timeshiftbuffer"
    [2015-03-24 21:00:53,318] [Log    ] [TVService] [INFO ] - Detected new digital BDA tuner device CINERGY T2 Stick HD DVB-T Tuner @device:pnp:\\?\usb#vid_eb1a&pid_8179#0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}
    [2015-03-24 21:00:53,318] [Log    ] [TVService] [DEBUG] -   check type with MS NP
    [2015-03-24 21:00:53,349] [Log    ] [TVService] [DEBUG] -   network type count = 0
    [2015-03-24 21:00:53,365] [Log    ] [TVService] [DEBUG] -   check type with specific NPs
    [2015-03-24 21:00:53,396] [Log    ] [TVService] [DEBUG] -   failed to connect to specific NP

    It seems that both components are found (device paths are consistent to the one I've seen in the DVBViewer configuration) but the DVB-T one is discarded since it cannot identify the correct network type.
    I tried forcing the card in the database and it shows up as "unknown", so no good there.

    I've tried both the drivers provided by Terratec (5.2013.0725.0) and the one for the PCTV292e (5.2013.1206.0) which are newer, but to no avail.

    Any suggestion? I'd really would like to avoid buying another tuner, and I'm definitely not dumping MePo!

    I've attached all the logs from TV Server Log folder, let me know if something else is needed. At 21:01:33 I've started a scan with the Dvbt provider (result = no signals and very rapid skimming of the frequencies), while at 21:10:28 I've started a new scan using the Generic provider (longer scan, still no signal). Not sure whether this can be useful or not since I did not expect to find anything on T2.

    Thanks in advance for any help!
     

    Attachments

    • log (2).zip
      726.2 KB

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Hello

    First, I'd like to compliment you on your analysis. Great job! You looked in the right places and tried the things I would have tried. (y)

    ...and should be recognized as two different tuners (DVB-T and DVB-T2)
    This is rather odd. It's the first time I've ever encountered a tuner that exposed different interfaces for DVB-T and DVB-T2. Perhaps TerraTec were thinking that this would enable improved tuning speed.

    ...but TVServer only shows one (DVB-T2).
    ...
    I tried looking at the logs and I found the following part which might be a good lead in finding whats wrong...
    ...
    It seems that both components are found (device paths are consistent to the one I've seen in the DVBViewer configuration) but the DVB-T one is discarded since it cannot identify the correct network type.
    I tried forcing the card in the database and it shows up as "unknown", so no good there.
    You're exactly right! :)
    TV Server is not able to determine the type of second "interface" (which is meant to be DVB-T). Both our ways of detecting the interface type - with the generic network provider supported network types, and with specific network provider connections - fail. As a result, we discard the interface.

    Attempting to add the card definition in the database is a clever trick... but I'm sorry to say it won't work, as you already have seen. TV Server doesn't store the tuner type. It always detects it when the tuner is detected. If the tuner type can't be detected then TV Server won't use the tuner, regardless of whether it is listed in the database or not.

    ...when scanning with the DVB-T component it skims rapidly through all the frequencies and no result is given (I doubt it even tries to tune, it's definitely too fast). A similar behavior is also found in TVServer if I set the card provider to Dvbt instead than Generic.
    Yep, 100% correct. When you see the rapid skimming in TV Server it means that TV Server is failing to tune.

    I've tried both the drivers provided by Terratec (5.2013.0725.0) and the one for the PCTV292e (5.2013.1206.0) which are newer, but to no avail.

    Any suggestion? I'd really would like to avoid buying another tuner, and I'm definitely not dumping MePo!
    Yep, trying different drivers was a good idea.
    So was trying the different network providers.
    I see you also increased the tune timeout - another good idea.
    ...and you even tried my patch for eMPIA tuners from -->this<-- thread.
    Really, you've tried and checked everything I would have tried and checked. (y)

    The only way this problem is going to be solved is by detecting the type of the second [DVB-T] interface correctly. I can only think of 2 ways to do that:
    1. TerraTec/Ultron fix their driver to make it compatible with TV Server's tuner type detection.
    2. We [TV Server] find a new way to detect tuner types which can successfully handle your tuner.
    On the first point: you could try to contact TerraTec and tell them about the problem. Honestly, my experience with TerraTec/Ultron in the past is that they have been quite unhelpful. In fact I don't think I've ever received a response to any email that I've sent them. So, my guess is that they probably won't change their driver for us. But it doesn't take long to send an email, so...

    On the second point: TVE 3.5 already has a new tuner type detection method, which I think is probably similar to what DVBViewer are using. I can try to back-port a small part of that code into TVE 3 later today (or sometime this week) and see if it will work.

    Aside from that I think you've tried everything and there's nothing further you could do.

    Best regards,
    mm
     

    BioEgo

    MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy
    Thanks a lot mm!! :)

    Really, you've tried and checked everything I would have tried and checked. (y)


    Well on one hand I'm honoured by the fact that my analysis was going in the right direction...on the other one I was hoping I missed some easy way to solve the issue:p

    This is rather odd. It's the first time I've ever encountered a tuner that exposed different interfaces for DVB-T and DVB-T2. Perhaps TerraTec were thinking that this would enable improved tuning speed.


    Yes it surprised me too! And the fact that they are using BDATunerC to refer to the DVB-T2 tuner is also something that's going to cause a lot of issues: TVE3 approach seems to be the best since it doesn't rely on descriptors but asks the card for which network types are supported, but ARGUS for instance sees it as a DVB-C card and doesn't let me try to tune it as DVB-T.
    DVBViewer on the other hand let's the user select the network type by hand, overriding what it detects from registry (it default to DVB-C when firts detecting the card by the way).
    Definitely not a very clean solution, and one bound to create issues along the line for what I see.:confused:

    ...and you even tried my patch for eMPIA tuners from -->this<-- thread.


    Yes I forgot to mention it: as soon as I found out the chipset I tried searching the forums for eMPIA related threads and that one was the most promising! Unfortunately it didn't work (not that I expected it since it was tackling a different issue, but it was worth trying!:))
    Anyway since it wasn't solving the issue at hand I reverted back to the original version of the dll.

    The only way this problem is going to be solved is by detecting the type of the second [DVB-T] interface correctly. I can only think of 2 ways to do that:
    1. TerraTec/Ultron fix their driver to make it compatible with TV Server's tuner type detection.
    2. We [TV Server] find a new way to detect tuner types which can successfully handle your tuner.

    I'll try sending an email later today to Terratec/Ultron and see if they answer me (you were lucky last time with the PCTV team...so maybe I'll be lucky too this time;)), I'll keep you updated on this.

    As far as the second point goes: I can try to install MP2 and check whether TVE3.5 detects the card, so you don't waste time backporting the code if it's not working (or at least it may give you more info on this!). I'll do that this evening (meaning some 12 hours from now, give or take a couple of hours depending on whether the kids and wife will let me use the system:whistle:) and report back with results and logs!

    Thanks!
     

    BioEgo

    MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy
    As promised here I am with the results of the TVE3.5 tests aaaanndd......IT WORKS!!!!:LOL:(y)(y)

    I installed MP2 Weekly build (2015-22-02--09-26) on another system (System specs updated accordingly, the new system is called TEST).
    I've used Terratec drivers for the test (v5.2013.0725.0).

    Starting up TVSetup from this folder (C:\Program Files (x86)\Team MediaPortal\MP2-Server\Plugins\SlimTv.Service\SetupTv): not really sure it was the right way to do it, but I still have difficulties using the new MP2 interface:oops:

    Card was identified with both components: DVB-T (as #5) and DVB-T2 (#6). DVB-T2 is identified as a DVB-C card (not really surprised here given that's the same thing happening in both ARGUS and DVBViewer).

    It took me a while playing with the advanced settings of the DVB-T card but using the following:

    - Idle mode: Stop (didn't try other setting here though)
    - Network provider: Specific
    - PID Mode: Auto
    - Preload: checked
    - Direct/custom tuning: Unchecked

    it was finally able to tune in on various channels (TV & Radio) and testing a couple of them with the preview confirmed that they were indeed working!

    In the logs the successful scan starts at [2015-03-25 21:54:22,425].

    The previous scans have been made with different settings combinations (mainly playing around with NP,PID and direct/custom tuning). A small thing I noticed: whenever I tried to use "Mediaportal" as Network provided it seemed to automatically revert to "Generic", not sure whether this was only a glitch of the interface or if that setting wasn't being accepted by the server.

    Anyway it appears that the new TVE3.5 can make it up with the quirks of this tuner:)

    Now it's just a matter of time since TVE3.5 gets ported to MP1 or MP2 reaches a more mature state....but at least I know I don't have to trash the new tuner or dump MePo(y)

    I can try to back-port a small part of that code into TVE 3 later today (or sometime this week) and see if it will work.

    It would be great of course, but feel free to do it at your own pace or to change your mind if it gets to complex(y)

    And of course if you need more logs or tests with this strange card just drop me a line and I'll be more than glad to help! Maybe one day also the DVB-T2 part will work (not that I expect to have any T2 broadcast in Italy very soon by the way:rolleyes:).

    Regards and thanks!
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    As promised here I am with the results of the TVE3.5 tests aaaanndd......IT WORKS!!!!:LOL:(y)(y)
    Ahhh, fantastic!!! :)
    Thank you for testing. (y)

    Card was identified with both components: DVB-T (as #5) and DVB-T2 (#6). DVB-T2 is identified as a DVB-C card (not really surprised here given that's the same thing happening in both ARGUS and DVBViewer).
    About the DVB-T2 tuner identified as DVB-C...
    Is this your tuner?
    http://terratec.com/details.php?artnr=10723#.VRMwhley98E

    If so, I think the "DVB-T2" in the description may just be a meaningless label or mistake, because the description at the above link says the tuner supports DVB-T, DVB-T2 and DVB-C. I can't see how DVB-C would be tuned unless it is with that "DVB-T2" interface.

    About the correct detection...
    The interesting bit from the log files is:
    [2015-03-25 20:21:35,576] [2700996] [50 ] [DEBUG] - BDA detector: tuner CINERGY T2 Stick DVB-T Tuner @device:pnp:\\?\usb#vid_eb1a&pid_8179#0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}
    [2015-03-25 20:21:36,034] [2701455] [50 ] [DEBUG] - check type with topology node descriptors
    [2015-03-25 20:21:36,186] [2701606] [50 ] [DEBUG] - descriptor count = 2
    [2015-03-25 20:21:36,187] [2701607] [50 ] [DEBUG] - function 0 = 71985f4c-1ca1-11d3-9cc8-00c04f7971e0
    [2015-03-25 20:21:36,187] [2701607] [50 ] [DEBUG] - function 1 = 2dac6e05-edbe-4b9c-b387-1b6fad7d6495
    [2015-03-25 20:21:36,300] [2701720] [50 ] [DEBUG] - BDA detector: tuner CINERGY T2 Stick DVB-T2 Tuner @device:pnp:\\?\usb#vid_eb1a&pid_8179#0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{b50b8116-da24-4f97-80d1-00451702c5f7}
    [2015-03-25 20:21:36,303] [2701723] [50 ] [DEBUG] - check type with topology node descriptors
    [2015-03-25 20:21:36,304] [2701724] [50 ] [DEBUG] - descriptor count = 2
    [2015-03-25 20:21:36,304] [2701724] [50 ] [DEBUG] - function 0 = 71985f4c-1ca1-11d3-9cc8-00c04f7971e0
    [2015-03-25 20:21:36,305] [2701725] [50 ] [DEBUG] - function 1 = 71985f4d-1ca1-11d3-9cc8-00c04f7971e0

    71985f4c-1ca1-11d3-9cc8-00c04f7971e0 means "RF tuner". All tuners have a node with this function.
    2dac6e05-edbe-4b9c-b387-1b6fad7d6495 means "OFDM demodulator". Note OFDM is used for DVB-T, DVB-T2 and DVB-C2.
    71985f4d-1ca1-11d3-9cc8-00c04f7971e0 means "QAM demodulator". Note QAM is used for DVB-C and US cable (OpenCable/clear-QAM/SCTE).

    It took me a while playing with the advanced settings of the DVB-T card but using the following:

    - Idle mode: Stop (didn't try other setting here though)
    - Network provider: Specific
    - PID Mode: Auto
    - Preload: checked
    - Direct/custom tuning: Unchecked
    Yes, I see that you did quite a few scans that were not successful, and I'm not able to explain that at present.
    Note that the "specific" network provider is the same as the "DVBT" network provider in TVE 3.
    PID filtering and direct/custom tuning aren't supported by your tuner, so changing those settings shouldn't make any difference.

    A small thing I noticed: whenever I tried to use "Mediaportal" as Network provided it seemed to automatically revert to "Generic", not sure whether this was only a glitch of the interface or if that setting wasn't being accepted by the server.
    A few years ago one of the team members created a network provider, which was available for team members to test. It was never publicly released, but some team members still use it.
    With TVE 3 the option to use that network provider is only visible when the MediaPortal network provider is actually available. I wanted to do the same with TVE 3.5, but it was tricky to show/hide the option properly. Configuration can run on any PC, and so we needed the server side to tell configuration whether the MP NP is available or not. Later builds of TVE 3.5 will show/hide the option properly. For now, if you try to use the MP NP and it is not actually installed/available (as in your case) TVE will automatically revert to the generic Microsoft network provider.

    It would be great of course, but feel free to do it at your own pace or to change your mind if it gets to complex(y)
    The patch is attached. :)
    Installation procedure is the same as for the eMPIA patch. Just replace the TVLibrary.dll after stopping the TV service...

    Thanks again! :)
     

    Attachments

    • TVLibrary [tuner_detection_by_node_function].zip
      207.7 KB

    BioEgo

    MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy
    First of all thank you very much for the patch: tried it and it works like a charm!!:)(y)
    As expected from your reply I had to use DVBT as provider, generic doesn't work (rapid skimming of frequencies).
    I've attached a zip with all the logs (I made the zip halfway through a longer scan, but there is a complete scan and I also tried a quick timeshifting and preview test on a channel mapped only to this card and they both works!).

    About the DVB-T2 tuner identified as DVB-C...
    Is this your tuner?
    http://terratec.com/details.php?artnr=10723#.VRMwhley98E

    No it's not that one: the product number is 130168. I can't seem to be able to find it on the English website, but the PDF with the specs I linked in the first post is in English (despite having an Italian name). Here is the link for reference: http://www.terratec.it/prodotti/tv/Cinergy_T2_Stick/caratteristiche.pdf

    As you can see it doesn't mention any DVB-C capability. Also in the .inf file included with the driver (attached) it refers to DVB-T2 and not DVB-C despite using the BDATunerC field.

    Code:
    USB28179.DeviceDesc = "CINERGY T2 Stick HD"
    BDACap.28179.Name   = "USB 28179 Device"
    BDATuner.28179.Name = "CINERGY T2 Stick HD DVB-T Tuner"
    BDATunerC.28179.Name= "CINERGY T2 Stick HD DVB-T2 Tuner"

    And TVE3 detects it as DVBT. The only definitive proof would be trying to tune into a T2 broadcast with it, but it's not possible for me at the moment for lack of broadcasts.

    I don't really know how to thank you enough for your support:)!! As already said I'll be more than happy to be of help if you need any further info or test!

    Thanks a lot and regards!
     

    Attachments

    • cinergy_t2_stick_hd_64.zip
      5.2 KB
    • Log_patch.zip
      519.3 KB

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    First of all thank you very much for the patch: tried it and it works like a charm!!:)(y)
    Wonderful! :D
    Thanks for the confirmation. :)

    As expected from your reply I had to use DVBT as provider, generic doesn't work (rapid skimming of frequencies).
    I've attached a zip with all the logs (I made the zip halfway through a longer scan, but there is a complete scan and I also tried a quick timeshifting and preview test on a channel mapped only to this card and they both works!).
    Thanks also for the logs. :)
    The behaviour with the generic network provider seems odd to me. Here is the error message:
    [2015-03-26 00:07:24,696] [Log ] [13 ] [INFO ] - dvb:confused:ubmitTuneRequest returns:0x80070057 - E_INVALIDARGParametro non corretto.

    [2015-03-26 00:07:24,696] [Log ] [13 ] [INFO ] - dvb:confused:ubmitTuneRequest failed - subchannel: 0

    Problem is that the message doesn't specify which parameter is not correct... and unfortunately I'm not able to guess it either. At the end of the day those network providers are Microsoft components (so we can't check the code etc.), so I suppose we just have to be satisfied that the DVBT network provider works.

    About the DVB-T2 tuner identified as DVB-C...
    Is this your tuner?
    http://terratec.com/details.php?artnr=10723#.VRMwhley98E

    No it's not that one: the product number is 130168. I can't seem to be able to find it on the English website, but the PDF with the specs I linked in the first post is in English (despite having an Italian name). Here is the link for reference: http://www.terratec.it/prodotti/tv/Cinergy_T2_Stick/caratteristiche.pdf

    As you can see it doesn't mention any DVB-C capability. Also in the .inf file included with the driver (attached) it refers to DVB-T2 and not DVB-C despite using the BDATunerC field.

    Code:
    USB28179.DeviceDesc = "CINERGY T2 Stick HD"
    BDACap.28179.Name   = "USB 28179 Device"
    BDATuner.28179.Name = "CINERGY T2 Stick HD DVB-T Tuner"
    BDATunerC.28179.Name= "CINERGY T2 Stick HD DVB-T2 Tuner"

    And TVE3 detects it as DVBT. The only definitive proof would be trying to tune into a T2 broadcast with it, but it's not possible for me at the moment for lack of broadcasts.
    Ahhh, I see - a different product. Hmmm.... interesting.
    I had seen the inf file. In my opinion it is quite similar to drivers for other tuners that use the eMPIA 28** series chipsets. I've seen a few DVB-T/T2 + DVB-C + analog tuners like that, and I suppose in general that the "BDATunerC" label can be used for any additional interface. However, the fact that tuner has a QAM demodulator node... and that DVB-T2 is OFDM like DVB-T... it's a bit confusing and messy.

    I agree that access to DVB-T2 broadcasts would be one way to test it. Another way would be with access to DVB-C broadcasts. Do you have access to them?

    I don't really know how to thank you enough for your support:)!! As already said I'll be more than happy to be of help if you need any further info or test!
    I'm very happy to have been able to assist with an interesting problem. :)
    At present there's nothing more to test except the possibility of the "DVB-T2" tuner with DVB-C.
    If you feel it is appropriate, perhaps you could consider a small donation to the team:
    https://forum.team-mediaportal.com/donate/

    Money goes towards operational costs - website hosting, development software etc.
    Please don't feel any pressure to do this. I'm simply happy to be able to help people, without expectation of anything in return. :)

    Best regards,
    mm
     

    BioEgo

    MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy
    Hi mm!
    I needed to sleep through it but this mornig two things suddenly dawned on me:
    1. I spent the night dreaming of device driverso_O
    2. The DVB-T2 has been named as DVB-C in one opportunity!
    When I first installed the drivers I followed the instructions included in the box (they are not shipping any CD now, you need to download them from their website): according to them the drivers were located here: http://www.terratec.de/130638 (which by the way also lead to the english page of the product, I mistyped the product number in my previous post, sorry:oops:)

    After installing those driver (the x64 version) I've noticed that in TVE3 the card was named "CINERGY T2 HD C", but since it was detected as a DVB-T card I did not pay much attention to that (maybe there's still a trace of that in the first logs I posted). After noticing that it was not working I tried using DVBViewer were I saw two cards (DVB-C and DVB-T) with the T one working, so I supposed that maybe the drivers from the German website were for a different version of the hardware and I searched for new drivers on the italian website, were I found the one I'm using now. Since with those driver I saw no DVB-C card anymore I just discarded that as a driver glitch and forgot about it.

    So a curious thought comes to my mind: what if they are using the same hardware for this stick and the DVB-T/T2 + DVB-C one? As a marketing strategy it could make sense: sell the hardware with less margin but increase the overall volume to reduce production costs. And then they just relabeled the DVB-C component in the drivers to hide the fact that the card could use it (otherwise people paying more for the other card might complain).:sneaky:
    Consider that I was evaluating both this one and the PCTV292e and settled on the CINERGY because it was almost half the price and I had no use for DVB-C!

    Disregarding the name it is a fact after all that TVE3.5, ARGUS2.3 and DVBViewer all recognise it as DVB-C (the fact that DVBViewer lets you change the type manually is just a confusing factor at the moment since I couldn't test it)....the only one detecting it as DVB-T is TVE3, not sure how to explain that.:confused:
    This along with your finding from TVE3.5 logs makes a bit of a compelling argument for it to be effectively a DVB-C card.

    I agree that access to DVB-T2 broadcasts would be one way to test it. Another way would be with access to DVB-C broadcasts. Do you have access to them?

    And this lead to the sad part of it all: there's no DVB-C in Italy, so until they open a DVB-T2 broadcast I cannot test it. There was an experimental T2 mux but they turned it off halfway last year and the plan to set DVB-T2 compliance as a compulsory standard for TVs has been delayed by the government from 2015 to 2017....I fear it will be a looong wait to have a broadcast to make those tests.
    Anyway I'll keep the situation monitored and update if I have more data on this!

    Is there any other way of identifying the hardware? Maybe some software tools or opening up the stick (if I find a way to do that without breaking it....or my wife will end up breaking me apart:whistle:), do you think this might help?

    If you feel it is appropriate, perhaps you could consider a small donation to the team:
    https://forum.team-mediaportal.com/donate/

    Money goes towards operational costs - website hosting, development software etc.
    Please don't feel any pressure to do this. I'm simply happy to be able to help people, without expectation of anything in return. :)

    Of course I'll do it:) No pressure at all, you guys are really doing a splendid job here and after all I also saved a bit of money not having to buy another tuner;)

    Thanks & Regards!
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Just a short response, as it is bed time for me... :)

    I think this is the LinuxTV page for your tuner:
    http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_T2_Stick_HD

    It mentions DVB-C support.

    The SiliconLabs product page for the demodulator chip listed on the LinuxTV page also seems to confirm DVB-C support:
    http://www.silabs.com/products/video/demodulator/Pages/Si2168.aspx

    Same for the tuner chip:
    http://www.silabs.com/products/video/hybrid-tv-tuner/pages/si21x6.aspx

    So if I had to bet, I'd bet that second interface is for DVB-C support, and that the driver was meant to disable DVB-C support for some reason (even though the hardware seems to support it).
     

    BioEgo

    MP Donator
  • Premium Supporter
  • May 15, 2008
    26
    6
    Home Country
    Italy Italy

    Confirmed, that's my tuner(y). To be 100% sure I compiled V4L-DVB drivers on my linux server and compared the dmesg output (attached for reference) after plugging in the tuner and it is the same as the one shown on linuxtv website.

    So if I had to bet, I'd bet that second interface is for DVB-C support, and that the driver was meant to disable DVB-C support for some reason (even though the hardware seems to support it).

    Everything seems to lead in that direction: I'm very curious to test it....it could be a cheaper alternative to the PCTV292e since they are equipping the same hardware after all.
    As far as the reasons for this choice go: I stick to marketing reasons....it's something even my company does with some equipment: we sell two versions "basic" and "pro" with the same hardware but the "basic" version firmware blocks some functions. At the end of the day it is cheaper than producing and stocking two different hardwares, and if you run out of stock of one of the two is just a matter of flashing the new firmware and you can switch models easily!:whistle:
    Usually though we just hide the functions, not masquerade them for something else!;)

    Thanks & Regards!
     

    Attachments

    • cinergyT2HD-V4LDVB-dmesg.txt
      4.4 KB
    Last edited:

    Users who are viewing this thread

    Top Bottom