RESOLVED: EAE Timeout Error & Permenant Buffering w/ EAC3 Audio Transcoding

Plex Media Server Desktops & Laptops
1

Hi Guys & Gals,

I am currently running into a problem where any media that uses EAC3 causes a permenant buffer and fails to play.
I know there are already many threads going back several years related to this problem, but I am unable to resolve the problem using multiple suggestions in previous threads.

Error Example:
Dec 08, 2019 22:09:23.001 [0x7f3c59ffb700] Error — [Transcoder] [eac3_eae @ 0x190bf40] EAE timeout! EAE not running, or wrong folder? Could not read ‘/tmp/pms-3d96690b-8fc0-4bd4-ae24-72d7c36fb807/EasyAudioEncoder/Convert to WAV (to 8ch or less)/00ur6ce7v8ui7peqjpf91fhk_1677-0-25.wav’
Dec 08, 2019 22:09:23.002 [0x7f3c0affd700] Error — [Transcoder] [eac3_eae @ 0x1c53f40] error reading output
Dec 08, 2019 22:09:23.003 [0x7f3c417fa700] Error — [Transcoder] Error while decoding stream #0:1: Input/output error

OS: Ubuntu 16.04.6 LTS
PMS: Version 1.18.2.2029 - Base (Not running on the PMS Docker Image?)

Attempted fixes include:
Rebooting Server
Updating OS,
Updating Plex Server,
Delete Codec folder under /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs,
Creating a new directory and pointing the transcoder to the new location, (REVERTED TO DEFAULT)
Running chmod 777 EasyAudioEncoder under /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-334-linux-x86_64/EasyAudioEncoder,

Is anyone able to tell me where Im going wrong here?
Its worth noting that this used to work, and no changes were made manually by myself between the last known good config and since errors have appeared.
Im guessing an Ubuntu update of some sort may have thrown a spanner into the works here given I run auto-updates and this would have been the only changes that took place.

Any advice would be greatly appreciated, let me know if you need any more details.

Thanks.

2

The errors you show are commonly seen when Linux runs out of iNotify watches.
iNotify is used when PMS is set to “Scan my files when changes are detected.”

The rest of your DEBUG logs, capturing the first two minutes after startup while it loads the iNotify tables, will tell if this is happening.

It happens because EAE and the transcoder need 1 slot for each transcode.
If the number monitored directories exceeds 8192 (including transcodes), the table fills.

You can use this procedure to count how many directories PMS is actually monitoring

3

Morning Chuck,

Thanks for the additional info, Ill make the relevant changes when I get back from work tonight.

If this doesn’t resolve the issue, Ill go ahead and attach the logs for you to take a closer look.

Thanks :slight_smile:

4

I lied, looked like a quick fix and did it just now.

It works!

Legend, Thankyou.

5

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