tone-3000/tone3000-plugin

Search I searched existing issues and this is not a duplicate Problem Problem Related to #82, but a distinct trigger: adding a new block (tapping the + insert slot) or swapping an existing block's tone also resets the chain view's horizontal scroll position to the far left, instead of scrolling to or landing on the block that was just added/swapped. On a long chain, this means every add or swap forces the same manual scroll-back that #82 describes for closing an expanded block view — but it isn't covered by that fix, since it's a different part of the UI losing track of where you were. Proposal When a block is added or swapped in, bring it into view automatically — ideally by opening its expanded view directly (matching what tapping an existing tile already does), or at minimum by centering its tile in the gallery. Either way, the viewport shouldn't default back to the start of the chain. Alternatives None needed — this should follow the same "land on what you just did" behavi

Search I searched existing issues and this is not a duplicate Problem When reopening a NAM model/IR dropdown menu, the list always defaults to the very top instead of jumping to and highlighting the currently loaded file. In folders or tone packs containing dozens or hundreds of files, this causes significant friction: the user loses visual context of what is active and is forced to scroll all the way back down to find neighboring files. Proposal When opening a dropdown menu: Automatically scroll the list view so the currently active item is visible in the viewport. Clearly highlight/check the active item in the list. Alternatives No response Area Interface

Search I searched existing issues and this is not a duplicate Problem When closing an expanded block view to return to the main signal chain, the horizontal viewport automatically resets and snaps to the far left (the start of the chain). On longer chains, this is disorienting and forces the user to manually scroll back each time to find where they were working. Proposal Preserve the horizontal scroll position of the chain. When exiting an expanded block view, the view should remain at the current position, preferably keeping the recently edited block centered or visible in the viewport. Alternatives None needed — maintaining scroll/viewport state on navigation stack pop is standard UI behavior. Area Interface

Search I searched existing issues and this is not a duplicate Problem Summary / Context Currently, the built-in EQ within processing blocks exhibits the following signal routing behavior: Default (Post): The EQ processes the entire output of the block affecting both the Wet and Dry signals combined. Pre mode: The EQ filters the signal prior to processing (effectively targeting only the path entering the block's algorithm, leaving the parallel dry intact). The Problem Filtering both the wet and dry paths combined in the default/post position is unintuitive and counter-productive for parallel processing workflows. In typical audio and plugin architectures, an internal block EQ is expected to shape the processed (wet) sound only, preserving the integrity and tone of the direct (dry) signal. Practical Use Case Reverb / Delay / IR Loading: When running a space IR, reverb, or delay block with a parallel mix (e.g., 30% Wet / 70% Dry), the user almost always wants to filter out harsh hig