Vegas 11 - mxf files in project

Leopardman wrote on 10/18/2011, 6:28 AM
I am working on 2 fairly large projects that consist of mainly 1440X1080x50i footage shot with an EX3 and some clips shot with a V1E.

Both these projects were created and rendered in Vegas Pro 10e 64 bit without any hassle.

I've upgraded to Vegas Pro 11 64 bit, installed without uninstalling Vegas 10e. When I opened the projects in Vegas Pro 11, I had no problems, all clips were properly identified and preserved and I saved the projects under Vegas Pro 11 to the same project names. I then proceeded to uninstall Vegas Pro 10e. This is when disaster struck. When I opened the projects in Vegas Pro 11 after the uninstall of Vegas Pro 10e, it did not "recognise" the mxf video clips and how these were edited from the project (.veg) file.

Fortunately I do make weekly (more often if required) backups (i.e. full copy) of all files. I could open a new project in Vegas Pro 11 and import mxf files, no problem.

I eventually reinstalled Vegas Pro 10e, copied the backup copy of my project (.veg) files as saved by Vegas Pro 10e to my project directory and re-opened it with Vegas Pro 11 without any problem. Again save the project using Vegas Pro 11, closed and re-opened again with Vegas Pro 11 with Vegas Pro 10e still installed, no problem.

Tonight I will uninstall 10e again and see if the problem persists with the mxf files.

Comments

ushere wrote on 10/18/2011, 6:39 AM
i have to ask why you're uninstalling 10e so quickly?

unlike some here who still have ver 4 (or was it 5) on their pc, i still have 9 and 10e. 11 looks good so far, but i wouldn't be burning my bridges quite so quickly ;-)

alos, has anyone done an uninstall of a previous version without causing problems with the exisiting one?

i uninstalled 9 w few months back when i was happy with 10e, only to find 10e wouldn'r even load. i restored from image and haven't had the guts to try uninstalling 9, let alone 10, for fear of problems.

could scs please advise whether it's safe to uninstall previous versions?
farss wrote on 10/18/2011, 6:43 AM
"When I opened the projects in Vegas Pro 11, I had no problems, all clips were properly identified and preserved and I saved the projects under Vegas Pro 11 to the same project names."

Sorry to be blunt but OMG, are you insane or what?
Never, ever do that. Every project I save includes the version of Vegas that it was created under e.g. "Edit - 536-V09.veg"

"Tonight I will uninstall 10e"

Why uninstall V10?
Only two days ago I hit some odd snag in V9 crashing when I added more than 4 m2t files to the T/L, V10 had the same affliction. I got around the problem by adding all the m2t files to a V8 project, saved that, opened the V8 project in V9 and all has been good ever since.

Bob.
apit34356 wrote on 10/18/2011, 6:52 AM
I'm with Farss on this, I think I have vers. 4 on one of my older computers still.... I like to keep the "best" on each version available encase of "problems". I do that with ACAD, MAx, etc.... probably more that I should, but when time is critical, I use whatever tool version works the best for the task! :-)
Leopardman wrote on 10/18/2011, 7:19 AM
Contrary to the problems you've indicated, these projects contain at least 70+ mxf and 20+ m2t clips on the timeline, edited these and similar projects without any hassles in any version of Vegas Pro 10. Average timelenght/duration of project is +- 2hours give or take 10 minutes either side.

_______________________________________________
Win 7 Pro 64-bit, Intel i7 2600k 3.4GHz, 8GB RAM, 500GB Boot drive, 2x1TB Raid drives, 1x500GB scratch drive, 2xBlu-ray DVD writers
farss wrote on 10/18/2011, 8:28 AM
"Contrary to the problems you've indicated, these projects contain at least 70+ mxf and 20+ m2t clips on the timeline, edited these and similar projects without any hassles in any version of Vegas Pro 10. Average timelenght/duration of project is +- 2hours give or take 10 minutes either side."

The fact that you were in the middle of a largish project and having no issues with the current version of the software that you were using makes what you did all the sillier.
To also over write your project file created in an older version of Vegas, despite Vegas warning you that you will not be able to revert, makes it even sillier. You have played fast and loose with Murphy's Law and paid the price for your transgression.

Unless you are having major issues with a particular version of any software, no matter who wrote it, installing a new version in the middle of doing anything vital is simply a dangerous thing to do. V11 is only hours out in the wild, the confidence level that there are no serious bugs is low, that's nothing unique to code written by SCS. It's not just the possibility of a major bug, the code could be fine but provoke some hitherto dormant hardware problem unique to your machine. Why temp fate, get your current project done and out the door and THEN install V11. Start off doing some smallish projects in the new version, slowly ease into it.

Bob.
Leopardman wrote on 10/18/2011, 9:01 AM
@Bob.

As indicated in my original post, I take backups (i.e. full copies - I don't use a backup utility as these often have more problems) on a regular basis, this includes my project definition file. I always maintain the original copy and use versioning as I progress through a project. Thus it was easy to copy back and have the project up and running/restored in Vegas Pro 10 in minutes.

I am definitely not as reckless as some of the comments may suggest. I've been in the game long enough and unless I can recover to the state the project has been in previously in less than 30 minutes, I would not even consider doing anything rash.

I doubt whether renaming the project file, i.e. Save As in Vegas Pro 11 would have made any significant difference as it still uses the source data from the old project definition to create the new one. I'll test it tonight. The error message that I got is that it could not map the frame numbers of the mxf clips to the meta data stored in the project definition file. The m2t clips were fine. It appears to have "lost" or corrupted the "In/Out points" of the mxf clips but not for the m2t clips.

Eddie
_______________________________________________
Win 7 Pro 64-bit, Intel i7 2600k 3.4GHz, 8GB RAM, 500GB Boot drive, 2x1TB Raid drives, 1x500GB scratch drive, 2xBlu-ray writers