[vlc-devel] qtkit mac development and threads

Feurstein, Michael Michael.Feurstein at wu.ac.at
Tue May 8 18:30:59 CEST 2012

> -----Ursprüngliche Nachricht-----
> Von: vlc-devel-bounces at videolan.org [mailto:vlc-devel-
> bounces at videolan.org] Im Auftrag von Rémi Denis-Courmont
> Gesendet: Dienstag, 08. Mai 2012 17:34
> An: vlc-devel at videolan.org
> Betreff: Re: [vlc-devel] qtkit mac development and threads
> Le mardi 8 mai 2012 18:09:49 Feurstein, Michael, vous avez écrit :
> > so. yeah. my question: how do i grab hold of the main thread
> The main thread is an abstract concept. I don't understand the grabbing
> metaphore here. What do you actually want to get?
> > and have an NSRunLoop run on it?
> It is up to the LibVLC application programmer what the main thread does. It is
> not up to you as the LibVLC plugin developer to decide. LibVLC and its plugins
> cannot make any assumptions in that respect.
> (In particular, the VLC media player runs a sigwait() loop. But that is
> irrelevant; as there are other applications doing other stuff.)
> > or put differently why doesn't it start transcoding/streaming
> > automatically as with an rtsp input?
> As the commit log implies, the plugin assumes that the main thread runs the
> Cocoa main loop. When that is not the case, then the plugin gets stuck.

So from this I assume that I need to manually start a cocoa main loop for the plugin to do its work - or is this as a LibVLC plugin developer outside of my scope?

Furthermore - from another perspective: if I start qtcapture:// via the GUI or terminal and press play (the non-automatic way) the plugin doesn't get stuck. Would it help to look into those steps source code wise? if yes - where would I have to look?

-Michael Feurstein

More information about the vlc-devel mailing list