hmm you may be right, plex does use those guid for transcoder/scanner playlists, but this doesn’t seem to be one.
:/tmp# file e467a151-e8e6-48d7-bde9-42cf4e50c07c
e467a151-e8e6-48d7-bde9-42cf4e50c07c: RIFF (little-endian) data, WAVE audio, 6 channels 48000 Hz
This is simply a bug, Transcoder does not honour TranscoderTempDirectory="pathname" and falls back on TMPDIR. Probably not fixable via a new .service file. (i would assume)
I’m sorry, this is not a ‘throw everything in one thread’ pile.
Please create a fresh thread with DEBUG logs ZIP which capture this
This is the topic the Thread was originally about, no need to create a new one.
The thread references by @TeknoJunky basically dances around this bug as well.
When using the transcoder to scan for intros it does not honour TranscoderTempDirectory= but uses TMPDIR
Setting TMPDIR to someting else is only a workaround, not a fix.
Outdated /etc/default and .service variables are a different issue.
I imagine it is coming down to semantics.
the transcoder temp location is for large tmp files for streaming
the tmp folder (where ever, how ever it is determined), is for everything else.
intro scanning is not streaming.
ergo it goes to tmp
link both to /dev/shm and then you don’t have to worry any more
It’s called TranscoderTempDirectory not StreamingTempDirectory.
shrug, so what if it is called skfhjndifuh932hn vs ufodjslfkdjnfd
I get it, you don’t want your ssd burned up with writes.
/dev/shm and done.
But it is not called skfhjndifuh932hn. It is called TranscoderTempDirectory. Words have meaning. People expect certain behaviour based on that meaning.
The GUI descriptions also says “Transcoder temporary directory” “Directory to use when transcoding for temporary files.” Not when streaming, not for large files.
How is setting TMPDIR=/dev/shm a solution when the bug is that the transcoder is not honouring TranscoderTempDirectory.
words shmurds.
expect nothing, and you will never be disappointed.
I guess your idea of transcoding is different than what plex dev’s determine as transcoding.
/dev/shm is a built in pseudo ram disk, that is half your system ram. google if you don’t know what it is and does.
the 2 temp locations variables will be fixed in an upcoming version, as already been stated.
anyway, you can either work around it, or keep letting it frustrate you, either way good luck.
I know you are just trying to help but this is not going nowhere. The variable issue is ANOTHER issue and has nothing to do with the root cause. Fixing the service file will not fix this bug. Please understand first how this are 2 separate issues before commenting any further.
Working around it or being frustrated are not the only 2 options. Reporting the bug is the third and correct option, so it can get fixed and not everyone has to work around it, which you are trying to make harder for some weird reason.
I worked around the issue before I made this Thread, the bug itself is less frustrating then replying to a “words shmurdsm” argument of a guy not fully understanding the problem yet insisting on his “solution”.
While I do appreciate you trying to help, I do not need you to explain /dev/shm to me.
What I need is @ChuckPa telling the dev team that the Transcode process is not honouring TranscoderTempDirectory setting when transcoding the audio to .wav while searching for the intro music.
Engineering deliberately put it in TMPDIR due to licensing requirements .
It must be on a filesystem which allows exec privilege.
The TranscoderTempDir is, by definition`, non-executable data.
EDIT: It must also support the Linux kernel’s inotify service.
1 Like
I don’t understand. TranscoderTempDir is per default /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/Transcode which is per default not mounted with noexec, since its part of the / tree, same as /tmp.
How do you execute a .wav file?
I am terribly sorry for saying this but,
This has gone far enough.
I am not going to debate or justify design considerations which are grossly out of scope of this thread.
Please accept what it is or not. The choice is yours.
Which definition?
The data put in /tmp is a wave audio, which is not executable
TranscoderTempDir default setting allows that.
What you said simply makes no sense.
That is a clear cut bug, as clear as it gets which circumvents administrators settings and can actually damage people’s hardware and you shrug it off with “accept it or not” Are you serious @ChuckPa
Btw
FULL STOP.
I am NOT going to disclose PMS internals as I cannot continue without doing so.
Regrettably, this thread is now closed.
