Hauppuage HVR-1600 Support (1 Viewer)

Andrew H

MP Donator
  • Premium Supporter
  • September 8, 2007
    576
    42
    Alabama
    Home Country
    United States of America United States of America
    I had most of the same problems indicated here by other posters, the digital portion of the tuner worked fine with the latest SVN. The analog side would find the channels but then when you went to watch tv all you had was a black screen. The card wasn't recognized at all after modifying the capturecarddefinitions in 0.2.2.

    I did get everything working though and I thought I would share what it took to get it working:

    1) Backed up 0.2.2. Uninstalled 0.2.2. Rebooted.
    2) Installed 0.2.2 again. Did NOT configure MP. Copied the CaptureCardDefinitions.xml file from page 2 of this thread to the MediaPortal directory, overwriting the installed xml file. Note to download the file noted on page 2, don't just try and append as shown in page1 of this thread as what is noted on page1 is incomplete.
    3) Now ran configure. Channels detected for both NTSC and ATSC(also note I am running a PVR-150 in addition to the HVR-1600). Everything went smoothly from here on out.

    One buggy thing I did notice with the configure is if you edit the properties of the capture card in configure it has the nasty habit of changing the source for the card to antenna from cable. If this happens you no longer can tune tv with the card. I suggest always rechecking this setting after changing any property associated with the tuner.

    This now allowed the analog and digital portion of the HVR-1600 to work fine, I can tune stations with both analog and digital.

    I will say now that the HVR-1600 is up and running that the picture quality of the analog side is awful compared to the PVR-150. I am hoping it's just the tweaking of some settings to make them comparable. If anyone has anything to add about tweaking the settings for this card it is much appreciated.

    I've also noticed that the HD reception causes a lot of crashes in MP. It appears to happen more often with weak signals.
    Does your S-Video A/V input work? I'd like to use my 1600 to capture DirecTV, or my Hi-8 video. I can't get MP to do anything with it even after establishing the 'channel' from the TV tab of the configure. Any help would be appreciated!
     

    garry

    Portal Pro
    December 11, 2005
    227
    17
    California
    Home Country
    United States of America United States of America
    I've been using a 1600 w/s-video under TVE3 for a few months, works great. Picture quality looks a bit better than my PVR-500.
     

    Andrew H

    MP Donator
  • Premium Supporter
  • September 8, 2007
    576
    42
    Alabama
    Home Country
    United States of America United States of America
    Here it is: https://forum.team-mediaportal.com/showpost.php?p=137997&postcount=20

    SIX MONTHS ago this poster discovered the erroneous line of code in the CaptureCardDefinitions.xml file, edited his personal copy and posted it for all to use!

    My HVR-1600 now does NTSC and A/V capture as it should! I don't know what it takes to get the master file corrected but we surely need to let someone know for 0.2.3.0 RC3.

    As far as you HVR-1800 owners go... A buddy of mine created an entry in his CaptureCardDefinitions.xml file and got the ATSC portion working. I can try to get a copy of it and post.

    An interesting side note -- picture on the box shows model 74021 LF; REV B3B2 and the UPC says WinTV-HVR-1600; model 1178; SL-1178-V2.1-US yet it identifies itself as the 74040070 That's OK seeing as the latest CaptureCardDefinitions.xml has FOUR models: 74000, 74020, 74040, and 74440. That dude's modified file was created before the last (74440) model was identified in 0.2.3.0 RC2. Also, he only deleted the bad line of code for the 74000 & 74040 models -- so if you have these others you need to use WordPad or some editing tool and correct your file to get NTSC working on your MP installation!

    THANKS guys... I heard you all talking about this error but didn't LISTEN! I'm glad the bulb went on, yesterday! I hope my post clarifies the differences in HVR-1600's for those still having problems getting NTSC running on it.


    UPDATE: Billy and Joe -- I highlighted the 74440 for you! It is included in the latest file and has the bad line of code. Your 74440 is not included in the xml file on page 2 hence update your file and see if that fixes it! I'm also assuming the TV2 (TV3) engines don't have this error because posters are saying the 1600 works fine under it.
     

    farmertom

    Portal Member
    September 7, 2007
    21
    1
    Home Country
    United States of America United States of America
    Hauppuage HVR-1800 ASTC settings.

    Hi,
    As requested i am posting the settings i have for my Hauppuage HVR-1800. This is for the ASTC tuner only.. this works for me, I hope it works for you...

    <capturecard commercialname="Hauppauge WinTV HVR1800 (ATSC)" capturename="Hauppauge WinTV 885 TS Capture" devid="ven_14f1&amp;dev_8880&amp;subsys_78010070&amp;rev_0f">
    <capabilities tv="true" radio="true" mpeg2="true" mce="false" sw="false" bda="true"/>
    <tv>
    <interface cat="capture" video="3" audio="4" mpeg2="1" sectionsandtables="2"/>
    <filters>
    <filter cat="networkprovider" name="Microsoft ATSC Network Provider" checkdevice="false"/>
    <filter cat="tunerdevice" name="Hauppauge WinTV 885 BDA Tuner/Demod" checkdevice="true"/>
    <filter cat="capture" name="Hauppauge WinTV 885 TS Capture" checkdevice="true"/>
    </filters>
    <connections>
    <connection sourcefilter="networkprovider" sourcepin="0" sinkfilter="tunerdevice" sinkpin="0"/>
    <connection sourcefilter="tunerdevice" sourcepin="0" sinkfilter="capture" sinkpin="0"/>
    </connections>
    </tv>
    </capturecard>


    farmertom
     

    MrBungle67

    Portal Member
    September 20, 2007
    15
    1
    43
    Home Country
    France France
    For all of you who have issues with the HVR 1600 with MP 0.2.2.0 OR 0.2.3.0RC1(no tuner detected) AND 0.2.3.0RC2 (tuner detected but no signal detected), you probably have the 74440070 version of the HVR1600 (that you can check in your device manager). This version of the HVR1600 was not in the capturecarddefinitions.xml file in the 0.2.2.0 and 0.2.3.0RC1. They added it in the 0.2.3.0RC2, which made me really happy when I saw that my card was finally detected.....but no luck....no signal detected!

    So after spending hours on this forum and especialy on this thread, and after comparing really clothely my capturecarddefinitions.xml file from the 0.2.3.0RC2 and the one on page 2 of this thread, here is what I found:


    In the file from page 2 (with the 74040070 tuner) :

    <capturecard commercialname="Hauppauge WinTV HVR1600 (NTSC)" capturename="Hauppauge WinTV 418 Video Capture" devid="ven_14f1&amp;dev_5b7a&amp;subsys_74040070&a mp;rev_00">
    <capabilities tv="true" radio="false" mpeg2="true" mce="false" sw="false" bda="false"/>
    <tv>
    <interface cat="encoder" video="2" audio="3" mpeg2="1" sectionsandtables="5"/>
    <filters>
    <filter cat="tvtuner" name="Hauppauge WinTV 418 Tuner" checkdevice="true"/>
    <filter cat="tvaudio" name="Hauppauge WinTV 418 TvAudio" checkdevice="true"/>
    <filter cat="crossbar" name="Hauppauge WinTV 418 Crossbar" checkdevice="true"/>
    <filter cat="capture" name="Hauppauge WinTV 418 Video Capture" checkdevice="true"/>
    <filter cat="encoder" name="Hauppauge WinTV 418 Encoder" checkdevice="true"/>
    </filters>
    <connections>
    <connection sourcefilter="tvtuner" sourcepin="0" sinkfilter="crossbar" sinkpin="%tvtuner%"/>
    <connection sourcefilter="tvtuner" sourcepin="1" sinkfilter="tvaudio" sinkpin="0"/>
    <connection sourcefilter="tvaudio" sourcepin="0" sinkfilter="crossbar" sinkpin="%audiotuner%"/>
    <connection sourcefilter="crossbar" sourcepin="0" sinkfilter="capture" sinkpin="0"/>
    <connection sourcefilter="crossbar" sourcepin="1" sinkfilter="capture" sinkpin="1"/>
    <connection sourcefilter="capture" sourcepin="4" sinkfilter="encoder" sinkpin="0"/>
    </connections>
    </tv>
    </capturecard>


    In the original file from 0.2.3.0 RC2 (with the 74440070 tuner):

    <capturecard commercialname="Hauppauge WinTV HVR1600 (NTSC)" capturename="Hauppauge WinTV 418 Video Capture" devid="ven_14f1&amp;dev_5b7a&amp;subsys_74440070&a mp;rev_00">
    <capabilities tv="true" radio="false" mpeg2="true" mce="false" sw="false" bda="false"/>
    <tv>
    <interface cat="capture" video="2" audio="3" mpeg2="1" sectionsandtables="5"/>
    <filters>
    <filter cat="tvtuner" name="Hauppauge WinTV 418 Tuner" checkdevice="true"/>
    <filter cat="tvaudio" name="Hauppauge WinTV 418 TvAudio" checkdevice="true"/>
    <filter cat="crossbar" name="Hauppauge WinTV 418 Crossbar" checkdevice="true"/>
    <filter cat="capture" name="Hauppauge WinTV 418 Video Capture" checkdevice="true"/>
    <filter cat="encoder" name="Hauppauge WinTV 418 Encoder" checkdevice="true"/>
    </filters>
    <connections>
    <connection sourcefilter="tvtuner" sourcepin="0" sinkfilter="crossbar" sinkpin="%tvtuner%"/>
    <connection sourcefilter="tvtuner" sourcepin="1" sinkfilter="tvaudio" sinkpin="0"/>
    <connection sourcefilter="tvaudio" sourcepin="0" sinkfilter="crossbar" sinkpin="%audiotuner%"/>
    <connection sourcefilter="crossbar" sourcepin="0" sinkfilter="capture" sinkpin="0"/>
    <connection sourcefilter="crossbar" sourcepin="1" sinkfilter="capture" sinkpin="1"/>
    <connection sourcefilter="capture" sourcepin="4" sinkfilter="encoder" sinkpin="0"/>
    </connections>
    </tv>
    </capturecard>
    </capturecards>


    So I first deleted the line as specified in previous posts, I changed radio="true" by "false", and I tried to replace "capture" by "encoder"....and that's it! Worked perfectly!

    I think it would be an easy fix in the next release.
    I hope I'll help some of you guys with this post!


    Damien
     

    Khidr

    Portal Member
    October 4, 2007
    8
    0
    Alright, I've been through this thread, have installed, uninstalled various MP versions, latest, svn, etc... I did catch that my card was the 7444070 version, made the appropriate changes, and still nothing... It tunes for both atsc and ntsc, then I get black screen, and no signal detected in mp.

    I am using mp on a vista machine, and am able to get decent qam and analogue in wintv (hauppauge's app), and gbdvr. Anything else for me to try? I can post logs tonight

    Thanks.
     

    Andrew H

    MP Donator
  • Premium Supporter
  • September 8, 2007
    576
    42
    Alabama
    Home Country
    United States of America United States of America
    Not to insult you, but the changes above are to the capturecarddefinitions.xml file. Using the ENCODER version should allow MP to identify your 7444070 and perform the channel scan from within the setup. BEWARE you will need to delete any channels from previous scans as MP will not ADD new channels if it thinks they're "old" e.g. previously scanned.

    I have the 74040 and never had any issue with ATSC, only the NTSC was difficult to do. You DO still need the RC2 version of the file to begin with BECAUSE it has the ATSC half of the card identified. The thing is, if MP doesn't recognize your version at the Setup/CaptureCards tab then how did you even get to running MP? Use the MP-configuration and get the cards all set before you even open the main MP program.
     

    Khidr

    Portal Member
    October 4, 2007
    8
    0
    no insult... that's the file I made the changes to, and I have no problem with Mediaportal identfying both the ntsc and atsc/qam tuners, I have no problem with it going ahead with the scan, it's just that it only scans black screens, and when I open it in mp I get no signal detected.

    But it does find the cards, and adds them fine. Sorry for not being clear. I opened the main program on the off chance that the tuning preview might not have been working, to double check that I had no signal.
     

    diehard2

    Retired Team Member
  • Premium Supporter
  • April 22, 2006
    518
    28
    Chicago
    Home Country
    United States of America United States of America
    If anyone can attach the xml file for the latest svn with the appropriate corrections, I'll upload it. About quality control, we only support that on the hauppauge 100-500 line of products. I don't have the documentation for the 1600 or 1800.
     

    MrBungle67

    Portal Member
    September 20, 2007
    15
    1
    43
    Home Country
    France France
    I'll do it tonight (in like 3-4 hours).

    I'm now working since 3 weeks with the HVR1600 (version 74440070) with absolutly no problem, direct watching, timeshift, recording......everything perfect! Of course, it's a must to have 0.2.3.0 RC2.

    Damien
     

    Users who are viewing this thread

    Similar threads

    I think 1.38 is easier, it's a minor addition, judging by the lack of bugs, 1.39 is still a long way off. Ideally, the TuningParameters settings would be moved to MPE1, along with all the skins. Then any minor fixes could be updated quickly.
    I think 1.38 is easier, it's a minor addition, judging by the lack of bugs, 1.39 is still a long way off. Ideally, the...
    Hello and good morning, atm I´m gonna try to install my new MP2 Server with a hybrid solution DVB-T2 and MagentaTV. For DVB-T2 I...
    Replies
    9
    Views
    2K
    There is a conflict as you have said between WinTV ad MP TV. MP TV takes over the Hauppauge HVR-1265 card. I may be even getting more channels with it. The Titan TV worked great until last year. Now it will not run the scheduler. WinTV scheduler will let me program manually but I have to set a program for each day. If I try to set...
    There is a conflict as you have said between WinTV ad MP TV. MP TV takes over the Hauppauge HVR-1265 card. I may be even getting...
    Sorry, but I have followed all the links that show how to upload specs and logs. I have read numerous pages that seem to be out of...
    Replies
    7
    Views
    4K
    Well, all that remains is to find someone who will add this render if it is a render.
    Well, all that remains is to find someone who will add this render if it is a render.
    Are there plans to support other video renderers? MadVR got added a while ago, but this a 'hardcoded' selection in the...
    Replies
    23
    Views
    2K
    The reason I was thinking I needed more RAM is that TV now seems to be HiDef and so the files have grown. I edit the files before storing them, to reduce some size. It is finding that slower, I think. Or it could just be because I'm expecting more? The Baseboard manufacturer says ASUSTech Computer Inc; Baseboard product P7P55D-E...
    The reason I was thinking I needed more RAM is that TV now seems to be HiDef and so the files have grown. I edit the files before...
    I'm not sure where to post this query - I've been told, during a conversation about costs of upgrading, that W11 may not support my...
    Replies
    4
    Views
    4K
    I see no reason in Windows XP or 7, in my experience, on ancient Atom, Windows 10 worked faster than XP or 7...
    I see no reason in Windows XP or 7, in my experience, on ancient Atom, Windows 10 worked faster than XP or 7...
    Hi all, I'm new to MediaPortal and looking forward to using it. Just one catch and I apologize if it sounds silly - I want to run...
    Replies
    3
    Views
    1K
    Top Bottom