Closed QBANIN closed 2 years ago
Can you upload the full client log (as a file so we can download it)? Make sure you remove any sensitive info from it first
Can you upload the full client log (as a file so we can download it)? Make sure you remove any sensitive info from it first
What do you mean by "full"? Since boot? The one in bug report was captured when the playback started with command adb logcat |grep jellyfin
not all useful lines will match against "jellyfin". instead what I'd do is force stop the app, run adb logcat > unfiltered_log.txt
before starting and keep the log going while you reproduce the issues, and then stop it. Note the PID of the app (I think it's the second or third column, which in that log is 6381). Then do cat log.txt | grep 6381 > filtered_log.txt
(replacing 6381 with the current PID)
not all useful lines will match against "jellyfin". instead what I'd do is force stop the app, run
adb logcat > unfiltered_log.txt
before starting and keep the log going while you reproduce the issues, and then stop it. Note the PID of the app (I think it's the second or third column, which in that log is 6381). Then docat log.txt | grep 6381 > filtered_log.txt
(replacing 6381 with the current PID)
Ok. Can you delete this issue? I'll make a new one with filename removed.
I closed it as requested. fyi:you can close issues you've opened.
We usually don't delete issues, just close them
@mueslimak3r Well this is not what I meant :) I just wanted to remove filename from the logs but it stays in edit history anyway. AFAIK the only way is to delete the issue (or not?)
You can edit something and then delete the edit history.
I took a look at the logs. It looks like the ffmpeg log you included in this issue is from 0.12.3? Can you find one from testing against 0.13? You can tell which is which because your device supports HLS so for 0.13 with exoplayer it would be writing to .ts (on server 10.8). The ffmpeg log shows writing to .mkv
Before putting time into that though, I suggest trying disabling "Allow encoding in HEVC format" in the Playback settings on your server.
Starting with 0.13 HEVC playback is supported by the app, and that means the server will encode in it if your server has that enabled.
Depending on your setup, it may just not be able to handle transcoding to HEVC. Lets see if the cause of the buffering issue is as simple as your server just transcoding VC1 -> HEVC too slow.
You're right. Tested again with HEVC encoding disabled and now the movie plays fine using 0.13.x player version. ffmpeg 0.13.0.txt
glad to hear it's working. Feel free to close this issue if everything's good now.
@mueslimak3r let me perform few more tests
Describe the bug
Since upgrade to Jellyfin 0.13.0 some movies doesn't start while using ExoPlayer because of "player error" or load for a long time at the begginnig anf then keep buffering ( pause and resume) every few seconds. VLC seems to be working fine but for me is unusable because it dowmix audio to stereo. Tried all 0.13.0-beta1 up to final 0.13 release and all of them are affected. The last bug-free version is 0.12.3.
Attaching logs from example movie, there are few more if you need more information.
EDIT: Replaced wrong 0.12.3 log output with correct one.
Logs
FFmpeg logs
Media info of the file
Application version
0.13.0
Device information
Amazon FireTV 4k Max 2021
Android version
Fire OS 7.2.5.5
Jellyfin server version
10.8.0 preview from https://hub.docker.com/r/nyanmisaka/jellyfin but official 10.7.0 is affected as well (no difference)