The other main benefit of GearShift is that in addition to extracting the m2t files and converting them to proxies, GearShift can also act as a batch converter to the CineForm codec, 4:2:2 YUV, or other codec/template that you choose, keeping the original filename and allowing you to shift back and forth between both those formats, or even just the original m2t format. If you have a slower computer, GearShift allows you to convert the m2t to a DV proxy that you can replace with the m2t's for final render back to DVD, which saves tremendous time when going to DVD, and keeps the files in the 4:2:0 colorspace the entire time, while allowing you to edit in a fast, easy format.
CineForm is a tremendous tool, but if you'd rather spend 25.00 vs 199.00, you more or less get the same result, albeit that the CineForm tool is a little faster.

Thanks for the prompt reply, gentlemen.


DSE,

You mentioned that going to 60p and then going to 24 p is better if you're working with higher resolution formats when you were in Atlanta. I can't figure out your workflow, could you explain?

Is this something that only Ultimate S or GearShift can do?

Thanks!

Be aware, that Vegas crashes if you go above a number of 60 m2t files in the timeline - paging file becomes to huge. That is a clear limitation of Vegas at the moment - and Sony recommends to work with Cineform Intermediates due to that limitation.

However, you can also work with original m2t footprint material. But then you have to organize your workflow in a way, where you work with a smaller number of m2t filts - capture longer pieces (so about 20 or 30 minutes a piece). Render that to proxy files in Gearshfit, edit your project. And for the final rendering swap back to the m2t files, and render your video.

Be aware of cluttering up your computer and loosing time. If you capture your m2t files with the Vegas6 utility, as you would if using GearShift ( a great script, not a utility program), unless you stop and start your camera in a linear edit like mode, to break up your footage into wanted or discarded segments, you will get one huge m2t file that you must keep on your system until the job is done, even if only small segments of that file will eventually be in your project. Cineform, if working right and if your computer is up to the job, will scene detect alowing you to discard unwanted scenes and allowing you to cut scene by scene and then discarding the unwanted cut original footage. So Cineform is much more efficient with HD usage. Also as the render compression is done at the time of capture there is no waiting on the massive renders needed when using the Vegas6 intermeadiaries whether from within Vegas itself or when using the GearShift script.

There is a cheaper - and similar - way if you wish to work with Cineform Intermediates:

- capture your m2t footage
- convert it to cineform intermediates (within Vegas-6)
- import that file in the freeware tool AV-Cutty, and apply an optical scene seperation
- export for each scene a cineform file from AV-Cutty
- import that into Vegas6 again
- delete the m2t footage if you wish to render from cineform intermediates to your final video

It takes longer, since you have to render the cineform intermediate after capturing in a separate step. The export from AV-Cutty does not render the file, so you do not loose quality due to that.

You find AV-Cutty here:

http://www.avcutty.de/english/index.htm

Wolfgang, be on the lookout for a new version of GearShift very soon. Free upgrade for those that already own GearShift, it will provide a few more time-saving alternatives, based in no small part on your constant and very useful feedback.

And one further point from me. Many V6 editirs I've noticed think you have to use Cineform or a Vegas6 intermeadiary (either from within Vegas6 or with GearShift). If you have an up-to-date regular computer - nothing high powered - just a current P4 3.2GH you can edit in Vegas6 very efficiently and with great results editing the native HDV. Since I decided Cineform was not worth the money and before I got GearShift I did just that and while monitoring may be frustrationg because of the low frame rate (usually 12fps to 5 fps during a transistion) it works just fine and is MUCH MUCH quicker than Cineform or an intermeadiary as there is no preliminary rendering and a very quick final redering, and uses no extra HD space over and above your original footage.

@ Douglas,

thank you for your kind words - and yes, I am keen to see the new Gearshift.


@ MH Stevens,

I have also a P4 3.2 Ghz, 1 GB Ram and a raid-5. So very similar pc-performance. But I think that you and I are both aware of the limitations to work with native m2t footage in the timeline.

Preview capabilities with such a machine is about what you have mentioned - 10 to 15 fps in according to my experience, but without any effects, so only original footage. And not at the highest preview quality. How do you evaluate complex things, like PiP Effects? To my opinion: either you apply RAM preview - what takes also time during editing. Or you can forget it. At least, as long as you do not apply either cineform or other proxys (DV, mjpeg, whatever).

The other constrain is the low limitation of m2t files, that Vegas is able to handle at the moment. 60 files is nothing, if I compare that with my typical projects in SD - where I have maybe up to 400 or 500 DV-avi files, from automatical scene separation. But fair enough to state: this limitation is valid for a workflow based on Gearshift and proxys, where you swap back to m2t material, too.

As long as you wish to render to your final product from original m2t footage, there is third limitation: we have no automatical scene separation for m2t footage at the moment at all. That brings up disadvantages for people, who wish to apply a workflow based on single scenes. Yes, there are workarounds: either you purchase the Cineform tool - or you work with AV-cutty based on Cineform intermediats. Or you work with Gearshift, render to proxys, make a scene separation in AV-Cutty for the proxys - and export an EDL List from Gearshift back to Vegas; group audio and video with a small script, that Johnny has developed; edit the project in Vegas; swap back to native m2t material after cutting, and render from m2t material your final video.

Both, proxys and intermediates, are not for free: you need additional harddisk space, you need time to render to proxys/intermediates. And it takes additional time, whatever workflow you prefer now. But in both cases you have additional preview capabilities, that is required for cutting in a typical project anyway.

In the future - when we will have dual- or quatro core machines, and maybe with Vegas7 where Sony have overcome the 60-file-m2t limit, and when we will have an automatical scene seperation for m2t too, maybe then a workflow will be sound, based on native editing of m2t in the timeline for huge projects too. But given the actual PC performance, given the actual product development of Vegas, I prefer a workflow based on proxys and Gearshift, allowing me to edit with a good preview capability, and based to render original m2t footage directly to the final video at the end of the process.

Wolfgan:
All methods have trade-offs - I only wished to point out that native HDV editing is possible with moderate power computing. Given a good HD setup (big RAIDs) and some wait time (overnight) then GearShift IS the best way for easy and pleasing preview.

No, if you have a RAID and a fast computer, GearShift is a somewhat unnecessary tool. You might as well just convert to 4:2:2 or Cineform directly from that point. GearShift's main value is in converting m2t to CineForm or proxy, or both, for people who have slower systems. Editing m2t is painful, period. If you're happy doing it, bless you. Most folks aren't, and won't be. Not to mention that most systems that are slower are substantially crash-prone when the processor is running at 100% while it decodes and re-draws the file, hence the value of editing with a proxy. This is how we used to have to do it in the "old days" and while it's definitely not the best scenario, many people don't have the best computers. But as I mentioned, if you're OK with editing m2t, that's good for you. Also realize that you get one render with it, that's it. That said, DV proxies and/or 4:2:2 YUV aren't for everyone either.
Whatever works for you, that's all that really matters.