fix: resolve downloaded bundled VST primaries - #64
Open
ciolansteen wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ionut Adrian Ciolan <iadrian@ciolan.net>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe VST primary resolver now falls back to broader installed-plugin lookup when a bundled candidate is absent from the plugin directory. Tests cover preference for the plugin-directory bundle and fallback to a downloaded pack. ChangesVST primary resolution
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix built-in Rig Builder gear resolving to
No VST assignedin current thin packaged builds, even after the downloadable VST pack has been installed and scanned.Root cause
Curated candidates carry a
bundledrelative path._pick_installed_primary_vst()first checks that path under the read-only plugin directory, which is correct for older fat bundles. However, when that file is absent, the second pass unconditionally skipped every candidate that hadbundledmetadata.Current thin builds place the optional pack under the writable config root instead. Those VSTs are present in the known-plugin scan, but the unconditional skip prevented name-based resolution and left built-in catalog entries without
vst_path; Studio then filtered them out.Fix
Keep the existing bundled-path lookup as the preferred path. If it is absent, allow the same candidate to use the existing
known_lookupfallback by name. This preserves fat-bundle behavior while enabling downloaded packs.Regression tests
Added focused coverage for both distribution modes:
bundledmetadata;Evidence:
The broader Python suite has three pre-existing failures on both
origin/mainand this branch (tests/test_vst_path_rehome.pyexpectations and a missingtools.content_packsmodule intest_vst_pack_download.py); this commit adds two passing tests without changing that baseline.Live data validation
Using the installed thin-build paths and the live known-plugin cache:
No runtime configuration or user files are modified by this change.
Summary by CodeRabbit
Bug Fixes
Tests