Lots Of Errors With Vlc, Is That Ok?

[Jamo]

Hi, I use VLC a lot. And usually use it from terminal to watch videos. However, when VLC in started from terminal it gives a lot of errors. Like in latest Tekzilla MP4 Large It gave me a bunch of errors. Is it OK, or should I react to those somehow. Im using Ubuntu 10.10.

Any of those errors doesn't effect videos in any noticeable way, but all that on terminal is irritating.

jarmo@jarmo:~$ vlc tekzilla--0187--top-5-products-at-macworld--large.h264.mp4 
VLC media player 1.1.4 The Luggage (revision exported)
Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
[0x9daa914] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Blocked: call to setlocale(6, "")
Blocked: call to sigaction(17, 0xb750c0d4, 0xb750c048)
Warning: call to signal(13, 0x1)
Warning: call to signal(13, 0x1)
Warning: call to srand(1296191984)
Warning: call to rand()
Blocked: call to setlocale(6, "")

(process:1587): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
Warning: call to signal(13, 0x1)
Warning: call to signal(13, 0x1)
Blocked: call to setlocale(6, "")
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one
number of reference frames exceeds max (probably corrupt input), discarding one

(<unknown>:1587): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'

(<unknown>:1587): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed

(<unknown>:1587): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed

[Sparda]

If it works, ignore them. These messages are likely to help you figure out why it doesn't work when it doesn't work (sort of always on debug messages).

[Jamo]

If it works, ignore them. These messages are likely to help you figure out why it doesn't work when it doesn't work (sort of always on debug messages).

It works well, but those are just too irritating.

[Sparda]

Check out VLC's man page, there might be an option to disable warnings. Alternatively, you could just send all of stdout to /dev/null.

[commodo]

Most likely you'll get a lot of errors in Windows or any other OS; probably not the same but a lot of them in any case.

To see them in Windows you have to open VLC, hit Ctrl + M (might work in the Linux/Mac GUI) and set the verbosity level to 2 (or more if it allows you to).

That way you can get all sorts of debugging info than can be useful. By default the GUI does not show you debug info, but starting it from the console does.

I used VLC to stream video (especially live video from capture cards) and using their debug outputs helped me out a lot. If you're really irritated about it, try setting in the command line the verbosity to zero; you can get a lot of help in their wiki page here.

VLC is probably the awesomest cross platform player and also streamer; although as a streamer it's still not very good (I have a passion for audio/video streaming). Lately I've been looking for an open source cross-platform tool that is simple to use and do VJ-ing and live TV video mixing. Haven't had much luck with finding one though; if in 2-3 years one won't appear I'll probably write one up myself in my free time :P

There is a new branching in the VLC project called VLMC (VideoLan Movie Creator), but that's not even in alpha yet (I think).