An unknown error occurred (4294967283) - Plex for Mac

Plex Players Desktop Players
, , ,
1

Server Version#: 1.40.0.7998
Player Version#: 1.88.1.96-c1c59fc1

So, I’m running LSIO container in unRAID. Using a 1660Ti for transcoding. Also transcoding to RAM with the following extra parameters: --mount type=tmpfs,destination=/tmp/plex_transcode,tmpfs-size=20000000000 --no-healthcheck

This works perfectly, transcoding uses the GPU and writes the chunks into /tmp/plex_transcode in the container which is mounted to tmpfs (ram).

Now the issue I’m seeing as I was stress testing the server, is that with the Plex on Mac I get this popup error a lot if I force a transcode quality:

An unknown error occurred (4294967283)

If I don’t do anything, don’t press Retry it eventually starts playing but direct playing. Then I force transcoding again and then it works. Or sometimes it shows up again and I have to do it again and then it works until the end of the entire movie.

None of my users have complained about anything, so I’m guessing this is desktop specific? Mac and/or Windows?

Any ideas? I have cleared the codec folder as well with the container turned off and turned on and same thing happened. Didn’t fix anything.

2

Bumping this.

Keeps happening on Plex for Mac.

Does NOT happen on my phone (android app) or xbox app. Can select any transcode quality and it’s just seamless. It’s only on Mac that it borks up.

3

Same error code occurred on my windows laptop, but it’s fine before this version.

1 Like
4

bump because it keeps happening.

5

@Sptz87 Please provide Server logs and client logs.

6

I’ll grab some logs tomorrow.

But in the meantime here’s a friend streaming @ 1080p 20Mbps. When she changes to 12Mbps then this happens:

Error msg doesn’t pop-up but same behaviour. It’s almost as if it’s disengaging transcoding. You can see it plays 1-2 seconds, probably the leftover transcoded chunks but disengages the gpu transcoding then quits.

1 Like
7

I just replicated the issue but on my local network. The issue of my friend above I’m not sure if it’s related to this but it might be as the behaviour is kinda similar. Except in this test case I just did after pressing retry it started working instead of closing the player.

compressed file is server logs, singular file is client log:

Plex Logs Mar 12.zip (4.5 MB)
Plex.log (995.1 KB)

1 Like
9

I asked my brother to try it on his windows laptop and same thing occurred.

telegram-cloud-photo-size-4-6030600959870224252-x

He was playing a 1080 remux file, it was direct playing remotely, I asked him to change to 1080p 12Mbps and the playback error ocurred.

Also, on a heavier 4K remux with Truehd 5.1 audio, it just simply closed the player back to the title page.

10

@Atomatth were you able to check the logs?

Btw this doesn’t seem to happen on the browser. It’s Mac / Win desktop apps only as it looks like. 3 different machines affected as I laid out.

11

@Atomatth

Was just testing this out again but on a chrome browser and got this:

CleanShot 2024-03-19 at 10.59.46@2x
CleanShot 2024-03-19 at 10.59.46@2x987×506 41.9 KB

Again, after pressing Retry it works. But for some users it just quits the video.

12

Can you DM me a sample of a video that is displaying this issue?

13

This happens on every single video

CleanShot 2024-03-19 at 13.40.46@2x
CleanShot 2024-03-19 at 13.40.46@2x875×572 7.09 KB

I can send you a sample, but it doesn’t matter if it’s a 4K 80Mbps remux or a 1080p 30Mbps file. This screenshot is from a 1080p 28Mbps. It doesn’t really matter what it is. As soon as I select to transcode this happens. One needs to press retry for it to work.

As I stated above, happens with 2 remote friends using the app on macos as well.

14

Another quick video showing it in action:

15

I posted what appears to me as the same or a related issue a while ago…got zero response. Have had this on my system since before Dec 2023.

1 Like
16

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