[cre8ive-marketing]

What does this change?

Two open enhancement issues, one commit each, with tests and a line in docs/ENGINES.md.

Issue	What changes
#396 All audio tracks	Video → video mapped only the first audio stream (-map 0:a:0), so a film with three languages kept one. MediaInfo now lists every audio stream (AudioTracks), and each is mapped and either copied (the target takes its codec) or encoded with its own options: -c:a:N, -b:a:N for that track's channel count, -ac:a:N. The streams' language tags come along. FLV and DV hold one track and keep the first, and video → audio still takes the first.
#397 .dst embroidery	Tajima DST designs are a read-only vector format. The vector engine draws the stitches as SVG polylines at real size (Vector/DstEmbroidery.cs), a palette colour per thread since DST stores no thread colours, and renders PNG, JPG or PDF from there. Records are decoded with the same bits as pyembroidery's DstReader: stitch, jump, colour change, sequin-mode switch, end. AutoCAD sheet sets also use .dst, so a file without the LA: header fails with that reason.

Settings schema 33 teaches existing vector donuts .dst. Like #393, it will need renumbering after #351. Happy to do that, or leave it to you.

How was it tested?

• dotnet format --verify-no-changes
• dotnet test: with FFmpeg 9.0.2 and rhwp 0.8.7: Core 456, Engines 1449, Setup 145, Cli 27, Platform 48 pass. App: 806 pass, 1 fail, SingleInstanceTests.Arguments_reach_a_first_instance_that_starts_listening_late, a timing test under the full run's load; it passes 3/3 alone and this PR doesn't touch it.
• New tests:
  • AudioTracksTests:
    • every track mapped, with per-track copy or encode and bitrates
    • one track keeps plain options, FLV keeps one, "remove audio" still drops all
    • option values never renamed
    • with FFmpeg 9.0.2, a real 1080p MKV with Japanese AAC, English Opus and Korean FLAC tracks → the "MP4 720p" preset keeps all three as AAC, with their language tags
  • DstEmbroideryTests:
    • stitches, jumps, colour changes and a sequin switch decoded
    • every step size (±1 … ±121) on both axes
    • a two-thread design → SVG at 29 mm with two colours → PNG
    • an AutoCAD-style .dst fails with the reason
  • DstFormatTests (Core): the format entry, and the upgrade with and without a user's own claim on .dst.

The DST bit layout was checked against pyembroidery's reader rather than only against the test's own encoder.

TracingTests.IsTracing treated every vector-engine step into SVG, except from SVGZ, as tracing. DST → SVG draws the stitches and joins SVGZ in that exception, so Tracing_is_never_a_step_towards_a_format_that_has_another_route still checks every other route.

Screenshots (UI changes)

No UI changes.

Checklist

• New UI strings are in all src/Filee.App/Assets/i18n/*.json files (none added)
• New third-party code or binaries are listed in THIRD-PARTY-NOTICES.md (none; pyembroidery was only read to check the format)

Fixes #396. Addresses #397: PNG, JPG and PDF are done; writing other embroidery formats such as PES or DSZ isn't part of this, so the issue can stay open for that.

[KnifeLemon]

Thanks @cre8ive-marketing! Both parts look right to me. Mapping every audio track with its own -c:a:N/-b:a:N/-ac:a:N keeps the one-track case exactly as before, FLV and DV keep the first, and video → audio is unchanged. The DST records decode with the standard bit layout, and failing an AutoCAD sheet set with a reason is a nice touch. I ran the new tests here too, including the three-language MKV with FFmpeg 9.0.2.

Two things we'll handle on our side when merging, no need to push:

• Settings schema: several open PRs add a migration, so we give each the next free number when it goes in (CurrentSchemaVersion, the v33 step and the test that starts from 32).
• The changed bullet in docs/ENGINES.md gets re-wrapped like the lines around it.

#396 closes with this; #397 stays open for writing embroidery formats, as you said.

[KnifeLemon]

Merged, thanks @cre8ive-marketing! When bringing it up to main we gave its settings migration schema 38 and described the DST record layout in our own words in DstEmbroidery.cs. It'll be in the next release.