EAC3 transcoding issue

Plex Media Server Desktops & Laptops
1

Server Version#:1.16.2.1297
Player Version#: 3.108.2

Hello,

I’M unable to transcode any video with EAC3 sound.
Each time, the video player starts, but no video is display. I only see the waiting sign.

While the problem occurs, I can see in the logs errors like:

Jul 22, 2019 22:53:51.001 [0x7fef84ff9700] ERROR - [Transcoder] [eac3_eae @ 0xc2ab80] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-88a9b466-ee4f-40e0-a2fe-0237a48fda02/EasyAudioEncoder/Convert to WAV (to 8ch or less)/21zqxfwxmdm3n2wcu61dksej_16986-0-4.wav'
Jul 22, 2019 22:53:51.002 [0x7fef627fc700] ERROR - [Transcoder] [eac3_eae @ 0xc2ab80] error reading output
Jul 22, 2019 22:53:51.002 [0x7fef627fc700] ERROR - [Transcoder] Error while decoding stream #0:1: Input/output error

If I check the “/tmp/pms-88a9b466-ee4f-40e0-a2fe-0237a48fda02/EasyAudioEncoder/Convert to WAV (to 8ch or less)/” directory I can see ec3 files, but no WAV.

-rw-r--r-- 1 plex plex 20480 Jul 22 22:55 21zqxfwxmdm3n2wcu61dksej_16986-0-31.ec3
-rw-r--r-- 1 plex plex 20480 Jul 22 22:55 21zqxfwxmdm3n2wcu61dksej_16986-0-32.ec3

I seeking for a solution since a while. I tried different methods found on this forum, but without luck.

Can you help me please ?

2

Is that temp directory on a network share or anything else non-local which doesn’t support file locking?

3

Thanks for your reply.
No, it’s on the main NVMe driver on which the system is installed.
I run it on Ubuntu 18.04 (headless) natively, but I have the same issue on 2 different docker containers. Each time, I use a copy of the same library.
I wondering if something can be wrong in my settings.

4

Are these in docker or SNAP or the native app?

5

Both (docker and native) act the same.
But I want to solve it for my native install since I just got a Quatro P4000.

1 Like
6

Are they, by chance, both mapped to the same system /tmp directory and colliding?

7

I just double checked and no colliding.

I did:

  • Stop PMS
  • Clean files/dir in /tmp
  • Start PMS
  • Play EAC3
8

I am not a docker guy by any stretch but I suspect it is a container configuration issue.

without the docker servers running, does it run natively ?

9

Sorry, it’s not cristal clear.
I have this issue since a while.
I’m used to run PMS on docker, but recently I got a P4000.
So, I migrated on a native installation and face exactly the same issue.
I no longer want to use docker.
Seeing the same issue on the native installation, I suspect that the problem either comes from my settings (copied from docker to native) or my system.

10

Thanks.

Let’s first do some easy things?

Which PMS version?
Have you ever cleared out the codecs and had it start over (fresh download) ?

11

PMS v1.16.2.1297
Yes, I stopped PMS, deleted “Codecs” directory and restart PMS several time

12

Which version, to best of your knowledge, is the last which worked ?

If you have that one, uninstall 1297 and reinstall it.

13

Thanks for your reply.
I don’t know exactly when it stopped working.
I tried to downgrade to 1.15.8.1198, but it didn’t helped.

My Library folder is pretty old. Copied from an install to another. So I tried to create new settings, and it worked.
Now I’m looking how to get back my database without copying settings.

14

End of the story.
Maybe somebody is in the same situation, so here are the steps to solve the issue.

The problem came from my Preferences.xml file. My oldest previous version is 1.12.0.4829-6de959918.
I basically stripped out the file to keep only server identity.

My file now looks like:

<?xml version="1.0" encoding="utf-8"?>
<Preferences OldestPreviousVersion="1.12.0.4829-6de959918" MachineIdentifier="blabla" ProcessedMachineIdentifier="blabla" AnonymousMachineIdentifier="blablabla" MetricsEpoch="1" AcceptedEULA="1" FriendlyName="BlaBla" PublishServerOnPlexOnlineKey="1" LastAutomaticMappedPort="0" PlexOnlineToken="bla" PlexOnlineUsername="bla@gmail.net" PlexOnlineMail="bla@gmail.net" PubSubServerPing="46" CertificateVersion="2" CertificateUUID="blabla"/>
15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.