Jump to content

Seek during recording fails: Invalid frame dimensions 0x0.


Mister Steve

Recommended Posts

Mister Steve

Often Emby has trouble seeking for playback position during a recording.   When this happens the duration shows a junk number, or NaNNaNNaN, or a fraction of the actual recording time.   I'm using an Android phone (screenshot below) and NVIDIA Shield, and seems to only happen if I'm watching then exit and try to resume.     It's maddening backing out of playback at half time, only to find you cannot resume and watch the rest of a game.   The 2nd half of the Bills-Chiefs game was probably boring and uneventful anyway so I'm sure we didn't miss much.   Details below.

Screenshot_20220123-214336.png

Example log from Shield playback.    It appears Emby first tries HW decoded playback, which fails with "Invalid frame dimensions 0x0. could not seek to position 85621.853" then falls back to SW decoded playback, which fails the same way.  Recording is from an HDHomerun Connect Quatro.

-----

Operating System: Linux version 5.14.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
OS/Process: x64/x64
Emby Server version: 4.6.7.0
Operating system: Unix 5.14.0.0


>>>>>>  User policy for emby
        EnablePlaybackRemuxing: True
        EnableVideoPlaybackTranscoding: True
        EnableAudioPlaybackTranscoding: True

>>>>>>  Affected codecs
Encoder VAAPI RocketLake-S GT1 UHD Graphics 750 - H.264 (AVC)
        Adapter #0: 'RocketLake-S GT1 UHD Graphics 750' Id:19594 (Driver: Intel iHD driver for Intel(R) Gen Graphics - 21.2.2 (1dd7d7f), Vendor: Intel Corporation)
        Frame Sizes: 32x32...4096x4096
        Color Formats: NV12
        Profiles: Main Profile (Level 6), High Profile (Level 6), Constrained Baseline Profile (Level 6)

Decoder VAAPI RocketLake-S GT1 UHD Graphics 750 - MPEG-2
        Adapter #0: 'RocketLake-S GT1 UHD Graphics 750' Id:19594 (Driver: Intel iHD driver for Intel(R) Gen Graphics - 21.2.2 (1dd7d7f), Vendor: Intel Corporation)
        Frame Sizes: max 2048x2048
        Color Formats: NV12
        Profiles: Simple Profile (High Level), Main Profile (High Level)


>>>>>>  FindVideoEncoder - Media: h264, UseHardwareCodecs: True, Mode: Custom
Info    Checking: 'VAAPI RocketLake-S GT1 UHD Graphics 750 - H.264 (AVC)'
Info    Check successful - selecting 'VAAPI RocketLake-S GT1 UHD Graphics 750 - H.264 (AVC)'

>>>>>>  FindVideoDecoder - MediaType: mpeg2video, Mode: Custom
Info    Checking: 'VAAPI RocketLake-S GT1 UHD Graphics 750 - MPEG-2'
Info    Check successful - selecting 'VAAPI RocketLake-S GT1 UHD Graphics 750 - MPEG-2'

>>>>>>  Processing Plan
Info    Name                                        CanDoInHardware      WillDoInHardware     Reason                                  
Info    VAAPI RocketLake-S GT1 UHD Graphics 7... >> True                 True                 Hardware Codec                           
Info    VideoInput                               >> True                 True                 Same adapter (/dev/dri/renderD128), s... 
Info    Deinterlace                              >> True                 True                                                          
Info    VideoOutput                              >> True                 True                 Hardware encoder                         
Info    VAAPI RocketLake-S GT1 UHD Graphics 7... >> True                 True                 Hardware Codec                           

>>>>>>  Projected Processing Formats
Info    Previous                HW-Context   Format       SW-Format           Size   Next
Info    mpeg2video           >> VAAPI        vaapi_vld    nv12           1920x1080 >> deinterlace_vaapi
Info    deinterlace_vaapi    >> VAAPI        vaapi_vld    nv12           1920x1080 >> 

/opt/emby-server/bin/ffmpeg -loglevel +timing -y -print_graphs_file "/var/lib/emby/logs/ffmpeg-transcode-xxxx_1graph.txt" -copyts -start_at_zero -analyzeduration 3000000 -f mpegts -ss 01:43:52.112 -c:v:0 mpeg2video -hwaccel:v:0 vaapi -hwaccel_device:v:0 /dev/dri/renderD128 -hwaccel_output_format:v:0 vaapi -i "http://127.0.0.1:8096/LiveTv/LiveRecordings/xxxx/stream" -filter_complex "[0:0]deinterlace_vaapi@f1[f1_out0]" -map [f1_out0] -map 0:1 -sn -c:v:0 h264_vaapi -b:v:0 15000000 -g:v:0 90 -maxrate:v:0 15000000 -bufsize:v:0 30000000 -sc_threshold:v:0 0 -keyint_min:v:0 90 -r:v:0 29.970029830932617 -profile:v:0 high -level:v:0 4 -c:a:0 copy -metadata:s:a:0 language=eng -disposition:a:0 default -fflags +discardcorruptts+fillwallclockdts -max_delay 5000000 -avoid_negative_ts disabled -f segment -map_metadata -1 -map_chapters -1 -segment_format mpegts -segment_list "/srv/dev-disk-by-uuid-xxxx/emby/transcode/transcoding-temp/649C7B.m3u8" -segment_list_type m3u8 -segment_time 3 -segment_list_entry_prefix hls/649C7B/ -segment_start_number 0 -individual_header_trailer 0 -write_header_trailer 0 -segment_write_temp 1 "/srv/dev-disk-by-uuid-xxxx/emby/transcode/transcoding-temp/649C7B_%d.ts"

21:30:57.256 ffmpeg version 4.3.0-emby_2021_02_27 Copyright (c) 2000-2021 the FFmpeg developers and softworkz for Emby LLC
21:30:57.256   built with gcc 8.3.0 (crosstool-NG 1.24.0)
21:30:57.256 Execution Date: 2022-01-23 21:30:57
21:30:57.265 [mpeg2video @ 0x25cb840] Invalid frame dimensions 0x0.
    Last message repeated 24 times
21:30:57.271 http://127.0.0.1:8096/LiveTv/LiveRecordings/xxxx/stream: could not seek to position 85621.853
21:30:57.271 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveRecordings/xxxx/stream':
21:30:57.271   Duration: N/A, start: 79389.741000, bitrate: N/A

 

Info    Previous transcoding attempt failed. Falling back to software transcoding.


>>>>>>  FindVideoDecoder - MediaType: mpeg2video, Mode: Custom
Info    Checking: 'Automatic software decoder'
Info    Check successful - selecting 'Automatic software decoder'

>>>>>>  Processing Plan
Info    Name                                        CanDoInHardware      WillDoInHardware     Reason                                  
Info    Automatic software decoder               >> False                False                Software Codec                           
Info    VideoInput                               >> False                False                Not a hardware decoder                   
Info    Deinterlace                              >> False                False                                                         
Info    VideoOutput                              >> False                False                Not a hardware encoder                   
Info    libx264 Software Encoder                 >> False                False                Software Codec                           

>>>>>>  Projected Processing Formats
Info    Previous                HW-Context   Format       SW-Format           Size   Next
Info    mpeg2video           >> -            yuv420p      yuv420p        1920x1080 >> yadif
Info    yadif                >> -            yuv420p      yuv420p        1920x1080 >> 

...


21:31:12.932 ffmpeg version 4.3.0-emby_2021_02_27 Copyright (c) 2000-2021 the FFmpeg developers and softworkz for Emby LLC
21:31:12.932   built with gcc 8.3.0 (crosstool-NG 1.24.0)
21:31:12.932 Execution Date: 2022-01-23 21:31:12
21:31:12.938 [mpeg2video @ 0x185e6c0] Invalid frame dimensions 0x0.
    Last message repeated 24 times
21:31:12.943 http://127.0.0.1:8096/LiveTv/LiveRecordings/xxxx/stream: could not seek to position 85621.853
21:31:12.943 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveRecordings/xxxx/stream':
21:31:12.943   Duration: N/A, start: 79389.741000, bitrate: N/A

 

Any ideas?

 

  • Haha 1
Link to comment
Share on other sites

10 minutes ago, Mister Steve said:

The 2nd half of the Bills-Chiefs game was probably boring and uneventful anyway so I'm sure we didn't miss much

LOL

Hi.  I hope you really did catch it.

Seeking/resuming while recording is a tricky area right now.  We are working on improving it.

  • Like 1
Link to comment
Share on other sites

Mister Steve
18 minutes ago, ebr said:

LOL

Hi.  I hope you really did catch it.

Seeking/resuming while recording is a tricky area right now.  We are working on improving it.

That's good to hear.   We went on a news blackout and resumed watching the next morning after the recording completed.

 

 

Link to comment
Share on other sites

MBSki
20 minutes ago, Mister Steve said:

That's good to hear.   We went on a news blackout and resumed watching the next morning after the recording completed.

Same here. And as a Bills fan I probably should've just deleted the recording and pretended that the game never happened. 🤬

Link to comment
Share on other sites

  • 2 weeks later...
On 1/25/2022 at 10:28 AM, mbarylski said:

Same here. And as a Bills fan I probably should've just deleted the recording and pretended that the game never happened. 🤬

More like pretend the Bills never happened. LOL

  • Haha 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...