<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thomas-<div><br></div><div>That seems to work if I invoke vlc from the command line. Is there a way to do that from the GUI version as well? FWIW I'm on Mac OS X.</div><div><br></div><div>Thanks,</div><div><br></div><div><br></div><div>Walt Horat</div><div>---</div><div><div><div>On Aug 31, 2011, at 12:14 PM, Thomas Brouckaert wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hey Walt,<div><br></div><div>Run vlc with the option -vvv for debug information.</div><div>You will see in the log every time VLC is looking for a module and which module VLC picked.</div><div>This should give you a pretty accurate view of the current modules.</div>
<div><br></div><div>I hope this answers your question.</div><div><br></div><div>Regards,</div><div><br></div><div>Thomas<br><br><div class="gmail_quote">On Wed, Aug 31, 2011 at 17:15, Walt Horat <span dir="ltr"><<a href="mailto:walt@genaudioinc.com">walt@genaudioinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Forgive me if this is an obvious question. I have just gotten VLC building successfully and am seeing my exploratory printf() statements in the console, and am trying to learn my way around. What would be really helpful to my understanding right now is to be able to log or otherwise view the state of the current (entire) module chain at the point of beginning playback of media. Any suggestions or help would be greatly appreciated.<br>
<br>
Thanks,<br>
<br>
<br>
Walt Horat<br>
---<br>
“My optimism is based on the certainty that this civilization is about to collapse.<br>
My pessimism lies on the things that are dragging us down in its fall”<br>
Jean-François Brient<br>
<br>
On Aug 31, 2011, at 4:38 AM, Rémi Denis-Courmont wrote:<br>
<br>
> Hello,<br>
><br>
> On Wed, 31 Aug 2011 09:38:33 +0200, Jean-Paul Saman <<a href="mailto:jpsaman@videolan.org">jpsaman@videolan.org</a>><br>
> wrote:<br>
>> Please review.<br>
><br>
> Without zero copy, there should really no value in using direct mode<br>
> transfers. It is probably even slower than normal copy mode.<br>
><br>
> In the even that the capture device do not support standard transfers, VLC<br>
> should automatically detect the problem from hardware parameters, and<br>
> select the correct mode with no a command line option. I do not know if<br>
> there are such devices, and I would expect that ALSA plughw would work<br>
> around the problem if it exists.<br>
><br>
> --<br>
> Rémi Denis-Courmont<br>
> <a href="http://www.remlab.net/" target="_blank">http://www.remlab.net/</a><br>
> _______________________________________________<br>
> vlc-devel mailing list<br>
> To unsubscribe or modify your subscription options:<br>
> <a href="http://mailman.videolan.org/listinfo/vlc-devel" target="_blank">http://mailman.videolan.org/listinfo/vlc-devel</a><br>
<br>
_______________________________________________<br>
vlc-devel mailing list<br>
To unsubscribe or modify your subscription options:<br>
<a href="http://mailman.videolan.org/listinfo/vlc-devel" target="_blank">http://mailman.videolan.org/listinfo/vlc-devel</a><br>
</blockquote></div><br></div>
_______________________________________________<br>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="http://mailman.videolan.org/listinfo/vlc-devel">http://mailman.videolan.org/listinfo/vlc-devel</a><br></blockquote></div><br></div></body></html>