Slow rendering from PPro in AME

Just updated all my CC apps and using Premiere CC 2014. Created simple output sequence and rendered it out in simple 1080i, H.264 Quicktime preset and only one CPU seems to be processing. Preferences are for CUDA processing as it's always been. Used to get almost faster than real-time rendering and saw 60 to 75% CPU utilization. This one took nearly 5 times real time to render.
Have dual processor Dell T7600, 32gigs, dual XEON 2.3GHz, Win7 Ultimate, NVidia Quadro 6000 (driver date 8-4-14, version 9.18.13.4066) Could Quadro driver be problem?
I am getting black screens occasionally when openning or shifting from media browser and/or Bridge back to Premiere.
Matrox MX02 for display monitor.

Seems to be OK today. All processors churning at about 70% for an H.264 1080P clip. Life's good. rg

Similar Messages

Slow rendering from DVCPro-HD to MPEG2-DVD?

I have a home built PC with a quadcore 9450 chip, 8GB ram, Vista-64 Business, Mercury rendering (GTX460) - so it's not a particularly slow machine. My current project is 2 hours, 45 minutes long, shot on DVC-Pro HD 720-30P. It is one continuous take from a concert. I've added chapter points for each song, but otherwise have not edited it (besides mixing the audio levels.) With CS5, to export to MPEG2-DVD (VBR-one pass, quality level 5) takes about 16 to 17 hours. A friend with an i7 computer (which I built for him) says I need to contact Adobe because it should not be taking that long to render. If I import the Premiere sequence directly into Encore, that render takes only a few hours (not sure of the exact time) but the quality sucks. My 17 hour render looks pretty awesome for such a long project. With CS4 and a similar length project, it was around 7 or 8 hours with the same machine. Is something wrong, or is it normal for such long render times?

If I understand it correctly, your time-line is 2:45 (hh:mm) long and takes around 17 hours to export. Correct?
That is pretty good for a Q9450 with 8 GB RAM. Those systems are on average around 15 - 20 times slower than a fast system with MPEG2-DVD export, so it would take a fast system around 1 hour. Now that looks like a perfectly acceptable figure. You have to keep in mind that with hardware MPE you can only compare that with CS4 export times with MRQ (Maximum Render Quality) turned on, and my guess is that you are comparing it to CS4 times WITHOUT MRQ.
Have a look at the PPBM5 Benchmark and notice where the Q9450 systems are. They are all pretty close to the bottom of the list.
Seeing those results, one can argue your statement.
so it's not a particularly slow machine.
Of course much depends on your particular time-line, but if I take my benchmark results (with a lowly i7-920) versus another Q9450 system, I guess that my export times with your time-line would be around 1:06.
Maybe not the reaction you were looking for, but I can't change statistical results.
@ Colin: The OP never said he has MRQ enabled. Where do you get that from? He said he had hardware MPE enabled. And with his timeline, setting MRQ on would not influence his export times, since there is nothing in his single track time-line to profit from MRQ and it is all handled by the MPE engine. At least in this case.

Frameserving from PPro CS6 to Handbrake?

I've been trying to figure out how to use Debugmode Frameserving utility with Premiere Pro CS6 and I seem to be missing a part of the workflow.
I'm not impressed at all with any of the h264 encodes I've been getting from PPro/AME CS6 aftering having seen the quality first hand of SONY Vegas Pro 13 frameserving to Handbrake - the final renders are jaw dropping in image quality and put the renders from PPro/AME to shame IMO - especially at lower bitrates.
I have the frameserving utility installed and can see it as a render option in PPro when exporting media but when I try to open the signpost file in Handbrake it throws an error message saying I need to first scan a source and setup my job before starting an encode.
I've been looking for days off and on trying to find a workflow solution but so far I've come up empty. Any suggestions outside of creating a master render and then hoop jumping over to Handbrake? Trying to streamline my workflow in Premiere Pro. This is beginning to become a major factor in whether I continue using Premiere Pro or not as I deliver ALOT of h264 MP4's to the production houses I work with for client work.

im not defending premiere here, but most software will use h264, which is locked down by several standards and committees/groups for hardware implementation. this wont change for any NLE unless they have access to x264 which is a separate community project. they are not restraint by the h264 standards and therefore are able to advance it past h264. i've used frameserver in the past, but not with premiere, so i dont have any tips to help getting it to work with premiere.

AVIs from AE need rendering in PPro

I'm an AE novice, so this is probably something simple. When I use AVI files from AE compositions in Premiere Pro, they require rendering (have the red line above them even where there are not effects or transitions) while AVIs captured from my camera or generated by Premiere Pro's "Export Movie" do not. A second render is a waste of resources and probably a loss of quality, so I'd like to get things configured so that PPro is happy with my AE-rendered AVIs the way they are.
My PPro project settings are DV NTSC, 29.97 fps, 720x480, pixel aspect ratio 0.9, display format 30fps drop-frame. My AE project settings are Timecode Base: Auto, NTSC: Drop Frame. I'm sure there is simply some setting that isn't matching, but I'm not sure what it would be. A lot of the terms in the Render settings are unfamiliar to me, so I don't know which ones would affect this issue. If it's relevent, the AE project I'm using was originally made in AE 6.0 and recently opened in CS4 and re-edited. Both AVIs that were made in 6.0 and the new one I just made in CS4 do the same thing in PPro (whose version is CS3, if that makes any difference).

Mylenium said:
AE does not support multi-frame temporal compression as required by many compressed formats, so the quaality will often be terrible, and secondly you will not get access to the DV CoDec such as used by Premiere. You may choose Microsoft DV and others, but in essence you'll be back to square one as those will laso require to be rendered/ transcoded in Premiere's timeline.
Sébastien Périer said:
Your workflow is one of the most used between the two apps, but it is
not automatic, you still have to match the 2 aformentionned points.
The impression I got from Mylenium's post was that even if I chose Microsoft DV as the codec, it will still require rendering, and also be lousy quality. I know that there are many "lossless-only" purists out there, but I am satisfied with the normal type of DV compression even for two or three generations, even though it is technically lossy - my final format is MPEG2-DVD, which is much more compressed. But if it didn't do any multi-frame comparison for its compression... Anyway, Mylenium scared me away from even trying to change the output settings, as it sounded like it would not solve my problem at all. But after reading Sébastien's post I decided to try it, and at least at first glance it appears to work fine - the footage goes on the PPro timeline without the red "I need to be rendered" bar, and at least on my screen the quality looks okay to me - I see no visible artifacts. I don't know how to tell if it is doing any frame-to-frame comparison, or how much harm I might be doing to the quality of my final DVD data by doing it this way, but it sure works faster!
...don't be confused with lossy & lossless codecs.
Don't worry, I understand that - a simple example is JPG vs. TIFF, as both compress but TIFF is lossless. But I don't know the subtle differences between different video codecs, and until yesterday I didn't know about the output settings in the render queue pane of AE. (Since everything else I have worked with on this Windows machine has always used Microsoft DV as the codec for AVI's, I was lulled into the assumption that that would be the default in AE as well.) If Mylenium is right that AE's output functionality for that codec is not as clever as that in PPro, perhaps this method will come back to bite me, but meanwhile, it looks like it will improve my workflow tremendously. Perhaps if I re-render my current clips it might even reduce some of my memory problems in PPro - right now, about once an hour or so I get a complaint from PPro about limited memory (or runtime error messages) and have to reboot. [In case you are tempted to ask, I have 2GB of RAM and have my paging file set to a fixed 8GB, but I'm still running out. I don't have that much AE footage yet, but I will be adding more.]
If my current settings (Render Settings: "DV Settings", Output Settings: "Microsoft DV") are not really the same as the normal Microsoft DV that I use for everything else(even though they are accepted as native footage by PPro), please speak up again. I won't delete the lossless versions of the clips (which are about 8 times the size of the DV ones) until I'm sure I won't regret changing my workflow.

Rendering from QT-DNxHD to other codecs causes black spots in the highlights. Causes?

Using a windows 7 pro machine, i7, 24gb ram, Nvdia GTX 570.
No other codecs that I have used have ever caused this issue. I am rendering from DVCPRO through an AE - 16 bit - rec 709 timeline to 10 bit QT-DNxHD (No problems at this point). I then edit in PP. No signs of problems at this point. From there I export via AME to AVI, H264 and Mp2 DVD. This is where it gets bad. All clipped highlights, coming from PP through AME, have black spots in them.
I have never worked with DNxHD before. I have heard good things and wanted to try it as a mastering codec. I'm sure this is not suppose to happen... am I doing something wrong?

Hey Jim, AVI is no spring chicken either....
Audio Video Interleaved (also Audio Video Interleave), known by its initials AVI, is a multimedia container format introduced by Microsoft in November 1992 as part of its Video for Windows technology.
As much as I dont care for its slow export time from PrP, QT is till a widely adopted stamdard by both consumers and professionals alike. I may have my preferences now for other workflows, but when dealing with clients and others its still the dominant and preferred wrapper of choice.

Slow rendering on rMBP when display is off

I'm batch rendering Premiere Pro CC timelines to MPEG 2.
These are 3 minute movies that take about 30 minutes when I render them direct from Premiere Pro CC.
When I queue them in AME the rendering goes slower.
Renderings then take up to 40-50 minutes. So in AME it's slower. But these times are do-able.
The rMB from late 2013 is blowing like hell (that's a good thing becuae then rendering goes fast). But when my display turns off after 15 minutes the rendering slows down. Renderings then take up to almost 2 hours per movie. The blowing of the fan stops when the display is off. But apparently the rendering speed as well.
In the preferences panel from the Mac "put hard disks to sleep when possible" is unchecked.
Of course I can have my screen always turned on. But another rMBP from mid 2012 has burn-in issues because of that.
So I'd rather have AME working when the display is off.
Could this also be an Open CL thing?
**UPDATE**
Rendering also slows down when minimizing the AME window!! It has to be active otherwise my rendering slows significantly down.
I hope there is a solution for this

Go to System Preferences>Energy Saver. Set the slider labeled "Computer Sleep" to "Never". When the Computer is sleeping, all currently running processes are put on pause. Your "Display Sleep" and "Computer Sleep" were probably both set to 15 minutes, so that it appeared as if the display going to sleep was the reason the blowing fan stopped.

Timewarp effect not applied when rendered from Media encoder CC

The timewarp effect (enabled using console veiw in PPRO CC) does nothing to footage when rendered through Media encoder...
It does however render when not sending it to the queue, and rendering straight from PPRO.

Fair enough,
Just hoping to raise attention of this...as I believe this should be a normal supported feature of PP as it once was back in CS3 days.....
Normal frame blending interpolation doesn't really cut it, and round tripping to AE is overkill for something already built into PPro....
But at least it's in there in some form

Motion in FCPX - click lag, hanging, tortuously slow rendering

Hello Colleagues,
I have 2 iMacs of different generations, both up-to-spec and up-to-date on OS, FCP, and Motion.
I am experiencing very poor performance when using Motion "generator" graphics: lag, hanging, slow renders, and sometimes even crashing.
I have verified folder permissions, verified fonts, eliminated all converted events/libraries from pre-10.1 - pretty much everything except uninstalling, trashing prefs, and reinstalling fresh.
Still, FCP seems to be FIGHTING ITSELF, with iStat showing that more than half of CPU effort is being used by "system" instead of "user" at any given moment (when Motion assets are present and enabled).
The performance is far poorer than it ever was on FCP7 with Motion 4, and it is far worse than FCP10.0.x with Motion 5 (one of my machines was previously used with FCP7, however, the newer one has been FCPX since its unboxing day in early 2013).
Does anyone have any suggestions for the next step in troubleshooting this problem?
Thanks,
Eric - CoralVision

Yay it's Luis and Russ! Hello colleagues!
Luis: I tink I posted a link to one of the troublesome assets for you, but I limped through the completion of that project by keeping the inspector closed. I still suffered lots o click-lag, spinny balls, and, at the end, an overnight render, but I got through. This was on a 90minute show choir concert that had about 12x 8 second lower 3rds, and about 3 minutes of full screen titles, rolls, and credits. All of the FCP generator assets were made by me from scratch in Motion5. The current post relates to a similar problem, but on a different machine with different assets. The current complaint is from my slightly older iMac (lower power than the new one but still quite capable when using the former versions of this software), and the generators came from Motion projects which were originally created in Motion4. So unless there is something wrong with my practice in using FCPX generators, something in common across the 4 or 5 projects where I have experienced similar problems, I think that a corrupt template is an unlikely explanation.
Russ: I run my systems stock - that is to say that the only 3rd party plugins I have installed are the Canon EOS and XF plugins I use for ingesting media. I don't have any plugins related to MoGraph, editing, rendering, or memory management. These are custom generators that I am creating, chasing the "template" functionality I used to enjoy between Motion and FCP7. So yes, user generated custom generators - and I have had similar problems with several batches of varying complexity and varying origin.
For now I will just have to adapt, observe, and troubleshoot. I have a sneaky feeling that I am doing something wrong in the way I am setting up the motion projects for publication, but I will surely announce it loudly if I learn anything new.
Thanks for checking in, fellows!
Eric D - CoralVision

PPro and AME crashes...all the time. When you start them up, when you work, when you export, ever since I downloaded the updates last week.

I've been trying to edit and export timelapses I've shot in July. It's been an uphill battle since then.
First Lr gave me mountains of issues (seems to be doing ok now) and now Ppro and AMe is doing the same. Since I've downloaded the update last week they have both just stopped working. AME doesn't even want to start up anymore. Ppro starts ok but won't export anything anymore. The is one older project that I've finished before the update. That exports fine. But any new project I've created since refuses. I'm dropping the images into a 4k sequence, the dropping the 4k sequence into a 1080 sequence so I can ad some movement. Bet even if I take the images directly to the 1080 sequence it crashes the moment I hit export.
The timeline on this project is KILLING me! It's not supposed to take this long.
Please help!

Hi LFW,
Lowflyingweasel wrote:
I'm in South Africa. Don't know if the service here is somehow different. But I have tried during business hours! Your set Business hours. The online chat has been unavailable for days. I tried them twice before starting this thread.
Sorry to hear that. I'll raise the issue with my superiors a bit later this today. I have heard our chat software is disconnecting randomly in some cases. We are updating that system, but I can find out more later.
Lowflyingweasel wrote:
I am a little desperate and cannot believe that this tread had been active for 8 days without contact??!! If I posted wrong, or you need more info or whatever, please, why didn't anyone simply say that?
I am responsible for handling this forum and other products in the digital video realm. Because of the volume, it is not possible to answer every post. We do rely on the community to help out for posts like this, but some of them simply get by us. Yours was especially neglected and I apologize for that. Our forums are very good most of the time, but for a guaranteed response, you were doing the right thing by contacting support. The fact that both the forum and support failed you is very troubling and I'll see to it that you get the help you need. Since chat is not working for you, try the phone. Once connected, ask for the "video queue" so that you will be routed to the appropriate support team immediately.
Lowflyingweasel wrote:
I have restarted, reinstalled, tried to re-write the preference file, 8 new project file, re-exported all the images and could manage all but 3 time-lapses. They simply will not export. Not in ANY format from Pr CC 2014 nor via AME.
You may want to trash preferences for both Premiere Pro and AME. See the instructions below. I will also include troubleshooting steps I have been giving users. These steps may help you, as well.
Try the following:
Quit Premiere Pro, then reboot the computer. Launch Premiere Pro once more
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Delete preview files: usually located here: Documents > Adobe > Premiere Pro > 8.0 > Adobe Premiere Pro Preview Files > [Your Project]Delete the preview files in this folder by dragging them to the Trash.
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot once more
Thanks,
Kevin

Exporting from PPro CS3 -- lots of trial and error - and Cineform?

Rather than showing up on this forum out of nowhere and asking, "what is the best codec for exporting HDV edited material from PPro CS3 when the desired presentation is standard definition DVD" I thought I would do my homework first, and post my results. Then, if anyone has any suggestions on how to improve or if their mileage has varied from my results, I hope to learn from your comments.
My camera is a canon HV20, filming in 1080/60i and capturing using HDVSplit (due to premiere's inability to keep my audio and video in synch). I am operating in Windows XP Pro w/SP2 with a dual core AMD 6000+, 2GB dual channel DDR2 800 RAM. Seems powerful enough for me.
My finalists in terms of visual quality when burned to DVD using Encore CS3, 7MB 2 pass VBR, came down to these:
1) H.264 max bit depth
2) QT Animation Sorenson
3) QT Animation Sorenson3
The H.264 takes a little longer to encode, but the visual quality wins out.
So, after doing this and reading posts on here about using Cineform AspectHD I thought I would download a trial and see what it does for me. The strange thing is, I don't seem to understand what advantage it offers, but surely it must be something since it costs $500!
After trying the Cineform trial for a couple of days, I'm not sure I understand what good it is doing. The CFHD files have to be rendered upon placing on the timeline, and they have longer render times when applying standard effects such as the Premiere color correction and time-remapping effects. No apparent difference in visual quality, but much larger file sizes to store. So why is it that folks use Aspect HD???
Hoping if you read this far you will share your preferred HDV-->SD export codecs and settings so I and others can learn from your efforts.
Oh yeah - and eventually, I will be purchasing a blu-ray burner so I want to export these same projects from Premiere into blu-ray format. But for now, it is standard def in 16:9 format.
Thanks for any comments or suggestions.
MS

My computer is similar to Mystroh and Esc in KC. I am not as picky and I want to work in standard definition, I've been making movies in Premiere since version 5.5. In Premiere Pro version 2 I have been making movies using 3 different Sony videocams, usually about 30 minutes long, and exporting to tape and DVD.
So, I splurged for CS3 Production Premium and installed it. No problem.
I composed my first movie called 'Swindle Part 1'and exported it to Encore, (direct to DVD - no authoring) and it bombed near the end of the transcoding phase with the following message:
PGC "Swindle Part 1" has an error at 00;29;46;09. Internal software error: %0, line Swindle Part 1, ref = Bpgc, time = 00;29;46;09
The referenced timecode is one second from the end of the sequence.
I tried again with different clips in a different project and got the same error message.
I can successfully export this movie to tape and to a movie.
Any ideas?

SLOW rendering times

Hi!
One of my biggest gripes is the slow rendering times with FCP. I know that it's some setting that I have wrong, but I can't figure it out for the life of me. I started with HD video captures using the ProRes 422 codec, but it would take a REALLY LONG time for it to render.
For simplistic sake, I started again with just a simple video I took of a screencast. The video is saved using Quicktime in 636x480, HD.264, and a SD (6-1-6) color profile. There is also no sound to the movie...just video. I figured that this would be a really simple way to try some things out, but I was wrong.
I setup FCP as a number of different codecs and resolutions. I imported the file by just dragging and dropping the .mov video into the Browser in FCP. I then dragged and dropped it to the timeline, and did a render/all.
Even by doing this, it is taking 8 minutes to render a 2 minute video. There must be something I'm doing wrong, and I can't figure it out. I was watching a youtube FCP demo and this guy rendered a video in about a minute on a g5. Being I have a dual-core intel, I can't imagine it taking as long as it is. I appreciate any help and I know there's a million threads out there...but I just can't seem to grasp this.
Thanks!

Hi! I suppose the information below would be helpful. I'd like to get started with a screen capture from Snapz Pro X. Here are some answers to the questions...
Program: Snapz Pro X Screen Capture v2.2.2
Record Settings Used:
- Compression Type: H.264
- 30 Frames Per Second
- Key frame every 500 frames
- Encoding Mode: Single-pass
- Compressor Quality: Best
FCP Version: 7.0.2
Within FCP, this is where I get confused because of all the options.
In the "Easy Video Setup" portion, I have...
Format: Apple ProRes 422
Use: Custom
- Sequence Preset: DV NTSC 48khz
- Capture Preset: DV NTSC 48kHz
- Device Control Preset: Non-Controllable Device
- Playback Output Video: Digital Cinema Desktop Preview - Main
- Playback Output Audio: Default
- Edit to Tape/PTV Output Video: Same as playback
- Edit to Tape/PTV Output Audio: Same as Playback
In the "Audio/Video" Settings, I have the following...
Sequence Preset: DV NTSC 48khz
Capture Preset: DV NTSC 48khz
Device Control PReset: Non-controllable device
Video Playback: Digital cinema desktop preview - main
Audio Playback: Default
Sequence Presets: Default settings for DV NTSC 48kHz
Capture PReset: Default settings for DV NTSC 48kHz
Device Control: Non-controllable device
a/v devices: digital cinema desktop preview - main
- mirror on desktop checked
- audio: default
- 'do not show external av device warning' is checked.
Now, if I right click on the project in the "Browser" window and choose "Sequence Settings", I have the following...
Frame Size: 640x480 NTSC 4:3
Pixel Aspect Ratio: NTSC - CCIR 601/DV 720x480
Field Dominance: None
Editing Timebase: 29.97
Quick Time Compressor: H.264
Quality: 100%
Audio Rate: 48khz
Audio Depth: 16 bit
Audio Config: Channel Grouped
Video Processing: All grayed out except 'normal' is selected for motion filtering quality.
================
Now, this is where I get really confused with FCP. Everybody says to set it up with the same settings you use to record. Does the "Easy Video Setup" work hand-in-hand with the "Audio/Video Settings"? Should you skip the easy setup and just jump into the A/V Settings?
WHile typing this message, I also noticed that the "Sequence Presets" in the Audio/Video Settings are set to 720x480 using millions of colors. In the settings for the file in the "Browser" Window, I have it set to 640x480, which is different than what's in the av settings. Should these be the same?
I'm just getting started with FCP, and these are just the questions I have. What is the 'workflow' one takes to do this? Start FCP, setup the 'audio/video settings' area, choose the preset, edit the sequence preset to something basic, and then drag and drop your mov files in? I suppose it's just confusing because you can set the video settings in FCP, in the 'easy setup', if you right click on the project and choose settings, etc... Which one has precedence over the entire project?
Sorry for so many questions.
Thanks in advance...

Incorrect Transfer from PPro CC with Codecs Mysteriously Gone Missing

I posted this question in the PPro Forum as well, but haven't had any luck getting a resolution. Perhaps someone here can help.
So, recently I've been having issues with PPro/Media Encoder CC after the last update. The issue is that once I try to export my H.264 sequences from PPro CC to Media Encoder, the sequence gets completely changed to the Animated GIF codec. When I attempt to change it back, H.264, and a number of other codecs, are no longer available in the Media Encoder list. If I then attempt to use one of the presets on the right dock-panel, such as H.264 > NTSC DV 720x480, the following error message prompts:
Media Encoder has encountered an error:
[..\..\src\Command.cpp-754]
Has anyone else encountered this batch encoding issue and, if so, has there been any updates/patches to resolve the issue?

Same here.
Installed Premiere Pro CC 2014 on a fresh, new Mac Pro (Yosemite OS X 10.10.1) and no DVD-Presets available in Media Encoder!
On my Macbook Pro Retina (also running Yosemite 10.10.1), DVD Presets are available in Media Encoder....
Any solutions Adobe?

PNG Renders from 3Ds Max turn pale when placed in InDesign , Why?

Hello.
When I place my renders from 3DS Max 2010 in Adobe InDesign CS6 with OS Windows 7 they become pale, even when exported as a PDF. I have tried Googling solutions but this keeps bringing up transparency settings.
I know this information is vague but I do not know what other information is needed.
Does anyone know why this is happening or a solution?
Thank you

You'll have a difficult time finding many people who place PNG files directly in InDesign.
That said, here is something you should check out. There is a setting for Applying Gamma Correction in the options when placing a PNG file. It was posted as an obscure feature in the most recent InDesignSecrets.com podcast:
http://indesignsecrets.com/watch_listen/indesignsecrets-podcast-204
Worth checking out to see if that might work.

End of file error - avi exported from PPRO

Encore 1.5
PPro 1.5
I have a project with 16 avi files exported from PPro. Four of them caused the error. I re-exported them and one was fixed. The other three keep causing the error.
I am starting to get a little crazy trying to figure out what is going on. Seems I remember that if the audio and video duration get goofed up in PPro then Encore gets cranky.
Is there a way I can fix this other than re-editing from scratch?
Thanks in advance.

Mark,
Are you Exporting as DV-AVI files? If you are, and they are mux'ed (Audio & Video multiplexed into one file), try as elemental steams, i.e. Video only DV-AVI and Audio only as PCM/WAV 48KHz 16-bit (or AC3 if you're doing DD 5.1 SS). If you have tried as elemental streams, then try with mux'ed DV-AVI (both Video & Audio). Elemental streams work best for me, and there are only the extra few steps:
Import Video (only) as Timeline
Import Audio (only) as Asset
Drag Audio from the Project Panel to appropriate Timeline. With proper Export from PP, they WILL match up perfectly in Duration.
With mux'ed files, you just Import as Timeline and are done - if that works.
Yes, Encore does get really picky. I always Export as elemental streams and never have any issues, but some have, and a mux'ed DV-AVI works for them - why? I do not know.
I do not know if there are any limitations with PP & Encore 1.5, as I have never used them, but others here WILL know if you need to watch out for version-specific issues.
Good luck,
Hunt

Best workflow for slow motion from Canon 7D?

Hey guys,
I am working with a slow motion clip for the first time and I am realizing that there isn't really an easy workflow with this. First of all, the clip was filmed with the Canon 7D, 60 fps. When I put in on the timeline, obviously I get rid of the audio. But then if I slow it down to 50% I get the typical frame blending crappy looking image that FCP gives me EVEN THOUGH the sequence settings are set to playing 30fps. In reality, I thought that when I import the clip in the timeline with those settings the clip would automatically be double-length... Stupid me. It's treating the clip like a normal regular clip and so when I slow it down it does the same thing it does with all clips - a terrible job at slow motion. So basically, at 50% it should be playing every frame and there should be no frame blending but apparently that's not the case.
So.. What's the best way to work with this? I tried putting the clip on a separate sequence and then slowing it down which did a much better job but then I had to export the clip out of FCP and bring it back in as a "new slow motion" clip if I wanted to preserve the effect. What happens if I have more than one clip? Is there a way to do "batch export" on all of them at once and not just one clip at a time? What's the fastest and best way to work with a 60fps clip in FCP and mix it in with the rest of my clips which are 30fps without it looking like crap?
I also just found out about Optical Flow in Motion and that's great but wow... the render time is many many hours for a 5 minute clip... that's crazy. I don't have that kind of time.
So... Please help! Thanks guys!

Step 1: Convert to ProRes. Log and Transfer, MPEG STREAMCLIP, Magic Bullet Grinder...whatever. Make it ProRes.
Step 2: Duplicate the clip if you want to also have it normal speed, because Step 3 is not undoable.
Step 3: Take into Cinema Tools and CONFORM to the frame rate you want. 29.97, 23.98...whatever the rest of the project is. This conform is permanent. It takes seconds, but is undoable. Thus what you did in Step 2.
TUTORIAL!
SMOOTH SLOW MOTION FROM 60P USING CINEMA TOOLS
http://library.creativecow.net/ross_shane/slow-motion_cinema-tools/1

Slow rendering from PPro in AME

Similar Messages

Maybe you are looking for