@tylerknight

First, good idea is to use Premiere CC topic so more people can see it.

Second, most probably it is related either to encoders installed in your system or to your sound card.

It is known issue with CS6, but as I remember there is still no general solution. I was hoping that they will fix it in CC. Some solutions have worked for some people, but for others problem persists. It happens with some codecs (AVC e.g.) and no problems with others (ProRes).

Huh, It is frustrating. Is it imposible for you to transcode and replace the footage?

@tylerknight I'm on Premiere Pro CC and used CS6 before that on Windows 7 machine. No problems for me when editing. I may have experienced an error with an audio clip dropping out after I exported and burned a BluRay disc. Does this error also occur when exporting files (I used (MPEG 2 - BluRay file format)?

I would lodge official complaints with Adobe and request upper level technicians to guide you through a thorough diagnosis over phone. If that can't fix it, I'd say it's time to switch if you're doing serious paid work. I happen be one of those people who like Adobe products and Creative Cloud, but if was getting those errors...and if Adobe techs can't fix...I'd be gone with the wind. FCPX or FCP7 maybe. Davinci Resolve Lite to color grade maybe.

Sounds like a real bitch of problem. Best of luck with quick solution.

@tylerknight ... sympathies. Hell of a problem to have.

Yet ... Adobe is clearly quite aware that a few out of the several thousand users have the problem ... as the staffers on the Adobe forums (who, btw, participate there on their own time as that is a user<->user forum) have acknowledged over and over. Yes, "a few" can be several hundred in the kinds of numbers they are talking about. They've constantly tried to fix whatever things they can find that can be fixed. This is apparently something that's a mix of hardware/combinations, codecs/combinations, and which Tuesday your mother's aunt washed her clothes. It drives their coders nuts. And as noted by several above posts in this thread, they're not having the issues, or have had it intermittently and or had it go away.

Very few (proportionally) computers have this problem. This is why they've frequently asked for complete log reports & that sort of thing, including wanting to remote-task with users with the problem as most of the time NONE of their 'staff' computers can be even caused to develop this. If you can't replicate, you can't isolate the code or other issues to fix. And when they've found one bit that they can isolate, it's frequently been a very "local" issue that only appears with the right mix of several different (and some very puzzling) factors.

So all this is to say it's a huge bummer for those like you that have one or several of the problem "childs" on your computer ... and as yes, it's been a long-time hanger-on issue for some, no one can guarantee a fix. So sadly, you might need to consider switching software. Not because Adobe's ignoring the problem, but because they can't guarantee a fix.

Like when Mac just released their latest OS, which caused a lot (but certainly not all) Mac users with AJA, Kona, & Blackmagic & high-end Nvidia (especially Quadro's) video cards to have mega-issues, which they were demanding that Adobe fix. The problems came about because of changes in the OS software that hadn't been "shipped" to Adobe to know about ... and for a bit they had a hell of a time as Apple wasn't particularly interested in helping with the problem. SOME Mac's with the oft-affected cards worked fine ... some had issues but they could find a work-around, and some basically puked. They've got most but not all of those issues fixed judging by forum posts.

Neil

I have asio drivers that came with it can you direct me to some others perhaps??

@tinbeo

I have tried that hundreds of times literally haha I have tried everything the internet and adobe have told me to do and nothing has worked. This is on multiple versions of premiere as well as several different systems with different processors, gpus, etc

I find it interesting that the Adobe staffers say they seem to have an excellent relationship with Apple still, and when things come up they get fairly quick attention from Apple to help solve things. Yet ... every flipping time there's a tiny-dot update to the Mac OS, a ton of people get mangled trying to use Adobe software for video editing. And then over a month or so most get "fixed" though at times Adobe has bluntly said to roll back to "Os ?.?" as they can't guarantee smooth operation with a different/newer version.

Coming from the PC side where we always used to have "inferior" OS & even hardware drivers, it's ... stunning ... to see how damn difficult the whole Mac side has gotten over the last year or so vis a vis Adobe DVA's.

So ... for those on the MAC still having issues, you might search about rolling back Mac OS for using with Adobe products. There's even official Adobe blogs that discuss this.

Neil

@DrDave

One last thought--90 percent of the people who report problems are those who immediately apply an update when it comes out. Most of these people, if asked, would probably say it is better to wait until the chaos and wreckage has been cleared. But, if given the choice, they invariably choose to be in effect beta testers, and wade into the chaos and wreckage.

You're obviously not an Adobe CC subscriber - everyone knows that CC updates are automatically downloaded and installed on release, and there is no such thing as reverting back to a previous version. That's just one reason why I'm still on CS5.5 with no regrets.

However, Adobe's worst Achilles heal on Windows is Apple's shameful failure to produce a 64-bit upgrade to QuickTime. It doesn't matter how many gigs of RAM you have, if you pile enough layers on an After Effects project it will eventually lock up with a QT32 memory fault. Then you Ctrl-Alt-Del into Task Manager, kill the QuickTime process, AE revives and you can save your project and reboot.

@lpowell I turned off the updates and have not installed the latest update because I heard people were having "problems." I've heard of ppl reverting to a previous version, so I figger it is possible, but I just use the disk image if I need it, and then I don't have to worry about "leftovers."

Totally agree with you on quicktime--it is seriously the pits.

@tylerknight another thought on dropouts, are these actual dropouts that you see in a DAW or is the program just complaining that there are dropouts?

Yea, they've changed a few things. It's theoretically an amazing idea, being able to use say a standard PrPro project file and work it "seamlessly" in a grading, effects, audio, or other graphics programs without need of exporting or going through the whole XML/EDL/proxy/online-offline/intermediaries process. And for when it works its wondrous.

There are a few kinks still, to be truthful. Updating versions within a major project's work-up, is clearly not a wise thing to do. The change from 8.1 to 8.2 was rolled out as a simple "dot" upgrade, but there were some major re-working of code and process in many places and that hammered some people. They've apologized for that on their forums.

Also many of their staffers who normally are regular presences on the forums for PrPro, Ae, or SpeedGrade ... are nearly non-existent but for a few comments now & then, which ... also given the timing of NAB in Vegas early next month ... leads me to believe they are trying to hammer a few kinks out of the works to announce at NAB. Looking forward to seeing what they've got.

As it is, I'm functioning pretty good in my one-man operation at the moment.

Neil

@DrDave

Intriguing company. Many moving parts shall we say? Very human in final ... effect. Some decisions seem (as a user) to have been very wise. Some bits & pieces seem ... not quite there? Some things can become very problematic for X number of users on Y OS with Z video card on the first Tuesday of spring.

That concatenation of interests, capabilities, responsibilities, and things out of their control keeps life ... interesting.

Yet I'm not complaining too much. I'm doing that whole Direct Link think betwixt PrPro & SpeedGrade rather slickly such that I do so appreciate the integration of their apps into a "workflow". It's not perfect but for my needs, far easier than anything else.

Neil