For the web, you might try a preset for Vimeo or YouTube. The whole process is outlined on my blog: Exporting media using Adobe Media Encoder CS5, CS5.5 and CS6. For festivals, you'd need to know their precise specifications as they vary widely. For example, here's the requirements for output at Sundance: We accept Film prints in 16mm or 35mm format, digital video on Sony HDCAM tape and DCP. For 35mm film prints, we screen 24fps in aspect ratios of 1.37, 1.66, 1.85, or 2.39. We accept sound formats of mono, stereo, Dolby SR and Dolby SRD (Dolby Digital). For 16mm, we accept prints in 1.37 aspect ratio with mono optical sound. For Sony HDCAM tape, we accept HD 1080 format in the following frame rates: 59.94i, 23.98psf, 25p, and 50i. If your video image is 4x3, 1.85, 1.66, or 2.35/2.39/Scope you must have it pillarboxed or letterboxed during the lab transfer for it to be screened without any image distortion. For HDCAM sound, we require LtRt or Dolby Pro Logic compatible stereo mixed tracks on channels 1 & 2. Optional: DolbyE onchannels 3 & 4 (not all theaters are equipped for DolbyE playback). DCP must be DCI compliant, keys must be open for window specified by festival, and HDCAM or 35mm backup copy must be provided in addition. DCP will only be accepted with prior approval. Please note that these specifications are subject to change each year. ... 더 보기

ascreenwriter wrote: Hello, I've just finished shooting what I am considering to be my directorial masterpiece.  Shot it on the Canon 5D (1080p, 24fps), and the footage looks amazing.  Now I am ready to start editing and have been using premiere lately, but I have yet to figure out the proper pipeline.  I want to know the best way to retain resolution before I delve into this project. My questions: 1)  What is the best way to start a new project and import the footage without having to render whilst editing, so as to retain all resolution and originality of the source footage? 2)  What is the best way/ codec/ format to export this same footage once editing is complete so as to retain that crisp 1080p for which the 5D is so recognized? 3)  What is the best way/ codec/ format to import and export/ render between premiere and after effects?  I am speaking mostly of vfx and color correction.  I also have some 30fps footage that I intend to slow down in AE and then import into premiere. I know this is pretty broad, but as a solo filmmaker I really need someone's guidance.  I rarely ever finish my films with the same, crisp look as the footage.  I need pipeline help, and really appreciate it! 1. Follow the advice above. Also use the Media Browser to import the footage in case you have spanned media files. Import files with the Media Browser. 2. It largely depends on what you wish to ouput to: Blu-ray, web, etc. This FAQ gives the best answer: What are the best export settings? 3. Use the Replace with Adobe After Effects Composition function. ... 더 보기

Neonhigh wrote: Hi Kevin, here some links of people having the same exact problem in other forums, including my reduser discussion where you can find some useful tips related to the subject: Hi Neonhigh, I've noted your case and will make sure the product team is aware of this as a top issue. Neonhigh wrote: Thanks for getting back to me. It was getting quite frustrating to not find any information on this matter. Yes, the problem is that there are multiple causes for this problem. For that reason, it's tough to pin down. Neonhigh wrote: I noticed that a new article in now available on Adobe's website. http://helpx.adobe.com/premiere-elements/kb/error-error-compiling-movi e-render.html I'll take a look at it as well thanks That's for Premiere Elements, unfortuantely. ... 더 보기

Ray Tragesser wrote: I am looking to load some native raw files from the new Blackmagic camera that happen to be in the raw CinemaDNG format. Trying to stay native here if possible. Thanks Ray Here's everything you need to know about the current state of Cinema DNG and Adobe: http://blogs.adobe.com/aftereffects/2012/09/cinemadng-in-after-effects-cs6-and-elsewhere.html ... 더 보기

irieger wrote: I filled a bug report. It is definitely a bug. DNG stills are also not importable. DNG handling of all important apps of the Suite was the reason I bought the Produciton Premium. In CS5.5 - I had only Premiere otherwise I wouldn't have bought the CS6 suite - I was able to include DNG files to my timeline so I expected it to also work in CS6 of course! To be clear: It's not a bug, it's a feature request. The experimental importer was on our Labs site, not natively installed. I am sorry you got caught between a rock and hard place, though. ... 더 보기

Jim Simon wrote: Weird that CS6 doesn't support cinemaDNG natively in Premiere. Right?  That's like Windows Media Player not supporting WMV files. Again, if you really want this go for a feature request. ... 더 보기

This looks like a great FAQ. I'm going to move it over there. ... 더 보기

Hi Neonhigh, If you are going to color correction, why do you need an output? Aren't they color correcting the native files? I need an output as reference for the VFX department, I need an output for the sound designer, I need an output for the producer, I need an output for myself and to send to my girlfriend. The question I should ask you is, why shouldn't I need an output? What's wrong by exporting my timeline in a format that is not r3d files for reference and production management? I was talking about color correction only, as they usually only need the native files. Of course, an output would be necessary for all the other things you mentioned. Nothing wrong with that. Neonhigh wrote: If you need an output for some reason, why are you rendering at all? As I explained I simply rendered because the software was having several random "Unkown" problems in exporting. I though rendering and exporting a file matching the timeline settings would have solved those annoying Unkown Errors, giving me at list an export based on the render sttings. Problem is that PPro CS6 fails also to render the timeline, and I needed to break the process in 30-40 segments in order to achieve a complete rendering. Rendering in Premiere Pro is primarily for playback, and not necessary for output. In fact, it's a waste of time in most cases. Render files are typically not used for an output unless you explicitly want to do so. Typically they are lower resolution "preview" files that you don't want to use. Regardless, you should have no trouble rendering sections of your Timeline. Are you updated to Premiere Pro CS6 (6.0.2)? Can you try an export without rendering? I wish PPro CS6 was reliable enough to allow me to simply export. I still did not solve the problem. Several people from the redusers forum are trying to help me as and they all ran into the same issue. Currently this are the issues: - PPro does not render the entire timeline I'm trying a test project right now and so far it is rendering OK. Can you point me to the reduser forum post where people were giving you assistance? - does not output the entire timeline (if not chopping it in 12-15 parts) I'll test that, as well. You should not have to segment the sequence in order to get an export. - Project Manager does not trim the project to pass it to over post prod facilities. Sorry, the Project Manager will not consolidate every media type. It will copy, however. This would be a feature request or bug report: http://www.adobe.com/go/wish Beside questioning me with why I want to render or export my project, Not questioning your capabilities or talents, I just wanted to know what you wanted to do, and why. Typically, most people don't render as much in Premiere Pro as they do in other NLEs and I was wondering why you needed an export to go to color correction. That's all. Many users in this forum (as well as on the entire internet) experienced th same Unkown Problem: http://forums.adobe.com/message/4661398 There could be many different variables which can cause that error. The troubleshooting doc you found addresses many of those. I will add the "Unknown Error" warning to the document. There is no "single fix" for this problem, I'm afraid, and these are our opinions and solutions on the matter. A legitimate gripe would be that the error is too generic, and I would agree with you there. The error should contain more details about how to remedy your issue. Please make a feature request for more descriptive error dialog boxes: http://www.adobe.com/go/wish I will also mention it to the product team. I understand that, being an "Unkown Errror" Adobe does not have a iniversal fix, but please don't ask me why I want to output my timeline. Again, I was only asking in the context of color correction. Of course, you want an output for various reasons. I've written up your bad experience in my case notes and I'll do my best to get you some better answers to your questions. You definitely should not have to jump through hoops to render or export a .R3D sequence. Neonhigh wrote: Here is a temporary fix for who runs into this problem: Yesterday, after trying everything I could think of I simply exported an XML, opened it in Final Cut Pro and exported all the files and formats that I needed. No Unknown Errors. Thanks for the workaround. I'll add it to my notes. ... 더 보기

If you are going to color correction, why do you need an output? Aren't they color correcting the native files? If you need an output for some reason, why are you rendering at all? Can you try an export without rendering? ... 더 보기

Is the framerate on the camera set as "variable?" ... 더 보기

PixelshotWDC2 wrote: Thanks. Feature request time. Good idea to map for lefty. You want to be able to turn on snapping for every edit point? Yes, make a feature request: http://www.adobe.com/go/wish ... 더 보기

Sorry you are having trouble LeccyNeil, Why is this happening now? It could be a number of reasons, unfortunately. Please go to Help > Deactivate. Exit Premiere Pro. Launch Premiere Pro and choose Help > Activate. That should help. I really don't recommend copy/pasting old codecs into a CS6 build. Still having trouble, file a bug report: http://www.adobel.com/go/wish Thanks! ... 더 보기

Paul Joy (UK) wrote: Hi Kevin, thanks for chiming in. Can you confirm the behavour of the known bug? Would it result in the whole card no longer being recognised as Canon XF footage or are we talking about separate problems here? Paul, I see you are on Premiere Pro CS6 (6.0.2) and bugs have been fixes regarding spanning in that version. Let me look into this a little more. ... 더 보기

Ah yes, the User > Library is now hidden from users. Thanks folks, I'll update the docs with this info. ... 더 보기

BigBrennan wrote: You know the saddest part of this is Adobe has been downright evasive about responding to this issue.  I've had 3 calls with techs who offered no help, no answers, or my favorite, insisted that I was doing something incorrectly.  Adobe keeps trying to close my help case without offering any additional assistance.  I've even been emailing a tech directly as he gave me his direct email address and now he has become totally unresponsive. My work around is using an external recorder that captures to pro-res files or using an old laptop to edit that has CS5 installed on it.  Also been editing in Avid until Adobe figures out what's going on Sorry, I can respond. It appears that Canon XF footage that is spanned had a bug in Premiere Pro CS6, however there were some fixes in the Premiere Pro CS6 (6.0.2) update. Can you confirm that you are on the latest version? If you are still having trouble, file a bug report, if you can: http://www.adobe.com/go/wish ... 더 보기

I have this doc: Create clips for offline editing. Beyond that, make afeature request: http://www.adobe.com/go/wish ... 더 보기

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 ... 더 보기