Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report (Android 6) #10998

Closed
6 tasks done
bw4518 opened this issue Apr 24, 2024 · 7 comments
Closed
6 tasks done

Report (Android 6) #10998

bw4518 opened this issue Apr 24, 2024 · 7 comments
Labels
device/software specific Issues that only happen on some devices or with some specific hardware/software question Not really an issue, but more of a question about how something works

Comments

@bw4518
Copy link
Contributor

bw4518 commented Apr 24, 2024

Checklist

  • I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected version

0.27.0

Steps to reproduce the bug

  1. Playing any video on YT

Expected behavior

Video plays.

Actual behavior

Logs following error.

Screenshots/Screen recordings

No response

Logs

Exception

  • User Action: play stream
  • Request: Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing https://www.youtube.com/watch?v=i5BElynqBEo
  • Content Country: SK
  • Content Language: sk-SK
  • App Language: sk_SK
  • Service: YouTube
  • Version: 0.27.0
  • OS: Linux Android 6.0.1 - 23
Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(140, null, null, audio/mp4a-latm, mp4a.40.2, 130338, en, [-1, -1, -1.0], [2, 44100]), format_supported=YES
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:578)
	at android.os.Handler.dispatchMessage(Handler.java:98)
	at android.os.Looper.loop(Looper.java:148)
	at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100) Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100])
	at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2154)
	at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1073)
	at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1051)
	at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:843)
	at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)
	at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:709)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1889)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:782)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:1007)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:502)
	... 3 more
	Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100) Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100])
		... 13 more


Affected Android/Custom ROM version

Android 6.0.1 / Omni (custom rom)

Affected device model

Samsung Galaxy Tab 2 (P5110)

Additional information

I have tried to change the audio track from M4A to WEBM format, but no change.

@bw4518 bw4518 added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Apr 24, 2024
@opusforlife2
Copy link
Collaborator

And this didn't occur on 0.26.1?

@opusforlife2 opusforlife2 added the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 24, 2024
@bw4518
Copy link
Contributor Author

bw4518 commented Apr 25, 2024

I don't know, its a 'new' device that got in my hands. I could test it, but I reported it since NewPipe should support it from Android 5+.

@github-actions github-actions bot removed the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 25, 2024
@opusforlife2
Copy link
Collaborator

opusforlife2 commented Apr 25, 2024

Still need to know if it happens on 0.26.1.

@opusforlife2 opusforlife2 added the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 25, 2024
@bw4518
Copy link
Contributor Author

bw4518 commented Apr 26, 2024

Yes, tested it today, the same error on 0.26.1.

@github-actions github-actions bot removed the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 26, 2024
@opusforlife2
Copy link
Collaborator

Could you try downloading the video and playing it with https://f-droid.org/en/packages/com.brouken.player/ ? This is also an Exoplayer based app.

@opusforlife2 opusforlife2 added the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 28, 2024
@bw4518
Copy link
Contributor Author

bw4518 commented May 2, 2024

I did try it. Probably the same error.

AudioTrack init failed 0 Config(48000, 12, 48000) Format(2, null, null, audio/
raw, null, -1, en, [-1, -1, -1.0, null], [2, 48000])

@github-actions github-actions bot removed the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label May 2, 2024
@opusforlife2
Copy link
Collaborator

Then this is a bug with your device. There's nothing Newpipe can do about it, being Exoplayer-based. You could investigate using other custom ROMs.

@opusforlife2 opusforlife2 added question Not really an issue, but more of a question about how something works device/software specific Issues that only happen on some devices or with some specific hardware/software and removed bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device/software specific Issues that only happen on some devices or with some specific hardware/software question Not really an issue, but more of a question about how something works
Projects
None yet
Development

No branches or pull requests

2 participants