Would you find it useful to have a sources list from your projects, one that tells you your track and the devices and patches used?
----Edit---
Original discussion was started here
viewtopic.php?f=48&t=7520714
sources list from your projects
-
- Posts: 790
- Joined: 09 Dec 2016
Last edited by Billy on 09 Dec 2020, edited 1 time in total.
-
- Posts: 88
- Joined: 28 Sep 2018
Why?
E.g. that you know which VSTs you used in which song. Makes testing new VST updates easier.
E.g. that you know which VSTs you used in which song. Makes testing new VST updates easier.
-
- Posts: 790
- Joined: 09 Dec 2016
Yes, so you can generate a list of things used to create the project.
-
- Posts: 2035
- Joined: 17 Jan 2015
It's also for the sake of archiving and looking at old projects from machines, systems and VSTs long gone, projects you can no longer open anymore. Maybe that file rendered with the final mix could be seen as the project's birth certificate one day.
-
- Posts: 184
- Joined: 31 Jul 2019
Can't see this being of use to me personally, because I just don't keep old projects - they're either finished or abandoned - either way, I don't tend to 'go back' to old stuff.
-
- Posts: 2807
- Joined: 19 Jan 2015
not against it, of course, but I wouldn’t find it very useful myself. I’d rather have a way to search for/highlight/toggle through each instance of a particular RE or VST in an open project (e.g. I know I’ve used a Note Echo somewhere, but don’t remember which track it’s attached to...so I can search within the project to find it in the rack).
-
- Posts: 211
- Joined: 16 Jan 2015
Instead of generating a "list" you could just save the patches and combinators in the Project folder! At least you could load them up easily, also save the patch as "Re|vst_name_PatchName"
Albuns: BandCamp | Youtubz: Noise Channel
-
- Information
-
Who is online
Users browsing this forum: CommonCrawl [Bot] and 0 guests