Let me ask for your forgiveness one more time.
No you are making me feel bad. Ineve was a developer but I did support myself for many years. I was a support manager for Compaq/HP at first and second levels, then I spent 7 years as the Desktop Product Service Manger. I was there 14 years.
It is easy to get stuck on either side of a support conversation where communication is not happening no matter how much is written.. Yao I know you are super busy. But I was providing aa wealth of troubleshooting information, trying to anticipate your questions before hand so you could begin to understand the problem with the least effort on your part.
When you started to focus on signal strength after all my posts should have made it obvious that is was a not simple signal strength problem, clearly the conversation was off track. I needed to be more clear and concise I guess.
Your respsonse is natural but I was trying to make clear that at the PC the HD Homerun is virtual and if it produces a high quality stream at one PC in the same Homegroup/subnet in fact on the same switch and not another it is not a signal quality issue no matter what the signal strength the MC 16 OSD tells us.
I know how to do troubleshooting, and I know how to be a good dance partner at doing collaborative troubleshooting. I was involved with hundreds of millions of dollars worth of Fortune 100 escalations to HP's Pengineering team. My second level guys could not send anything into 3rd level (Desktop Product Engineering )unless the case had been reviewed by me and was vetted thoroughly. The way we worked is we interfaced with the clients, duplicated their issue captured sample units and hand delivered it to engineering who made the bios patches, board revs or whatever ECNs were necessary. We owned the case until resolution, which sometimes took months.
I have no way of knowing if the issue belongs to JRiver or Silicon Dust. What I can say is that the Silicon Dust software is very,very mature and I have the latest SiliconDust stuff on each of these these boxes. In fact the HD Homerun firmware and software versions are only some days old.
The HD Homerun ATSC tuner at the PC this is strictly a software impelementation and if you are getting 100 percent signal strenght on one or more units than it is not a source problem. Now it could be nic related, timing related, bios related... but if the HD Homerun can play perfectly on all 4 boxes in HD Quick TV and WMC as well as play perfectly in JR MC on two of the boxes.. it is not a signal problem... when these channels play they are rock solid no pixelation, no stuttering, they just work or they don't work.
Both boxes that don't work are intel system boards with the same nic and probabvly the same chipset. I do know they are running different bioses. one of these Clarksdales was built with a retail box H55C mainboard patched to all the latest firmware and software.
The Gateway Clarksdale is running current nic and video drivers, I have no idea about the MEI drivers. chipset drivers or the bios. It is the wife's machine and I don't mess with it except when it doesn't work.
For testing and to relieve your concerns about signal strength I placed a very high quality motorola 15 dB drop amp in line. It of course made no difference because it was never actually a signal issue.
If I get time over the next days I have an E3300 box that is not in production. It just needs a GPU put back in it to bring it online. It has a Gigabyte board... I am going to bet it also plays the HD Homerun perfectly in JRiver... there is something with these Clarksdales. possibly with the nics configurations most likely that is creating a timing problem for MC 16. Not for WMC, they are completely robust with HD Homeruns in WMC on all 4 boxes.
I even have an Atom that I can test with...