# EasyAudioEncoder Issues

**URL:** <https://forums.plex.tv/t/easyaudioencoder-issues/778857>\
**Category:** Plex Media Server\
**Tags:** server-linux, server-docker\
**Created:** [March 1, 2022, 2:34pm UTC](https://forums.plex.tv/t/easyaudioencoder-issues/778857 "2022-03-01T14:34:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tstraus13](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@tstraus13](https://forums.plex.tv/u/tstraus13)\
**Post date:** [March 1, 2022, 2:34pm UTC](https://forums.plex.tv/t/easyaudioencoder-issues/778857/1 "2022-03-01T14:34:28Z")

</div>

Server Version#: 1.25.6.5577  
Player Version#: 7.29 (iOS)

When I go to play a 4K rip on my iOS or any device that needs to do transcoding of the audio. I get constant errors about EasyAudioEncoder Timeouts because it is unable to find the .wav files it is expecting. Looking at the directory where EAE is transcoding to, I find files with a .mlp extension. If I change the extension from mlp to wav on one of those files it plays fine in VLC. It seems as though Plex might be looking for the wrong file or EAE is not naming the file properly? I will attach screenshots of the error and the files it is generating.

 ![Screenshot 2022-03-01 093230](https://global.discourse-cdn.com/plex/original/4X/c/5/f/c5f2b74345efd09805fe26f1287ec966e1b8d6f0.jpeg)  
 ![Screenshot 2022-03-01 093258](https://global.discourse-cdn.com/plex/original/4X/3/5/8/358df1a33c0130ae91da8ebfffc454f53cbe1c97.png)

---

<div class="post-metadata">

**Author:** ![tstraus13](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@tstraus13](https://forums.plex.tv/u/tstraus13)\
**Post date:** [March 1, 2022, 3:33pm UTC](https://forums.plex.tv/t/easyaudioencoder-issues/778857/2 "2022-03-01T15:33:27Z")

</div>

Well it turned out to be the common inotify issue for the linux system. I didnt think that was the issue since it seemed to be working and creating the transcoding files but I was wrong. For those running into this issue it is likely the inotify issue that is the solution to similar posts. You basically just need to increase the limit. I will provide a link to the process of doing it on Ubuntu. Thanks.

> <https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached>

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [March 1, 2022, 3:45pm UTC](https://forums.plex.tv/t/easyaudioencoder-issues/778857/3 "2022-03-01T15:45:13Z")

</div>

If I may add ?

> [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/9):
>
> Increase the number of directories Linux can monitor (inotify) for PMS The default size of the Linux inotify table is 8192 directories (\*1). When PMS is configured to update automatically when media is added, with properly organized media, especially music, this table rapidly fills and exceeds the default allocation requiring you to increase it. The solution to this is straight forward. Increasing the table size is easy. The first step is to determine how many directories to alloca…

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [May 30, 2022, 3:45pm UTC](https://forums.plex.tv/t/easyaudioencoder-issues/778857/4 "2022-05-30T15:45:21Z")

</div>

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