> On Sep 18, 2018, at 7:36 AM, GENESTIER Denis
> wrote:
>
> Hi Ross,
>
> I have found a problem in my algorithm for the RawVideoRTPSink (seen by the
> use of video in small resolution (like 32x24)).
> Here is a patch.
Thanks. I have now installed a new version (2018.09.18) of the code tha
Hi Ross,
I have found a problem in my algorithm for the RawVideoRTPSink (seen by the
use of video in small resolution (like 32x24)).
Here is a patch.
Thanks again for your support.
Denis.
liveRaw.patch
Description: liveRaw.patch
___
live-devel mail
Thanks. I’ve made this fix now.
FYI, the actual patch is simpler than the one that you proposed. It’s just:
diff -c RawVideoRTPSource.cpp~ RawVideoRTPSource.cpp
*** RawVideoRTPSource.cpp~ 2018-08-28 13:28:28.345447000 -0700
--- RawVideoRTPSource.cpp 2018-09-10 04:04:11.162413000 -070
Hi Ross,
By checking some degraded cases, I found a memory double deletion in the
RawVideoRTPSource.cpp, line 122.
Here is a patch to avoid this.
Denis.
correction.patch
Description: correction.patch
___
live-devel mailing list
live-devel@lists.live
> I just noticed you have forgotten to remove all the "*.orig" and a
> "liveMedia/stGDDpcY" files and from your tar ball delivery
Oops - my mistake. I’ll remove these from the next release of the software.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
__
Thanks Ross for your reactivity and your code review.
I just noticed you have forgotten to remove all the "*.orig" and a
"liveMedia/stGDDpcY" files and from your tar ball delivery
Regards,
Denis
___
live-devel mailing list
live-devel@lists.live555.com
Denis,
Many thanks for this. I have now installed a new version (2018.09.05) of the
code that includes your changes (with some small, mostly cosmetic, changes).
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
Hi Ross, how are you doing?
Here is a patch for managing the raw video stream in server's side, based on
the last live555 version.
I created a new sink "RawVideoRTPSink" and used it in the context of matroska
file streaming with the codecID V_UNCOMPRESSED (by the way I also added the
codec V_MJ
> Oops - my mistake. It should have been instantiated in the
> “RawVideoRTPSource” constructor.
>
> I’ve just installed a new version (2018.08.28) of the code that fixes this.
And sure enough - I made a mistake there, so I’ve just installed a new new
version (2018.08.28a) that should fix it fo
> On Aug 28, 2018, at 8:44 AM, GENESTIER Denis
> wrote:
>
> OK, many thanks Ross.
> Currently, I am still testing your version and it seems to give the same
> results that mine.
>
>> Yes, because it is possible (in RFC 4175) for data from more than one line
>> to be contained within a singl
OK, many thanks Ross.
Currently, I am still testing your version and it seems to give the same
results that mine.
> Yes, because it is possible (in RFC 4175) for data from more than one line to
> be contained within a single RTP payload, you need to subclass
> “BufferedPacket” to allow for this
> Also I did not used any "BufferedPacket" subclass, but maybe am I missing
> something?
Yes, because it is possible (in RFC 4175) for data from more than one line to
be contained within a single RTP payload, you need to subclass “BufferedPacket”
to allow for this. (Perhaps your ‘raw video’
Hi Ross,
As Promised, here is a patch for our first step for supporting raw video stream
: the receiver side.
It also contains a correction for the compilation of the mingw config that was
broken (my mistake because of my last submission on the keep alive on socket
:-D)
I have tested it with on
First, my apologies for the long delay in responding to this question. (I have
been traveling recently, including a couple of weeks “en vacances” in your
wonderful (though unusually hot :-) country.)
> On Jul 12, 2018, at 9:32 AM, GENESTIER Denis
> wrote:
>
> Hi Ross,
>
> We do have to d
Hi Ross,
We do have to deal with special camera that display only raw video, i.e.
uncompressed format (RFC 4175).
We are aware that is an heresy to stream video in that way, but you know how
clients may be with their legacy's devices!!!
In a first draft for supporting this, I am intending to cr
15 matches
Mail list logo
