Throttling Not Happening

[derfy79 3]

5 hours ago, BlackDub said:

@Luke4.8.10.0 does not fix the problem

 

10:19:55.113 Too many packets buffered for output stream 1:1.

10:19:55.155 Conversion failed!

10:19:55.155 EXIT

+1 

same things here

[Neminem 1518]

Found this in another post, I think that 4.8.10.0 is an emergency patch.

And will not fix your problem

We can say the releas notes are lagging, what was fixed.

Release 4.8.10.0 · MediaBrowser/Emby.Releases (github.com)

• Fix hardware transcoding regression on some Linux platforms

Edited October 1, 2024 by Neminem
Adding

[BlackDub 50]

One month later.. no news..

[LAPS0082 13]

Yea unfortunately... Pretty annoying do this workaround after every reboot

[donniedarko83 6]

Yeah months later still no fix. No status updates nothing just silence 

[derfy79 3]

yeah it would be interesting to have an update or at least for them to tell us they are working on the problem

[BlackDub 50]

1 minute ago, derfy79 said:

yeah it would be interesting to have an update or at least for them to tell us they are working on the problem

the best solution is stay on 4.7, developers doesnt care users/clients

[guunter 49]

27 minutes ago, BlackDub said:

the best solution is stay on 4.7, developers doesnt care users/clients

If subtitles are an issue have you tried switching to burning in the subtitles and turning off subtitle extraction? You need to disable it in the transcode settings and then in the Subtitle options change it to burn in. This solved any issues i had with subtitles but it does make it so your cpu transcodes the subs but your gpu will do the video.

[LAPS0082 13]

Sure this could be another workaround I'm not happy with.

But obviously this is a bug (as it's working on 4.7) which should be fixed.

[BlackDub 50]

On 30/10/2024 at 15:16, guunter said:

If subtitles are an issue have you tried switching to burning in the subtitles and turning off subtitle extraction? You need to disable it in the transcode settings and then in the Subtitle options change it to burn in. This solved any issues i had with subtitles but it does make it so your cpu transcodes the subs but your gpu will do the video.

I tried the 3 options and same conversion failed !
2025 and no fixed

[BuzStringer 33]

Hi i've also started getting this issue, is there any update on an fix yet?  im using Docker is it possible to roll back to 4.7?

[BlackDub 50]

The problem also affects if you have an Intel graphics card (igpu 12700k)

ffmpeg-transcode-017838fe-3448-42e0-b991-56f000e6924a_1.txt

[BuzStringer 33]

Is there any update. ETA to fix please? these workarounds are not ideal and without them Emby is pretty much unusable.

Hardware Accelerated Transcoding is the main reason I am paying for Premiere, and it's not working... 

[BlackDub 50]

13 hours ago, BuzStringer said:

Is there any update. ETA to fix please? these workarounds are not ideal and without them Emby is pretty much unusable.

Hardware Accelerated Transcoding is the main reason I am paying for Premiere, and it's not working... 

""""""""""""""""""""""""""

  On 15/05/2024 at 21:04, ctaranto said:

For those who are having the same issue, here's what I did to fix this in my environment:

Install the Diagnostic Options plug-in

Scroll down to the Parameter Adjustment section

In Text to Replace:  -segment_write_temp 1

In Replacement Text: -segment_write_temp 1 -max_muxing_queue_size 100000

Save

"""""""""""""""""""""""""""""

After a week of testing, these settings "temporarily" fix the bug. The impact on RAM is not significant with multiple transcodes.

I choose values from 100,000 to 150,000

[kikinjo 281]

Blackdup, your workaround is working until emby server restart, after that you are again on square one.

Unbelievable that we are still waiting for this.....but hey for some basic stuff we are waiting for 5 years, this one should be done in about 25 years

[LAPS0082 13]

Will try your workaround thank you. @Emby Devs is there any update on this except: "We are working on this"?

[BuzStringer 33]

22 hours ago, LAPS0082 said:

Will try your workaround thank you. @Emby Devs is there any update on this except: "We are working on this"?

This is beyond a joke, This was first reported in March, 9 Months ago.  This is a Paid feature. 

What am i paying for? it's certainly not support or working features 

[BlackDub 50]

1 minute ago, BuzStringer said:

This is beyond a joke, This was first reported in March, 9 Months ago.  This is a Paid feature. 

What am i paying for? it's certainly not support or working features 

It is a problem that affects the MAIN feature of emby premiere, hardware transcode. Yes, this is a joke.

[BuzStringer 33]

34 minutes ago, BlackDub said:

It is a problem that affects the MAIN feature of emby premiere, hardware transcode. Yes, this is a joke.

Going to test Jellyfin over christmas, It now supports hardware encoding, Dolby Vision, Atmos, AND Dolby Vision to SDR Tone mapping, (which Emby still cant do) 

The Two main issues are apparently the Clients aren't as good, and remote access can be a trickier. 

But Jellyfin does has far more useful plugins. 

I am frustrated that Smart Playlists for Emby has taken 10 YEARS,  and it's still not ready, and this feature breaking bug has taken 9 Months, which should be fixed in days. I would be more lenient, even happy, if this was free software, but i am not getting any value from my subscription. 

If Jellyfin ticks all the boxes over the next month, i'm out, and glad i didn't pay for lifetime... Lifetime is how long you have to wait for something to be fixed.

[LAPS0082 13]

Maybe you could fix this as a christmas gift?

Sincerly

Your paying customers 

[donniedarko83 6]

Probably next year for Christmas

[BuzStringer 33]

Still no reply from the Emby team? wow.

[Luke 42077]

Hi, we are looking into this. Thanks.

[BuzStringer 33]

On 4/13/2024 at 10:07 PM, Luke said:

OK we'll take a look at it. Thanks.

 

On 5/6/2024 at 6:24 PM, Luke said:

Hi, we are looking into it. Thanks.

 

On 6/25/2024 at 12:03 AM, Luke said:

Hi, we’re looking into it. Thanks for reporting.

 

22 minutes ago, Luke said:

Hi, we are looking into this. Thanks.

Thanks, but you have been, looking into it, for 8 Months... you must have seen it by now. can we have a timeline please?

[BuzStringer 33]

Any update? Can we have an ETA On the fix please?