Bill Buchanan
Forum Replies Created
-
Vince
“20 C” Are you certain that’s correct? 20C is 68F. I run that processor overclocked to 3gb with a Zalman fan, and at idle it runs about 90F. When rendering mpg2 (for DVD generation), it gets up to about 120F.
Bill Buchanan
Buchanan Film Co -
Since setting up the monitor for serious color/brightness/contrast,etc. correction is extremely limited with a consumer set, you should not use the monitor you mentioned for those critical functions if the work you’re doing is to meet professional standards. That said, your monitor should suffice for editing/sfx work.
Bill Buchanan
Buchanan Film Co -
Alex:
It’s true! With few exceptions every former commercial director screws up at least their first feature by cutting them like they’re a two-hour spot. Bay’s Armageddon is almost impossible to watch. In an interview given around the time of its release, Bay announced, “Not one shot is on the screen more than 2 and a half seconds.”
Not to put myself on his level, but as a former spot director my first several corporate-sponsored documentaries had so many gratuitous cuts I can’t stand to watch them.
Bill Buchanan
Buchanan Film Co -
You misunderstood what I wrote. Those “over 5,000 clips” were shots I had digitized from over 75 hours of footage. I didn’t have 5,000 shots on the timeline; they were in the bins. Even Michael Bay would have a hard time making a film with that many cuts in it.
I have over 4TB in a Raid 5, which of course has no bearing whatsoever on PPro. PPro doesn’t know or care what kind of storage the sys has. It’s only concerned with the data in that storage and its throughput speed as it relates to a particular project. PPro had no problems whatsoever accounting for all those shots/pointers, nor any problem with however many shots/scenes ended up on the timeline. It started choking when various effects/keyframes, etc. are added to video and audio, which apparently requires much more memory than the pointers in the bins or on the timeline.
Before I broke the project into 6 parts, it took about 7 to 8 minutes to load. The project file was about 143mb. Later after each part had undergone all the finishing processes, each one required about 3-4 minutes to load.
X64, as I said, handled the separate parts better than the 32-bit side of my sys.
Bill Buchanan
Buchanan Film Co -
Vinny
Sorry if I hurt your feelings and/or diminished your sense of self-importance. Working with projects that require only “120 clips” is nothing for which you should feel ashamed or fear being perceived as an aspiring home-movie maker. Regarding your “take” on my situation, you are wrong on all accounts.
Let me try to do a better job of conceptualizing this for you by putting it in context. I just finished a 90 min doc with over 5,000 NTSC uncompressed clips in the library, which as you may have read is not uncommon. Using PPro2, I rough cut the show without breaking it up. I broke it up into 6 parts only when I began to color correct, add video and audio effects, etc., which as you may have also read builds up the size of the project file and its memory requirements dramatically. The /3gb switch was necessarily enabled from the outset.
I used WinXP X64 to finish the more complex parts. Though Adobe does not officially support X64 for PPro, it works like a charm, but for a few annoying quirks.
Smoke is a facility-oriented app as you may have also read and expensive as hell. In my view not the sort of app most independent cutters working in long-form would opt for for any number of reasons, not the least of which is its cost and the time required to recoup the investment. I considered it long ago along with all the other so-called pro-level NLEs. I choose PPro based on its affordability, features and the Adobe name, believing it could handle long-form projects as well or better than the others in its class. Needless to say, I was partially wrong.
Bill Buchanan
Buchanan Film Co -
“…120 clips…” I don’t believe that constitutes a “large project” as described by Jack Kelly. When project files get into the 30 to 100 or more meg range, with thousands of clips, lots of video and audio effects, etc., things tend to go haywire in a hurry with PPro. I’m still on PPro 2, because apparently the well-documented memory issues with PPro were not entirely addressed in CS3, though some have stated they were. I’ve found editing large projects on the XP 64 side of my dual-boot box a bit easier, though not without problems. There seems to be a concensus among pro users that PPro is not the way to go for long-form work involving thousands of clips, etc.
Bill Buchanan
Buchanan Film Co.Bill Buchanan
Buchanan Film Co -
You’ll have to use an auto-save version assuming you didn’t have autosaved disabled. Very important to save backup copies of your projects (on different drives} several times a day. Murphy lives and will get you sooner or later if you don’t. Hope he hasn’t already.
Bill Buchanan
Buchanan Film Co.Bill Buchanan
Buchanan Film Co -
I’m running a dual-boot sys–xp32 and xp64, using an decklink hd extreme, intel core duo, and a quadro 1500. Sys works like a charm on both sides. I use the x64 side primarily for editing (PPro 2) (large projects with 1000s of clips) and the xp32 side for rendering, etc.
I’ve done very little with AE on either side, but I know it works well on the xp32 side and suspect it will with xp64, since PPro 2 does.
Bill Buchanan
Buchanan Film Co. -
Look in your project bin(s) and see if there’s a “Sequence” hiding somewhere. If so, double-click on it and see if that opens your missing timeline. Please post the results as I am considering upgrading and bringing a PPro v2 project into it.
Bill Buchanan
Buchanan Film Co. -
Thanks, Aanarav. No. It’s a 10-bit uncompressed NTSC SD project. Same as the v1.5 project into v2.
Bill Buchanan
Buchanan Film Co.