Tim Kolb
Forum Replies Created
-
Premiere Pro CS5 does DPX sequences…FCP doesn’t do DPX sequences, but I believe that Color does directly…
TimK,
Director, Consultant
Kolb Productions, -
[Kirk Swann] “Thanks for the help thinking out loud.”
No slight was meant…I was just sort of talking it through myself…and i guess, typing.
TimK,
Director, Consultant
Kolb Productions, -
[David Dobson] “The main problem I have with DSLR projects though is that the audio comes in separately (from another source) and syncing it leaves you with sequences and not master clips and editing from sequences into sequences, not something I have done much of, is a real pain.”
This workflow has been on the radar for Adobe, as most user requests are…although I know they aren’t oblivious to dual system sound workflows as if they want PPro to move into higher-end parts of the business, it’s important.
I don’t work with documentaries and I guess when I launch the app, I’m doing lots of other things so I guess I don’t time it…though as I said, I only occasionally run into projects with 10 hours of media or more.
I had the last one in house when CS5 was released. It was XDcamEX footage…about 17 hours worth. 8 sequences with selects as it was all interviews…I don’t really recall it being remarkably slow to load, though PPro does traditionally take a bit longer than some other apps, but I’m not a programmer or software engineer, so I have no technical insight on it.
I do know that I think I’ve froze PPro CS5 on Win 7 64 a grand total of about 3 times since release.
So…I suppose taking a bit to load isn’t as big a deal to me if I only have to do it once at the beginning of the session…
TimK,
Director, Consultant
Kolb Productions, -
It looks like it’s the FCP HDV rewrap… Isn’t AiC an I-Frame codec?
I think that this (along with the DVCProHD QT codec) is providence of FCP alone.
I’d second the ProRes suggestion…
TimK,
Director, Consultant
Kolb Productions, -
It certainly sounds odd…
What’s been changed on your system lately?
These drives have been used before…and they’ve had times when they’ve had more data on them than they do currently?
Have you taken any sort of disk maintenance measures? (Transfer the data off and re-format the drive in case there’s a strange file fragment that is haunting it or something silly like that…)
TimK,
Director, Consultant
Kolb Productions, -
Where is your scratch drive set?
A large export will create temporary data on a drive (usually the system drive) during the process.
Can you watch all your drives during export and see which one is filling up?
The other thing is the external drive itself…where is it from? Did you format it? If you’re on Windows and it’s formatted as FAT 32, your filesize will be limited to 2 or 4 Gigs (also true for any scratch drive…the drive doesn’t fill, but the file goes over the max size…)
TimK,
Director, Consultant
Kolb Productions, -
That is strange.
I’m doing a project on CS5 now with primarily ProRes HQ footage and it runs without issue.
A display card won’t help you decode video…it can help preview effects.
I wonder if CS5 being a 64 bit app has something to do with it? QT is still 32 bit, even in some QTX processes it falls back on QT 7.x… On Windows Adobe had to write their own QuickTime server application to get around the 32 bit limitation of QT, but I suppose Apple is less interested in allowing that sort of workaround in OSX.
It still seems strange to me…
TimK,
Director, Consultant
Kolb Productions, -
Well…I think some of this is relative.
Can you do it? Probably so…
Would I recommend a single socket quad core for H264 DSLR footage?…
Hmmm…not if you are expecting Final Cut Studio with ProRes performance…
TimK,
Director, Consultant
Kolb Productions, -
That is a tough question to answer knowing that answering it wrong could wreck your world for a project…
I’ll say this:
Factual:
Dslr footage is a handful and PPro CS5 can handle it, but the system you run on HAS to be a monster to make it work. Staying native will help by reducing the necessary drive speed and capacity, but you’d need a. Dual Quad-Core Intel with multithreading to make it seem responsive for a long form project IMO. Not to mention that 16GB or RAM should be considered minimum. PPro has the capability, but the hardware needs to supply the torque.
Anecdotal:
In my personal experience talking with users, PPro CS5 seems to give Mac users more quirks than Windows users… I’m probably going to get beat up on that one, but it’s just something I perceive (perhaps ultimately incorrectly) from my interactions with users… QuickTime is a limitation these days and I know that CS5 being 64 bit and the enduring dependence on QT 7.x codecs, even running under QTX remains a hurdle.
I won’t touch any Apple vs Adobe feud issues as I think both sides have their plans and they don’t necessarily face the same ultimate direction.
I guess I might ask a local reseller if they have a serial you could try PPro CS5 with on your system and test some dslr footage (no mpeg codecs are supported in the trial) and see how it works.
With native footage, there is an instant of “buffer” time when you hit the spacebar which I’ve heard some users say was enough to disrupt their flow. I haven’t found that ‘beat’ to be a problem myself, but I’m on Windows.
OK…maybe we can get some other opinions and experiences added here without having a flame war.
I think the key is to not respond to the question unless you’ve actually edited with PPro CS5 on a system that is actually spec’d to run it. Many users I’ve seen over the last handful of years seem to expect Quantel performance on machines designed for QuickBooks…
TimK,
Director, Consultant
Kolb Productions, -
Also keep in mind that a Media Encoder queue can include straight clips that need transcoding and AE comps as well as PPro sequences…
It all sounds a little elaborate until the day arrives when these capabilities allow you to go home and let the computer churn as opposed to staying late to type seven keystrokes every 60-90 minutes…
TimK,
Director, Consultant
Kolb Productions,