Jump to content

transcode Cannot allocate memory


ClearSeve

Recommended Posts

ClearSeve

It feels like the requested memory exceeds the device itself. How to solve this problem
thank you

07:05:15.190 [hevc @ 0x2df4000] Error parsing NAL unit #0.
07:05:15.190 [hevc @ 0x26fddc0] get_buffer() failed
07:05:15.190 [hevc @ 0x26fddc0] thread_get_buffer() failed
07:05:15.190 [hevc @ 0x26fddc0] Error parsing NAL unit #0.
07:05:15.191 Error while decoding stream #0:0: Cannot allocate memory
07:05:15.191 [hevc @ 0x2d30540] get_buffer() failed
07:05:15.191 [hevc @ 0x2d30540] thread_get_buffer() failed
07:05:15.191 [hevc @ 0x2d30540] Error parsing NAL unit #0.
07:05:15.191 Error while decoding stream #0:0: Cannot allocate memory
07:05:15.191 [hevc @ 0x2df4000] get_buffer() failed
07:05:15.191 [hevc @ 0x2df4000] thread_get_buffer() failed
07:05:15.191 [hevc @ 0x2df4000] Error parsing NAL unit #0.
07:05:15.191 [hevc @ 0x26fddc0] get_buffer() failed
07:05:15.191 [hevc @ 0x26fddc0] thread_get_buffer() failed
07:05:15.191 [hevc @ 0x26fddc0] Error parsing NAL unit #0.
07:05:15.192 Error while decoding stream #0:0: Cannot allocate memory
07:05:15.333 [hevc @ 0x2d30540] get_buffer() failed
07:05:15.333 [hevc @ 0x2d30540] thread_get_buffer() failed
07:05:15.333 [hevc @ 0x2d30540] Error parsing NAL unit #0.
07:05:15.333 Error while decoding stream #0:0: Cannot allocate memory

 

ffmpeg-transcode-361ab838-3e85-4bbe-b34b-4964e55d3d3e_1.txt

Link to comment
Share on other sites

ClearSeve

Sorry, I may have sent this post to the wrong section

Edited by ClearSeve
Link to comment
Share on other sites

@ClearSeve - I assume the log is from a conversion, right?

Can you please try without subtitle burn-in? You can use the Diagnostics Plugin to disable.

Thanks,
sw

 

Link to comment
Share on other sites

ClearSeve
4 hours ago, softworkz said:

@ClearSeve - I assume the log is from a conversion, right?

Can you please try without subtitle burn-in? You can use the Diagnostics Plugin to disable.

Thanks,
sw

 

image.thumb.png.97604440b0acf5148ac7f5d10fa75b3c.png

 

Disable this option?

Disabling this option is also an error message

I found that if hardware acceleration is not enabled, the conversion can be successful

ffmpeg-transcode-99863944-ff27-46f1-b9a2-b29abec48908_1.txt

Link to comment
Share on other sites

Oh, the option is not longer there. It was named "Disable Subtitle Burn-In". It was moved to another place and then plans had changed.

Link to comment
Share on other sites

ClearSeve
4 hours ago, softworkz said:

Oh, the option is not longer there. It was named "Disable Subtitle Burn-In". It was moved to another place and then plans had changed.

Can't I try this method?

Link to comment
Share on other sites

12 hours ago, ClearSeve said:

Can't I try this method?

Yes, try playing the video in the chrome browser, make sure the subtitles are disabled, and then use the quality setting to force a full video transcode. See how that compares.

You'll probably want to restore the quality setting to what it was before when you're done.

Link to comment
Share on other sites

2 hours ago, nick0323 said:

I have got the same issue, which run in my docker container(linuxserver/emby), and another docker container seems good.

ffmpeg-transcode-fb3b47a0-fe4a-44cd-ba24-d707c2bd50f1_1.txt 45.92 kB · 1 download

Hi @nick0323 can you try our official docker container and let us know how that compares?

https://emby.media/docker-server.html

Thanks !

Link to comment
Share on other sites

On 6/28/2022 at 7:35 AM, ClearSeve said:

Can't I try this method?

I'm afraid, there's nothing we can do in the context of the current release. 
But we can  work on that during the next beta period.

I'm sorry, that I don't have any better options right now.

The only things that might work are:

  • Do not use subtitle overlay
  • Disable VAAPI hw decoding - this will keep everything before encoding in software which will take less memory, but maybe it would still be too slow for subtitle burn-in.
Link to comment
Share on other sites

nick0323
On 7/7/2022 at 12:42 AM, Luke said:

Hi @nick0323 can you try our official docker container and let us know how that compares?

https://emby.media/docker-server.html

Thanks !

I'm tried the debian version in the host instead of docker container, the issue is steal exist, when i select the specific subtitle(PSGSUB). It worked fine when I didn't select any subtitles.  Then when I selected the previous subtitles, it worked fine as well. It always works fine in emby v4.6.7.

This only happens in specfic Meida files with PSG Subtitles, but not all media files.

Should I increase the iGPU memory in the BIOS setup or it just the ffmpeg issue?

Link to comment
Share on other sites

23 hours ago, nick0323 said:

I'm tried the debian version in the host instead of docker container, the issue is steal exist, when i select the specific subtitle(PSGSUB). It worked fine when I didn't select any subtitles.  Then when I selected the previous subtitles, it worked fine as well. It always works fine in emby v4.6.7.

This only happens in specfic Meida files with PSG Subtitles, but not all media files.

Should I increase the iGPU memory in the BIOS setup or it just the ffmpeg issue?

Can you please attach the ffmpeg log from the debian version? Thanks.

Link to comment
Share on other sites

  • 3 weeks later...
MSOBadger

I appear to be having the same issue.  I recently moved my install from an Unraid docker container (which had been running rock-solid) to a Linux (ubuntu server) VM install on a Proxmox node.  I moved over to this new build in order to get QuickSync transcoding.

Since migrating over, I've had remote users reporting getting repeated "no compatible streams" error.  I had not experienced the issue myself until now (most of my local devices are direct-play).  I just now experienced the same error myself while accessing my server remotely (via chrome).  Looking into the logs, I'm seeing this same "transcode cannot allocate memory" error.

Server log and FFMPG transcode log files attached.  Any thoughts?

embyserver (2).txt ffmpeg-transcode-61284984-c78d-441b-8e75-9879d849643b_1.txt

Edited by MSOBadger
Link to comment
Share on other sites

  • 2 weeks later...
On 7/29/2022 at 12:41 PM, MSOBadger said:

I appear to be having the same issue.  I recently moved my install from an Unraid docker container (which had been running rock-solid) to a Linux (ubuntu server) VM install on a Proxmox node.  I moved over to this new build in order to get QuickSync transcoding.

Since migrating over, I've had remote users reporting getting repeated "no compatible streams" error.  I had not experienced the issue myself until now (most of my local devices are direct-play).  I just now experienced the same error myself while accessing my server remotely (via chrome).  Looking into the logs, I'm seeing this same "transcode cannot allocate memory" error.

Server log and FFMPG transcode log files attached.  Any thoughts?

embyserver (2).txt 562.63 kB · 4 downloads ffmpeg-transcode-61284984-c78d-441b-8e75-9879d849643b_1.txt 45.85 kB · 6 downloads

Hi, @softworkz is looking into this. Thanks.

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...
MSOBadger
On 8/24/2022 at 9:27 PM, softworkz said:

@ClearSeve @MSOBadger - this should be fixed now - would you be able to try with the latest beta 4.8.0.8+ ?

Thanks,
softworkz

Sorry for the delayed reply - between work and a couple trips I'm just getting to install and test out beta 4.8.0.8 now.    I installed the beta this morning and will put it through the paces on this end and report back.  Thanks @softworkz!

  • Thanks 1
Link to comment
Share on other sites

  • 1 year later...
On 12/19/2023 at 6:53 AM, 6387363TOY said:

I've provided my logs which may be helpful

Hi, are you able to try the 4.8 beta server and see how that compares?

Link to comment
Share on other sites

6387363TOY
On 12/21/2023 at 5:04 AM, Luke said:

Hi, are you able to try the 4.8 beta server and see how that compares?

I'm running version 4.8.0.64, and I don't have any problems hardening PGSSUB with this version!

Sorry I was so busy a while ago, I just saw your reply, thanks!

  • Like 1
  • Thanks 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...