Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
Please, support PV!
It allows to keep PV going, with more focus towards AI, but keeping be one of the few truly independent places.
Convert GH2-files before editing
  • 58 Replies sorted by
  • StylzStylz

    @thepalalias--hmm, I do need a faster system and hard drive though. It's just that my dnxhd converted files are much bigger than the mts ones I transcode from, yet they play much smoother. Most people tend to transcode in cs6 for that reason specifically(or because of grading), but boy do I dream of a system that will allow me to eliminate that whole process entirely.

  • vstardustvstardust

    (Wrong topic)

  • itimjimitimjim

    @Stylz more importantly, I find that footage upconverted to ProRes 422 HQ through 5DtoRGB is better quality than how Premiere/AE natively interprets the MTS files. That and it handles them faster, especially in AE.

  • nomadnomad

    Plus, you avoid the "digital rain" effect.

  • actact

    I use last two month Brorsoft MTS Converter to convert MTS to Avid DNxHD mov. Very cheep, you can try demo version first. It use CUDA engine of NVIDIA graphic card. It save me lot of time convert at Adobe Media Encoder (PC with unsupported by Adobe Mercury Cuda video card) or Carbon Coder.

  • nomadnomad

    Did you have files with "digital rain" when played natively in Premiere? Does it fix that?

  • omnidecayomnidecay

    I hate quicktime due to their stupid gamma shift shit. I use a combo of HQX from grass vally (edius), UT, and native AVCHD. With this combo there are actually a few different workflows that I like:

    • Benefits of each codec - Grass Vally HQX : Everything is in 10bit 4:2:2 so you get out of 8bit 420 hell. This is like prores422 UT: Has 8it 4444 with alpha (RGBA). Its 8bit so you down res a little if coming from HQX 10bit 444 AVCHD: native codec, smaller, makes editing super easy, only transcode once to finishing 444

    Workflow A

    1. Convert to a high res 444 codec and place the footage in a separate bin
    2. Edit the native .mts files till picture lock
    3. Relink all clips in the timeline from the AVCHD to high res capture codec

    Workflow B

    1. Convert to 10bit 422 codec and use this to edit
    2. Export to high res 4444 codec for grading/color correction

    Side Notes

    • When you install HQX codec you do get a canopus lossless codec but its 8bit. the HQX codecs are the only 10bit codecs from grass vally.
    • You have more control over HQX codecs then the others. You get two slider options (Q and Size) that allow you to really fine tune your compression level. Q = amount of compression, Size = bitrate. I will typically leave it on the super fine option and call it good.
    • UT comes with 4 codecs: 420, 422, 444, 4444 (444 with alpha) all at 8bits.

    HQX Whitepaper: http://www.grassvalley.com/docs/WhitePapers/professional/GV-4097M_HQX_Whitepaper.pdf

    UT Codec: http://www.videohelp.com/tools/Ut-Video-Codec-Suite

    Edit: I forgot, I use Premiere Pro CS6 and Media Encoder.

  • SunscreenSunscreen

    I'm on a Macbook pro4.1 (2.5GHz intel duo-core, 3 GB of Ram, NVIDIA Ge Force 8600 GT)

    I use MPEG Streamclip to transcode my .MTS files & despite getting the "unrecognized media" error from MPEG Streamclip upon importing my .MTS files to the batch ... My .MTS files transcode to an apple intermediate codec flawlessly. No gamma shift issues.

    I'm currently cutting with FCP 5.1.4; compositing with After Effects CS4; exporting using compressor; authoring using Encore CS4.

    I'm currently saving up for an Edius Workstation. That way I can skip the entire transcoding headache & get down to cutting.

    I hope this workflow helps anyone running with an older system similar to mine. Cheers!

Add a Comment