Is imperative have the line "env->taskScheduler().doEventLoop();"
enabled to keep server streaming?
Yes!
LIVE555 applications use an event loop, and operate in response to
events that are handled within the loop. To write such an
application, you need to be familiar with the concept of event
I notice the server reads from a open (by fopen) file and i think i
should change this to read direct from the buffers my sender thread
constanlty receives.
I'm right??
Yes, that should work.
As I said before, see
http://www.live555.com/liveMedia/faq.html#liveInput for guidance.
--
Ross F
Other point,
Is imperative have the line "env->taskScheduler().doEventLoop();" enabled to
keep server streaming? Apparently this avoid start the server and keep
processing the resto of the source code.
Without this line, VLC returns "main input error: open of 'rtsp://
10.0.0.49:8554/mpeg2Transpo
Hi, Ross
maybe i was unclear about my point.
Until now, i can compile my application with C and C++ sources. So, i'm able
to copy the "testOnDemandRTSPServer.cpp" code to my application.
I want do that to turn the thread responsible for send the TS generated data
(in mu app) in a RTSP server and
I'm achieving some level of success in using LIVE555 as a library
for my C application until now. The goal is live streaming TS
(Transport Stream with H264 video and AAC audio) direct from my
application to VLC client.
But i believe some changes must be done because the program i'm
using as e
