transcoding temp folder

[justinrh 260]

Settings shows this:

but the embyserver.txt log shows:

   2022-05-18 19:35:03.363 Info Main: Transcoding temporary files path: C:\Users\adminguy\AppData\Roaming\Emby-Server\programdata\transcoding-temp

Shouldn't these be the same?

[Luke 42082]

if the server is  being denied write access to that location, or it is unavailable, then it will revert back to default.

[justinrh 260]

Looks like Emby has access ...

[Happy2Play 9783]

Would need to see the server log.

[justinrh 260]

embyserver-63788515200.txtembyserver.txt

I show the pertinent part of the log in the first post, right?

Well, the log today shows the correct path.  The log from yesterday does not (and I restarted Emby a few times with the same result).  And I haven't touched anything.  We have a mystery.

[justinrh 260]

Well, it did it again.  Emby dashboard told me I needed to restart (plugin update?), so I did.  The log shows the wrong transcode folder again.  I forced a transcode - the log shows the correct folder being used during transcode.  Bug in initialization reporting in the log?

[Happy2Play 9783]

Please show a server log with at transcoding session and possibly a ffmpeg log.

[justinrh 260]

embyserver.txtffmpeg-transcode-f1dca6c3-c894-4d76-a97f-c558cebbf5d3_1.txt

Are you chasing a rabbit, Happy2Play?

[Happy2Play 9783]

@Lukeis there an issue showing custom path on start-up (Info Main)?  As a roll-over log shows that correct path (Info App).

Info Main vs Info App

Info Main: Transcoding temporary files path: C:\Users\adminperson\AppData\Roaming\Emby-Server\programdata\transcoding-temp

Info App: Transcoding temporary files path: Z:\Emby\transcoding-temp

But per the log it appears custom path is being use for the sessions shown in these logs.

[Luke 42082]

Yea I think it's just logging the default path.