Good Lord! I crossed all of my fingers and toes, threw a four-leaf clover in my pocket and updated one of our machines to 8.2.0 (I gave the dog's breakfast that was 8.1 as wide a berth as possible... I've only loaded a dingle project so far, so I can't speak to its stability or reliability, but MY GOD, THE BLUE IS HORRIBLE. Like, objectively, unequivocally HORRIBLE. It's one thing seeing it in screen caps, but to actually be faced with the UI in person...? *shudder* I'm going to head off and file another bug report about this... ... View more

I'm not exactly the most technical guy in the world, but, to me, the (seeming?) absence of this problem on every platform but the new MacPros points to a hardware issue, no? Or possibly some kind of HW/SW compatibility issue? AFAIK, the AMD DXXX line of GFX cards are only used in the 2013+ MacPros. Defective HW would also explain why the rendering issue shows up for some people, but not others, and why it's persisted through several OS iterations. It seems clear that there was a bug in OSX 10.9.3 that caused a rendering glitch, but maybe the post 10.9.4 rendering glitch that people are seeing is unrelated to the 10.9.3 OSX glitch? I'd raised this possibility a while ago, so I apologize for repeating myself, but a heat-dissipation issue might explain things --- the trashcan design can't keep the video cards cool enough, so when they're under load (ie. during render, or playback, depending on the content being played), they heat up, components expand, things start to futz up. The lack of glitches when going software-only would also be explained by this, since the GFX cards are being completely bypassed. This would also explain why people are seeing similar problems in Resolve. It wouldn't explain the lack of issues in FCPX, unless FCPX is capable of using the video cards more efficiently than 3rd party programs, or unless FCPX is primarily reliant on the CPU for rendering. Dunno, just throwing stuff out there. ... View more

Nope. I had just stumbled across the post by 'I Just Want to Work' in a related thread, thought it might be of some help here. I'd tag him directly, but he's got a space in his username; the forums can't seem to figure that one out... https://forums.adobe.com/people/I%20Just%20want%20to%20work @I%20Just%20want%20to%20work I'm trying to be sympathetic to you guys, Kevin; I know there's not much you personally can do about these issues... If you guys are so confident that your updates work, why not put your money where your mouth is? It takes time to update and test these updates; I can't just let the updater run and say "have at 'er!". I've got to test a host of older projects to make sure they'll work properly --- we've lost days worth of work by updating to a broken version of PPro, continuing work, and realizing after the fact that, for example, our C300 footage wasn't spanning properly. We'd roll back to a previous version of PPro, but our projects would be a complete loss, since there's no compatibility. I've got to do import tests with footage from our different cameras. I've got to do render tests to make sure that we can actually export our work once we've finished. If you're so confident that 8.1 will work, then why not back that up? If I update and everything works as promised, then fine; if not, and I have to rollback, I think we should be compensated for that time. That's only fair. We're paying you to provide a service: working software. If you can't deliver that, why should we have to take the heat for that? You can't treat your customers like glorified Beta Testers. Again, I apologize to you, Kevin. My rants are about a larger issue than what's being discussed in this thread. Given the seemingly strong possibility that this particular problem is an Apple hardware or software bug, there's only so much Adobe can do to help... There are only so many ways you can say "it wasn't us!". ... View more

I came across this post by I Just Want to Work in another thread that may shed a little light on this problem: Re: Premiere Pro CC and the New Mac Pro (2014) If it is a confirmed issue on Apple's end (HW or OSX-related), that's at least a step in the right direction. As G.I. Joe always says, "knowing is half the battle." ... View more

JesseSchluntz wrote: If this issue haunts me again, my local Apple Store has agreed to arrange a new computer. if this does not happen again, I'm going to be calling on every Premiere Pro editor who's been dealing with this issue to sign a letter I'll draft to Adobe and Apple demanding, as their customers, to figure out this issue immediately. I'll use this thread to reach out if things come to that. We haven't had any issues (with this particular glitch, anyway...) since the 10.9.4 update, but I will happily sign that letter. Anything to try and get Adobe to do more extensive beta testing, rather than just rushing out bug-filled updates! ... View more

Between the new UI and the bugs, almost everyone I know has either reverted back to 8.0.1, or didn't install 8.1 in the first place. I'd be curious to know how many Adobe users are still on 8.0... Not that they'd share them, but Adobe must have those stats; if large numbers of their users refused to use the latest, "greatest" update, I would imagine that would help send Adobe a message, too. ... View more

A sneak peek at the UI for the PPro 8.2 update...!?! SO MODERN, YOU GUYS! Word is that the Beta testers are having a hard time with it, but, y'know. Whatevs. (Don't mind me, I'm just being an a-hole... ) ... View more

coastalmedia wrote: To give an analogy; Say you purchased a new car, but soon after found you couldn't drive it for as long as you wanted because the dealer changed the colour of the instruments.... How would you feel if the dealer asked you to "Drive your other car" until they got around to fixing it with the release of the next model??? Youo're still paying the finance each month, for a car you can't use. Don't think you'd be so happy about driving your old car. This is the crux of the issue, for me. Adobe's subscription model is predicated on the provision of a service (working software). If they poop the bed with their software and send out a half-baked, glitchy release, the subscribers have to either deal with it, or leave. I've literally spent days troubleshooting glitches after foolishly installing a 0-day update. Adobe's usually pretty good with at least attempting to help solve the issue, but the "solution" tends to either involve rolling back the software to an earlier version (wasting time, and breaking compatibility with any projects started in the updated app) or some sort of workaround-and-wait-until-its-possibly-fixed-in-the-next-update scenario. Either way wastes our time and money. Everybody makes mistakes, and I agree that, bugs and hilariously misguided design decisions aside, Adobe generally makes really good software. It's frustrating that the customers have to bear the weight of their mistakes, though. If I make a mistake with one of my projects, or can't deliver a finished product on time, I don't get to release a half-finished video, shrug and be, like, "I'll fix it sooner or later; in the meantime, just put the half-finished version to air. It's close enough, right?" ... View more

shooternz wrote: To be fair. This is 100% not true. Look, you guys, ******** about this in the forums isn't really going to solve anything; it's not like Adobe even bothers listening to customer feedback.. No no, you're right of course. My bad. ... View more

To save you guys the search: Adobe - Feature Request/Bug Report Form ... View more

Look, you guys, bitching about this in the forums isn't really going to solve anything; it's not like Adobe even bothers listening to customer feedback... It sounds like the best we can do is start filing bug reports en masse and hope for the best. Seriously, how did anyone think that a med-dark blue was a good idea for highlight text. I get that yellow is a fatiguing colour to look at for extended periods of time, but when paired with an overwhelmingly dark, neutral background, that's not really a concern. Yellow is also the most visible colour in the spectrum, handy when you're, y'know, trying to read small, important type on a high-rez screen... In terms of aesthetics, blue pairs quite nicely with lighter neutrals, but generally looks horrible with dark neutrals. As I'd mentioned above, given your customer base, your first concern should be with the user experience, and whether you're making it easier for customers to do their job. Arbitrary, pointless UI changes with seemingly no forethought put into them are only going to p*ss off your customers. Remember, the more difficult you make it for us to earn money using your software, the less likely we are to continue to subscribe. ... View more

Looks like Adobe's got a bad case of the Apples! Apple not paying attention to their customers, I understand; they make very little money off of the Pro market. Very few Apple users rely on their iPhones or whatever as a revenue stream. Adobe constantly confounds me, though. It frequently seems like they don't understand (or don't care) that the vast majority of their customers use their software as a source of income. That's something that needs to treated very cautiously and respectfully; if you f**k with somebody's income, you'd better have a good reason, not just, like, "well, the designers think that yellow is SO 2012." Inconveniencing a bunch of cellphone users is one thing; they'll whine about it on the internet for a few weeks, and move on, no worse for wear. Making it more difficult to DO OUR JOBS (even in as small and seemingly inconsequential of a way as making text more difficult to read) is a completely different story. As I've said in another thread, time = money. If it takes me longer to do something, that's less money in my pocket, or less time to spend with my family. ... View more

I love that Adobe's official response is, essentially, "yeah, our Beta Testers really didn't like it, either, but we went ahead with it, anyway!" "several beta testers reported that they started off not so keen on the new look, but within a short time they came to like it." ... View more

Hahaha my friend actually did that; he didn't do it to fix the Xbox, though, it was to completely break it, so he could get a free replacement unit from Microsoft... ... View more

Jason Van Patten wrote: just how solidly everything is bolted together inside For sure, I was thinking more of the sautered/glued connections on the components themselves, rather than the overall construction of the box, though. Just a kooky theory that I thought I'd share! ... View more

This is totally out of left field, and is based on absolutely nothing but pure guesswork, but the random, intermittent nature of the bug, might be the result of a manufacturing defect...? Anyone remember the XBox360's Red Ring of Death? IIRC, it was caused by a combination of substandard components and poor cooling: the box couldn't dissipate the heat efficiently enough, so the internals; as the internal components heated up, they would start to flex, and the adhesives would start to soften -- not a lot, but enough that with repeated heating/cooling cycles, severe issues would start to develop. I was skeptical that Apple's "revolutionary" single, central fan-based cooling system would be able to handle the crazy amount of heat generated by processors/video cards under load; I've noticed our trash can gets pretty warm at times. Maybe it's possible that the cards/parts/connections/whatever are slightly flexing due to the heat, introducing errors into the encodes...? The internals wouldn't always be under the same amount of load, so that might explain the seeming randomness of the glitches...? Like I'd said, it's really far-fetched, and is based on literally no actual evidence, so take it with a grain of salt... Food for thought, though! ... View more

It's kind of a stupid workaround anyway, since it involves modifying the project file in a text editor... ... View more

Don't have it in front of me, but I think that with a CC membership, you have access to installers dating back to CS6 via the CC Installer app. Something about scrolling down the list, changing a filter to "Previous Versions", and installing from there. I had to install PPro CS6 a few months back in order to get a copy of Encore on my system. Arg. Don't get me started on Adobe's handling of Encore.... ... View more

This is in no way a solution to the actual problem, but if you still have CC or CS6 kicking around, can you edit the project file to make it compatible with previous versions, and finish the project in an older copy of Premiere? I haven't tried it myself, but there are details here: Re: Can't Open CC project file in CS6 ... View more

Unfortunately, it sounds like the only real 100%-for-sure fix is to not use the new Mac Pro. If you don't need a machine with a lot of power, you can switch to an iMac, or a late-model MacPro tower; if you want something with hyped-up specs, you might be better moving to a custom-built PC. The plus is that CC is cross-platform, so you can easily bounce all of your projects back-and-forth between Mac and PC. Kevin, I'd like to second Emmanuel's request for some sort of official compensation mechanism from Adobe; I think it's more than fair that you guys offer some sort of recompense for downtime, or for periods when your software is unusable. If Emmanuel and the others on this thread have been unable to use your software for 6 months, while they wait for a fix, it's not unreasonable to expect that their subscription be extended by 6 months, free of charge. To be clear, I don't even have a horse in this particular race... We got lucky; one of our seats was down for two weeks at most before the 10.9.4 fix was released (10.9.4 seems to have solved the issue in our case). That's not to say we haven't had long bouts of downtime with OTHER bugs, like the Canon MXF spanning issue with PPro 7, for example, or the myriad of other Adobe Creative Cloud issues we've had to deal with... ... View more

Are you speaking of the artifacts on export with the new Mac Pro or something else? Remember, we involved Apple and AMD in finding a fix. If it's something else you're speaking of, be sure to create a separate post and I'll see what I can do to help. Thanks, Kevin Thanks for replying, Kevin. As I'd mentioned in previous posts, the update to 10.9.4 fixed the HW render issue for us with our Canon MXF-based workflow. The other stuff I'm referring to are the litany of bugs, glitches and not-ready-for-primetime features we've dealt with over the past year or so. I won't clutter up this thread with a list of unrelated issues; some have been patched with varying degrees of success, some we've found workarounds for, and a few we've just given up on out of frustration. Before you ask, we've filed bug reports, and one of our guys has been in contact with (less than helpful) phone support. ... View more

ChadRHorn wrote: Derjis, I think you are confusing your problems with the ones that prompted the creation of this thread. Some of us (presumably those who bought the first Mac Pros off the line) have random horizontal lines in every export we do, regardless of the source material footage if we render with the aid of our hardware. This means every project we ever want to export takes HOURS longer than it should have, leading me to always copy the files over to my old laptop to export until this gets fixed. Many people joined the thread later with problems regarding RED footage, but as those issues get fixed we continue to have random horizontal artifact regardless of source material (in fact, in purely title based projects with no source material I have had some). If I didn't have my laptop, FCP would be a much faster workflow. A totally fair point. The OSX 10.9.4 update fixed the exporting issues with our new MacPro (early June purchase). Mind you, our workflow is largely Canon MXF-based. To play Devil's Advocate, if this is limited to specific hardware, and the initial problem was widely known to have been caused by Apple, then it seems likely that this is still a problem that should be laid at Apple's feet, no? I won't bother trotting out a played-out "BUT APPLE JUST WOOOORRKKKSSSSSS" joke... 😕 ... View more

Boru wrote: Yea, you are right I should stay off the forums when I am frustrated at software that is advertised to work and is loaded with bugs. Take a chill pill, dude. We're all here because we're in the same boat. There's still a chance that this is an Apple issue, since people are only reporting problems on the new MacPros (I think?). To be clear, this is extremely frustrating, and I am in no way letting Adobe off the hook for releasing buggy, not-ready-for-prime-time software. That being said, in my 15+ years of editing on more than a half-dozen different software packages, I've yet to run into an app that DIDN'T have serious issues at one point or another. I think Adobe (rightly so!) is catching a lot of heat because of their forced push to a subscription-based software-as-service model. That and, y'know, their half-baked "cloud services"...  It's pretty tough to swallow BS like this when you're getting a monthly reminder that you're paying for something that doesn't actually work as advertised... If it's a dealbreaker for you, there are plenty of NLE options out there. I'm guessing Kevin won't look too kindly on me linking to them, but off the top of my head, you could move to Resolve, Avid, Vegas, FCPX. If, for some reason, you think you'll be better off running on ancient, rickety 32-bit software that can't even play MP3s back properly, you can always export an XML out of Premiere and move back to FCP7. Again, don't get me wrong. I'm SUPER unhappy with the clusterf*** that is CC, and we are piloting a couple of different solutions, so we can move away from CC. The reality is that if we want Adobe to actually pay attention, the only real recourse we have is to speak with our wallets... ... View more

The biggest mistake I made was leaving Final Cut Pro.  It is not time to go back. Come on, now, that's just silly. I've got FCP7, MCA6.5 and PPro all running on our systems; I have to bounce around between them, depending on client needs (although I only find myself cracking open FCP7 for legacy projects, these days...). To be quite frank, would rather plunge red-hot needles into my eyes than have to edit anything other than a quick 30sec broadcast spot on FCP7. Having to render or every g*****mn thing is TORTURE, never mind all of the other stupid little idiosyncrasies with FCP7. ANYway, the continued problems with RED footage are kind of worrisome... I've got a project coming up in late September that will have a partial RED workflow. I was hoping that this would be sorted by then, but that's looking less and less likely. I may have to bundle everything up and do the final exports on my home PC.  😕 ... View more

TCmotion wrote: I don't know if a sigh is warranted there- 10.10 is still in early beta. Not really fair to expect full compatibility, especially from third party developers. Save your sighs for if we're still seeing these problems after release… Totally fair. 10 weeks out from golden master, and I'd hope that the OS would at least be capable of launching major 3rd Party apps, but maybe I'm expecting a bit much. I'm not a programmer, so take that for what it's worth... ... View more

*sigh* Mac OS X 10.10 Yosemite and Premiere Pro ... View more

Marta Chevanne wrote: Is it working? Any NEW issues? I think I'm going to wait some days before installing this update (everything is working just fine for me right now...). Smart move. Personally, I won't be updating unless I find something broken with the current version. My faith in Adobe and Apple is at an all-time low right now... ... View more

Believe me, I know that this is probably the sh***iest of all possible solutions, but is it still possible for you to return your Mac Pro? We were literally a few days away from returning ours when the 10.9.4 update dropped. You only have a two week window to return the hardware, but we called up "Genius" tech support (*rolls eyes*) and yelled at them; they agreed to extend the grace period by a couple of weeks, so we could wait a little bit longer for a fix to be implemented. Our reasoning was basically "[expletive deleted] if you can't make a product that actually works, then give me my money back"; the plan was to return the box, then re-purchase once the problem was actually fixed, or look into alternatives. Luckily (hah, "luckily"), we wound up not having to worry about it, but we were reeeealllly close... Both Apple and Adobe don't seem to realize that there are other options out there; their customers seem frustratingly willing to put up with the piles of [expletive deleted] both companies are all too willing to serve up. It may not happen soon, but eventually people will walk away... ... View more

I can't wait to see what Yosemite breaks... Looks like the safest bet is to take a page from the ol' Avid MC 2.7 handbook: if things are working properly, NEVER UPDATE OR INSTALL ANYTHING. ... View more

Yuuuuup. I couldn't be happier with my decision to build a custom PC rig vs. buying one of the new Mac Pros... ... View more