feat: Add Studio One project scanning support

[rogerb831]

This PR adds Studio One project scanning support to OwlPlug.

Changes

• Add StudioOneProjectExplorer for .song file format (ZIP-based XML)
• Add StudioOneAudioMixerPluginCollector for audio effect plugins
• Add StudioOneSynthPluginCollector for instrument plugins
• Integrate Studio One support into ProjectSyncTask
• Add STUDIO_ONE to DawApplication enum
• Implement plugin name normalization in PluginLookupService to handle platform suffixes (x64, x32, etc.)
• Prioritize classInfo over deviceData for plugin name extraction to avoid instance names
• Filter out autosave files from scanning
• Add minimal debug-level logging matching other DAW patterns

Testing

Tested on Windows with Studio One project files. Successfully extracts:

• Audio effect plugins from audiomixer.xml
• Instrument plugins from audiosynthfolder.xml
• Properly matches plugins using normalized names

Notes

• Studio One .song files are ZIP archives containing XML files
• Plugin names are extracted from classInfo to avoid duplicate instance names
• Autosave files (containing "(Autosaved)" or in History folders) are automatically filtered

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[DropSnorz]

Hi @rogerb831, thanks for your PR !

I'll take a look in the next days.

[rogerb831]

Hi @rogerb831, thanks for your PR !

I'll take a look in the next days.

Thanks for that. Fair warning, I'm not a dev by trade and this was heavily enabled by AI. But I'm happy to address whatever issues come up.

[DropSnorz]

Hi @rogerb831, thanks for your PR !
I'll take a look in the next days.

Thanks for that. Fair warning, I'm not a dev by trade and this was heavily enabled by AI. But I'm happy to address whatever issues come up.

Don't worry too much with codacy code complexity, recent changes in complexity compute broke my previous rules, so it's sometimes failing even with acceptable complexity.

[DropSnorz]

Hello @rogerb831

Thanks for your contribution, it could be great to have Studio One support in OwlPlug !

I've added some elements in #217 and reviewed your changes here.

Overall, the logic is valid and design aligns well with the existing principles.
Some adjustments and refactoring steps are required before we can move forward with this PR.

Let me know if you need help with any of the changes.

[rogerb831]

Hi @DropSnorz, I've addressed all the feedback from your review:

✅ Fixed redundant format detection logic - Removed unnecessary startsWith() checks, now using only contains() for VST2/VST3 detection

✅ Refactored StudioOneDomUtils - Created private findAttributeByXId() helper method and refactored all public methods to use it, eliminating code duplication

✅ Fixed log level - Changed cleanup failure logging from debug to error in StudioOneProjectExplorer

✅ Eliminated code duplication - Moved extractPluginName() and extractPluginFormat() methods to StudioOneDomUtils as static utilities, removing ~60 lines of duplicated code between collectors

✅ Moved normalization to collectors - Plugin name normalization now happens during project sync (in collectors) rather than during lookup, ensuring cleaner database data as requested

✅ Reverted PluginLookupService - Restored to original simple implementation since normalization is now handled during sync

All changes have been committed and pushed. The code is now cleaner, more maintainable, and follows the patterns you suggested. Ready for re-review!

[rogerb831]

Hi @DropSnorz, I realized we missed some additional feedback from your review. I've now addressed those items:

✅ Simplified ArchiveUtils.extractFiles() - Refactored to match your suggested implementation exactly:

• Removed complex parent directory management (PathCollection, collectParentDirectories, etc.)
• Removed compression stream support (assumes ZIP format for Studio One .song files)
• Simplified to a single method using Collection parameter
• Aligned variable names and error messages with your suggestion

✅ Fixed Document:Generator usage - Now only uses Document:Generator attribute (removed Document:Creator check) as requested

✅ Individual XPath exception handling - Each XPath query now has its own try-catch block with appropriate default values, making the code more robust

All changes have been committed and pushed. The code now fully addresses all your feedback and is ready for re-review!