- volume and mute hotkeys are handled by core now, providing a proper osd screen
- some fixes in detection if key combo is valid hotkey
- fix for mem leak

This is a temporary workaround until someone add support for f4v.

Work-around #4915
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

The comments field is also encoded as "COMMENTS=" instead of description. For example, Audacity encodes the comment box as "COMMENTS=" instead of "DESCRIPTION=".
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Ref #6652
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

The updateStatus() function should not interrupt the user and reset his position while he is dragging the volume slider.

Close #6652
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Some muxers are unable to read the spec...

With disabled webserver, linking fails at least on OSX and Linux, see
http://forum.videolan.org/viewtopic.php?f=12&t=101229 f.i.

The bit per samples must be exact for the avcodec decoder.
It closes #6799.

This is usually not visible, since you need avcodec+avformat, instead of
ts/faad. Close #6847
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Strings from the lua stack stop being valid after you pop them

This fixes a corner case where the old volume of an output plugin using
software amplification would be wrongly applied to the next output
plugin instance (if that used "hardware" amplification).

This was really just a glorified manner to set a pointer to NULL
(actually to a dummy function but whatever).

It is broken since 12edd19f and it crashes if type = 1.
Signed-off-by: Rafaël Carré <funman@videolan.org>

0xffff is full volume, which I understand to mean 0dB.

Currently, two objects of the class VLCMainWindow are generated. The first is alloated
from intf.m (triggered by the first log message that arrives) and is initialized by
both init and initWithContentRect. The second object is created from inside the nib file,
and is instantiated ONLY with initWithContentRect. Therefore, up to now _o_sharedInstance
had the wrong object and all calls to sharedInstance would cause problems.
But somehow, o_mainwindow in intf.m is updated to the correct second object, although it holds
the first object at start.

Furthermore, o_fspanel is also instantiated through the nib file.