everything I’m doing is a feature, not a demand … you can patch as you like, and it wont break any existing patch or workflow.
the reason for these changes stem from discussions @oweno and I have been having regarding issues with ‘Save New’ (which was designed to help saving of patch state)
however, Save new, copies the entire patch directory, with some patches this can result in MB’s of externals, Soundfonts and wave files get copied, even though they are the same thing. this is clearly nuts!
the idea, is to separate volatile data, assets and ‘programs’… if you think about it, this is exactly what is done on your desktop computer, and for many good reasons
(a small technical note… USB and even SD cards are not designed for constant rewriting, so copying and deleting unnecessary will over time increase the ‘failure rate’ of cards… not an issue for manual copying, but minimising ‘systematic’ copying should be a goal)
as to if/when patches will be updated… well thats up to patch developers.
obviously I have things Im working on that will utilise these features, and hopefully demonstrate to users and patchers how this will work, and the benefits.
(hence, why i stated the intention of how to be used… as this is my planned usage)
p.s. as stated previously, these ‘releases’ are betas to allow testing/feedback from users and patch developers.
all changes are being included in the C&G code base, so will be released as part of an official C&G update in the future.