Project Feature - Base structure

[DropSnorz]

No description provided.

[kmturley]

Exciting that you are working on this feature. I tried to implement something similar for StudioRack:
https://github.com/studiorack/studiorack-core/blob/main/src/project.ts
https://studiorack.github.io/studiorack-site/docs/02-create-a-project-config

However it's a bit of a mess and needs a rethink. It kind of works in the command line and electron app.

The main idea was that someone can create a project.json file, which links to their DAW file, and lists all the plugins they are using. Then they can install all the exact plugin versions with the click of one button. Then open the project with a click of a button in their DAW

Recenetly there has been a new development which could also be interesting for this feature:

"The DAWproject format provides a (vendor-agnostic) way of transferring user data between different music applications (DAWs)."
https://github.com/bitwig/dawproject

Would be interesting to see if Owlplug and StudioRack could have deeper integration with dawproject files.
For example you could read the plugins directly from the dawproject file instead of having a separate .json file.

[DropSnorz]

Hello @kmturley !

It's good to have some news from you!

The main idea was that someone can create a project.json file, which links to their DAW file, and lists all the plugins they are using. Then they can install all the exact plugin versions with the click of one button. Then open the project with a click of a button in their DAW

Yeah, I want something similar for OwlPlug, the idea is to track missing plugins. Here I'm trying to directly parse DAW native project files to extract the list of plugins. I have to carefully select which DAW will be supported to avoid a lot of maintenance due to breaking changes introduced by DAW updates. I'm trying with Ableton Live .als files for now. The format is very stable, I can extract plugins from an .als file the same way for Ableton 8 (2009) up to Ableton 11 (2021).

Recenetly there has been a new development which could also be interesting for this feature:

"The DAWproject format provides a (vendor-agnostic) way of transferring user data between different music applications (DAWs)."
https://github.com/bitwig/dawproject

Would be interesting to see if Owlplug and StudioRack could have deeper integration with dawproject files.
For example you could read the plugins directly from the dawproject file instead of having a separate .json file.

Oh great, thanks, I was not aware of this repo by Bitwig, but of course, I'm very interested in supporting an open project format. Even if it's not a strong market share, it's very well documented, and implementing it shouldn't be too complicated.

[DropSnorz]

Code review done

• Fix some typo / import issues
• Recompute lookups after plugin sync