fix: move NAM block size sync before JACK client restart

Browse Source

The profile change handler was calling nam_host.set_block_size() AFTER
jack_client.start(), creating a race where the JACK callback fired with
the new buffer size while the old NAM subprocess was still running at
the old block_size. Pipe byte counts desynced => NAM returned passthrough.

+ also: auto_connect disable during restart, connect_fx_ports reorder,
  Tone3000 gear/sort/pagination params, NAM engine switch API endpoints

...

This commit is contained in:

Shawn

2026-06-17 17:09:38 -04:00

parent 1b2747abb1

commit 6008776e3c

12 changed files with 646 additions and 190 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

dogfood-output/screenshots/downloads-overlay.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 15 KiB

dogfood-output/screenshots/main-page.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 32 KiB

dogfood-output/screenshots/search-results.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 60 KiB

dogfood-output/screenshots/settings-audio.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 48 KiB