Good news indeed. It also demonstrates a serious commitment to the entire customer base, current and future.

Gents,

Could you provide some 'small' test files (particularly VFW:- UT & HuffYUV via WeTransfer - send to This e-mail address is being protected from spambots. You need JavaScript enabled to view it *add a note to say what the file is for and who you are.

We've tested Lagarith CODEC in the new 11.0.2 (internal) build and it's working fine.

Many Thanks.

I am sending up 2 sets of: FFVH, ULRG, ULY0, ULY2. One set is CGI,the other live action. The CGI stuff looks better in these formats.

I hope to have them all uploaded by the end of the weekend.

Is there something else I can do?

Is there any chance that M-JPEG support will be re-added in addition to what you've already mentioned? I'm in the same boat as the OP, but unlike him RTV1 has been giving me issues and because of it my day became a search for workarounds to make other workarounds work to make other workarounds work

There are so many AVI codecs that it will probably be impossible for the devs to test every one of them. With Lightworks now using the MainConcept directshow subsystem, what it should do is first check the fourcc of the codec to block those that are proprietary that need a license for professional use, and if it's not one of those, then simply use the default directshow process for VFW support by adding the File Source and AVI Splitter filters to the directshow graph and let directshow connect the required codec filter to Lightworks' MainConcept rendering filter. This would allow any VFW codec a user has installed on his computer, except the proprietary ones, to be imported into Lightworks. Since there is such a huge number of open source or freely available VFW codecs, I think hard coding a list of those to block would be easier to maintain than a list of codecs to allow, unless you only want to allow a small number of tested ones.

I don't know anything about the internal workings of the MainConcept subsystem so I'm not certain it could work this way, but a possible problem might be the color space conversion pixel shader that Lightworks uses on imported files. The MainConcept subsystem must pass to Lightworks which color space a video file is that's being imported so it can generate the correct conversion shader that's contained in the ColourConvert.fx file in the Shaders folder in the installation directory. If it gets it wrong it ends up as black video.

If any of you folks have animation, I'd pick one of those codecs that you like and send a clip up. It's a good opportunity to show the good people at Lightworks what your preferences are. Gameplay, animation, slideshow, computer generated art,...