[Xesdeeni]

I tried looking on DC for an IR receiver, but they only have the remote/receiver for the Fusion. I sent an e-mail, but I didn't get a response (or my company's e-mail filter thought the response was SPAM).


Kei, should I give a call to DC?


Xesdeeni

 

[TPeterson]



Quote:
Originally Posted by sfhub /forum/post/0


Either I'm confusing you or you are confusing me

I thought the nVidia discussion was referring to the DVI port outputting RGB standard 16-235 or extended 0-255 range?


I don't know many people outputting YCbCr from the DVI-D port of an nVidia. I don't even know how to convince my nVidia card to output YCbCr from the DVI-D port. The HDTV options in the driver specify HDTV timings but I believe the output is still RGB.


Maybe I'm just totally confused.

From MIT's answer to my question about the "MyHD DVI output" and a cursory reading of some spec. sheets for DVI driver chips I had the impression that digital DVI outputs are always YCbCr. My comment about RGB/YPbPr referred to the MyHD analog output on the main card. I have not studied the details of the full DVI spec. so it's very possible that my conclusion about its digital output being always YCbCr is incorrect. (And I haven't looked at Nvidia's information on their chips and drivers at all, so that's wide open)

 

[TPeterson]



Quote:
Originally Posted by kdtjlamb /forum/post/0


Check that... the Video will become jerky... the audio is fine.

Overheating seems a definite possibility. Can you run for a while with the cabinet open for more cooling to see if the problem still occurs? If it does or doesn't, you'll have your answer.

 

[alk3997]



Quote:
Originally Posted by TPeterson /forum/post/0


Well, that explains why I'm not finding those parameters...I don't have a USB MyHD remote.


Perhaps someone else who has a USB remote and has observed the freeze-on-FF problem can confirm Andy's fix?

FYI...Ran another three files without any problems. This is now the longest I've gone without a hang-up. So, I'm gaining more confidence that the registry change had an affect.


Also, the final registry folder should have been "Parameters" instead of "Parameter". I'll fix in my original append.

 

[TPeterson]



Quote:
Originally Posted by alk3997 /forum/post/0


FYI...Ran another three files without any problems. This is now the longest I've gone without a hang-up. So, I'm gaining more confidence that the registry change had an affect.


Also, the final registry folder should have been "Parameters" instead of "Parameter". I'll fix in my original append.

Sounds good. I'd still like to hear from some other folks with USB remotes who've seen the problem and have successfully tried this fix...anybody??

 

[sfhub]



Quote:
Originally Posted by TPeterson /forum/post/0


From MIT's answer to my question about the "MyHD DVI output" and a cursory reading of some spec. sheets for DVI driver chips I had the impression that digital DVI outputs are always YCbCr. My comment about RGB/YPbPr referred to the MyHD analog output on the main card. I have not studied the details of the full DVI spec. so it's very possible that my conclusion about its digital output being always YCbCr is incorrect. (And I haven't looked at Nvidia's information on their chips and drivers at all, so that's wide open)

Not trying to beat a dead horse, I'm really trying to understand.


How do you configure the MyHD DVI port to output YCbCr? It only works when I configure it for RGB in the MyHD setup panel. All PC monitors I know of only support RGB on the DVI interface so MyHD must be sending out RGB or it wouldn't look right with those monitors. I don't even know if DVI supports YCbCr at all. It isn't in the DVI 1.0 spec but folks could have amended the spec and I don't rule that out.

 

[sfhub]



Quote:
Originally Posted by alk3997 /forum/post/0


FYI...Ran another three files without any problems. This is now the longest I've gone without a hang-up. So, I'm gaining more confidence that the registry change had an affect.


Also, the final registry folder should have been "Parameters" instead of "Parameter". I'll fix in my original append.

You might have mentioned this already, but if you change the parameters back, does the freeze happen again?

 

[TPeterson]



Quote:
Originally Posted by sfhub /forum/post/0


Not trying to beat a dead horse, I'm really trying to understand.


How do you configure the MyHD DVI port to output YCbCr? It only works when I configure it for RGB in the MyHD setup panel. All PC monitors I know of only support RGB on the DVI interface so MyHD must be sending out RGB or it wouldn't look right with those monitors. I don't even know if DVI supports YCbCr at all. It isn't in the DVI 1.0 spec but folks could have amended the spec and I don't rule that out.

There is no way to "configure" the MyHD DVI output. As has been pointed out numerous times in the MyHD threads, you must check the "RGB" and not "YPbPr" mode to enable the daughtercard's output port. The answer from MIT implied that that output is derived from an SMPTE spec that stipulates YCbCr (16-235/240) levels and that no translation of them (to 0-255) is performed. They may well be translated from YCbCr color space to "equivalent" RGB values if that's what the DVI spec requires--I don't know, but I do know that you're as well (or better) equipped to find out as am I.

 

[sfhub]



Quote:
Originally Posted by TPeterson /forum/post/0

The answer from MIT implied that that output is derived from an SMPTE spec that stipulates YCbCr (16-235/240) levels and that no translation of them (to 0-255) is performed. They may well be translated from YCbCr color space to "equivalent" RGB values if that's what the DVI spec requires--I don't know, but I do know that you're as well (or better) equipped to find out as am I.

This is what I expected the answer from MIT to have been. I'll just go on the assumption that this is what they meant.

 

[DPlettner]



Quote:
Originally Posted by TPeterson /forum/post/0


There is no way to "configure" the MyHD DVI output. As has been pointed out numerous times in the MyHD threads, you must check the "RGB" and not "YPbPr" mode to enable the daughtercard's output port. The answer from MIT implied that that output is derived from an SMPTE spec that stipulates YCbCr (16-235/240) levels and that no translation of them (to 0-255) is performed. They may well be translated from YCbCr color space to "equivalent" RGB values if that's what the DVI spec requires--I don't know, but I do know that you're as well (or better) equipped to find out as am I.

I have never tried calibrating MyHD. I always figured that it would be difficult since I had to calibrate both the TV and MyHD. Probably a good approach would be to calibrate my HDTV input for the video card using the instructions in this thread, and then calibrate MyHD at the same input using only the MyHD controls. Cliff used to post some information on this subject, such as this post from the archives. In this old thread, it appears that he is recommending much higher channel gains than the defaults (with a much lower saturation). However, MIT may have changed things.


-Dave

 

[rathwine]

I have the ff lockup, but all I have to do to fix it, is hit rewind once. I have the usb receiver, but could not find the registry keys you noted. Thanks, Troy.

 

[TPeterson]

Troy, the "lockup" that Andy and others (including, recently, your humble scribe) have occasionally seen is not cured by any remote or keyboard entry--it's a true lockup that requires the reset or power button to "cure".


But it's interesting nevertheless that you don't find those Registry keys either, if you have the USB remote! Did you use Regedit's search to look for the actual key names that Andy provided?

 

[rathwine]

I did not find the listed entries. I did a search for them individually, and also searched for Myirc. The only listings I got for MyIRC were some open keys, and locations for the myirc.exe program. Hope this helps. I am running windows 2000 and Myhd130 on that machine, with the usb remote. My other computer has winxp, and a serial remote. Take care. Troy.

 

[sfhub]



Quote:
Originally Posted by TPeterson /forum/post/0


But it's interesting nevertheless that you don't find those Registry keys either, if you have the USB remote! Did you use Regedit's search to look for the actual key names that Andy provided?

Well, I have no remote, usb or serial, and I have those keys that Andy mentioned.

 

[Muse]



Quote:
Originally Posted by TPeterson /forum/post/0


Troy, the "lockup" that Andy and others (including, recently, your humble scribe) have occasionally seen is not cured by any remote or keyboard entry--it's a true lockup that requires the reset or power button to "cure".

I'm wondering if it's the same lockup I get. I have the 120 with daughterboard on Win2000 and once in a while (probably timeshifting or watching a .tp recording) out of the clear blue (probably with a press of the rewind button, but not certain) I get a lockup. It's attended by an audio recycle, sort of a tone that plays over and over real loud every 1/5 second or so. There's nothing to do but hit the reset button. Fortunately, I always retain my timeshift files in my buffer, and more than anything because of this occasional problem. It's happened to me 3-4 times, I'd guess. Does this sound like what you're talking about?


Please let me piggyback another question: Having a MyHD 120/daughterboard combo, is most of the info found in this thread pertinent to my situation? Any guidelines on that? Thanks.

 

[rathwine]

I checked my Myhd120 in winxp machine, and I have those listings. I could not tell you if I have any lockup issues, because that machine only records, I do not play back on it. I was wrong before when I said that I had the serial on that machine, I actually am using the usb remote from the 130 on the 120/winxp machine, and the serial on the 130/win2000 machine. I am sorry that I can not help on the lockup issues, but at least I can account for the keys with the usb dongle. Troy.

 

[TPeterson]



Quote:
Originally Posted by sfhub /forum/post/0


Well, I have no remote, usb or serial, and I have those keys that Andy mentioned.

Sorry, you can disregard the PM I just sent, as I hadn't seen this post. Have you seen the lockup? Also, was there no remote attached when you installed MyHD.exe?

 

[sfhub]



Quote:
Originally Posted by TPeterson /forum/post/0


Sorry, you can disregard the PM I just sent, as I hadn't seen this post. Have you seen the lockup? Also, was there no remote attached when you installed MyHD.exe?

I want to say for sure I had no remote attached when I installed, but it was so long ago I can't say for certain. I looked back in my MyHD box and the USB remote receiver is still in the zip lock package with the twisty tied and looks like it was never touched, and I never used the physical remote (batteries are still wrapped) so I'm reasonably confident I've never installed the USB remote.


I do have the keys, but don't have the lockup problem, but I wouldn't expect to (if the analysis is correct that this is USB remote related) since I don't use the USB remote.

 

[TPeterson]

Hmmm...I have seen the problem, but far less frequently than Andy has--perhaps because I don't have the USB receiver and its driver active.


I don't have the Registry keys, presumably because I had the serial receiver installed before the USB ones even came out. I'll try a fresh install with no receiver attached and see if those keys get installed. (I doubt that they'll have any effect on a non-USB remote setup, however, even if they do turn out to be significant for the problem)


Andy, would you please try resetting the keys to their previous values to see if the freezes return??


And would one of the others who've seen this problem let us know if you have the USB receiver (and the keys) and see if you can reproduce Andy's result???

 

[newHDfan]

When I click on TitanTVHelper in the My HD folder, it gives "Failed to read packet!" error. The driver and application version is 1.66. I set the application as MyHD in the titantv.com setup page.


What does TitanTVHelper do? Is it useful?


Thanks!