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

Transcoding fails due to bad ffmpeg parameters, but only for this client #827

Open
BrunoMSantos opened this issue Dec 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@BrunoMSantos
Copy link

Describe the bug

I noticed this playing flac files that meet the criteria for being transcoded (high bitrate meeting a threshold). On Android it all works fine (log attached), but not for the desktop player (in Linux if relevant, logs attached as well).

The thing that puzzles me is that in both cases the transcoding should be equivalent (flac->aac), though for some reason, the ffmpeg command ends up being different depending on the client and fails for this one. Maybe this is an issue with the server in fact, but given that I can only reproduce it with this client, I'm posting it here 1st.

Logs for the respective transcodes:
android.txt
desktop.txt

The relevant errors to help others search for the issue:

[flac @ 0x5e63e50dbb00] Invalid audio stream. Exactly one FLAC audio stream is required.
[out#0/flac @ 0x5e63e50db140] Could not write header (incorrect codec parameters ?): Invalid argument

To Reproduce

  1. Set up client and server such that transcoding is necessary for audio files.
  2. Play a sufficiently high bitrate flac file.

Desktop:

  • OS: Linux
  • Server v10.10.3; desktop client v1.11.1; android client used for comparison v2.6.2
  • Installation Method: pacman (server package from extra and desktop client from aur)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

1 participant