Tim Kolb
Forum Replies Created
-
ProRes encode is still the sole providence of FCP and AJA’s KI Pro HDSDI-fed recorder products (limited to FCP installs on Mac as well).
Of course ProRes can be played back and used as source material in anything as long as QT is installed on Mac or Windows.
TimK,
Director, Consultant
Kolb Productions, -
Unfortunately it’s not terribly useful to check the asset properties in PPro, it says that everything is “8 bit” in the “properties” (it’s a bug in the software).
Bridge might be a better place to check it.
TimK,
Director, Consultant
Kolb Productions, -
What you want is an effect called “calculations” in CS3.
PS transfer modes are in there.
TimK,
Director, Consultant
Kolb Productions, -
[Ann Bens] “This might help:
https://tv.adobe.com/watch/learn-premiere-pro-cs5/using-final-cut-pro-with-a...”Joost’s video is good for transferring project files, but the media assets have to be readable by both applications. DV in an AVI or QT wrapper moves back and forth pretty easily. HDV after it’s been captured and re-wrapped by FCP doesn’t…
TimK,
Director, Consultant
Kolb Productions, -
Part of the issue is the resolution you chose isn’t the resolution of any video format save the stored DVCProHD codec, which isn’t square pixel (PAR 1.0) and isn’t interlaced (no fields).
No clip ultimately bound for computer play back should have “fields” as computers don’t do interlaced…you should always export as progressive.
Also, if you want to use 720×480 DV next time, the Power Point presentation would need to be exported (as slides or however you did it) as 640×480…or 720×540 square pixel so you can work with it.
However, WMV files are still better than DV for playout from PPT as Vince said. Power Point is pretty clutsy as a video viewing application and the smaller the data rate, the better.
TimK,
Director, Consultant
Kolb Productions, -
It sounds like something was wrong with those files that you added to the project and the sequence became corrupted.
TimK,
Director, Consultant
Kolb Productions, -
[Vince Becquiot] “It should however improve the latter with timelines that are effects heavy.”
Agreed.
On a timeline that isn’t full of CUDA enabled effects, the encode difference may not be that remarkable.
(In the top of the effects panel, click on the little lego block-like thing that has an arrow on it and says “Accelerated effects” when you roll over it. This will show you the effects in the system that CUDA will accelerate.)
TimK,
Director, Consultant
Kolb Productions, -
Are you sure the server is blameless?
The transfer to the local drive could have been affected by a server anomally…
It seems odd that it would cross projects…and drives… These alternate projects you tried… They have no media in common?
TimK,
Director, Consultant
Kolb Productions, -
Unfortunately FCP has a rewrap process that is unique to FCP in that Apple saw fit to only include the decoder for that particular file structure with FCP. It is (along with several other FCP edit codecs that Apple has decided to only include with FCP), not included with the standalone QT package for Windows…OR Mac.
The footage could be exported to ProRes (the decoder is included in QT Pro for Mac/Win) or if a 9x data size difference doesn’t work for your situation, the footage should be recaptured as actual HDV native…
Perhaps your friend could rent a camcorder to recapture?
TimK,
Director, Consultant
Kolb Productions, -
I think that people may expect CUDA to have more impact in decode/encode functions than it’s currently designed for… These functtions remain cpu based, the Premiere Pro CUDA payoff comes in executing effects previews.
TimK,
Director, Consultant
Kolb Productions,