ExoPlayer Audio Playback speed issue about exoplayer HOT 7 CLOSED

That sounds like a bug in the underlying platform. Are you streaming audio using HLS, or something else, and do you have a test stream we could look at?

from exoplayer.

Hi,

I am only using the below mentioned code to play stream using ExoPlayer. The URL is "http://sgpc.net:8000". You can also try http://new.sgpc.net:8000.

And this is the full code that I am using

private void playExpoPlayer(AudioTemplate audioTrackObject) {
final String BASE_URL = audioTrackObject.url;// "http://sgpc.net:8000";

    Uri builtUri = Uri.parse(BASE_URL);

    // Build the sample source
    FrameworkSampleSource sampleSource = new FrameworkSampleSource(this,
            builtUri, null, 1);

    // Build the track renderers
    TrackRenderer audioRenderer = new MediaCodecAudioTrackRenderer(
            sampleSource, null, true);

    // Build the ExoPlayer and start playback
    exoPlayer = ExoPlayer.Factory.newInstance(1);
    exoPlayer.prepare(audioRenderer);
    exoPlayer.setPlayWhenReady(true);
    exoPlayer.addListener(this);
    MediaButtonHelper.registerMediaButtonEventReceiverCompat(audioManager,
            mMediaButtonReceiverComponent);

    notifyChange(PLAYSTATE_CHANGED);

}

Just to add the link "http://sgpc.net:8000" only work for 3 minutes on "Samsung" phones using Android default "MediaPlayer" class. And that was the reason I have tried ExoPlayer for Android 4.1 + versions. With ExoPlayer the link works smoothly on my Samsung S4 but now my users have started reporting that the audio play back speed is double than normal speed.

Thanks,
Khushwant Singh

from exoplayer.

Hi Again,

It looks like the issue is only with Android 4.2 version.

Thanks,
Khushwant Singh

from exoplayer.

Hi,

Any update on this or any workaround?

Thanks

from exoplayer.

It's likely to be a platform issue, in which case there's probably not an easy workaround for the problem.

from exoplayer.

Closing since it's likely to be a device specific issue. Sorry.

from exoplayer.

We have the same problem here and had a larger discussion about that issue.
There seems to be a larger group of devices that have this issue. Maybe exoplayer should check if as well if the device is supported in forehand and throw a DeviceNotSupportedException to make clear what is happening.

from exoplayer.