Reply to thread

Message

<blockquote data-quote="subtwo" data-source="post: 1125904" data-attributes="member: 125133">Just checking back on this to see if there is anything further to help with my situation.&nbsp; I contacted Silicondust hoping there was something they could do from their end and have posted below their analysis of my situation.&nbsp; It looks like there is a known bug with Mediaportal/HDHomeRun devices.&nbsp; Is this bug actually logged?&nbsp; I couldn't find it in the Jira TVE35 log.&nbsp; Is there anything I can do to help get the bug fixed?&nbsp; I'd be willing to work with a developer to test any new HDHomeRun code.&nbsp; I'm also a C# programmer so I could possible get involved in development as well.Silicondust Analysis:There is a bug in their program in that it follows an incorrect process to release the tuner, and that has to be fixed on their end to resolve the issue. A basic explanation of what is happening: the control process for the tuner requires the equivalent of making a phone call to the tuner. MP calls up a number, the HDHomeRun answers, exchange hellos, then proceed with whatever needs doing, say goodbye, then hang up. All the actual video streaming takes place over a separate path, so the control connection gets closed out because it's just sitting there not doing anything. If something needs to change later, a new connection/call is made. What you're seeing with the 5-10 second thing is the connection sitting idle for a bit (during which time things can be exchanged over it), but then closing out. After that period when you try to stop the stream, instead of establishing a new connection, it tries to reuse the old one. It's like trying to talk to someone you already hung up with by yelling at the phone sitting on your desk, it's not going to accomplish anything because there's no connection and the other end isn't listening.</blockquote>

[QUOTE="subtwo, post: 1125904, member: 125133"] Just checking back on this to see if there is anything further to help with my situation. I contacted Silicondust hoping there was something they could do from their end and have posted below their analysis of my situation. It looks like there is a known bug with Mediaportal/HDHomeRun devices. Is this bug actually logged? I couldn't find it in the Jira TVE35 log. Is there anything I can do to help get the bug fixed? I'd be willing to work with a developer to test any new HDHomeRun code. I'm also a C# programmer so I could possible get involved in development as well. Silicondust Analysis: There is a bug in their program in that it follows an incorrect process to release the tuner, and that has to be fixed on their end to resolve the issue. A basic explanation of what is happening: the control process for the tuner requires the equivalent of making a phone call to the tuner. MP calls up a number, the HDHomeRun answers, exchange hellos, then proceed with whatever needs doing, say goodbye, then hang up. All the actual video streaming takes place over a separate path, so the control connection gets closed out because it's just sitting there not doing anything. If something needs to change later, a new connection/call is made. What you're seeing with the 5-10 second thing is the connection sitting idle for a bit (during which time things can be exchanged over it), but then closing out. After that period when you try to stop the stream, instead of establishing a new connection, it tries to reuse the old one. It's like trying to talk to someone you already hung up with by yelling at the phone sitting on your desk, it's not going to accomplish anything because there's no connection and the other end isn't listening. [/QUOTE]

Verification