how are you? just to be clear - I paid money for your soft that doesn’t work!
How long I have to post at this forum without ANY help?
PMS is NOT free software and I have the problems. where can I get support? or you may be prefer moneyback?
every f*_ng time I try to use PMS I’m fa*_ing at logs!!
is this your position and relationship with customers?
this time I tried to watch Perfectos Desconocidos (2017) and have fun.
guess what I’m doing? I’me reading stupid logs and posting to this forum.
Not what you want to hear, but I suspect this may be an encoding issue like MovieFan referenced above. Can we take one of the files thats not playing, and run it thru handbrake for a reencode and see if it performs differently?
Ive been using Plex for years and have very very few actual issues.
I admit that you and MovieFan are right, but how to explain that the one movie is bad encoded for the one TV and good encoded for two other TV’s (one of them is Samsung too)? I referenced this above.
Also I suppose that software have to have some system requirments like “only nvidia h.264 codec is suietable for our product to display a movie” or “only RTX4090 is suietable for our product to be able to encode a movie” - but I don’t see those info.
Also I suppose that software may inform user about critical exceptions like “I can’t encode this Movie because I don’t like an encoder used to make it” - but I don’t see those info too.
I want too much?
I can do whatever you or somebody else ask me to do to fix this problem, but I will not reencode a thousands of Movies and Series and nobody can convince me that is really not PMS problem.
I have been using Plex for years too but last two years I read logs and this forum more than watch a movie.
Lets try re-encoding a problematic file, say mkv h264 1080p30 settings in handbrake.
If you have an encoding issue, you have an encoding issue. But we havent been able to prove that yet. (See request above)
Not sure this is relevant but I did see this in your logs:
Feb 02, 2025 19:52:23.850 [79504] DEBUG - [Req#9efc/GPU] Got device: Intel(R) Iris(R) Plus Graphics 655, intel@unknown, default true, best true, ID 8086:3ea5:8086:2074, DevID [8086:3ea5:8086:2074], flags 0x38f6
Feb 02, 2025 19:52:23.850 [79504] DEBUG - [Req#9efc/GPU] Got device: Intel(R) Iris(R) Plus Graphics 655, intel@unknown, default false, best false, ID 8086:3ea5:8086:2074#2, DevID [8086:3ea5:8086:2074], flags 0x38f6
Feb 02, 2025 19:52:23.851 [79504] DEBUG - [Req#9efc/GPU] Cuda library was not found on the system
Please keep both files in your library. When you start having buffering issues, try playing both. We need to see either 1 stuttering, or both. Having neither does not give any concrete information. Without being able to establish that the original file is stuttering I am unable to prove any correlation between the two. IE, if we fix a roof that leaks when it rains, do we really know its fixed unless we have more rain?
I will have Duplicates. will try to figure out how to select a duplicate file to play.
but the other and most important question is about what to watch: should I watch only this movie day by day to get shuttering? If so I would prefer to do this test with “Groundhog Day”.
that not quite correct paradigm - we have a roof that leaks time to time and not every rain.
this appears to be a permissions issue: Transcoder: Failed to delete session directory (boost::filesystem::remove_all: Access is denied [system:5]: "C:\Plex_transcode_temp\Transcode\Sessions\plex-transcode-af1dd055bdb3b31f-com-plexapp-android-1d4bacfa-6cac-4bcb-af2c-2c00222cf967\media-00030.ts")
And “delete” is very special NTFS permission - you need to uncheck it if you want to forbid delete operation.
In the overwhelming majority of cases (default) “delete” is granted with “modify” permission.
anyway here is very simple and clear inherited NTFS permissions
the thread you referenced gave a code The request is not supported [system:50] which is weird and likely a compatibility issue with boost. Yours very specifically says Access is denied [system:5] which is a permissions issue.
While i try to track this down please kerp working with @dbirch. It may be helpful to restart pms, trigger a transcode on the samsung tv without issues then trigger a transcode on the tv with issues. (The restart is so that those are the only 2 playbacks in the log)
Actually, given that the issue occurs on direct play this is not necessarily a PMS issue as PMS does not touch the data in this case, it appears to be an issue with the TV in question. I suspect we will need the client logs