I would say go for it if it's something that interests you. That's the
beauty of open source: you can do those things. Of course, the downside is
any Python wrappers/bindings may go stale as Ross (
http://www.rossfinlayson.com/) continues to push live555 in his own
direction. I don't want to discou
Thanks Jeff and Ben.
Given that the live555 will be the core library for the video streaming server
would it make sense therefore to prototype in Python and transfer to C++ when
reasonably clean. Perhaps Boost Python would help with this ? Are there good
resources for a Python video streaming se
I was wondering too becasue, my first thought is keep it simple and work in
the language the library supports. (Software engineering for me is "same
stuff, differnt language")
c/c++ is the best cross platform compiled language for me
python is the best cross platform scripting language for me.
Ha
> The video appears to remain fine, but the audio gets unbelievably scratchy
> once more than one client connects. With only one client, everything streams
> and plays fine; with more than one (and it appears to grow worse and worse as
> more clients grow), the audio starts to get scratchy, sort
I honestly think you're trying to put a square peg in a round hole here. If
you're planning to use Live555, unless someone has any evidence to the
contrary, I believe you should do everything in C++ and forgo trying to do
anything in Python.
On Sun, Feb 7, 2016 at 10:29 PM i...@interstrat.com wro
Ross, in addition to the DWORD_PTR, the only feedback I'd have is to use
waveInPrepareHeader(shWaveIn, toRelease, sizeof(WAVEHDR));
instead of
toRelease->dwFlags &= ~WHDR_DONE;
In your releaseHeadBuffer() method. I imagine it's probably doing the same
thing, but in the event anything changes u
Thanks. This will be included in the next release of the software (in a few
hours).
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-de
OK. I got into work just a bit ago and was going to check on your initial
question
"Was this the *only* change that you had to make here".
But I believe it is. I will respond here in a couple hours with my final
answer there, just in case.
I totally appreciate why (I imagine most people using yo
Hans,
Thanks for the note.
> - I got the source from the debian package currently available in jessie, not
> sure if this is the most recent?
No, unfortunately the version of the code that you used (2014.01.13) is *very*
out of date. We support only the most recent version of the code.
See
On 08-02-16 15:55, Hans Maes wrote:
- I got the source from the debian package currently available in
jessie, not sure if this is the most recent?
Sorry, should have looked further before posting the first time. Seems
the most recent version is 2016-01-29
Below is a patch against that versio
>> By the way, off topic (and I don't know if you care to know), but I had to
>> fix something in your waveInCallback method (in
>> WindowsAudioInputDevice_common). The callback method needs to have DWORD
>> parameters changed to DWORD_PTR to support 64-bit Windows.
>>
>> static void CALLBACK
Hello,
I noticed the openRTSP testprog had support for absolute seek start time
(-U option, "Range" header) but not for the absolute seek end time, but
support for the end time was present in the rest of the code.
I needed this for a small project I'm working on so I created this very
minor pa
Thanks for the note.
I’ve just released a new version (2016.02.08) of the code that should fix this.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/
Hi all,
I was trying to make call to my IP phone using playSIP with the following
arguments
./playSIP -a -A8 sip:Dialogphone@192.168.0.195
For any reason after answering a phone then playSIP crashed, Any idea please?
Below is the log:
root@systemcontroller testProgs]# ./playSIP -a -A 8 sip:Dia
14 matches
Mail list logo
