Jump to content

Throttling Not Happening


Leinad86

Recommended Posts

Leinad86

Hello everyone,

I have exactly the same problem. Some users report that films/series start to buffer shortly after starting. The strange thing is that sometimes the problems occur and sometimes they don't. Yesterday evening I was able to recreate the problem after a report from a user, and this morning the series is running without any problems. If you play the film/series without transcoding there are no problems. What I also noticed is that when you look on the dashboard, the orange bar for the transcoding progress is completely filled!

Attach 2 logs and 2 pictures.

It also started for me after I updated to Emby 4.8.1.0.

Unraid 6.12.6
Emby 4.8.3.0
Transkoding Temp is a NVME
GPU RTX 4000
Ryzen 5700x
64GB Ram

Many thanks in advance

 

 

2024-03-09 07_47_18-NVIDIA GeForce Overlay DT.png

embyserver-63845566167.txt ffmpeg-transcode-17dc4851-90e1-47bd-a226-3b4b9a050e95_1.txt ffmpeg-transcode-4683450c-5ea8-4de7-b94f-791fa2d3d996_1.txt

20240309_070308000_iOS.png

Edited by Leinad86
Link to comment
Share on other sites

@Leinad86that'd odd. can you try setting the transcode temp folder back to default and see how things compare? thanks.

Link to comment
Share on other sites

Leinad86

Hi Luke, thanks for the quick reply.

I deleted everything in the transcoding settings, it should just be default. Unfortunately the same.

08:14:24.113 Too many packets buffered for output stream 1:1.
08:14:24.133 [libmp3lame @ 0x1154080] 3 frames left in the queue on closing
08:14:24.256 Conversion failed!
08:14:24.256 EXIT

The orange bar on the dashboard is complete again. It's just strange that the series runs without buffering! That's what I mean, sometimes it doesn't buffer!

ffmpeg-transcode-28be56e6-f34f-4bf7-9e61-047f4d8ed093_1.txt

Link to comment
Share on other sites

JoLarsson

Try disabling hardware transcoding. It's not a good fix but it's worth a try.

I have some weird intermittent buffering issues and subtitle issues that only appears when using hardware transcoding.

Link to comment
Share on other sites

Leinad86

I have now loaded the Emby Server Beta Docker from Unraid. Quickly set up and the films that don't run with normal Docker work wonderfully here. I'm attaching two more logs. Each from the two servers. Both run on the same hardware.

I still have to test the series that doesn't work.

Now the question for me is whether I should switch my main Emby installation to beta! Or is there a fix coming soon?

ffmpeg-transcode-d7906b7e-abff-4652-895a-fa7e8e0a7e63_1.txt ffmpeg-transcode-a3476fcc-7572-468a-85a1-6211de9f6e04_1.txt

Link to comment
Share on other sites

On 3/12/2024 at 4:06 AM, Leinad86 said:

I have now loaded the Emby Server Beta Docker from Unraid. Quickly set up and the films that don't run with normal Docker work wonderfully here. I'm attaching two more logs. Each from the two servers. Both run on the same hardware.

I still have to test the series that doesn't work.

Now the question for me is whether I should switch my main Emby installation to beta! Or is there a fix coming soon?

ffmpeg-transcode-d7906b7e-abff-4652-895a-fa7e8e0a7e63_1.txt 153.4 kB · 1 download ffmpeg-transcode-a3476fcc-7572-468a-85a1-6211de9f6e04_1.txt 7.82 MB · 1 download

These two comparisons are different files though, or at least different file paths. Can you provide a comparison from the same file? Thanks.

Link to comment
Share on other sites

Leinad86
Posted (edited)

I have now installed Emby 4.7.14.0 as a test.

Can someone tell me why HW transcoding works without problems here and not in 4.8.3.0?


What can I do to make it work again without problems? It doesn't happen in every film, just in some. The same with series. And whenever a problem arises, the transcoding progress display on the dashboard jumps to full. Sometimes the film continues to run without any problems and sometimes it starts to buffer.

The same thing happens with different films/series. Unfortunately I don't see any pattern. The logs always look the same. Do you need more?

4.8.3.0_Dashboard.png

Emby_4.7.14.0.txt Emby_4.8.3.0.txt

 

Edited by Leinad86
Link to comment
Share on other sites

visproduction

Related:
https://superuser.com/questions/1315664/why-ffmpeg-increases-file-size

Slight changes either in Emby encoding settings or how ffmpeg makes lossy copies of already lossy media can cause Invalid NAL unit size.
Some encoding issues in a video may cause ffmpeg to not handle encoding at the preferred user setting and then automatically changing the encoding to a lower quality to compensate may also fail on media that has prerecorded encoding issues.

The best way to rule out such encoding issues is to use a test video and not rely on random encoded videos.
---
Related issue solved:
https://github.com/mpv-player/mpv/issues/11268

Quote

 

Do you get the same error if you use https instead of http? That would rule out your ISP dropping packets.

yes, that's the problem, why is it such a ________?

 

Link to comment
Share on other sites

Leinad86

Yes, something has been changed, unfortunately I personally don't have the understanding to find out what exactly and where the problem lies.

I can only say that with V 4.7.14.0 everything worked without any problems.

Link to comment
Share on other sites

Leinad86

Does no one have any idea what could be the problem?

Will the problem be solved in the near future?

Link to comment
Share on other sites

Leinad86


Can someone give me some information here?

A we have no idea where the error is is better than no answer.

 

Thanks

Link to comment
Share on other sites

Happy2Play

Suggests TranscodingPosition is broke in 4.8.  But the devs will have to look at.

From logs above

4.8

  C:\Users\Media\Downloads\Emby_4.8.3.0.txt (8 hits)
	Line  298: >> ThrottleBySegmentRequest: RequestPosition: 00:00:39 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -39s (Treshold: 120s)
	Line  472: >> ThrottleBySegmentRequest: RequestPosition: 00:01:33 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -93s (Treshold: 120s)
	Line  657: >> ThrottleBySegmentRequest: RequestPosition: 00:02:27 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -147s (Treshold: 120s)
	Line  831: >> ThrottleBySegmentRequest: RequestPosition: 00:03:18 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -198s (Treshold: 120s)
	Line 1014: >> ThrottleBySegmentRequest: RequestPosition: 00:03:48 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -228s (Treshold: 120s)
	Line 1194: >> ThrottleBySegmentRequest: RequestPosition: 00:03:51 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -231s (Treshold: 120s)
	Line 1379: >> ThrottleBySegmentRequest: RequestPosition: 00:03:54 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -234s (Treshold: 120s)
	Line 1565: >> ThrottleBySegmentRequest: RequestPosition: 00:03:54 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -234s (Treshold: 120s)

4.7

  C:\Users\Media\Downloads\Emby_4.7.14.0.txt (62 hits)
	Line  499: >> ThrottleBySegmentRequest: RequestPosition: 00:01:15 - TranscodingPosition: 00:01:09 - ThrottleBuffer: -5s (Treshold: 120s)
	Line  900: >> ThrottleBySegmentRequest: RequestPosition: 00:02:03 - TranscodingPosition: 00:02:51 - ThrottleBuffer: 49s (Treshold: 120s)
	Line 1295: >> ThrottleBySegmentRequest: RequestPosition: 00:02:03 - TranscodingPosition: 00:04:27 - ThrottleBuffer: 145s (Treshold: 120s)
	Line 1321: >> ThrottleBySegmentRequest: RequestPosition: 00:02:06 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 163s (Treshold: 120s)
	Line 1326: >> ThrottleBySegmentRequest: RequestPosition: 00:02:09 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 160s (Treshold: 120s)
	Line 1331: >> ThrottleBySegmentRequest: RequestPosition: 00:02:09 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 161s (Treshold: 120s)
	Line 1336: >> ThrottleBySegmentRequest: RequestPosition: 00:02:12 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 158s (Treshold: 120s)
	Line 1341: >> ThrottleBySegmentRequest: RequestPosition: 00:02:15 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 156s (Treshold: 120s)
	Line 1346: >> ThrottleBySegmentRequest: RequestPosition: 00:02:15 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 156s (Treshold: 120s)
	Line 1351: >> ThrottleBySegmentRequest: RequestPosition: 00:02:18 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 153s (Treshold: 120s)
	Line 1359: >> ThrottleBySegmentRequest: RequestPosition: 00:02:21 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 151s (Treshold: 120s)
	Line 1367: >> ThrottleBySegmentRequest: RequestPosition: 00:02:21 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 151s (Treshold: 120s)

 

Link to comment
Share on other sites

On 3/25/2024 at 1:02 PM, Happy2Play said:

Suggests TranscodingPosition is broke in 4.8.  But the devs will have to look at.

From logs above

4.8

  C:\Users\Media\Downloads\Emby_4.8.3.0.txt (8 hits)
	Line  298: >> ThrottleBySegmentRequest: RequestPosition: 00:00:39 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -39s (Treshold: 120s)
	Line  472: >> ThrottleBySegmentRequest: RequestPosition: 00:01:33 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -93s (Treshold: 120s)
	Line  657: >> ThrottleBySegmentRequest: RequestPosition: 00:02:27 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -147s (Treshold: 120s)
	Line  831: >> ThrottleBySegmentRequest: RequestPosition: 00:03:18 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -198s (Treshold: 120s)
	Line 1014: >> ThrottleBySegmentRequest: RequestPosition: 00:03:48 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -228s (Treshold: 120s)
	Line 1194: >> ThrottleBySegmentRequest: RequestPosition: 00:03:51 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -231s (Treshold: 120s)
	Line 1379: >> ThrottleBySegmentRequest: RequestPosition: 00:03:54 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -234s (Treshold: 120s)
	Line 1565: >> ThrottleBySegmentRequest: RequestPosition: 00:03:54 - TranscodingPosition: 00:00:00 - ThrottleBuffer: -234s (Treshold: 120s)

4.7

  C:\Users\Media\Downloads\Emby_4.7.14.0.txt (62 hits)
	Line  499: >> ThrottleBySegmentRequest: RequestPosition: 00:01:15 - TranscodingPosition: 00:01:09 - ThrottleBuffer: -5s (Treshold: 120s)
	Line  900: >> ThrottleBySegmentRequest: RequestPosition: 00:02:03 - TranscodingPosition: 00:02:51 - ThrottleBuffer: 49s (Treshold: 120s)
	Line 1295: >> ThrottleBySegmentRequest: RequestPosition: 00:02:03 - TranscodingPosition: 00:04:27 - ThrottleBuffer: 145s (Treshold: 120s)
	Line 1321: >> ThrottleBySegmentRequest: RequestPosition: 00:02:06 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 163s (Treshold: 120s)
	Line 1326: >> ThrottleBySegmentRequest: RequestPosition: 00:02:09 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 160s (Treshold: 120s)
	Line 1331: >> ThrottleBySegmentRequest: RequestPosition: 00:02:09 - TranscodingPosition: 00:04:49 - ThrottleBuffer: 161s (Treshold: 120s)
	Line 1336: >> ThrottleBySegmentRequest: RequestPosition: 00:02:12 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 158s (Treshold: 120s)
	Line 1341: >> ThrottleBySegmentRequest: RequestPosition: 00:02:15 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 156s (Treshold: 120s)
	Line 1346: >> ThrottleBySegmentRequest: RequestPosition: 00:02:15 - TranscodingPosition: 00:04:50 - ThrottleBuffer: 156s (Treshold: 120s)
	Line 1351: >> ThrottleBySegmentRequest: RequestPosition: 00:02:18 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 153s (Treshold: 120s)
	Line 1359: >> ThrottleBySegmentRequest: RequestPosition: 00:02:21 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 151s (Treshold: 120s)
	Line 1367: >> ThrottleBySegmentRequest: RequestPosition: 00:02:21 - TranscodingPosition: 00:04:51 - ThrottleBuffer: 151s (Treshold: 120s)

 

What do you see in 4.9?

Link to comment
Share on other sites

Happy2Play
41 minutes ago, Luke said:

What do you see in 4.9?

It appears to be working fine for me on 4.8/4.9 on Windows.  As what I posted came from the Unix 6.1.74.0 logs above.

Spoiler

21:06:03.893 elapsed=00:00:48.59 frame= 6484 fps=133 q=19.0 size=N/A time=00:04:30.38 bitrate=N/A throttle=100 speed=5.56x    
21:06:04.446 elapsed=00:00:49.14 frame= 6485 fps=132 q=15.0 size=N/A time=00:04:30.43 bitrate=N/A throttle=100 speed= 5.5x    
>> ThrottleBySegmentRequest: RequestPosition: 00:02:33 - TranscodingPosition: 00:04:30 - ThrottleBuffer: 117s (Treshold: 120s)

Enter throttle value: <int, ms wait per input cycle> (0 to disable)

Disable throttling
21:06:04.954 elapsed=00:00:49.70 frame= 6486 fps=130 q=19.0 size=N/A time=00:04:30.48 bitrate=N/A throttle=off speed=5.44x    
21:06:04.958 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:04.966 SegmentComplete=video:0 Index=89 Start=267.308700 End=270.311700 Duration=3.003000 offset_pts=0 start_pts=267308700 Frames=72 filename=7ACF91_89.ts
21:06:04.966 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_90.ts.tmp' for writing
21:06:05.231 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:05.240 SegmentComplete=video:0 Index=90 Start=270.311700 End=273.314700 Duration=3.003000 offset_pts=0 start_pts=270311700 Frames=72 filename=7ACF91_90.ts
21:06:05.240 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_91.ts.tmp' for writing
21:06:05.392 elapsed=00:00:50.20 frame= 6605 fps=132 q=11.0 size=N/A time=00:04:35.44 bitrate=N/A throttle=off speed=5.49x    
21:06:05.485 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:05.495 SegmentComplete=video:0 Index=91 Start=273.314700 End=276.317700 Duration=3.003000 offset_pts=0 start_pts=273314700 Frames=72 filename=7ACF91_91.ts
21:06:05.495 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_92.ts.tmp' for writing
21:06:05.734 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:05.744 SegmentComplete=video:0 Index=92 Start=276.317700 End=279.320700 Duration=3.003000 offset_pts=0 start_pts=276317700 Frames=72 filename=7ACF91_92.ts
21:06:05.744 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_93.ts.tmp' for writing
21:06:05.890 elapsed=00:00:50.70 frame= 6745 fps=133 q=14.0 size=N/A time=00:04:41.28 bitrate=N/A throttle=off speed=5.55x    
21:06:06.008 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:06.016 SegmentComplete=video:0 Index=93 Start=279.320700 End=282.323700 Duration=3.003000 offset_pts=0 start_pts=279320700 Frames=72 filename=7ACF91_93.ts
21:06:06.016 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_94.ts.tmp' for writing
21:06:06.289 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:06.296 SegmentComplete=video:0 Index=94 Start=282.323700 End=285.326700 Duration=3.003000 offset_pts=0 start_pts=282323700 Frames=72 filename=7ACF91_94.ts
21:06:06.296 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_95.ts.tmp' for writing
21:06:06.391 elapsed=00:00:51.20 frame= 6874 fps=134 q=19.0 size=N/A time=00:04:46.68 bitrate=N/A throttle=off speed= 5.6x    
21:06:06.563 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91.m3u8.tmp' for writing
21:06:06.571 SegmentComplete=video:0 Index=95 Start=285.326700 End=288.329700 Duration=3.003000 offset_pts=0 start_pts=285326700 Frames=72 filename=7ACF91_95.ts
21:06:06.571 [segment @ 0000021821366800] Opening 'C:\Users\Media\Desktop\TEST\programdata\transcoding-temp\7ACF91\7ACF91_96.ts.tmp' for writing
>> ThrottleBySegmentRequest: RequestPosition: 00:02:33 - TranscodingPosition: 00:04:46 - ThrottleBuffer: 134s (Treshold: 120s)

Enter throttle value: <int, ms wait per input cycle> (0 to disable)

Setting throttle value to 100 ms
21:06:07.101 elapsed=00:00:51.80 frame= 6984 fps=135 q=20.0 size=N/A time=00:04:51.26 bitrate=N/A throttle=100 speed=5.62x    
21:06:07.654 elapsed=00:00:52.35 frame= 6985 fps=133 q=16.0 size=N/A time=00:04:51.31 bitrate=N/A throttle=100 speed=5.56x    

image.thumb.png.793e09a285ec0fce27121b42a9e6adba.png

Edited by Happy2Play
Link to comment
Share on other sites

Happy2Play

Devs will have to analyze that file but would assume there is something wrong with the encoding as I get no "RequestPosition".  Could be to small of a clip though.

image.thumb.png.26559306be9e3a59212a6c11500a9ee0.png

Reprocess clip and throttle was not able to kick in on such a short file.

Edited by Happy2Play
Link to comment
Share on other sites

Happy2Play

Playing one of my episodes it looks like Throttle kicked in after processing 12 minutes.

image.thumb.png.70568db96368694e3fd91f16f2772475.png

  • Thanks 1
Link to comment
Share on other sites

pwhodges

You need the Diagnostics plugin installed to have the User Sessions page of the dashboard.

Paul

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...