You should also pay attention to the moire issue (sensor line skipping) with the Canons wish doesn't exist on the GH1/GH2.
prolost.com/blog/2009/12/3/you-didnt-believe-me.html
www.dvinfo.net/forum/photo-hd-video-d-slr-others/501209-so-canon-60d-panasonic-gh2.html

Yes, that is a problem with almost all DSLR cameras, not only Canon. It's just more or less visible. There is a workaround for the 600D - just use the 3x digital zoom to get rid of it and always use 1080p resolution, never 720p.

The digital zoom is not a computed zoom, it is a real zoom using the inner part of the huge sensor. The moire is then gone almost completely and no antialiasing artefacts if you use 1080p. Of course you must play with the focal lenght to compensate.

Back to topic:

Most, but not all, of my files have AVCHD with AC3 audio tracks, so I will have to wait for the update. Fortunately my EOS600D files import nicely with (PCM) audio.

I am very impressed about the responsiveness of the software and Lightworks in general. It's a pleasure working with it so far.

Only a week ago I would have invested real money (that's a lot more than 60 bucks!) into LW, opportunity given. Now after struggling with LW v11 Free for a week, I decided otherwise. A thank you to all those who suggested workarounds for AVCHD files. Unfortunately they all result in unduly large file sizes. This is the point where I would abandon the works - altogether, and return to Edius 6. Yet, my preference of the LW work space, made me reconsider. LW v11 will be temporarily shelved in the Unused file until AVCHD works natively, with AC-3 audio, in the Pro version. In the meantime I shall return to LW beta, including the Matrox codec & Edius 6. I shall monitor this forum from time to time. I will likely purchase Pro upgrade plus keyboard as soon as you guys convince me that AVCHD incl. AC-3 works on Import as well as on Export.

Administrator: May I suggest that you introduce a feature in the forum that makes it obvious whether a new entry is by a Pro user, or alternatively, a Free user? It would help users to compare as well as to determine whether suggested solutions may be applicable. Prethnx

jacquestoo said:

We were thinking along similar lines. This is a good idea.

BTW - we're working all the time to optimise our codec support. You may not think it from some of the responses on the forum but we believe we have chosen the right framework, and it will allow us to provide similar (very comprehensive) codec support across Windows, Linux and OS X.

Optimising all the codecs is a big task and we're not quite finished yet: hence some rough edges. But we are making good progress and you'll see the results over the coming weeks. Yes, please keep checking back!

mediaDS wrote:



I also have the Canon 600D (Actually the T3i model as I am in the US, but it's the same camera) and noticed your post that the files import nicely with (PCM) audio. Are you importing them natively, or transcoding on import in order to get the files to work? I am still having to transcode on import in order to use mine. I am looking forward to the day when I will not have to transcode or convert the files to use them.

Please let us know!
Ken

Hi Ken

I import the files directly without any transcoding. Plays perfectly and no problems editing them so far.

cheers

Dieter