Inexplicable problem: project with R3Ds is messed up

macgregor

macgregor

Veteran
Hi all. I still can´t understand the problem here.
Today I opened a project I´ve been working on for several months already. This project was created on Vegas10 and uses R3D files and a couple quicktimes in it. My surprise was huge when i discovered that some of the clips in the timeline were showing images that were off. The in/out of several clips are all wrong, showing moments of the raw file that are not what I selected. The timeline slots look the same though. And if i expand each clip in the timeline, I can see that the original R3D file is there, it´s not trimmed or has any damage. So if i look for the mark in I can maybe find it 40 seconds to the right or to the left. It´s like the clips were randomly slipped in time, but keeping the position in the vegas timeline.

Then I though, uhmm maybe the TC in the project got messed up or the project file is corrupted. Then I opened a previous version of the project (I keep lots of projects version in case somethng goes wrong). Then I open the previos version and... same problem! It´s showing me the right clips but in a completelly different time inside the clip!

Then I open even older projects, same problem!

uhmmm, so maybe it´s a problem with the R3D file. That´s strange because you can´t trim R3Ds, so I can´t understand how the file was damaged. So i connect an external drive where i have a back up copy of all the projects and files... same problem!!!!!!

This makes no sense. It must be Vegas that got crazy. Then i tried a completely different computer... And the damn same problem is there!

I feel like suciciding now. Any ideas guys?


UPDATE: PROBLEM SOLVED AT THE END OF THE THReAD
 
Last edited:
wish i can dive into vegas to help out but mine started crashing non-stop like it has some kind of stability expiration date.

try loading the clips from a different location.
 
Wow multiple backups of assets and project files and still the same problem...

Maybe try re-installing vegas ?

Did you update vegas recently ? Maybe try rolling back to older version of 10 ? Do both computers you tested have the same version of vegas installed ?
 
does Vegas handle R3D's differently then other formats? maybe a reference file was deleted from the file system?
 
Vegas creates files to store the R3d metadata when you perform a change in the file (like white balance). BUt that does not affect the TC. And it couldn´t have happened with the back up HDDs too!
 
This is likely a longshot, but try opening the veg.bak file. If it was saved before the problem happened, it might put everything back right.

It looks like whatever happened was saved into the .veg file. Why this would happen, I don't know. The only similar problem I've encountered was with Raylight, and it happens with P2/MXF audio -- but it always clears up when you close and restart.
 
But Jim, opening any previous saved project file before the error happened also show the problem. Even backed up copies of the entire project in a completely different hard drive with files shows the same problem.
 
Like I said, it was a longshot.

If you use a slip edit to put one of the clips back right and then save the project to a new .veg file, does the new file keep your correction?
 
Hey Macgregor,

I had a problem like this once when conforming a film.
I think the problem is related to the .RMD (metadata) file not updating TC correctly.
I had this problem particularly when multiple pieces timecode in a sequence
referenced the same clip.

I'm not sure of the specifics of how your editing but if you remove your existing
.RMD file from the problem clips (don't delete the original of course) and force
the creation of a new .RMD file this may fix things.

Brian Timmons
BRITIM/MEDIA
 
THanks but it doesn´t help.
THe R3Ds are not particularly long.
I´ve moved a couple project files (version 22 and version 14, saved months apart) and one of the "corrup" R3Ds into a new folder. Nothing else. Then I open the file, skip all the missing files and there you go, the clip shows footage that is off.

This makes no sense. I could understand the R3D is corrupted somehow, but the backup copies show the same thing. I´ve been editing with these files for over a year so far, and this problem occured from night to day. Nothing crashed. Nothing was broken.
 
move only the R3D's and project files to an external drive and open the project on a different machine if possible.
 
Sorry, this probably won't be much help, but I had this same exact problem on Vegas 9 with Cineform files several months ago. It only affected clips on one track, but each of the cuts were at the beginning of each clip instead of where I had cut/trimmed them. I pretty much tried every suggestion in this thread to no avail. Also viewing the Event Edit Details corresponded to the glitched cuts so exporting an EDL would have still retained the problem.

In the end, I just decided to start over from scratch, but saved very frequently and cycled through 4 different file saves to try to ensure I had a recent backup (aside from the auto) in case the problem reoccurred. It never did and I still don't know what caused it, but I always make sure to create a bunch of backups and save more frequently now.
 
well if you have to start over, dont do it in vegas.. feel ya on this one.. did you try the sony vegas forums for help?
 
Last edited:
Problem solved!!!!

I just found out the issue. Vegas has a nice feature that lets us save a project with "copy media with project". And it doesn´t work well with R3Ds that have been split by the RED ONE. R3D files can´t be larger than 2GB so when shooting long takes, the camera splits the file into sequential files (take1_001.R3D, take1_002.R3D and so on). But once you drop file_001.R3D in the timeline it´s recognized as 1 single file and uses all the sequential parts.

When Vegas copies the media with the project it only copies the part it needs for the project BUT it seems the TC is then affected if not all the R3D parts are present.

Therefore I had to manually copy those files that were spit. Luckily it was only 2 and took me 20 seconds. Problem solved.

I guess i should email Sony so they fix this in the future, but I´m a lazy guy... ;D
 
You must log in or register to reply here.
Back
Top