Sounds like you need a reinstall. It should not take that long merely to create a bin. Can you try that? cornelius_3 wrote: I have the latest version and the latest MacBook Pro 15" everything maxed out and Premiere still has a lot of issues with importing footage.   It takes 30 seconds to 1 minute to create a new Bin.   That is just stupid, to create a folder it takes a minute but when I hit spacebar video footage plays back immediately?    Buggy at best. Oh and if I import multiple folders it crashes premiere if there are RAW CR2 images in the folder.  Premiere sucks at indexing. ... 더 보기

Can everyone with a performance problem try this and see if it works for them too? Thanks! Thomas Mikel wrote: SOLVED FOR MAC!!! My ealier OSX was Lion (10.7.x). Now I installed OSX Mountain Lion (10.8.x) and it didnt help at all. Then I uninstalled the adobe programs and reinstalled and it worked like a charm. Rendering is fast, no jittering while playback etc. Just like it should be. Earlier a editing friendly video clip (ProRes) with a title on top of it wouldnt play realy time. Now I have multiple heavy filters on the clip and it plays back real time without any problems. Like I said, just like it should be. ... 더 보기

bhansonwdsc wrote: And I guess I should have added that I really need to be able to attach separated caption files to individual video clips rather than just one for the whole project. So that would be another feature request. Am I the only one that needs to do this? Thanks. No, you're not. Keep those feature requests coming! ... 더 보기

Sounds reasonable. Can you file a bug report?  Updated link (3/19): After Effects: Hot (1390 ideas) – Adobe video & audio apps ... 더 보기

WShawn wrote: Did you have an opportunity to check my project file?  I can find no combination of settings that duplicates the behavior of the old Lens Blur effect.  Yeah, I checked it out. Here's what I came up with. You don't want to crank up the Blur radius too much or you will get that halo problem. Does this work for you? ... 더 보기

Hi Shawn, It is behaving as designed. You might try adjusting the Blur Focal Distance (Blur Map) and the Blur Radius for better results. The Camera Lens Blur effect is much more accurate than the original one, though you certainly do need to adjust parameters according to the particular shot. See what Ash Beck says about the Camera Lens blur effect at 2:22 in this video: http://tv.adobe.com/watch/ae-me/ae-me-ash-beck/ ... 더 보기

BlueScarecrow wrote: Hope? Hmmmm. I was hoping to make a career for myself in video production. I invested 10 years and thousands of dollars in Avid and got the same runaround that's evident on this forum. Everytime the software crashed Avid told me to buy something else; that same thread is evident here also. For a huge conglomerate like Adobe, with all of it's resources, to sit back and hope to find, wish to discover or stumble across a solution is absolutely unconscionable. Pardon me, I didn't mean to say we hope to find a fix. We have a fix. We are just waiting for third-parties to fix their stuff, so we can fix our stuff. Let's hope it gets into an update or CS Next. In the mean time, yep, file a bug report: http://www.adobe.com/go/wish ... 더 보기

Keith Moreau wrote: Kevin, thanks for your post. Wow, I posted this 7 months ago and the spanned AVCHD problem still isn't fixed in CS 6? That's incredible. Tell me I'm misinterpreting your answer. Thanks much! -Keith Hi Keith, As an editor that came into the world of software engineering, yes, it is incredible how long things take to fix, change, or upgrade. As I mentioned, sometimes there are road blocks that we have no control over, so that takes more time. This is on my Top Issues list, meaning that it is a top priority for the community. Again, I'm sorry this issue is affecting so many of our users. ... 더 보기

BlueScarecrow wrote: AVCHD files will never be supported by Adobe until it becomes profitable. Until then they will spin and dance and tell you your computer processor is too slow, or you don't have enough ram or you have the wrong operating system or you have to transcode or buy some more software or hardware... Just like Avid. I lost thousands of dollars with Avid and wound up throwing my Avid Media Composer in the garbage. Funny... there it seemed to fit fine. Complacency and greed killed Avid and now it looks like complacency and greed have their sights on Adobe. Remember: There is a season for all things. I wish you could see how hard we are working on this problem. When there are issues affecting a lot of our customers, we definitely know about it. If that issue is taking a long time to fix, know that there are often times other parties holding up the show. On behalf of Adobe, I apologize that this problem is persisting. We hope to find a fix as soon as possible. ... 더 보기

benwinter wrote: I'm very glad to hear of all your successes on PC machines. I switched to Mac three years ago. If anyone recommends to you switching as well, it wasn't me, I'm not that duplicitous. Yesterday I was dragging a clip to the timeline (an innocuous action I assumed) when this greeted me EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Check your CUDA drivers. Also look at this thread: http://support.apple.com/kb/HT3773?viewlocale=en_US&locale=en_US benwinter wrote: Before that, Premiere was crashing until I deleted all my media cache files. Two cups of tea while I waited for conform files to rebuild. Necessary sometimes, as media cache files can become corrupt. benwinter wrote: On the 11th of December Premiere crashed four times with EXC_BREAKPOINT (SIGABRT) because, well who knows, maybe I looked at it funny. A clean reinstall of OS X, then reinstall your CS6 apps. Those steps should fix this. benwinter wrote: Then there was this problem, until Adobe finally patched it http://forums.adobe.com/message/2767953 (Audioprefetch.cpp crashes Premiere) Great! benwinter wrote: And this one http://forums.adobe.com/message/4551305 (Mac Serious Error) The "Mac Serious Error" thread is a serious error itself. It has problems Mac users have had that are unrelated to the Serious Error warning. This problem should be fixed as of Premiere Pro CS6 (6.0.2). If you are still getting the Serious Error warning, please file a bug report: http://www.adobe.com/go/wish benwinter wrote: More on that kernel panic http://forums.adobe.com/message/4522951 Cineform files crash Premiere when loading thumbnails in the bin, that still hasn't been fixed as far as I know—although Adobe and Cineform were apparently "working together"—and was the reason I said au revoir. Have you filed a bug report? http://www.adobe.com/go/wish Thanks. ... 더 보기

benwinter wrote: Brand new Mac Pro 2010, I suppose not so new anymore. A quick look through my console log shows crashes of all different flavors over the past week or two. A while ago I started touching Cmd+S after almost every edit. If I lose a particularly large amount of work or multiple failures in a row I usually go make myself a cup of tea. I go through a box of Tazo in about 10 days. Zen is my favorite, then peppermint. Give us more details about your system, please. ... 더 보기

Export the original file from Apple Motion with an alpha channel using the Animation codec. In the mean time, I'll take another look at the bug and make sure it has been looked at. ... 더 보기

7marcin wrote: It's Adobe. Do not expect their software will work as you would expect it to.... and they will not fix bugs - you have to buy new version... 7marcin, That's not true at all. With CS6 we've had two patches: 6.01, and (6.02, 6.03). Info on 6.0.1 Info on 6.0.2/6.0.3 Do we fix ALL bugs? No, that's impossible. We prioritize based on a number of things, a chief one among them is the bug report/feature request form: http://www.adobe.com/go/wish ... 더 보기

I don't think so. Please file a bug report: http://www.adobe.com/go/wish ... 더 보기

Activation issues may be preventing certain importers from functioning correctly. That is why Jim suggested that solution, and I agree with him. It's the first thing I would try. Thanks! ... 더 보기

cavisto wrote: Soooooo ridiculous that Premiere cannot do this simple task.  We just upgraded to CS6 mc, a good $2k later and we still don't have broadcast needs met.  We broadcast in over 15 million - TV stations and cable head ends- they will not even talk to us if we don't have CC.  ADOBE!!!  THIS SHOULD BE PRIORITY #1!! Just let us output to file with CC!!  Please!! Make a feature request then: http://www.adobe.com/go/wish Thanks! ... 더 보기

Gerry, Indeed, it appears that he alpha channel exists in FCP, but not in After Effects or Premeire Pro. How strange! I'll file be sending this to the teams right away. Thanks so much for sending me the files. ... 더 보기

So this is an exported file? Sorry if I made any rash assumptions. Typically, this problem stems from an alpha channel not being exported. I'd like to get my hands on that file to see if there's a bug we don't know about. Can you send to me? I'll PM you with my contact. ... 더 보기

Yes, the Animation codec will also export with an alpha channel, as you found out. It's a much, much larger file size over ProRes 4444, however. I came to the conclusion when I saw your Motion project inside FCP7 with the alpha. I'm assuming it's not a rendered file, but the Motion file sitting on the Timeline. Yes? When viewed this way the alpha channel is interpreted automatically when used in a FCP project. When you export the file, the alpha is lost unless you do so with an alpha channel. That's all I'm saying. No matter, it looks like you fixed it. BTW, I was on the FCP team for FCS1 and FCS3 at Apple, so I'm very interested in these cross platform topics. ... 더 보기

As I suspected, the graphic was not exported with an alpha channel. It appears that Apple has changed the export dialog box. For export, choose ProRes 4444. Then go to the render tab and choose Color > Color + Alpha as described in this video: ... 더 보기

Are you sure that the very same file exhibits transparency in FCP but not Premiere Pro? It sounds like you don't have an alpha channel in that file. I just created a file with alpha, exported it from Premiere Pro CS6 with the ProRes 4444 codec and it works as expected when imported back into Premiere Pro or After Effects. Where was the file created? How was the file exported? If it was exported from AME, was it exported with 32bit color? Was the render at maximum bit depth checkbox checked? If exported from QuickTime did you have the Millions of Colors+ option enabled? ... 더 보기

muzflowers wrote: 6.0.3 update does not fix this problem too. 6.0.3 was a Windows only update and only to solve a security certificate issue. No other features were added or bugs fixed. If you have the problem that preview files are not being used, please file a bug report: http://www.adobe.com/go/wish Thanks! ... 더 보기

That's a pretty complicated effect requiring rotoscoping. Typically, jobs like this are done in After Effects. Do you have After Effects? If so, see this introduction on rotoscoping: http://helpx.adobe.com/after-effects/using/animating-shape-paths-masks.html#rotoscoping_introduction_and_resources ... 더 보기

A bug has been filed with engineering. They're looking at it right now. More news when I hear it. Thanks! ... 더 보기