Thank you for the settings update suggestion. I’m interested in testing it.
Regarding editing the settings.toml,
I tried following the suggestions here
- Power up PS with env PS_START_PAUSED=true (this was passed using an unraid container variable)
- Complete initial PS welcome steps (authenticate, tell it not to automatically organize, etc)
- Once it loads the ‘paused status’, stop the container with Unraid
- Edit config/settings.yaml
- Start the PS container with unraid
- Launch the WebUI but find that it starts back over with the ‘welcome’ settings screen. If I re-complete these steps, it replaces the settings.toml file, which removes my prior edits.
Here’s a snip of what I changed. Just removing the comment characters+whitespace and altering the lines you have in the post above:
# CAUTION: this is an advanced setting. Editing this may cause videos that
# require transcoding to not be imported, or not be viewable on all browsers
# and platforms. See
# <https://forum.photostructure.com/t/poor-transcoding-of-videos-in-wider-color-spaces-rec-2020/646>
# for more details.
#
environment: "PS_FFMPEG_TRANSCODE_ARGS"
ffmpegTranscodeArgs = [
"-c:a",
"aac",
"-c:v",
"libx264",
"-pix_fmt",
"yuv420p",
"-vf",
"colorspace=all=bt709:iall=bt601-6-625:fast=1",
"-movflags",
"faststart",
"-profile:v",
"high"
]
I suspect I’m introducing syntax error(s) causing PS to replace the file? I don’t think I’m introducing linux/windows whitespace problems…at least I’m making an effort to avoid that.
Any obvious newb mistakes you notice in my settings.toml changes?
Happy to rtfm regarding settings.toml…can you suggest a post/doc different from the steps above?
Thanks!