<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
> On Jun 26, 2013, at 8:24 AM, Yaobing Deng <<a
href="http://lists.live555.com/mailman/listinfo/live-devel">yaobing
at jriver.com</a>> wrote:
<br>
>><i> Meanwhile, in order to make their device work in our
application (JRiver Media Center), we are temporarily ignoring the
payload type <br>
>> discrepancy, in the following way, until SiliconDust
fixes the problem.<br>
><br>
</i>> Remember that under the terms of the (L)GPL, you are
therefore legally required to make your 'kludge' available to all
customers of your<br>
> application.
A much better solution, therefore, is to get 'SiliconDust' to fix
their buggy, non-standards-compliant hardware (e.g., via a firmware
<br>
> upgrade). Then, you won't need to make (and therefore won't
need to distribute with your own product) any changes to the
"LIVE555 <br>
> Streaming <br>
> Media" code.
Ross Finlayson
Live Networks, Inc.
<a href="http://www.live555.com/">http://www.live555.com/</a><br>
<br>
Thanks for the reminder about the GPL. I do have that in mind when
I replied your last message (and sorry for forgetting to fix the
subject line). Would it not be sufficient by making my changes
public on this developer mailing list (as I attempted in my previous
reply)?<br>
<br>
We change this block
<br>
<br>
// Check the Payload Type.
<br>
if ((unsigned char)((rtpHdr&0x007F0000)>>16)
<br>
!= rtpPayloadFormat()) {
<br>
break;
<br>
}
<br>
<br>
to this
<br>
<br>
// Check the Payload Type.
<br>
// Kludge - HDHomeRun Prime advertises the value 96, but
sends the value 33
<br>
if ((unsigned char)((rtpHdr&0x007F0000)>>16) !=
rtpPayloadFormat() &&
<br>
((unsigned char)((rtpHdr&0x007F0000)>>16) !=
33 || rtpPayloadFormat() != 96)) {
<br>
break;
<br>
}
<br>
<br>
inside function MultiFramedRTPSource::networkReadHandler1().
<br>
<br>
<br>
</body>
</html>