Failing to record when a new (HDMI) capturer is connected

[yarikoptic]

We are switching to using HDMI and thus

• I connected (in addition, moved Horea's dongle USB to USB hub) additional Magewell, HDMI one now
• changed config.yaml where I typed (from photo of the device) its serial
• it seems to react to connect but doesn't record (fetch/look at logs/2025-11-04T11:15-05:00.log)

❯ tail -n 40 logs/2025-11-04T11:15-05:00.log | head -n 15
2025-11-04 11:16:13.869 [INFO] [3744511] 2025.11.04-11.16.13.667:	Started Recording: 
2025-11-04 11:16:13.869 [INFO] [3744511] Apct Rat: 1920x1080
2025-11-04 11:16:13.869 [INFO] [3744511] FR: 60
2025-11-04 11:16:13.876 [INFO] [3745768] REPROSTIM-METADATA-JSON: {"cap_isotime_start":"2025-11-04T11:16:13.667743","cap_ts_start":"2025.11.04-11.16.13.667","json_isotime":"2025-11-04T11:16:13.876093","json_ts":"2025.11.04-11.16.13.876","message":"ffmpeg thread terminated","type":"session_end","version":"1.11.0.347"} :REPROSTIM-METADATA-JSON
2025-11-04 11:16:13.876 [INFO] [3745768] Renaming con/duct info : /data/reprostim/Videos/2025/11/2025.11.04-11.16.13.667--.mkv.duct_info.json -> /data/reprostim/Videos/2025/11/2025.11.04-11.16.13.667--2025.11.04-11.16.13.876.mkv.duct_info.json
2025-11-04 11:16:13.876 [INFO] [3745768] Renaming con/duct usage: /data/reprostim/Videos/2025/11/2025.11.04-11.16.13.667--.mkv.duct_usage.json -> /data/reprostim/Videos/2025/11/2025.11.04-11.16.13.667--2025.11.04-11.16.13.876.mkv.duct_usage.json
2025-11-04 11:16:13.876 [ERROR] [3744518] Rest method "repromonSendMessage" HTTP request failure: Couldn't connect to server
2025-11-04 11:16:13.876 [ERROR] [3744518]   - RestResult(httpCode=0, data=, error=Rest method "repromonSendMessage" HTTP request failure: Couldn't connect to server)
2025-11-04 11:16:13.876 [ERROR] [3744518]   - url=https://localhost:9095/api/1/message/send_message?category=1&description=reprostim-videocapture%20session%202025.11.04-11.16.13.667%20end%2C%20saved%20to%202025.11.04-11.16.13.667--2025.11.04-11.16.13.876.mkv&device=1&event_on=2025-11-04T11%3A16%3A13.876320&level=1&provider=2&registered_on=2025-11-04T11%3A16%3A13.876332
2025-11-04 11:16:13.876 [ERROR] [3744518]   - RestConfig(baseUrl=https://localhost:9095/api/1, apiKey=..., accessToken=..., verifySslCert=0, connTimeoutSec=3, verbose=0)
2025-11-04 11:16:13.876 [ERROR] [3744518]   - RestMethod(name=repromonSendMessage, url=/message/send_message, usePost=1, contentType=application/json, accept=application/json, bodyParams=null, queryParams={"category":"1","description":"reprostim-videocapture session 2025.11.04-11.16.13.667 end, saved to 2025.11.04-11.16.13.667--2025.11.04-11.16.13.876.mkv","device":"1","event_on":"2025-11-04T11:16:13.876320","level":"1","provider":"2","registered_on":"2025-11-04T11:16:13.876332"})
2025-11-04 11:16:15.774 [INFO] [3745778]   [NOT MATCHED]
2025-11-04 11:16:20.072 [INFO] [3744511] Skip Restart Recording, waiting for recovery timeout
2025-11-04 11:16:21.091 [INFO] [3744511] Skip Restart Recording, waiting for recovery timeout
2025-11-04 11:16:22.108 [INFO] [3744511] Skip Restart Recording, waiting for recovery timeout

video capture log points to incorrect audio

❯ tail Videos/2025/11/2025.11.04-11.16.13.667--2025.11.04-11.16.13.876.mkv.log

2025-11-04 11:16:13.863 [INFO] [3745768] [alsa @ 0x55cae5a2f200] cannot open audio device hw:3,1 (No such file or directory)

2025-11-04 11:16:13.863 [INFO] [3745768] hw:3,1: Input/output error

2025-11-04 11:16:13.869 [INFO] [3744511] 2025.11.04-11.16.13.667:	Started Recording: 
2025-11-04 11:16:13.869 [INFO] [3744511] Apct Rat: 1920x1080
2025-11-04 11:16:13.869 [INFO] [3744511] FR: 60
2025-11-04 11:16:13.876 [INFO] [3745768] REPROSTIM-METADATA-JSON: {"cap_isotime_start":"2025-11-04T11:16:13.667743","cap_ts_start":"2025.11.04-11.16.13.667","json_isotime":"2025-11-04T11:16:13.876093","json_ts":"2025.11.04-11.16.13.876","message":"ffmpeg thread terminated","type":"session_end","version":"1.11.0.347"} :REPROSTIM-METADATA-JSON
2025-11-04 11:16:13.876 [INFO] [3745768] Session logging end: session_logger_2025.11.04-11.16.13.667

• for now I stopped the service since it just floods with that message

• actually I tried to disable audio by entering empty value there (or is that not the way?) but still the same

❯ grep a_dev config.yaml
  # Optionally, specify "a_dev" ALSA audio device explicitly (e.g. hw:1,0)
  # "auto" value, to calculate "a_dev" automatically based on
  a_dev: "" #auto"
  # NOTE: in case v_dev specified explicitly, a_dev value
❯ tail Videos/2025/11/2025.11.04-13.48.13.297--2025.11.04-13.48.13.493.mkv.log
2025-11-04 13:48:13.473 [INFO] [3755856]   libswresample   4.  7.100 /  4.  7.100

2025-11-04 13:48:13.473 [INFO] [3755856]   libpostproc    56.  6.100 / 56.  6.100

2025-11-04 13:48:13.480 [INFO] [3755856] [alsa @ 0x556494e5e480] cannot open audio device hw:3,1 (No such file or directory)

2025-11-04 13:48:13.480 [INFO] [3755856] hw:3,1: Input/output error

2025-11-04 13:48:13.493 [INFO] [3755856] REPROSTIM-METADATA-JSON: {"cap_isotime_start":"2025-11-04T13:48:13.297362","cap_ts_start":"2025.11.04-13.48.13.297","json_isotime":"2025-11-04T13:48:13.493503","json_ts":"2025.11.04-13.48.13.493","message":"ffmpeg thread terminated","type":"session_end","version":"1.11.0.347"} :REPROSTIM-METADATA-JSON
2025-11-04 13:48:13.493 [INFO] [3755856] Session logging end: session_logger_2025.11.04-13.48.13.297

note: sound this time was not going through HDMI but sent through aux... yet to see what we should do about that...