(regression from 46f782a9)

(since the callbacks do not know the actual offsets)

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

Currently, the period time is more critical, so constrain it first.
Both values are interdependant with some drivers.

This is not fool proof, as the run-time version is not checked.
But versions 0.4/0.5 crash due to a bug in the libvdpau DRI2 code.

This reverts commit a08cf819.

This is the frequency for SACD Digital eXtreme Definition.

Higher sample rates exist, notably DSD's 2822.4kH but that is not PCM
and the bitrate computation would really risk 31-bits integer overflow.

Since b71c85b3, the output from the avcodec video decoder
requires the vout to handle the cropping. This uses an updated
version of the jni_SetAndroidSurfaceSize function to be able to
pass the visible size separately from the full size.
Signed-off-by: Martin Storsjö <martin@martin.st>

Characters with accents are not encoded, but apostrophes happen

With google accounts it's happening now

As said in Apple documentation drawRect should not be implemented for view based on opengl es layer.
Instead contentScaleFactor should be changed manually if needed. Underlying opengl es layer will adjust its scale accordingly.
Signed-off-by: Felix Paul Kühne <fkuehne@videolan.org>

This is exception of bonjour, because of jlj

Note that the visual plugin still depends on a GPL'd fft.
Note that the new vsxu plugin is still GPL (depending on a GPL library
anyway)

This reverts commit e61ba5a7.

Close #9117

The buffer size must be a multiple of the number of channels*sample_size or looping will break the channel layout.

Close #8483

Refs #9108

Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

This fixes ANativeWindow usage on 2.3 and 3.x. Therefore, revert
back to preferring ANativeWindow over the private symbols.
Signed-off-by: Martin Storsjö <martin@martin.st>

Even if ANativeWindow is a public API, the release call seems to
crash on a Nexus One (running 2.3) and on a Galaxy Tab (running 3.2).
The exact reason is not known or understood yet, but it might be
due to accessing and dealing with the Surface from both Java (via the
SurfaceHolder class) and via the ANativeWindow API.

Therefore, only use the ANativeWindow if the old methods aren't
found (that is, on 4.3).

The ANativeWindow output works fine on firmwares as early as 4.0
though.
Signed-off-by: Martin Storsjö <martin@martin.st>

Fix ba8cad3a