I was told recently that I should convert my video files to something else to improve rendering and exporting times. I shoot HDV, and recently started usung a DN60 for a tapeless workflow. I have CS6 and a reasonably fast computer.
I was under the impression that Premiere and AME handled HDV and all the other filetypes natively. Why then am I experiencing slow performance after all I have done to improve my system? What should I convert to? And wouldn't that be a time-consuming process in itself?
I continue to have problem after problem. As a future feature request, I would like to see a built-in troubleshooter for CS6 that would tell me where bottlenecks and other problems are in the system. I LOVE Adobe apps when everything is working, but unfortunately that is very seldom in my case.
My workflow consists of shooting HDV, ingesting M2t from DN60 or capturing from tape. Editing in Premiere, maybe some After Effects work for titles, etc, and on to Encore for DVD or AME for YouTube.
In this latest problem I'm having, AME is stuck for the past 30 minutes reading XMP trying to encode .h264 for YouTube.
You 1st thing you need to do is insure your sequence matches your video... which you will know when you put a video on the sequence timeline and there is NO red line over the timeline
Please NOTE that the PPro CS6 screen may look a bit different
For CS5 and later, the easy way to insure that your video and your project match
See 2nd post for picture of NEW ITEM process http://forums.adobe.com/thread/872666
percoplus wrote:
I was told recently that I should convert my video files to something else to improve rendering and exporting times. I shoot HDV, and recently started usung a DN60 for a tapeless workflow. I have CS6 and a reasonably fast computer.
I was under the impression that Premiere and AME handled HDV and all the other filetypes natively. Why then am I experiencing slow performance after all I have done to improve my system? What should I convert to? And wouldn't that be a time-consuming process in itself?
Long-GOP codecs are more CPU intensive, so yes, you will experience slowness you wouldn't with intraframe codecs, due to the CPU ops needed to render each frame to your display in real-time.
Yes, it will take time to transcode, and it will eat up drive space, but you may make up the lost time in the editorial process. My general rule is the shorter the project and less the footage, the more incentive to edit native. Otherwise, transcode.
My impression (not scientific) is that working on Long-GOP codecs is only going to be more painless on the fastest of multi-core systems. "Reasonably fast computer" may not be good enough. Try transcoding to AVI, Cineform, DNxHD or ProRes, and see for yourself what works best for you.
http://www.youtube.com/watch?v=BJLIwxaaiyA
You should watch this video because you should be able to edit multiple layers of native AVCHD and native HDV using a medicore Core i7 system or at least I can.
i'm on an i7 1155 system w 32 gb RAM 64 bit Windows 7, SSD system drive, RAID 0 drives for storage and previews. GTX 580 Amp! graphics. tuned up per Bill Gherke's instructions maybe
I understand that speed is subjective, and I am generally happy, but too often, these hangups negate whatever speed I have.
i would def like to see some kind of housekeeping function i n the CS to detect bottlenecks and config problems
North America
Europe, Middle East and Africa
Asia Pacific