Hi Etienne,

I am not sure if I understood well your problem, but I have a strange behaving in Gem too with VLC plugin. I have 2 identical IP cams on a local network, and while the first cam streams video smoothly or almost smoothly, the other cam shows a one second stream max or less, than stops at the last frame and never goes on.

Already tried many computers with ubuntu 14.04.2 and looks the same. While in a browser or VLC i can see the stream, in Gem with videovlc plugin it stops.

Here are some error reports from the terminal, maybe it is interesting for you:

MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (100000). 80761 bytes of trailing data will be dropped!
../../../include/vlc_xlib.h:46:vlc_xlib_init: Xlib not initialized for threads.
This process is probably using LibVLC incorrectly.
Pass "--no-xlib" to libvlc_new() to fix this.
[b0e398c8] vdpau_avcodec generic error: Xlib not initialized for threads
[b0e398c8] vdpau_avcodec generic error: Xlib is required for VDPAU
[b0e643c0] core vout display error: Failed to change zoom
[b0e643c0] core vout display error: Failed to set on top
[b0e643c0] core vout display error: Failed to change source AR
[h264 @ 0xb0e329c0] Invalid level prefix
[h264 @ 0xb0e329c0] error while decoding MB 88 40
[b0e643c0] core vout display error: Failed to change zoom
[b0e643c0] core vout display error: Failed to change source AR

Popesz

On Mon, Mar 9, 2015 at 1:08 PM, Etienne Landon <landon.etienne@gmail.com> wrote:

Sorry, it took me some time to try different things. Thank you IOhannes for keeping this alive ^^

Hehe, Labomedia is a nice place for informations, but to handle with care. But that tutorial allowed me to have vlc plugin working some years ago, and as little changed since I don't see why it doesn't work anymore.

So far still no luck, but with my latest tries I had some interesting behaviour, that makes me think this might more be a vlc plugin issue as IOhannes suggested. Moreover Antoine kindly sent me it's binaries (those that are working on his computer, and they behave the same on my computer as the Gem I compiled. So let's say it's not related to compilation.

Looking in the plugin path direction, I realized that whatever vlc options I add with the path (like --plugin-path, or -vv), then pd doesn't crash, but doesn't display the frames. If pd is launched from terminal I get error messages from vlc core, so it seems like Gem and vlc are definitly talking to each other, and that it's a further negociation between them that causes the crash. Ubunt reports and gdb bt point at lua, it looks like lua scripts are used to parse metadata and get the plugin vlc should use, but I can't understantd why this works with vlc in cli but not in Gem.

Any idea what could be the issue ? I'm making a fresh install each and every time, vlc and vlc-dev from repo, no customisation. Even tried installing only the components suggested by Antoine on the other thread related to vlc (VlC plugin - missing openGL header)

2015-03-07 20:54 GMT+01:00 IOhannes m zmölnig <zmoelnig@iem.at>:
On 03/04/2015 10:16 PM, Jack wrote:
> For info, le right message is : [driver vlc, device screen://( and not

or just [device screen://(
Gem will try to open the given device with each backend until one claims
that it can open it.
so if no other backend nows how to open "screen://", Gem will end up
automatically selecting videoVLC for you.

fgmsdar
IOhannes

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list