When using "--lavfi-complex", "--profile=low-latency" and "--untimed" do not work

Important Information

• mpv version: v0.36.0-250-g02b49458
• Windows Version Edition: Windows 10 Pro, 22H2, 19045.3208
• Source of the mpv binary: Windows Build by shinchiro

Reproduction steps

Tested with a .ts or HTTP network stream:

This works:
start mpv http://[EXAMPLE.STREAM.COM/1].ts --external-file=http://[EXAMPLE.STREAM.COM/2].ts --external-file=http://[EXAMPLE.STREAM.COM/3].ts --external-file=http://[EXAMPLE.STREAM.COM/4].ts --lavfi-complex="[vid1] [vid2] hstack [t1] ; [vid3] [vid4] hstack [t2] ; [t1] [t2] vstack [vo]"

This does not work:
start mpv http://[EXAMPLE.STREAM.COM/1].ts --external-file=http://[EXAMPLE.STREAM.COM/2].ts --external-file=http://[EXAMPLE.STREAM.COM/3].ts --external-file=http://[EXAMPLE.STREAM.COM/4].ts --lavfi-complex="[vid1] [vid2] hstack [t1] ; [vid3] [vid4] hstack [t2] ; [t1] [t2] vstack [vo]" --profile=low-latency --untimed

Expected behavior

Adding --profile=low-latency --untimed allows the stream to re-connect after a network interruption, as it does correctly with a single stream

Actual behavior

Adding --profile=low-latency --untimed causes an error that stops MPV from opening.

Log file

output.txt

Compare the working and failing mpv command lines, then inspect the attached output.txt for the error triggered by --lavfi-complex with --profile=low-latency and --untimed. Trace the relevant option-handling or filter-graph entry point identified by that error. Done means the combined options no longer prevent mpv from opening and the multi-stream setup reconnects after a network interruption.