Plex freezing a transcode no matter the client stating out of space

Plex Media Server
,
41

Sorry for delay.

Engineering has some files which recreate this.

We’ll probably see fixes after the holidays now.

Use PMS 1.29.2 if you need to.

1 Like
42

I can confirm that I have this same problem. If I play a 4K movie with Dolby TrueHD 7.1 and my server does a hw transcode, I get this error:

“Plex Error while decoding stream #0:1: No space left on device”

If I play a 4K movie with DTS-HD MA 7.1 that does a hw transcode (such as Harry Potter and the Prisoner of Azkaban), the movie plays just fine.

I am using Plex server v1.30.0.6486 on Ubuntu 18.04.6 LTS.
Note: I have a lot of free space in my Plex server, and I checked inotify, and it is not a problem.

43

@randmanplex

As stated – Switch back to 1.29.2 until Engineering releases a fix.

ALL who find this –

Further confirmations is not required.

All needed information, including recreation details with sample videos, have been given to Engineering.

1 Like
44

ChuckPa, speaking for myself, I appreciate all your help in resolving these kind of issues. I am sorry, if my post has become a frustrating situation for you. I, and I believe others, would just like to be kept appraised of the current status of this fix and what the root cause of this issue is.

As you suggested, I am running 1.29, but there have been new versions of PMS released and we just don’t know if the correction is in there or not without attempting the new version, then having to roll back again if it is not. If you could provide a release version it is expected in, or maybe some assurance that you will announce the patch here, that would be great.

45

@ranger671

To shed clarity on the TrueHD issue:

  1. All versions of PMS after 1.29.2 have TrueHD issues.

  2. No work to resolve the issue has been performed. I’ve been trying to collect samples from folks which reliably reproduce the problem .

  3. I have been assigned (loaned) to Engineering to perform the first level debugging of this for Engineering.
    – This involves running the smallest sample which recreates the error with 100% reliability under the debugger

  4. I am then to take my findings (Copy / paste text + append debugger files) and pass to the Engineer to walk through the code and resolve.

I will announce the fix when it’s release.

ALSO

PMS Release Announcements will mention a fix for TrueHD .
The internal number for it is: #14023

2 Likes
46

Hi Chuck, it seems like you folks got a good grasp of the issue, but I noticed something else related to this issue that I haven’t seen mentioned (happens on the same versions and the console errors are the same). I have a file with an mp3 audio track that exhibits the same issue, so it’s not exclusively TrueHD tracks. Reverting to the 1.29.2 version plays it as expected.

47

Donomans, can you share the encoding options and encoder name of the affected mp3? I listen to a lot of both music and audiobooks and have not run into that as of yet and would like a clearer understanding if you are willing.

48

@donomans

Can you send me or attach (if small enough) the audio file which recreates this?

49

Unfortunately, I’m not quite sure what the encoder name or options were - I didn’t encode it. It’s an old dvd rip from a decade ago of some garbage out of print movie - xvid in an avi container with a 128kbps stereo mp3 audio track.

50

I can send you the full file if you’d like (though not sure what the easiest way to do that would be?) - it’s ~700mb, so not enormous but I think bigger than what I can attach here

51

I want to jump in with some additional data points for you @ChuckPa.

Although 1.29.2 does appear to solve the issue for me as well, I believe there is an additional factor in play that I didn’t see in the thread.

  • Video #1: Abominable

    • 4K HEVC (H.265 10-bit)
    • Container: MKV
    • Dolby TrueHD (Atmos)
    • Raw rip from MakeMKV of the 4K Blu-Ray (BD-100)

  • Video #2: Abominable

    • 1080p AVC (H.264 8-bit) L5.1
    • Container: MKV
    • Dolby TrueHD (Atmos)
    • Raw rip from MakeMKV of the Blu-Ray (BD-50) transcoded with Handbrake

  • Video #3: Top Gun Maverick

    • 4K HEVC
    • Container: MKV
    • Dolby TrueHD (Atmos)
    • Raw rip from MakeMKV of the 4K Blu-Ray

The table below represents which server version and file exhibit the errors:

Video #1 Video #2 Video #3
PMS v1.29.2
PMS v1.30.1 :heavy_check_mark: :heavy_check_mark:

I tested the above on the following clients:

  • Plex Web
    • Brave Browser (Chromium-Based)
    • Not capable of Direct Play
    • Attempted Automatically Convert, 1080p High, and Convert Maximum
  • Xbox Series X
    • Attempted Direct Play and Transcode 1080p
  • Apple TV HD
    • Not capable of Direct Play (no HEVC 10-bit decode support)
    • Attempted Automatically Convert, 1080p High, and Convert Maximum
  • Apple TV 4K
    • Attempted Direct Play and Transcode 1080p

Though I didn’t verify on each of the above tests, for the tests that I did, the logs all showed the errors that were already identified in this thread.

The interesting thing is that all 3 samples have a TrueHD audio track with Dolby Atmos metadata. The distinguishing feature appears to be the encoding of the video stream rather than solely the audio stream. In other words, it is possible there are multiple bugs present or or this bug is more complex than initial triage indicated.

Let me know if any other info may be helpful and thanks for all the work in diagnosing/fixing the issue.

52

TO ALL HERE:

I have a candidate fix for the TrueHD audio problem being experienced in PMS 1.30.x

If anyone is interested in helping confirm the problem is resolved, I have the experimental packages

@Kevin.Boyd

Your testing appears to support the findings on this side.
The error isn’t as much the codec as the upstream processing for any Dolby EAE.

This upstream issue has been fixed

2 Likes
53

Chuck, I’d be happy to test it. Please let me know if you would like me to do so. Should be able to d/l and test this evening.

54

@ranger671

Which package format do you need ? amd64.deb ?

PROCESS -

  1. STOP PMS

  2. Make a backup of your Databases directory (This is experimental PMS)
    –No QA testing performed

  3. Install

  4. Play TrueHD content

  5. Observe

  6. Report (include logs if needed)

  7. Shutdown

  8. Restore Databases

  9. Install previous PMS 1.29.2 version

Link sent via PM

55

Yes, an amd64.deb would be perfect.

56

Initial testing with Blue Thunder shows plex playing right through the bad spot. Watched an additional 10 minutes with no issues and will continue to test more tonight.

2 Likes
57

Further testing - played ‘30 Days of Nights’ and ‘Lion King’, both with Truehd and exhibited the issue with no problems. A little information for anyone else who might move in this direction, the database migration took 12 min. and at one point I was afraid I was encountering a lock up right after the upgrade. Patience is a virtue in this case.

59

fwiw, i am experiencing this issue on my x64 version of Version 1.30.1.6497 on a windows server.

60

Folks,
We’ve been testing the fix to this and all looks good.

For those of you who need Dolby now , I recommend (non-destructive) downgrading to 1.29.2 which predates the issue.

I suspect, but have no confirmation at this time, Engineering will include this in the next PMS release :crossed_fingers:

3 Likes
61

Looks like the fix did make it into the most recent release. Thanks @ChuckPa and the engineering team for running this to ground.

1 Like