Recapture
by Will Moffitt
on
Jun 20, 2006 at 5:52:56 am
I'm having trouble recapturing files with my VelocityQ. I orignally captured hours and hours of footage at low rez (17). Now I want to recapture a timeline at higher rez (40) and I'm having trouble. When I am done recapturing the whole timeline, the system crashes on exiting capture. If I try to recapture selected clips, it works fine, but often when I return to Velocity after having saved and exited and worked in other programs, I find that my recaptured clips are not recognized by the timeline. Database srew-up? They are on the hard drive in the recapture directory, but the origninal low rez clip has returned to the timeline.
What should I do? I have a 30 minute show that needs to go to TV stations at the end of this week.
And on a similar subject, what is the best drive situation today for a VelocityQ turnkey system. If I had had enough space to capture 40 hours of material at high rez in the first place I wouldn't be having these recapture problems.
Re: Recapture by mYthprod on Jun 20, 2006 at 10:37:50 pm
I'd get with tech support on this one. I'd hate to speculate on something that may be an easy answer for them, especially if you have a short fuse on this project. If you have the high-res clips on your drive you could try right-clicking on the clip and "replacing" them, I'm not sure if they'll keep their edits or not. I deal in short form work mostly so I don't have a need to recapture often, maybe someone else in here will chime in.
As far as large drives a lot are using SATA drives and hooking them onto the Q with a sata-to-scsi adapter. I don't use those but they're worth a look. The editors on dpsedits talk about them from time to time so a search would likely yield their 1-2 favorites. Seems like Wayland or Boyd might've had an opinion on that - could try searching their names or searching for the adapters or just do a google search and see what's out there. I rarely buy anything anymore without googling for reviews and user opinions. :-)
- MythProd
(John David Hutton)
Build Your Own VelocityQ. See how:
http://www.customflix.com/Store/ShowTtl.jsp?id=205835
_______________________________________
Supermicro X5DA8, Dual Xeon 3.0 GHz
Windows XP Pro, SP1
VelocityQ, Version 9.1.41, Quattrus 140
VelocityX, Version 1.0.01
Kansas City, Kansas - United States
_______________________________________
Re: Recapture by Chris Blair on May 30, 2008 at 2:18:42 am
Are you changing the default directory structure (and name) that Velocity is creating for you? If so, this will cause a crash. Let Velocity create it's new directories and LET it put the files where it wants. Replace will typically work.
A dirty little secret of the Velocity line is that batch recapture has never worked correctly. Not from their earliest versions of the product line (Perception RT) all the way up to VelocityHD.
It has to do with a fundamentally flawed treatment of timecode by the software and a lack of understanding of the purpose of timecode by their software people. Even if you get Velocity to capture then replace without crashing, many of your clips will replace with incorrect in/out points on the timeline. Some will only be off by 15 frames or so, but others can be off by several seconds. There's no consistency to the error. I've had long discussions with their software development people over the years as a beta tester about how timecode SHOULD be treated...which as an absolute time locator for each video/audio clip.
Their software people believed that timecode should ONLY be a reference to the in/out point that an editor creates within a timeline. Which meant that if you change the location of a clip on your drive, more often than not Velocity will lose track of the timecode within the clip itself and "reset" the clip back to it's beginning point. That means if you have a 20 minute clip and your in-point on the timeline is at timecode 19 minutes...then you move the clip to a different drive and re-associate or replace it on the same timeline, Velocity thinks it should "reset" the "in" point back to 0. So your clip would be off by 19 minutes! The crazy thing is that this doesn't ALWAYS occur. It seems that it happens more often with clips residing on tracks other than track 1.
I argued and pleaded with their development team (along with a few other long-time users) for years before finally giving up. They just didn't understand the point of timecode, which is to absolutely identify the location of a clip to within 1/30th of a second.
The best way to go from low-rez to high-rez is to delete your low-res footage (or off-load it to a back-up drive if you're a nervous nelly like me) then re-capture from your original batch capture lists to the higher resolution.
If drive space is an issue...then you're in for a long and painful trip.
Chris Blair
Magnetic Image, Inc.
Evansville, IN
www.videomi.com
