Playback fails after server update to 3.0.5621.4

[Nodja 9]

After updating to 3.0.5621.4 (using the emby/embyserver docker image) playback fails after a certain moment. 

For the file in the logs any kind of playback after the 1:58 mark will fail.

 

I've upgraded the Android TV client from the current play store version to the latest git (1.0.44) and the problem persists.

 

The logs attached are from a resume attempt after a server restart.

I can do some regression testing if needed.

 

edit: forgot to say that the files play fine on the web client.

 

 - Nodja

server-63568347390.txt

transcode-b5f23de5-b18a-4fde-bf80-37e7ac0d482d.txt

Edited May 27, 2015 by Nodja

[ebr 16185]

Pretty sure this is going to be a server issue.

[Nodja 9]

I took the time to do a git bisect and it placed the blame on commit 372bb5316e6a684c698d78cefe6431b8464206ed
I've attached logs from a checkout at that commit.
 
I don't understand ffmpeg/hls enough to know what the flags are doing so I have no idea what's wrong, but here's the difference:

 

Good command line (from the previous commit 82b70ca40f6545c0cfb58d0b6f167e01e83bc9e6)

E:\projects\MediaBrowser\ProgramData-Server\ffmpeg\20150331\ffmpeg.exe -ss 00:03:18.444 -fflags +genpts -i file:"D:\Media\test\My Love Story!! - 1x03 - My Blue Ogre.mkv" -to 00:05:18.444 -map_metadata -1 -threads 0 -map 0:0 -map 0:1 -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 1907138 -bufsize 3814276 -vsync vfr -profile:v high -level 42 -force_key_frames expr:gte(t,n_forced*1) -vf "scale=min(iw\,1280):trunc(ow/dar/2)*2,subtitles='D\:/Media/test/My Love Story!! - 1x03 - My Blue Ogre.mkv:si=0',setpts=PTS -198/TB" -flags -global_header -copyts -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,asetpts=PTS-198/TB" -hls_time 3 -start_number 67 -hls_list_size 0 -y "E:\projects\MediaBrowser\ProgramData-Server\transcoding-temp\2c1820265d205cb85266a13a4097e254.m3u8"

 
Bad command line:

E:\projects\MediaBrowser\ProgramData-Server\ffmpeg\20150331\ffmpeg.exe -ss 00:03:19.344 -t 00:02:00.000 -i file:"D:\Media\test\My Love Story!! - 1x03 - My Blue Ogre.mkv" -map_metadata -1 -threads 0 -map 0:0 -map 0:1 -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 1907138 -bufsize 3814276                  -vsync vfr -profile:v high -level 42 -force_key_frames expr:gte(t,n_forced*3) -vf "scale=min(iw\,1280):trunc(ow/dar/2)*2,subtitles='D\:/Media/test/My Love Story!! - 1x03 - My Blue Ogre.mkv:si=0',setpts=PTS -199/TB" -output_ts_offset 00:03:19.344 -flags -global_header -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,asetpts=PTS-199/TB" -hls_time 3 -start_number 67 -hls_list_size 0 -y "E:\projects\MediaBrowser\ProgramData-Server\transcoding-temp\7cbb0ed61ab56507d9b7c8b7d86e542e.m3u8"

 
Should I post this on the server section so Luke can take a look at it?

server-63568642200.txt

transcode-a7391d87-0de0-49e2-9220-725466669905.txt

transcode-eb30ff37-748a-4888-b0db-b8da26c185c8.txt

[ebr 16185]

Should I post this on the server section so Luke can take a look at it?

 

Yes.

[Nodja 9]

Note: I originally posted this on the Android TV forum here but ebr thinks it's a server issue to I'm posting here.
 
Playback seems to fail for certain files on Android TV after updating to 3.0.5621.4 the weird thing is that it only fails after a certain seek timestamp.
For example, I play a file, it plays fine for the first 2 minutes, but after that playback stops. If I attempt to resume, playback fails (black screen), and fails for any seek time after the 2 minutes.

 

I took the time to do a git bisect and it placed the blame on commit 372bb5316e6a684c698d78cefe6431b8464206ed
I've attached logs from a checkout at that commit.
 
I don't understand ffmpeg/hls enough to know what the flags are doing so I have no idea what's wrong, but here's the difference:
 
Good command line (from the previous commit 82b70ca40f6545c0cfb58d0b6f167e01e83bc9e6)

E:\projects\MediaBrowser\ProgramData-Server\ffmpeg\20150331\ffmpeg.exe -ss 00:03:18.444 -fflags +genpts -i file:"D:\Media\test\My Love Story!! - 1x03 - My Blue Ogre.mkv" -to 00:05:18.444 -map_metadata -1 -threads 0 -map 0:0 -map 0:1 -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 1907138 -bufsize 3814276 -vsync vfr -profile:v high -level 42 -force_key_frames expr:gte(t,n_forced*1) -vf "scale=min(iw\,1280):trunc(ow/dar/2)*2,subtitles='D\:/Media/test/My Love Story!! - 1x03 - My Blue Ogre.mkv:si=0',setpts=PTS -198/TB" -flags -global_header -copyts -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,asetpts=PTS-198/TB" -hls_time 3 -start_number 67 -hls_list_size 0 -y "E:\projects\MediaBrowser\ProgramData-Server\transcoding-temp\2c1820265d205cb85266a13a4097e254.m3u8"

 
Bad command line:

E:\projects\MediaBrowser\ProgramData-Server\ffmpeg\20150331\ffmpeg.exe -ss 00:03:19.344 -t 00:02:00.000 -i file:"D:\Media\test\My Love Story!! - 1x03 - My Blue Ogre.mkv" -map_metadata -1 -threads 0 -map 0:0 -map 0:1 -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 1907138 -bufsize 3814276                  -vsync vfr -profile:v high -level 42 -force_key_frames expr:gte(t,n_forced*3) -vf "scale=min(iw\,1280):trunc(ow/dar/2)*2,subtitles='D\:/Media/test/My Love Story!! - 1x03 - My Blue Ogre.mkv:si=0',setpts=PTS -199/TB" -output_ts_offset 00:03:19.344 -flags -global_header -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,asetpts=PTS-199/TB" -hls_time 3 -start_number 67 -hls_list_size 0 -y "E:\projects\MediaBrowser\ProgramData-Server\transcoding-temp\7cbb0ed61ab56507d9b7c8b7d86e542e.m3u8"

I can provide a file that fails if needed. Let me know if you need anything else.

 

 - Nodja

server-63568642200.txt

transcode-a7391d87-0de0-49e2-9220-725466669905.txt

transcode-eb30ff37-748a-4888-b0db-b8da26c185c8.txt

[CBers 7451]

Any relation to this thread:

 

http://emby.media/community/index.php?/topic/21871-playback-pauses-when-ffmpeg-wakes/

 

Hopefully you have access to the Alpha area.

[Nodja 9]

One of your transcode logs seems to have the same issues so it might be related.

 

Can you do a git bisect to identify the faulty commit? Might be the same one.