[Live-devel] RTSP source for VDR
Olivier DJIAN
odjosc at free.fr
Fri May 11 14:35:34 PDT 2007
Hi,
Finally, I succeeded writing the MediaSink object and all seems to work fine.
However, on an Athlon 1800+ computer, VDR consumes 100% CPU when plugin with
liveMedia is used (RTSP source) and 3% if not (using a DVB PCI card source).
I wonder how the "forever loop" works (e.g.
env->taskScheduler().doEventLoop())
Does someone have suggestions to help me diagnose where in my liveMedia using
there is some excessive cpu-consuming code (I don't make any video decoding
nor encoding with liveMedia as VDR uses TS stream directly) ?
Thanks for your help.
Olivier.
Le mardi 30 janvier 2007, Ross Finlayson a écrit :
> > > I.e., you must write an appropriate "MediaSink" object to handle the
> >>
> >> incoming TS data. (However, if you plan to just store this in a
> >> file, then you can use most of the "openRTSP" code as is. Or, you
> >> can just run "openRTSP" with the "-v" option, to get the incoming TS
> >> data written to 'stdout'.)
> >> --
> >
> >Unfortunately, it's not that easy because I'm only writing a plugin for
> > VDR.
>
> Therefore, you're going to have to figure out how to write such a
> 'plugin' that works with the "LIVE555 Streaming Media" event loop.
> Because I don't know anything about how such a plugin works - in
> particular, whether it has its own event loop (in which case you'd
> need to somehow merge it with ours), or whether it has its own
> thread, doing reads synchronously - I'm probably not going to be able
> to help you any more with this. I suggest consulting an appropriate
> mailing list for your VDR software.
More information about the live-devel
mailing list