Graphic bug? Fault?

Try El Capitan, FCPX 10.3, and Pro Video Formats 2.0.5.

I am going to try the El Cap and 10.2.3 tomorrow, it is late now, I am exhausted, thanks for all the ideas, as I am 2 days past deadline, I guess a wasted effort, but in the name of science I will go forth and find a solution!

10.3, on El Cap.. um, I think I might not try that, 10.3 is not new code, it is old code dressed in new looking GUI, kind of like a store bought roast chicken, not a new chicken roasted, but an past the sell buy date, roasted and sold as new...

I think your constant ranting about Apple is limiting the assistance people will be willing to offer. You have received some good suggestions to help isolate your problem and you would probably be best served to act on those.

I don't know if anyone else has mentioned this - I don't have time to fully read throught the thread right now but your animation codec files should be optimised as ProRes 4444 with alpha. That way optimising wont break the Animation Codec files alpha channel. All of the footage that doesn't need alpha transparency you can optimise as ProRes 422 or 422HQ as you were before. But you can't just do it all as one single batch.

Steve McGarrigle wrote: I don't know if anyone else has mentioned this - I don't have time to fully read throught the thread right now but your animation codec files should be optimised as ProRes 4444 with alpha. All of the footage that doesn't need alpha transparency you can optimise as ProRes 422 or 422HQ as you were before.

Thinking this probably isn't the issue here as i've just tried animation codec on top of ProRes 422 and they seem to play together nicely in 10.3 - even on export.

Does the purple square always take up half of the picture and is any of your original media interlaced? Thinking it could be a field based issue even though you have tried ( exporting?) both progressive and interlaced. I know it's random but does it flicker when you press play?

The purple squares are of different sizes, they occur on different parts of the video and are of varying duration, always purple with tiny dots, sometimes 1/2 screen, sometimes just a flash.

I have checked, it is not hardware, the animation codec I first thought was the problem, I re-encoded it to 4444 with alpha and the alpha channel on 4444 with alpha is not working, use the animation codec and the video alpha channel works.

It is not a moan, but something within either or in combination with Sierra and FCPX is not working, changing to 10.x from 10.x is pointless. it is the the same code, 10.3 changed nothing fundamental in the coding, not a moan, fact!!!!

I am still trying to build up the stamina to re-install El Cap and 10. something, 10.2.3 or 10.3...
The purple squares random as they are, software, which can only be either Sierra or FCPX, either or both, has to be both, as FCPX is part of Mac OS, it uses the code of Mac OS, any way, the job is gone, just frustrating!! Lesson learned!

Apple employees went on record at the FCPX summit saying 10.3 has been re-engineerd to prepare for the future. You may well be a qualified developer who's been through the code yourself and can call them on it? But everything I've read contradicts what you state as fact.

I'm sorry you're having problems and I wish you well but you just keep disagreeing with everyone. How can you be positive its not hardware? I'm not sure how else to help?

At the office when we buy Avids we leave them as they come. No updates, and they work for years (as well as avid does) until they break. All I can suggest in the future is once you have a working system again disconnect from the Internet and leave it as it. Then you know what to expect. Or have a super duper clone handy to boot from in times of stress like this so you can go back to a known working configuration.

I hope you get things working again!

I am sure that may have a grain of truth, but the fact is, it was not a huge update to download, which can only mean one thing, it only changed a tiny portion of code, the user interface icons and and a few other things, the meat of the code was left unchanged, if this was to be changed, it would have been a 6 or 8 GB download, not the tiny update that it was from 10.2.3. to 10.3..

How else can I explain, if more was changed, it would require more data to be downloaded, how else can you change from less to more without using more data code??

I am not sure when it was but I remember a couple months ago, a very similar issue/conversation was held here and it ended up being hardware related. If I find it I will post it.

dgwvideo wrote: I think your constant ranting about Apple is limiting the assistance people will be willing to offer.

Yes. Yes it is.

MsJustine, I honestly hope you can fix the problem.
I must confess, however, that I'm getting less and less motivated to help.

This thread is hard to follow because of all the ranting.

Next Time you run into a problem...

Try to use the process of elimination to zero in on the root of the problem.

• The first thing I would have tried- before switching OS and FCP versions, is to Optimize the source footage.

• Changing multiple variables at one time may end up fixing your problem, but it will not yield any definitive answers.

When problem solving a situation like this, it's best to use a controlled procedural approach and only change one thing at a time in order to isolate the underlying cause.

So converting to prores solved the flashing problem but didn't respect alpha? That's a good indication. If you look into the apple documentation yiu will see that the animation codec was deprecated under mavericks which means it is not gauranteed to be supported in future updates. Code can be removed as well as added which is one way a lot can change in a small update.

Thats handy to know that codec was depreciated. Would something like Edit Ready handle the alpha channel correctly?

Don't know. It depends on a lot of things. I imagine compressor should do the job as well. It might just take a bit of fiddling - but I don't know if that's the problem. using a legacy codec - that would be where I'd start looking

Duplicating this on my three Macs, they work fine here, so if it is software related, it is not universal. That happens.

Based on personal history with the IT industry, I will stick with a hardware problem. I bet the graphics circuitry in that laptop may have an issue. I could be wrong, but I'm sticking to that, unless some other facts come to light.

As for the upgrade to the underlying code in FCPX, yes, it was a major re-coding to much of it. That in no way influences how big or small the upgrade is that downloads. Simply improving code often means less code, not more. And based on my history with IT, I am inclined to believe Apple. They've no reason to lie about it at all. The UI was written from the ground up, no revamped, "fact". And, none of that has anything to do with troubleshooting a screen graphics issue.

Did you install the latest Pro Video Camera update, with the updated and new codecs? It was released just days after FCPX 10.3.

If this was an issue with FCPX 10.3/Sierra/MacBookPro it would be documented by now. It's not. That leaves us with a totally random event or some other, nearly invisible, causal relationship with something in the video file pathway. We used to see similar glitches in ye olden days (1996) of daisy chained SCSI drives. Debugging it was a binary search, changing only one variable with each pass: the SCSI card, one cable at a time, one terminator at a time, one drive. took hours.

The image you posted suggests a hardware issue but you say you're using the ancient Animation codec? That's like trying to edit AVIs. Did these come from someone using a PC?

You say this inexplicable glitch will cost you year of employment? Shoot, man, that's just nuts. It's just a computer. Computers break, stuff fails, code degrades. Find a credit card in your apartment that has some head room on it and buy a new Mac. Or one of those Asus thingies.

Ok, what I did was to duplicate as snapshot, then the snapshot I opened onto the timeline, sent an XML to my dropbox, deleted the video off the timeline, re-started FCPX, imported the XML.

There are no purple squares on the timeline, but on rendering, the purple squares appear, it seems RENDER ALL is the problem, I simply cannot get RENDER SELECTION to work..

Has this been asked yet? What exactly are your hardware specs?

Does each and ever drive connected to your Mac have at least 20% of their capacity left as free space?

Have you run Disk Utility to repair things?

Have you run Disk Warrior to repair things better?

Have you used "FCS Remover" to TOTALLY remove FCPX and reinstall it?

Have you installed the latest codec update that 10.3 requires?
t.co/fFmaxzJtYO

Has this been asked yet? What exactly are your hardware specs?
Model Name: MacBook Pro
Model Identifier: MacBookPro11,1
Processor Name: Intel Core i5
Processor Speed: 2,4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 8 GB
Boot ROM Version: MBP111.0138.B17
SMC Version (system): 2.16f68


Does each and ever drive connected to your Mac have at least 20% of their capacity left as free space?
YES

Have you run Disk Utility to repair things?
No, as it is a fresh install, totally wiped the Mac laptop SSD

Have you run Disk Warrior to repair things better? Is that an Apple app?

Have you used "FCS Remover" to TOTALLY remove FCPX and reinstall it?
NO

Have you installed the latest codec update that 10.3 requires? YES