I would like to have the ability to generate a list, a text file, with all the plugins used in a specific project. It would help me in the process of sending a Cubase project (the whole folder with audio, tracks, .cpr file and so on). It would be really nice if the person I send the project to has a list so s/he knows what plugins to get in order to get the project to work properly.
2 Likes
It would be good to have a meta database which keeps track of all plugins in all songs
+1
i had to spend time manually marking this down during project-archiving for backward-compatibilityās sake - and was wishing this was implemented as well.
very generally speaking, it would be nice to see future āpluginsā transform into the form of āmodulesā that could be instantly downloaded and compiled as a project loads. i am aware iām not talking forseeable future hereā¦
This is yet another among my āVersion Controlā and āProject Managementā feature requests that go back years.
What is mildly gratifying to me is that it appears that others are finally getting on board.
Itās long past time for Cubase to take this sort of thing seriously.
A good model is what is used in the printing bizā¦ itās called a Pre-Flight Report. (See InDesign). It shows one ALL the assets required for a project (images, fonts, the devices used). Cubase should be able to have a similar facility. It could start with a report that listed:
ā¦input devices
ā¦VST plugs used
ā¦out config
ā¦MIDI tracks, with assigned gizmos
ā¦ext. hardware
ā¦etcā¦
So when you opened an archived CPR youād know what you needed. Or if you move a CPR to another place you can know ahead of time what they will need.
2 Likes
Another good and seemingly easy to implement feature.
And while weāre on requesting a metadata reporting feature, why couldnāt we have āhistoryā metadata also:
Dates and times of all
- recordings (both MIDI and audio)
- off-line processings
- bounces
- etc
+1
+1
You might check out plugview (windows), it will read the contents of the cpr and list the used plugins and number of instances. You can copy the list to the clipboard. I use it with Cubase 8.
https://solasistim.wordpress.com/2010/03/27/plugview-a-little-insight-into-your-daw-projects/
1 Like
Plugview seems to be exactly what Iām looking for! Thank you very much!
+10
Iāve been hassling the makers of my other DAW to implement this for years. Still waiting thereā¦
+1
would also like to see CPU usage per plugin so I can better budget CPU cycles and easily track down which tracks need to be frozen or bounced
That sounds like I really nice feature to be implemented. It deserves an own thread in āFeature Requests and Suggestionsā!
+++ STEINBERG wake up please !!!
This is much more important with the announced removal of VST2 support in the coming 2 years. The ability to have a list of all projects with the version of Cubase used together with the list of Plugins (and their format) used is going to be key to allow users to manage the migration and keep just the older versions of Cubase needed to be able to go back to work on older tracks.
2 Likes
I got scared when I clicked that link and found the blog had been deleted, but I located the tool on the authorās site: twodev | plugview
Thanks for posting about this- itās something Iāve always wanted as well!
EDIT: The tool hasnāt been updated since 2011 but still reads modern Cubase CPRs and seems to correctly detect plugins used. Its feature to identify missing plugins doesnāt seem to work right, but thatās no dealbreaker. Also, I see it was developed by the same guy who did ReSonic Player, which is a tool I use frequently. Cool!
4 Likes