@donkpow:

@timzett: eg. lwks 64-bit does not use QT, so there should be no change.

it's more about exporting in lwks 32-bit via quicktime.

s

Anyone remember year 2K?

It seems all LW users have been exposed to QT security vulnerabilities for many years. Hands up those who have been bitten; if there's a rush I'd have to ask why have you not come forward before these dire warnings.

Notwithstanding the report publicised by, yes you guessed it, a commercial computer security software crowd; have no intention of uninstalling QT for Windows here. Not sure if it's technically possible but perhaps some other computer security software organisation might be able to detect any possible attacks via this not so new route?

Hardly ever start-up the QT Pro software - often use the QT SDK integration in 32 bit LW. More often than that import camera files in .mov wrappers - not hearing any urgency from camera makers to switch wrappers. Not sure if anyone can actually quantify the risk associated with the current matter across the many variants of using QT files/SDK/Player/Pro/other-players. Is the vulnerability via the QT application only/partly/not at all?

Seems to me Apple is being shown to be a bunch of self-interested folk - with no regard for Windows users who have been loyal customers for years - cone to think of it that's also a possible exact description of Microsoft relative to that organisation's push with the Win10 behemoth. On that basis perhaps all Windows users should uninstall Windows, take a break on a beach somewhere, or better still go to the cinema?

Haven't used or missed QT since the nineties.

You can use ffmpeg to remux .mov containers to .mp4

Helpful, but not if you have ProRes or DNxHD in a QT wrapper I would have thought. Roll on MXF, I say!

still "cineform" would/could be an *excellent choice* (see> *the lobster* film ,-)
just hit CF "transcode" on import, just hit render CF ...
s

afaik same sys as lwks - win / mac / lx

Cineform is a codec, MXF is a wrapper like QT.

I don't need any wrapper. let's say I can work *hypothetically* in ".CNF" - lets say it's the cineform extension, which is of course a wrapper (proxy, standard, film, film+ etc.) - still I'd no troubles with 3rd party unsupported wrappers ...
s

let's see what next lwks will bring ...

Let's say unicorns are real and you don't have to work for a paycheck.

I don't post every feat. req. on the forum - of course. unicorns - they are real ...

cineform
www.dma.ufg.ac.at/assets/24991/cineform_s.png


Geraldine Brezca is real too - still some ppl think she does a bad job ,-)
www.dma.ufg.ac.at/assets/24991/intern/0102_How_to_Slate_Film_the_RIGHT_way.mp4

Funny clip.

indeed ,-)
"it is rumored that tarantino only makes such good films, because he has the perfect "clapper operator" woman on set"
,-)
s

,)

added a screen shot - "how to read clapper boards" - NP4-1
-> www.lwks.com/media/kunena/attachments/32848/NP4-1_S.png

www.dma.ufg.ac.at/assets/24991/intern/0102_How_to_Slate_Film_the_RIGHT_way.mp4

s

lghtwrks wrote:
That was the right link back:
Almost 4 years ago I was still using Lightworks 32 bit, and by then not only the export issue was there but also a playback issue with MOV Containers (also e.g. with MPEG2 I-Frame), that the video in the timeline would just show a "green screen".

So now I give it a go without QuickTime now

This has been suggested as a possble way around this:

www.reddit.com/r/AfterEffects/comments/4eyy81/possible_workaround_for_quicktime_security_issue/