#32 FFmpg-based enable by default

[Sebastian Hahn]

Hi

On Samsung Galaxy the player doesn´t work with aac+ stream (some Sony models have that problem too), it does if the FFmpg-based is enable.

All users with aac+ experience a 40 seconds delay (for a 32 Kbps stream) and a 20 seconds delay (for a 64 Kbps stream) to load. If the FFmpg-based is enabled it loads instantly (by mp3 streams too).

Examples (click on Android icon):
http://avradio.avnam.net/players/combinados/streaming1725/ (acc+ 32 Kbps)
http://avradio.avnam.net/players/combinados/contundente/radio.html (aac+ 64 Kbps)
http://avradio.avnam.net/players/combinados/avradio/radio.html (mp3 128 Kbps)

Is there any chance to get FFmpg-based enabled by default? We have tested it on aac+ and mp3 and it works in all models.

Thanks.

[Sebastian Hahn]

• Description has changed:

Diff:

--- old
+++ new
@@ -4,7 +4,7 @@

 All users with aac+ experience a 40 seconds delay (for a 32 Kbps stream) and a 20 seconds delay (for a 64 Kbps stream) to load. If the FFmpg-based is enabled it loads instantly (by mp3 streams too).

-Examples:
+Examples (click on Android icon):
 http://avradio.avnam.net/players/combinados/streaming1725/ (acc+ 32 Kbps)
 http://avradio.avnam.net/players/combinados/contundente/radio.html (aac+ 64 Kbps)
 http://avradio.avnam.net/players/combinados/avradio/radio.html (mp3 128 Kbps)

[William Seemann]

Sebastian, per your previous request, I enabled the FFmpg-based player by default for aac+ streams on Android 2.x, 3.x. At this point I won't enable the FFmpeg-based player by default for all streams because that code still needs a lot of improvement. Although the player works, it has some quirks and I feel that using it by default may result in a poor user experience. I will take this into consideration moving forward as I'm currently in the process of rewriting the FFmpeg-based player.