[Rikki Blow]

MacBook Pro here – nothing wireless.

[Rikki Blow]

I’ve still got QT7.7.3 running OK in Sierra 10.12.2 and still occasionally use it for quick rough cut and export options.

[Rikki Blow]

yep i concur.
seems very sensitive to the order and speed of key/mouse-click. sometimes appears not to work, then you do it again more carefully and it’s ok.

depending on power of your system, i think FCPX sometimes lags in responding to keys. another example i find is selecting a clip then hitting Control-R to render – somtimes if you do it too quickly it won’t render until you hit those keys again.

another example is sometimes it misses the first letter when i’m writing in text having just created a text object with Control-T.

try slowing down before your Shift-move and see if that sorts it.

[Rikki Blow]

well maybe it’s a UK thing, but i know lots of firefox users 🙁

[Rikki Blow]

tried 2020 and any difference was negligible.

however, have been doing a bunch of tests using ‘Drop’ – a neat little screen colour analyser, and after playing around with monitor profiles and different browsers, i’ve got some more details to report.

main headline – this seems to be a HUGE problem with Firefox. (v 54.0 on Sierra on 2016 Touch Bar 15″ MacBook Pro)

I created a short video in FCPX of a simple solid orange screen (RGB 244/70/28) and uploaded it to youtube and to vimeo.

looking at the vids on Safari browser (which I don’t often use), they are coming back within reasonable tolerance of those RGB values. the only slight anomaly is that the YouTube generated thumbnail choices are a lot redder, but I tend to upload thumbnails generally and these always look fine on both Firefox and Safari.

but looking at both Vimeo and YouTube on the Firefox, the solid orange videos appear bright red (like 255/0/0!! – although the self-generated thumbnail on Vimeo reads 255/30/00).

doing a bit of research on Firefox, seems a few other folk have complained of some colour problems. I tried setting my icc profile in the Firefox color_management configuration (which was a suggestion on one mozilla forum), but this didn’t help – and i haven’t got any further with this.

one other big difference of note between Safari & Firefox:
when i was playing around selecting different colour profiles on my monitor, i discovered that Safari would change its look in the same way as the rest of my monitor screen, but Firefox would briefly blink as I changed, and while the rest of my screen takes on new colours, the web page reverts to however Firefox was displaying it – ie keeping the colours constant.

all this is probably straying far outside the remit of an FCPX forum, sorry, but it started with my concerns over export settings and why my video colours might be changing so much when uploaded.

if anyone has any Firefox colour knowledge they’d like to share, I’m still baffled what’s happening and why it’s not a big deal the hasn’t been fixed by Mozilla (unless it’s some system or software setting i’m missing here).

attached is a pic of various oranges! top left is YouTube on Firefox, top right Vimeo. in the middle is the quicktime i uploaded. bottom left and right are Safari on YouTube and Firefox respectively. hopefully you can see why this freaking me out!

[Rikki Blow]

unfortunately i don’t have a broadcast monitor, but i’m a bit confused – if it’s a monitor thing then surely watching a youtube video would have have the same cast as watching the quicktime or the pre-edit in final cut.

they might ALL be wrong, but not JUST the uploaded/compressed one.

am i misunderstanding something about calibration?

[Rikki Blow]

yep i know that youtube filters and compresses, but this is such a big shift, and although i guess the video looks generally a tiny bit redder if you look hard, it’s this particular shade of orange that seems to go way off – also the fact it’s doing the same on vimeo makes me really wonder if i have some weird camera or FCPX colour profiling setting wrong somewhere along the workflow, but i’m just not sure where to look. i don’t think it stems from any camera setting though, because i’ve imported and edited footage from other cameras with same result.

[Rikki Blow]

bit rate info:

[Rikki Blow]

hi noah

well yes, i uploaded a 20 second colour test in prores 422 and that remains the brand orange.

but clearly i can’t start putting up 8 minute interviews in this codec.

do you think that fiddling about slightly with the orange values i might be able to find something that compresses closer to what the brand colour should be? or will the whole orange range just turn red?

isn’t it weird that vimeo is also turning this red? that’s why i decided to ask on an FCPX forum rather than a YouTube forum – it seemed unlikely both youtube and vimeo were using the same compression technique.

[Rikki Blow]

I’m the world’s idiot on codecs, but I’ll throw in a crazy idea that might just work.

I export 1080 movs from FCPX regularly, but require an mp4 version for posting on twitter – MOVs simply don’t upload on that platform.

So, on a Mac, I simply rename the .mov to .mp4, and say yes when the warning pops up, and hey presto, it uploads to twitter and plays fine.

Clearly no data loss with that method.

Whether it will work on files your client needs, I don’t know, but it might just be worth a try.

Happy for someone to point out why this is working for me on twitter, and/or the general error of my ways.