So I took the plunge and made my big patch (124 files!) a project. The organization is amazing, and it seems to work muuuch better than when it first came out.

It still didn't move over all my files when consolidated (media files, .fxp files, and exported coll files), but after manually moving them they work A-ok.

I've got a couple of questions for those of you who have committed to projects for big patches.

1. Has the 'no save' thing been the death of your exploratory editing? I often will just start messing around with things, quite far sometimes, but then revert to saved by just not saving the file. The 'no save' thing scare me a bit as everything I do is being saved all the time without being able to revert versions at all. I suppose I could make a snapshot every time I want to mess with the patch, but sometime I don't know that I want to do that, so I'd have to make a snapshot every time I open the patch!

2. In my patch, I change a few things when I share a new version with the public. (ie making a vst choice open up any vst vs a specific one) I even make it so windows users have to swap out a subpatch due to an external I use not being on windows. How do you manage things like that? I can make a snapshot before I start doing that, but it appears like the snapshot doesn't 'unpack' into a full version of the project. So how can I make some changes, snare the project, then go back to my own version of it? And is it no longer possible for an end user (using runtime) to swap out a subpatch and run the project with the new file?

3. Is it me or is it impossible to order files in the project window? The files seem to get added in a willy nilly fashion, and drag/dropping works erratically and unpredictably. There doesn't appear to be an option to have it automatically alphabetise the files in each section. I've got over 40 patchers, and over 30 media files, and with how unpredictable/erratic the drag/drop is, it would take me over an hour to get things in the "right" order manually.