@Jamabaiz @johnebaker

Hi. I don't know if this will be useful or not.

When I export a project for backup to an external drive I always copy the files as well into the export.

Opening the project by using the MVP file within the folder has always imported everything.

I have just double checked this by replacing my external drive and opening a project from it I have never worked from before.

I have not found a need to change anything in the MEP Folders for Exports Imports or Recordings that I reserve for up to date projects that are always done on two internal drives.

I know some people will balk at the extra storage space taken and cost with this method but it ensures I do not lose files or have hassle setting up projects if the files originated on more than one drive.

Ray.

@CubeAce, @Jamabaiz

Hi Ray

. . . . When I export a project for backup to an external drive I always copy the files as well into the export. . . . .

Do you mean you use the 2 step process:

1. File, Backup Project, Copy project and media to a folder 
2. Copy any media that could have been used in the project to the same folder.

The reason I have written it is this way is that step 1 only copies the media that is on the timeline, it does not copy spare/unused media that you may want to use if you go back to the project at some future time.

John EB

@johnebaker

Hi John.

I always use this setting for MEP and VPX project backups.

Which gives me this project folder contents.

You are correct, it only backs up content used by the project not all the files from each folder used. But then they are not needed to open a stored project. Surely that is a different problem.

Ray.

@CubeAce @johnebaker @Jamabaiz

Like you and John I use the same tool to backup the project and its required files. Up until now, in the original project folder I’ve retained only a tiny few of the scores or hundreds of files that I’ve used or toyed with using or edited etc during the project’s development. Such as my Notes(ProjectName).txt, the final MP4, the final MVP (even though it obviously cannot run from there), etc. But, prompted by John’s comment, maybe I’ll simply move those across to the backup folder. Neater.

@terrypin

Hi Terry

. . . .Like you and John I use the same tool to backup the project and its required files . . . .

I don't, and never have, used the backup option in MEP/VPX - I have an entirely different method, my projects are structured in a 'standard' named folder structure for each project based on an empty master project folder template with the following structure

all resources used and/or created are dropped into the appropriate folders, and sub folders you cannot see in the image above.

The whole project folder is backed up to external drive(s) using SyncBack, with filters set to not copy any of the temporary files MEP/VPX creates, after the initial backup only files that have been added or changed are backed up - this also enables me to easily sync a project with my laptop if I need to work on it while away.

I have mapped a drive to emulate the W: drive on my PC so there in no need to change anything between the computer and laptop - they both have a W: drive, MEP folder locations are set up identically, and the same folder structures for projects.

Sounds complicated, however, it is easy to setup and do, and avoids the missing files issue when moving projects between 2 different machines.

John EB

@CubeAce

Hi

Ray

. . . . But then they are not needed to open a stored project. Surely that is a different problem . . . .

Not if, as I stated - 'you may want to use if you go back to the project at some future time' - which is what my next series of projects to do - have to redo some video files in FLV format to mp4 - I have the projects complete as described above, however may have some minor issues loading them due to the MEP versions they were created on (17 and MX) - fortunately there are no special transition effects, animations, etc in them.

John EB

@johnebaker

Hi John.

however may have some minor issues loading them due to the MEP versions they were created on (17 and MX) - fortunately there are no special transition effects, animations, etc in them.

Again, that is another yet another 'Kettle of Fish' when dealing with digital content and a major drawback when dealing with archive material.

It's not even possible to get really old programs to run with virtual machines if the drivers are missing or the newer computer configurations don't allow certain connections. I've always thought about rebuilding a Window 98 pc for that very purpose. Put in my Yamaha DX sound card and with it's complete DX built in Synth and effects. I would then be able to load my early Cubase programs that uses a serial port connector no longer found on modern boards for the operating dongle.

Just think what would / may happen if we went to 128 bit systems in the future or the current formatting structures had to change or if we went away from binary systems.

At the pace of change at present that shows no signs of slowing down if not actually speeding up we will soon find ourselves having to upgrade machine specs even more frequently. Android doesn't update anything older than four years old due mainly to the hardware not able to keep up. I assume Win 10 is doing the same sort of things in the background making older systems less compatible.

However, coming back to the topic.

Revisiting an old project. Is it really worth it unless you have lost your master export copy? You may as well start afresh with the original source files in my own personal opinion. As you said older effects may not be present or work unless you feel a newer program can make a better quality copy with tweaks from newer plug-ins.

Ray.