EDIT:

Sorry, please ignore the hint below. I have read up on it since i posted it. It might be in fact more vulnerable than the original Quicktime. According to WIKIPEDIA it's just a knock-off of Quicktime. In any event it hasn't been updated since 2010. I wasn't aware of these circumstances when I posted. Please forgive me. I hope my bad hint isn't causing anyone grief.

Hey get over it! I've been using Quicktime Alternative for years. It works perfectly well with Edius (all versions from 4 through , as well as DaVinci Resolve versions 12 and 12.5. I suggest you try it with Lwks. I don't see why it shouldn't work.

Over on the Avid forums there was some discussion about QTalt a few days back. The consensus there was that it wasn't a good idea either.

I also clearly remember that, back when I used 32 bit Lightworks, the QT player was not required.
The component required was called 'Apple Application Support' in Control Panel - Programs.
So after installing the full package (for whatever reason) one could easily uninstall the QuickTime player to comply to what is in the Reddit article, still being able to play back .mov containers in Lightworks.

On the other hand it would be interesting to know how many people really do use Lightworks in 32 bit mode still, and if so, why

Here's what I did, with all my machines:

1. Fully uninstalled QuickTime
2. Downloaded latest version of QT
3. Open installer. This will display "QuickTime for Windows" window > click NEXT
4. "License Agreement" window > click YES
5. "QuickTime 7 Setup" window > choose CUSTOM
6. "QuickTime 7 Product Feature" window > click on the "QuickTime Player" icon
7. Choose "Entire feature will be unavailable". This will leave a red X, both in "Quicktime Player" and "Optional QuickTime Features" > click NEXT
8. "QuickTime for Windows" > Uncheck "Automatically update QuickTime 7 and other Apple software" > click INSTALL

Make sure you uninstall the Apple updater. Sorry, to tell you, you'll loose your beloved Quicktime player. But wasn't this what we set out to achieve? I believe step 8 to be crucial, as we don't know what the thing might download. There's no advantage to an updater anyway, considering that there won't be any updates coming.
Hope this helps!

@timzett
eg. exporting codecs that just have an qt implementation in windows
still too many apps depend on qt ...
s

lghtwrks wrote:
I see. Well the alternative might be transcoding, with a probable drawback of quality degrade and additional time consumed.

E.g. MediaCoder should be one of the tools capable on such task, likely even with only remapping the content, thus preserving full image data.

... the prob is the _export_ codec for lwks32-bit/QT, eg. DNxHR, NewTek 444, aso ...

not to mention the java/QT implementations which many apps use ...

s

For the QuickTime issue AVID has posted this for their users:

QuickTime Support and Security on Windows

I think the sanest advice from AVID is:

"Q: What is the risk of not removing QuickTime from a Windows system?

A: As of this posting, Avid is aware of no confirmed security risks regarding QuickTime on Windows systems. Users should be cautious when downloading QuickTime files from the internet to ensure they are not downloading files with malicious code. Users should always only download files from known, trusted sources. Simply browsing the internet or using QuickTime files that have not been downloaded from the internet or other unknown sources should not pose a security threat. "

I guess it's immodest to quote oneself but what the heck - post #112752

If you click on the link submitted by @briandrys, you'll notice that Avid's suggestion is 100% congruent with mine, dating several days back. (See my post, above in this thread).

I was going to say what AVID said but I was waiting for them to catch up.

FTB I'm going to stick with EDIUS, as its proprietary CanopusHQ is absolutely every bit as good an intermediate codec as DNxHD/DNxHR and/or Prores422. Its a free download if I'm not mistaken. Yet I don't know about its compatibility.

Here's an old thread, discussing the use of the CANOPUS HQ/HQX codec.

www.lwks.com/index.php?option=com_kunena&func=view&catid=12&id=12472&Itemid=81