Videomaker – Learn video production and editing, camera reviews › Forums › General › Video and Film Discussion › Convert AVCHD to DV-AVI for editing? › Birdcat, On my HMC150, if
On my HMC150, if I import the entire folder of AVCHD files, it should import the metadata as well which includes MXF files (and tells where to span the video files from one to the other). When I do this, I have no gap in Audio or Video. However, if I simply import the clips from the clip folder, I have to merge them separately and do experience a little gap in the Audio and Video.
One thing I think is important to remember about AVCHD and it being compressed is that Color tweaking in Post is more limited than uncompressed footage. Those who are used to the feature coming from DV SD footage may be sorely disappointed. When you shoot with AVCHD, it is ultra important to get the shot right.
In terms of the Adobe suite, I started with CS4 shortly after purchasing my HMC150 a little over two years ago. version 4 was glitchy when working with AVCHD natively and I often experienced freezes and hangups.. However, when 4.1 update was released, most of these problems went away for me. I was sorely disappointed with the performance of 4.0 and even made calls to my camera vendor (Who in turn put me in touch with the Panasonic rep who in turn put me in contact with a developer from Adobe). He is the one who pushed me to do the update to 4.1 and I was absolutely ecstatic with the results. Granted, I was using a Core I7 920 with 6 Gig of RAM at the time.
When CS5 came out, I took the plunge and upgraded. I also upgraded to 12 Gig of RAM as well as got myself a Nvidia GTX285. The results for native editing were indeed astounding. I am able to apply many transitions and filters and am able to preview them without having to render first and this saves me much time. However, when it comes time to transcode to a different format for output (Through Media Encoder), This is where time is not saved, It still has to decompress the AVCHD footage and in turn, causes longer transcoding times. Because of the nature of GPU processing (it could be described as “Quick and dirty” in terms of video rendering), it works for preview but actual transcoding is done by the computer processor.
Still, with mercury, time is saved by not having to transcode to edit easily. It truly is convenient and though I still have long transcoding at the end, It really does make my workflow easier because I don’t have as many “Intermediary transcoding” when applying filters or transitions to see how they look. not only, Mercury makes it much easier to do PIP editing with AVCHD because it pretty much emulates the look on the fly (Again without having to render an edit to see how it looks).
I also work with Final Cut Pro at work and though all AVCHD is logged and transferred into the Pro Res medium, it seems to be a much quicker procedure of transcoding with less processing power. The only disadvantage is that the transcoded footage is about 3 to 4 times larger in file size than the AVCHD footage. Maintaining a larger data drive will be important for project performance and management.
All in all, one thing I often see overlooked in terms of Video editing performance on a PC is “dealing with Fragmentation”. Before I do a long transcode, I always defragment the drive first. Severe fragmentation from copy large files here and there severely slows performance when it comes to transcoding large files. To ensure quick transcoding, I always suggest defragmenting before you perform the transcode (or even render).
I did, as a precautionary measure, purchase Cineform and sometimes do use it (especially when combining footage from my HMC150, HMC40 and my 5d MK II). It just keeps everything in the same preset workflow and makes things much smoother. Other times, I will just simply edit the AVCHD footage natively.
Hope this wasn’t too much for my first post!