u/4x-gkg

I fly gliders in Australia and got an Insta360 X4 on a suction cup.

Even now in winter, when it's less than 20° on the ground, the camera keeps turning off after running for a while and says something like "anomaly detected"when I turn it back on again (and then continues to record for a while when I press the record button).

The battery is full and I have an external power bank connected via USB.

It already has the cooling bracket on it but it doesn't make much of a difference.

I do not connect to it with the phone while it's recording, so it's not busy with WiFi or Bluetooth.

Searching the web and asking AI, the next step might be to take out the internal battery and rely on the external power bank. I plan to try it next time I go to a gliding camp in a few weeks.

Does anyone have more tips about how to deal with it?

In continuation of the same journey I asked about before, my current flow with TDarr is:

input file -> ffmpeg begin -> ffmpeg custom arguments -> ffmpeg exec -> "move to original directory"

I'm executing this on a test library with one sample problem file.

The flow is meant to remove all the non-SRT subtitles and keep one AC3 audio stream.

The "Output Arguments" field I set is:

-map -0:a -map -0:s -map 0:v:0 -map 0:a:0 -map 0:s? -c:v copy -c:a ac3 -c:s copy -map -0:s:m:codec_name:hdmv_pgs_subtitle?

("Input Arguments" was left empty)

The ffmpeg command tdarr actually builds looks like:

tdarr-ffmpeg -y -i /media/test/test08.mkv -map 0:0 -c:0 copy -map 0:1 -c:1 copy -map 0:2 -c:2 copy -map 0:3 -c:3 copy -map 0:4 -c:4 copy -map 0:5 -c:5 copy -map 0:6 -c:6 copy -map 0:7 -c:7 copy -map 0:8 -c:8 copy -map 0:9 -c:9 copy -map 0:10 -c:10 copy -map 0:11 -c:11 copy -map 0:12 -c:12 copy -map 0:13 -c:13 copy -map 0:14 -c:14 copy -map 0:15 -c:15 copy -map 0:16 -c:16 copy -map 0:17 -c:17 copy -map 0:18 -c:18 copy -map 0:19 -c:19 copy -map 0:20 -c:20 copy -map 0:21 -c:21 copy -map 0:22 -c:22 copy -map 0:23 -c:23 copy -map 0:24 -c:24 copy -map 0:25 -c:25 copy -map 0:26 -c:26 copy -map 0:27 -c:27 copy -map 0:28 -c:28 copy -map 0:29 -c:29 copy -map 0:30 -c:30 copy -map 0:31 -c:31 copy -map 0:32 -c:32 copy -map 0:33 -c:33 copy -map -0:a -map -0:s -map 0:v:0 -map 0:a:0 -map 0:s? -c:v copy -c:a ac3 -c:s copy -map -0:s:m:codec_name:hdmv_pgs_subtitle? /temp/tdarr-workDir2-A1BPxGVHa/1782011621889/test08.mkv

I'm using Google Gemini a lot to work on this, and it explains that the "-map -0:a -map -0:s" will negate these extra streams that tdarr adds automatically, but is there a cleaner way to tell tdarr not to add them in the first place?

This is with TDarr release 2.78.01

Thanks.

I'm trying to setup a flow to simplify my files.

I now get errors when it tries to run exiftool but it's not installed in the container:

[2026-06-20T18:45:12.283] [INFO] Tdarr_Node - verbose:Running exiftool on file CLI error code: 234 [2026-06-20T18:45:12.317] [ERROR] Tdarr_Node - Error: FFmpeg failed at /app/Tdarr_Node/assets/app/plugins/FlowPlugins/CommunityFlowPlugins/ffmpegCommand/ffmpegCommandExecute/1.0.0/index.js:211:27 at step (/app/Tdarr_Node/assets/app/plugins/FlowPlugins/CommunityFlowPlugins/ffmpegCommand/ffmpegCommandExecute/1.0.0/index.js:33:23) at` [`Object.next`](http://Object.next) `(/app/Tdarr_Node/assets/app/plugins/FlowPlugins/CommunityFlowPlugins/ffmpegCommand/ffmpegCommandExecute/1.0.0/index.js:14:53) at fulfilled (/app/Tdarr_Node/assets/app/plugins/FlowPlugins/CommunityFlowPlugins/ffmpegCommand/ffmpegCommandExecute/1.0.0/index.js:5:58) at process.processTicksAndRejections (node:internal/process/task_queues:104:5){}

The docker tag is ":latest" which is currently 2.78.01

How can I address or work around this problem?

Thank you.

I hope I can share this here. Large Iranian support noted in the largest annual pro Israel march in Toronto ever

Long story short - AI tells me that Frigate doesn't support "tiered storage" and if I move any of the media to another path then I'll confuse it.

The idea is that nvme ram and SSD are expensive and have shorter life span (and can crash on the spot, without warning signs, which is what just happened to me on a 6 y/o SSD card), so it would be nice to be able to tell Frigate something like "store and process new media on path A (which resides on fast storage), and after a few hours/days, move the media to path "B" (a slower, larger, cheaper storage medium).

Is there such a feature? Is it in the plans?

I can come up with a script to shuffle old files and symlink them from the location Frigate expects to find them, but it would be nice to avoid such a hack.

I wonder if I could use this to alert me when my external home doors are opened at night or when we are out, or when my son forgets the window open.

I have Frigate 0.17 running in a docker container under Portainer connecting to mqtt and sending events.

The issue is that it only works for me if I set the password directly in the Frigate configuration file.

I'd like to pass the password via an environment variable, so I can keep the configuration file in git.

I tried various variations of

password: "{FRIGARE_MQTT_PASS}"

(with or without quotes, single or double quotes, with or without $)

but nothing works. It just doesn't connect to mqtt and Home Assistant shows no events, except when I set the literal password in Frigate's config (then HA shows events)

What am I missing?

Thanks.

With all this talk on the regime being starved of cash and the Iranian currency crashing, would you expect anything to shift come around May 21st when the next government salaries are supposed to be paid?