Thank you very much for this piece of information, Nabolom!

Just curious: Open CL 2.0 is a Software Upgrade Adobe has to implement in their software? That would certainly explain a lot.

However:

1. Why doesn't every Mac Pro experience this issue (see Post 38 for instance)?

2. What about other Software like REDCINE-X (which does have the horizontal line issue as well, according to reduser.net)?

I think Adobe is aware of this as well as Apple and AMD...

Found this article that, Kevin, you seem to be highlighted in..   Sounds like we will all be waiting and holding our breath....This reminds me of my Nvidia card issues with my old MacPro.....dang it!!!!

OS X 10.9.3 breaking Mac Pro graphics card compatibility with critical video editing apps | 9to5Mac

Pete

Hi Jesse,

Updating a version of OpenCL refers to the OS in this case. Eric Bowen of ADK says that, "So far word on the 10.9.4 Beta [is that it] fixes the issues with Premiere." Here's the post: Re: 10.9.3 newMacPro GPU broken : Adobe Premiere Pro

I know you weren't running OS X 10.9.3 when the issues started, but I hope the next OS X update solves your issue. Since you've repeatedly had this issue, you might want to have your computer looked at by Apple, as well.

Thanks,

Kevin

Hello Kevin! this few past hours the way you communicate seems fair to us...But man, we 've been struggling here and no one at adobe responded...of course back them when people are happy yes... So, I am glad you are saying something at least to us...A lot of us here spent 7k to have a dream premiere pro Workflow. We love Adobe! we just want to fix the problem...a lot of us are having it, and I remember back in March when I mentioned this, I sounded like the black sheet with a defect Mac Pro, and here we are now...All Struggling with Renders with 4k RED RAW exports, Horizontal Lines, etc etc etc

Keep us posted man... any update is good, so we do not make stupid decisions...

Thanks

Alain M

JesseSchluntz wrote:

 

AMD's chief engineer claims the cards are fine and Adobe needs to get OpenCL 2.0 running.

Before folks get to spun up about OpenCL 2.0 versus 1.2, note: 10.9.3 still has OpenCL 1.2, not 2.0.  So it's not up to Adobe to update anything as far as support for OpenCL 2.0.  On OS X:

$ grep CL_VERSION /System/Library/Frameworks/OpenCL.framework/Versions/A/Headers/cl.h

#define CL_VERSION_1_0                              1

#define CL_VERSION_1_1                              1

#define CL_VERSION_1_2                              1

Note that 1_2 (ie: 1.2) is listed as the most recent OpenCL version.

If we look at the version 2.0 cl.h file downloaded from Khronos and do the same grep, we see:

$ grep CL_VERSION cl.h

#define CL_VERSION_1_0                              1

#define CL_VERSION_1_1                              1

#define CL_VERSION_1_2                              1

#define CL_VERSION_2_0                              1

See that a #DEF for CL_VERSION_2_0 is in place?  It doesn't exist on the cl.h file on OS X.  OS X is still at OpenCL 1.2.  The AMD "chief engineer" that so-and-so supposedly talked to doesn't quite know what he's talking about, it seems.

(For folks that don't understand but are interested in what I just looked at:  the files in /System/Library/Frameworks/OpenCL.framework are the OpenCL application libraries, header files, and whatnot.  Those are the files needed to write OpenCL-capable applications (such as Pr)).

Based on the findings, it's likely that Apple ninja-patched the OpenCL 1.2 libraries, and ended up making them worse.  And that's what Pr and AME are likely tripping over.  If folks who are beta testing 10.9.4 are to be believed: this problem goes away.

Don't waste time replacing your cards.  And I'd suggest to stop pestering Adobe to "update to OpenCL 2.0" when OS X doesn't support it (yet).

Jason Van Patten wrote:

 

JesseSchluntz wrote:

 

AMD's chief engineer claims the cards are fine and Adobe needs to get OpenCL 2.0 running.

Before folks get to spun up about OpenCL 2.0 versus 1.2, note: 10.9.3 still has OpenCL 1.2, not 2.0.  So it's not up to Adobe to update anything as far as support for OpenCL 2.0. 

Thanks, Jason.

The problem exist and I'm not sure who's fault it is or who needs to fix things.   All I know, as an Apple and Adobe user, is that I expect these huge companies to provide software and hardware that works and works without glitches.   I also expect these companies to be courteous with their customers and show some interest in situations like these.   I'm feeling very let down by this situation.

Please Adobe, acknowledge the problem and let us know what you are doing to fix it.  If you (Adobe) believe it is Apple's fault then please tell us what you, together with Apple are doing to solve these problems.

I have my MacPro 12 core with D700 cards at tekserve in NY for them to change the cards.   And today I went there to find out that they are still doing tests on the computer and that they had not found anything wrong yet.

While being there I tested one of their display models, an 8 core with D500 cards and premiere installed.  Using footage that they already had in the computer (various codeqs) I actually managed to make it crash once while rendering.  Then I managed to make it render with the horizontal flickering lines.

Basically, I'm now sure the problem is not limited to just a few of us, and I know it happens in Premiere Pro.

So please Adobe, please Apple and AMD, stop pointing fingers and work together and inform us about what is happening.

Hello MaoSoto,

MaoSoto wrote:

 

The problem exist and I'm not sure who's fault it is or who needs to fix things.  

As Jason Van Patten indicated in a previous post, this issue has to do with OS X 10.9.3. Apparently, the issue is fixed with the upcoming version of OS X 10.9.4.

MaoSoto wrote:

 

All I know, as an Apple and Adobe user, is that I expect these huge companies to provide software and hardware that works and works without glitches.

I understand your expectation and, of course, we strive to do that.

MaoSoto wrote:

 

I also expect these companies to be courteous with their customers and show some interest in situations like these.   I'm feeling very let down by this situation.

I'm sorry you feel that we haven't participated in this conversation or have been discourteous. I have responded a number of times and reported the incident to our engineering department, and a Quality Engineer has also participated in this thread.

MaoSoto wrote:

 

If you (Adobe) believe it is Apple's fault then please tell us what you, together with Apple are doing to solve these problems.

I can't speak specifics, sorry. However, we continue to be in constant communication with all our partners about customer issues, including Apple.

MaoSoto wrote:

 

Basically, I'm now sure the problem is not limited to just a few of us, and I know it happens in Premiere Pro.

Thanks for testing that out. I imagine all those computers are running OS X 10.9.3, so I can understand if they exhibit the same issue.

MaoSoto wrote:

 

So please Adobe, please Apple and AMD, stop pointing fingers and work together and inform us about what is happening.

Sorry this is happening to you. I hope that the OS X update will solve your issues and you'll be back up and running with hardware acceleration ASAP. Keep in mind that you can downgrade OS X to a previous version and you should have hardware acceleration functioning, but not sure you wish to do that.

Thanks,

Kevin

Hi Kevin,

Thanks a lot for replaying to this.  I really appreciate it.

As you might have noticed this thread started before 10.9.3.  The horizontal flickering lines actually started happening on 10.9.2.  The lines used to be thiner and not so noticeable, but they were there.   Updating to 10.9.3 made the lines way more noticeable.

There might really be an issue with the OS but there has also been an issue with Premiere from even before. Please let that know to the engineering team.

Again, I'm really grateful that you are now participating here and for keeping us updated.

Hi,

No problem.

MaoSoto wrote:

 

As you might have noticed this thread started before 10.9.3.  The horizontal flickering lines actually started happening on 10.9.2.  The lines used to be thiner and not so noticeable, but they were there.   Updating to 10.9.3 made the lines way more noticeable.

Let's hope that OS X 10.9.4 solves the issue introduced in 10.9.2. They both have the same version of OpenCL.

MaoSoto wrote:

 

There might really be an issue with the OS but there has also been an issue with Premiere from even before. Please let that know to the engineering team.

The engineering team has been investigating the issue, so they definitely know.

MaoSoto wrote:

 

Again, I'm really grateful that you are now participating here and for keeping us updated.

Sure, no problem!

Have a good weekend,

Kevin

I just purchased a brand new Mac pro fully loaded 12 core maxed ram and 2 cinema displays along with a new one year subscription to Adobe CC. I noticed very apparent issues immediately after I got everything hooked up and running. First and foremost- I am having choppy playback of video and audio (Using Canon 5D footage) and that on a 12 core Mac and a Thunderbolt 2 RAID. It is extremely frustrating and difficult to edit footage that plays back choppy and glitchy and almost impossible to edit audio that is intermittently dropping out.

I also cannot render my timeline/ sequence (it locks up- no progress) and when I export to AME it takes forever to link and load. I'm also having a weird issue where my audio won't play back through my external speakers coming from line-out of the Mac. Sometimes it plays and sometimes not.

I have tried all the suggested fixes: turning off GPU acceleration, etc. The problems persist!

I have spent quite a bit of time talking to Adobe and Apple regarding these issues. ADOBE is not much help. Two of the three techs I spoke to just told me they were aware of some issues but had no idea when it would be fixed. They shared my screen with me- they saw the issues and had no fixes. The third tech actually tried to do something but was unable to troubleshoot the issue. He was going to look further into the issue and call me back- but I have not heard from him.

I finally spoke to someone high up at Apple. His name is Adam Mason (a CPU Senior Advisor) He told me what no one else did (or would) that the issue was recent- apparently started after the last Mac OS update. It's an issue with the Firepro D700 graphics card and Premiere. He said it has a high priority because a LOT of (new) Mac Pro users are complaining. I just hope the fix happens soon and solves ALL of my issues not just one. I see a lot of people posting about rendering issues but no one has mentioned the choppy playback issues I am having!

The bottom line is I cannot edit professionally on this system and I have reverted back to my 2008 Mac Pro running a 3GB eSata RAID on Premiere Pro CS6. The footage plays back smoothly and I don't have any issues. This has been my salvation- nothing can ruin your reputation and business as fast as not meeting your deadlines!

As you can imagine I am very upset and disappointed with this situation. I have more than $15,000 invested including Thunderbolt peripherals and 2 new Thunderbolt Apple Cinema displays....and it's essentially a paperweight! I am considering returning the Mac Pro and getting a refund on Creative Cloud and waiting until all this mess is fixed before I order another Mac Pro again.

At the very least Adobe should be giving me credit for my subscription until I can actually use it. I paid for a year of CC and who knows when I will start using it?

I just want a straightforward answer from Adobe and Apple and AMD since they are the ones working on it as to when I can expect PERFECT and I do mean perfect performance from their software on the new Mac Pro. I will not accept anything less!

Thanks Jesse- I'm surprised you are not experiencing issues. Are you using a (new) Mac Pro? The reason I ask- I loaded PP CS6 onto my new Mac Pro to see if it would operate normally as it does on my 2008 Mac PR0. It does not act normally. It also has stuttery playback of video and intermittent audio cutting out.

Is anyone else on this thread having stutery playback issues? I'm curious becasue no one has mentioned it.

Also please let me know- those of you who have owned the new Mac Pro since it came available for purchase (I believe back in October 2013) Hove you had any stuttery playback issues and rendering issues when you first got your new Mac Pro or was it only recently that these issues appeared? and if so when?

Thanks!

Hi Jim,

You didn't mention horizontal lines in your outputs, so could you please create your own post? Though your issues are important, I don't want to go off thread here.

Thanks,

Kevin

I am seeing horizontal lines also during the playback. Sometimes. Not constant though. On export almost everytime with Open CL

Sent from my iPhone

Hi Kevin- Yes the lines I am experiencing are intermittent and happen during playback in the sequence. They appear quickly and disappear just as fast. They are more pronounced when acceleration is on.

There have been rumors that the current beta release of 10.9.4 will fix problems outlined in this duscussion. THIS IS NOT THE CASE. After loading 10.9.4 (beta) I am still seeing repeated crashes.  Currently - The late 2013 Mac Pro with AMD FirePro cards ARE NOT COMPATIBLE with Premiere - Adobe/Apple needs to to post this.

Silberfarb wrote:

 

There have been rumors that the current beta release of 10.9.4 will fix problems outlined in this duscussion. THIS IS NOT THE CASE. After loading 10.9.4 (beta) I am still seeing repeated crashes.  Currently - The late 2013 Mac Pro with AMD FirePro cards ARE NOT COMPATIBLE with Premiere - Adobe/Apple needs to to post this.

It might be helpful for folks if we keep the issues separate, because my gut tells me they are.  We have 2 issues that I can see:

1.  Random horizontal lines in playback, the rendered output, etc.  Some screen caps make it seem almost like an interlacing problem but that's purely speculation on my part.

2.  App crashes w/AME and Pr.

This specific thread is centered around topic #1.  Reports on Creative Cow seem to indicate that #1 is solved with 10.9.4.  If that's not the case, in other words those running the beta ARE still seeing random horizontal lines, then we still have an unknown.

Hi Jason,

I'm definitely not a programer but I think the problems are related. See attached. Screen shot - horizontal lines with 10.9.4. Regardless - I think it is still safe to say that currently Premiere will not run on late 2013 Mac Pros.

Silberfarb wrote:

 

I'm definitely not a programer but I think the problems are related.  I think it is still safe to say that currently Premiere will not run on late 2013 Mac Pros.

That's new data that we haven't had, so far.  Unfortunate, but good info nonetheless.

Can you put that .MOV file up somewhere where I can download it?  Or is it leading to some copyrighted material that you're not able to share?  I ask because I disagree with your statement about Pr running on the new Mac Pros.  Again: I have literally had 0 problems with it, so far.  I'd like to see if I can replicate the problem you're seeing, because I've, thus far, been unable to.

Sure I can post it to Vimeo (it's for a documentary so please do not use it other than for testing). My e-mail is bsilberfarb@gmail.com. Out of interest, are you still running 10.9.2? or did you update to 10.9.3?

PS: Perhaps I should qualify and say currently late 2013 mac pros running 10.9.3 are not compatible with Premiere.

Silberfarb wrote:

 

PS: Perhaps I should qualify and say currently late 2013 mac pros running 10.9.3 are not compatible with Premiere.

I'm running 10.9.3. ;-)

Defenetely not compatible mac pro 2013 with premiere cc.  Many users have same issues. And i dont think it is a bad batch of apple that shipped to us. 

I hope soon this issue gets resolve

Sent from my iPhone

I have having this issue with rendering out from my new Mac Pro as well. I sure hope this if fixed soon! Rendering out using software only is painfully slow when you are on deadline!

My company bought two new Mac Pros just after they were introduced. One of them had the lines (like post #1) from day 1, while the other functioned flawlessly with no artefacts what so ever. Unfortunately we had activated automatic updates, and with the 10.9.3 update we got severe artefacts and hangs during playback in PP CC on the "functioning" Mac as well. CS6 works without problems, but as several users have mentioned, not being able to utilise the powers of the new Macs kind of defeat the whole purpose of the investment.

We even got our initial problem computer replaced by Apple (it also went into endless reboot loops every time we rendered something in AME). Got the replacement computer yesterday and did a clean install (it came with OS 10.9.3). This computer shows artefacts in CC similar to those shown in post #102.

As an end user, it´s frustrating to see how everybody seems to be pointing fingers at each other and how long an issue like this takes to be fixed. Premiere CC is being marketed as the perfect solution for editing on the new Mac Pro, when clearly, for the time being and quite a lot of users, it is not. We are anxiously awaiting updates that will fix this problem, but if they don´t disappear, we seriously have to consider the base of our whole editing, animation and encoding platform.

Purchasing a new Mac Pro to replace a 2008 tower was a huge financial step and months were spent researching.  Much of that research was done on adobe's site.  All of this information convinced me that Adobe CC and the new Mac Pro would completely rock out together.  I understand that unforeseen issues sometimes occur, but maybe Adobe should take down or amend some of this previous information that is informing their client's decisions.  I bought this new machine to work with Adobe CC and I'm experiencing the line issues, and once AME opens - it won't quit without a hard shut down using the button on the machine (which can't be good).  It shows up twice in the Force Quit window, lot's of 'serious problem' crashes in Premier.  All sorts of weirdness.  Apple is taking my issues seriously - but they have no solutions other than to downgrade to 9.2 (my machine came with 9.3) - which from what i've read might not work.  Turned off OpenCL which seems to work for fixing the lines problem in exports - but still constant crashes and weirdness.  Hope there's a complete solution soon...

http://tv.adobe.com/watch/davtechtable/working-with-premierepro-cc-the-new-mac-pro/

=====

http://blogs.adobe.com/davtechtable/2014/03/working-with-premierepro-cc-the-new-mac-pro.ht ml

========

http://blogs.adobe.com/premierepro/2014/03/premiere-pro-cc-on-the-new-mac-pro.html

There has been a lot of confusion and misinformation recently about how well Premiere Pro CC runs on Apple’s latest professional desktop machine, the new Mac Pro. I’m happy to say that, due to the meant-to-be combination of the Mercury Playback Engine and the immense power of the hardware, you can expect absolutely phenomenal performance. In this video, our man Dave Helmly takes you through just what it can do (and there’s even a surprise at the end, so if you ever work with RED media, I suggest you watch the whole thing).

=====

https://forums.adobe.com/thread/1412328

No, it's not true. The new MacPro and Premiere Pro CC work very well together. I'm not sure where you heard anything negative. As one of my colleagues says, "The performance of Premiere Pro on this hardware is way more than most people need," so the software is already optimized for the new Mac Pro. In fact, its dual GPUs can be utilized for export, for better quality and faster speeds. Read about that here.

I've been experiencing the whole spectrum of issues reported here with the 2013 Mac Pro and Premiere.  I do think the freezing/lockups are related to the colored lines, screen artifacts.  Every time I start seeing the screen issues, within a matter of minutes the machine completely locks up, like back in the old days before OS X.  Nothing short of a forced shutdown will bring the machine back to working order.

I've also experienced system-wide lockups just by having Premiere running in the background.  I left it open last night, machine went to sleep, I came back later to wake it up and found that the mac had frozen up during sleep!

Jason, I don't think the screen issues are related to any typical video compression or interlacing issues.  I have experience dealing with those issues and believe this is not related.  It does however remind me of when my 2008 Mac Pro graphics card was failing.  I would get similar screen weirdness splattered across the entire screen.  Replacing the graphics card fixed this issue on my 2008 Mac Pro.  What's curious about the current problem is that the screen artifacts are usually contained within the preview or program monitors, which suggests to me a software issue.  I think we can corroborate this by some reports I've seen of users getting their graphics card replaced by Apple and still having the issues.

Regarding the OpenCL discussion: Users of the beta of OS 10.9.4 are reporting no remedy for these issues.  Do we know for certain that the beta of OS 10.9.4 contains the latest version of OpenCL?  I think it's supposed to be version 2.0

I'm hoping we hear an official word on this soon, as my pricey new machine isn't good for 90% of what I need it for.  Using my 2008 Mac Pro to edit video for now, feeling like I'm back on my Commodore VIC20.

Douglas S. Nagel wrote:

 

Jason, I don't think the screen issues are related to any typical video compression or interlacing issues.

Don't think "interlacing" as it relates to video display.  Think "interlacing" as it relates to using 2 things to do 1 thing.  In other words: the 2 GPUs sharing the load.  It's merely an idea though, and there may be nothing to it.  If Apple gave us a software switch to magically disable one of the GPUs, we could try this whole thing again and see if the artifacts/lines still exist.  Unfortunately, there's no magic software switch that I know.

What's curious about the current problem is that the screen artifacts are usually contained within the preview or program monitors, which suggests to me a software issue.  I think we can corroborate this by some reports I've seen of users getting their graphics card replaced by Apple and still having the issues.

I have no doubt it's a software issue.  The question remains: whose software?  Apple's or Adobe's?  Personally, I think folks going through the grind of getting their GPUs replaced are wasting their time.

Regarding the OpenCL discussion: Users of the beta of OS 10.9.4 are reporting no remedy for these issues.  Do we know for certain that the beta of OS 10.9.4 contains the latest version of OpenCL?  I think it's supposed to be version 2.0

I'm not on the Apple Dev program, so I have no access to 10.9.4.  I haven't a clue if they updated OpenCL to 2.0 in 10.9.4, but my gut tells me they wouldn't do that.  They might for 10.10.  For those with 10.9.4 beta, it would be really easy to find out.  From a terminal window:

grep CL_VERSION /System/Library/Frameworks/OpenCL.framework/Versions/Current/Headers/cl.h

and check the output.  If one of the lines says:

#define CL_VERSION_2_0        1

then it's OpenCL 2.0.

Jason Van Patten wrote:

 

Don't think "interlacing" as it relates to video display.  Think "interlacing" as it relates to using 2 things to do 1 thing.  In other words: the 2 GPUs sharing the load.  It's merely an idea though, and there may be nothing to it.  If Apple gave us a software switch to magically disable one of the GPUs, we could try this whole thing again and see if the artifacts/lines still exist.  Unfortunately, there's no magic software switch that I know.

 

Ah, indeed.  That would be a good test to be able to run if it was available.  I found this interesting comment on an article from a google search:

"Im running the previous Mac Pro but with an R9 280X GPU in it that has the same Tahiti based chip on it as the D700 found in the 6,1 Mac Pros. I have had nothing but problems with video as well with the 10.9.3 update!"

I forgot to mention that I'm running the AMD D300 here.

Perhaps Silberfarb could run that terminal command for us in 10.9.4?

Same thing here. Lines, artifacts, freezing on export in premiereCC and encoderCC. Dual 700, 6 core new MacPro with 6bay Promise TB Raid and 64GB RAM.
Today i recognized that i can export using OpenCL in encoderCC when i come from aftereffectsCC.
Another new problem occurred during encoding with encoderCC. I startet the queue and nothing happened. I stopped the queue and premiereCC asked me to finish the job before canceling.
I clicked yes and suddenly the encoding progress started. Logic? Nope. I would call it bug.

Everything concerning exporting, encoding, with premiereCC and from pCC to meCC is messed up.
I really don't know what's wrong, but i think it's at first a premiereCC problem.

I also was on the FMX 2014 in Stuttgart on a Adobe workshop. They showed the next version of premiereCC (includes p****r tracking and better ae dynamic link functions!!! whoohoo) on a MacBook Pro.
4 to 6 weeks was his announcement, that was the 24th of April. Add another 4-6 weeks and we'll gonna see the next version.
Before that launch date Adobe will probably not work on a update to this problem.

Dual graphics topic: I thought one of those cards is just for displaying content on x screens and the other is only for processing. They are splitted for separated tasks, aren't they?

Hasenbau wrote:

 

Dual graphics topic: I thought one of those cards is just for displaying content on x screens and the other is only for processing. They are splitted for separated tasks, aren't they?

Only one of them is used for displaying via the Thunderbolt and HDMI ports.  They're both used for OpenCL compute as needed.

Is there a fix for D700 users yet or is this strictly an OSX issue? What has everyone been doing?  AME with Open CL GPU acceleration is useless for h.264 and ProRes encoding. When is 10.9.4 out? 

I have the same premiere pro cc crash problems with the the fire pro d500 and the new Mac Pro

mercury playback software only solves the crashes but render and playback time suffer

I was so excited today to finally begin working with my new mac pro. Got the 12 core, 32gb ram, dual d500 GPUs running 10.9.3. After loading in some projects from my older mac, linking files, and rendering my timeline I immediately noticed this severe bug. Horizontal jagged lines, flash frames of other footage, and neon pink/green color overlays. I'm now more comfortable knowing that other people are having this issue but still bothered about all the confusion as to what exactly is the solution. With some beta users of 10.9.4 still experiencing the problem deeply troubles me. Adobe has an update/event planned for the 18th so hopefully this will perhaps fix this issue??? I wish I could provide some assistance to others here but alas I am not as technical as others. I will try to turn off Open CL tomorrow and hopefully that will be a bandaid until the next update from Apple or Adobe.

Exactly bryceu27. We all have been sold the nMP and CC as a perfect combo, but now we're left  completely in the dark with no proper response from anyone. i don't like it.

Tore Jonssen wrote:

 

Exactly bryceu27. We all have been sold the nMP and CC as a perfect combo, but now we're left  completely in the dark with no proper response from anyone. i don't like it.

It must be restated, perhaps several times, that this is a user-to-user forum.  We're lucky to have some Adobe participation here, but it isn't promised, guaranteed, nor should we expect it.

Please note that I'm not trying to make excuses for Adobe, or for Apple.  I'm merely pointing out what we should expect here on these forums.

The engineers at Adobe are well aware of the issue.  If they can fix it, I'm sure they will.  However, it may be something Apple-related, and if so, the Adobe guys may not be able to do anything about it.  Often times, it's way harder to figure out what the problem actually is than it is to fix it.  I think we're all in that discovery phase right now (we being: the customers, Adobe, and perhaps even Apple).

I can understand the frustrations as I'm starting to see the artifacts in my video outputs as well.  I'm not trying to belittle or otherwise downplay how important this is for professionals, as time is money and I can see how the down time this is causing can be costing ya'all a lot of cash.  Raising a stink here on the user forums isn't going to make anything happen any faster, unfortunately.  Open cases with Adobe's tech support.  Provide them with source footage and project files.  Tell them exactly how you reproduced the problem so that they can take said footage and do it themselves.  The more we do to help Adobe, the quicker this may get solved (assuming it's something Adobe-related).