[Al Bergstein]

Raphael, the clips that are MOV aren’t audio, their video. whenever I convert a clip in L&T I end up with MOV files. That’s how they are stored. I do shoot with both a 7D and a Panny HMC150. The 7D creates “native” mov files, but they are not drop in compatable with FCP. I run them through depressor first.

When I go to my “capture scratch” files, all my video and audio clips are mov, not just audio.

Alf

[Al Bergstein]

I agree with what Alan is saying across the board. In your neck of the woods you may have to play well with others, and if those others are using the tools you mention, then use them. I use Vegas a lot, it’s really fast for small jobs, but a lot of folks up here use FCP, so I have that too, and can work with them easily. There’s a lot right with the Mac OS for ease of use. Find the right tool for you and your workgroup, pay the price, and go earn the money to pay for it. All in all, a few days editing pays for most of our tools. That’s pretty sweet.

My personal opinion is that there is a lot difference between a person in Hollywood who is a head’s down 8 hour (or more) editor with a large budget to do things really state of the art, and someone like me doing small scale low budget jobs in the hinterlands. I don’t think I’ll ever want to pay for AVID and those much higher end tools, when I have tools that work for me. Where is Adobe trying to fit? Special effects and graphics specialists, Hollywood superproduction, high end prosumer? I think it’s special effects from what I’ve seen, leveraging AE & Illustrator. Apple is straddling high end prosumer and Hollywood wannabe’s, more into video than special effects. Vegas is squarely in the consumer up to prosumer market, given their easy upgrade path from consumer product. Am I wrong on these assumptions?

Alf

[Al Bergstein]

Thanks for the advice to all of you. You really are saying that the only data pointers of those files is the name of the hard drive? That copying all the files and renaming the hard drive does the job? Sheesh, that would save me time. But I agree with Jerry that checksumming the work is a good thing. Now some developer ought to get to work creating a tool that does just that. hmmm. I think that there are copy tools that do checksums… I’ll have to take a look.

Alf

[Al Bergstein]

Is there anything special about Animation rendering? There’s no documentation that I’m aware of on it…Just create my title sequence and render it in Animation?

Alf

[Al Bergstein]

Thanks for the thoughts, I’ll check out the article later in the evening…Only thing I can think of is that I added some stills I needed recently, but as you can see from the error message, it was a huge pile of files that had never given me problems in 10 months of editing, rediting etc. Only thread here is that I used MM to migrate them all to the external OWC drive. Must be something that FCP didn’t like. Maybe I’ll try posting on Apple’s support site and see what I get, or even send an email to Larry Jordan, who doesn’t seem to frequent the boards but has just about as encyclopedic a background as anyone.

Bottom line, like you both said, there was no problem with anything, so I’m ignoring it until I can’t. It may have something to do with shifting RT settings to do multiclip in another FCP project. It shouldn’t follow to another open project sequence, but who knows. At least by posting it with the screen shot, I hope to save someone else a bit of persperation when they come looking for an answer in the future. New drives, new problems…

I do wish there was an easy way to migrate everything FCP from one drive to another without going project by project. Just repoint scratch drives etc and let them rebuild over night… Or is there some tool to do that? I’ll re-ask in another post.

Alf

[Al Bergstein]

Ok. I decided to reinstall the NVIDIA software. That did the trick. My best guess is that I had only taken the default W7 NVIDEA drivers when I installed my card on this newer machine, (my HP motherboard fried after only one year in Dec), and had not tried Vegas since then (a few weeks back, and I had FCP to fall back onto). Boris tech support was very good, but we didn’t need to get into the depths of this. So the upshot is if you upgrade your computer but not your video card, make sure to get driver updates for the new machine. All appears well now, testing will continue.

Alf

[Al Bergstein]

Yes, I use two monitors. I’ll .intact support this morning.

Alf

[Al Bergstein]

Whether it matters, a Vegas error message that comes with it.
Extra Information
File: C:\Users\Al\AppData\Local\Sony\Vegas Pro\10.0\dx_video_grovel_x64.log
File: C:\Users\Al\AppData\Local\Sony\Vegas Pro\10.0\svfx_video_grovel_x64.log
File: C:\Users\Al\AppData\Local\Sony\Vegas Pro\10.0\dx_grovel_x64.log
File: C:\Users\Al\AppData\Local\Sony\Vegas Pro\10.0\vst_grovel.log

Problem Description
Application Name: Vegas Pro
Application Version: Version 10.0c (Build 470) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 10.0\vegas100.exe
Fault Address: 0x0000000000000000
Fault Offset: 0x0000000000000000

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 10.0\vegas100.exe
Process Version: Version 10.0c (Build 470) 64-bit
Process Description: Vegas Pro
Process Image Date: 2011-01-03 (Mon Jan 03) 17:40:24

I do have a crash dump (460 MBs or the like if you want it)

Alf

[Al Bergstein]

A problem you may run into is something that is hard to see. Be sure to try your output on both a flatscreen, which I assume you are going to be working on, and a video projector. I’ve had a hard time tweaking my latest 16 minute doc for proper color display on projectors, it *appears* there may be some odd lighting in some clips that cause wierd color shifts when moving to the projector (I’ve tried many projectors all with wildly different results, both high end and low end). The final project looks fine on display, just not projected. seems as though some things, like filtering for broadcast safe may be essential,and without using the color scopes, you just won’t see it and other problems.

So you might want to prepare for that eventuality and look at the clips a bit with a video projector to see if the lighting is well done (shot with a lot of controlled lights, not a lot of wild tungsten or flourescent filtering in to blend with daylight, etc.). If it’s not, you may be in for a lot longer grind… words to the wise…

I’ll probably spring for Walter’s DVD soon (G)…he seems to have spent some time doing this…I’d like to get a good solid indepth overview on color grading in general, as I find the scopes in other competing tools. Good luck!

Alf

[Al Bergstein]

Ok. Some thoughts. 32 bit caused me no end of grief on out of memory issues. I think this is your problem. If you HAVE to have your add ons in 32 bit, then you will likely continue with out of memory problems. I have not had an OOM problem in 64 bit windows 7. I had them with 32 bit.

I don’t totally agree with Stephen. Windows 7 is more stable and faster than Vista, but you MIGHT have to upgrade BIOS for it. I worked for a large OS company, and saw the BIOS changes that EVERY single OS upgrade brought. If your vendor recommends it DO IT. There is a reason. We were the beta pigs to learn this the hard way, and I lived through a huge number of blue screens waiting on companies like HP and Dell to get the BIOS upgrade done. It’s real. But if you aren’t experiencing Blue screens, then you might put it off. BIOS is there for a reason. It’s not just a bit of random code. It’s being superseded, but still might affect 32 bit versions of Windows. Go WIKI BIOS and read up on what it does. It’s not trivial. It helps drive compatibility from version to version of Windows.

Since you don’t always need the 32 add ons, run both versions of Vegas, and use 64 when you can. Let us know what happens.

Alf