Procedure to clone a project for revisions?

iragrollman · Joined: 22 Jul 2009 Posts: 2

We have been using GPME 8 for a while and clients are requesting revisions of existing projects. Sometimes it is an additional track or more typically a replacement for a track with something wrong in it.

Short of recreating the project manually, reentering the CD-Text and other metadata, is there a supported way to clone the project and then work on the new copy? Seems like something that could be done with set the project working directory, temp directory and audio directory.

Also we are looking for a supported way to not duplicate the audio files from where they are actually kept (on a network share) into the audio directory of the user's machine.

Regards, Ira Grollman, OMKT Disc Services

neilwilkes · Posted: Fri Oct 23, 2009 10:55 am Post subject:

So you want to make a second copy, keeping the initial version intact, where you add or alter existing material?

What type of discs are you creating here please - it looks like Red Book CD.

iragrollman · Joined: 22 Jul 2009 Posts: 2

Exactly correct on the copy of existing project. It is essential to keep the prior version(s) available for production, especially for compilation projects which may have 20 different artists, all on different source availability schedules.

These are Red book Audio CD's, although it would be nice to be able to do the same with wedding vidoegrpahy DVD's that we also produce.

Regards, Ira Grollman, OMKT Disc Services

Michael Szabo · Posted: Fri Oct 30, 2009 7:18 pm Post subject:

Based on your description of a "use case" for this functionality, I agree that this is a valid request, however, GEAR PRO Mastering Edition was designed to be run on a local machine with one user doing jobs. Having multiple instances of a project to work with, although valid under this use case, would require re-saving existing projects with slightly different project (.vol) names, or changing GEAR's Working Directory for each project as a way to accommodate such a work-flow will become a maintenance nightmare.

You could, I suppose, pull this off using batch files, where each batch file itself changes GEAR's Working Directory etc. Having source files on network shares, again, valid under this scenario (knowing Ira's workflow a little bit), is also outside what GEAR PRO Mastering Edition was intended for. At most, mapped network paths would be the farthest I would recommend using GEAR within a network environment.