Patrick Doan
Forum Replies Created
-
Patrick Doan
September 10, 2011 at 12:14 am in reply to: Rendering a frame range, preserving frame numbers (AE CS5)Normally you isolate a segment of the sequence to render when a new iteration is being requested to render. If the sequence lasts 3 minutes and you just need to update 12 seconds of that 3 minutes, it makes sense to render that 12 seconds rather than rendering out the entire sequence again, especially if the sequence is intensive and slow to render.
It seems I will have to use some batch renaming software to rename the exported sequence.
Best
-
Patrick Doan
September 9, 2011 at 4:42 am in reply to: Rendering a frame range, preserving frame numbers (AE CS5)after browsing around for 5 – 10 minutes, i can’t seem to find a check box which asks whether i want the range being rendered to start at 00000 or to start at the current frame number. which would be strange because i have been doing “range rendering” since After Effects 6.0 and never had to checkbox anything – it would number the frames automatically, as it should.
here is a screenshot of my render queue settings:
-
so a small update:
As a test, I created a new Premiere Pro project and dropped all my exported PRORES422 footage into the timeline, and it runs perfectly fine, silky smooth. So this situation is particularly odd.
At this point I have 2 options:
– continue swapping my R3D footage with the PRORES footage and deal with the lag
– or re-edit my sequence from scratch, manually replacing the footage in the process of remaking the edit.Also interestingly: If I do the reverse – ie. replacing PRORES footage with R3D footage – I don’t seem to have any lagging problems, at least with the small test I did.
I didn’t think the “Replace Footage” command would be so painful, oh wells..
-
Hello
I’ve attached screen images with some settings. I’m editing with my footage connected via Firewire-800 on a Lacie 500gb drive, which never caused me problems (in fact it caused me joy, myself coming from a Windows background 🙂
I suppose the export settings in REDCINEX could be too high, but I’ve never had problems with exported footage. Of course I’ve never tried to do “proxy footage” replacement like in this case. And the reason why I am undergoing this footage replacement task is because I only realised after I finished editing that the source R3D footage would not be easy to color correct – or key out the green in this case – because they were not using the right color profile.
I tried flushing video cache, but it doesn’t seem to do the trick, even though the cache is below 100mb anyway. I also have no problems with playback when the exported Quicktime Prores 422 footage is running with Quicktime Player.
Thanks again
Quicktime Movie Info (exported footage)
Red Movie Settings (source footage)
Red CINEX Export Settings (from source footage)
-
Patrick Doan
November 21, 2008 at 11:14 pm in reply to: Pixelated output from Premiere CS4 via Media encoderI’m having the same problem with the export settings.
I usually have no problems in Premiere Pro CS3 to export a quicktime with Photo JPG compression at 100% – the results are very crisp. However, with CS4, i’m using the same exact settings, and the output is very pixelated, in addition to the file size being small (around 5mb, instead of 50MB), as if it ignored my settings. I’ve been using PNG compression as a substitute.
Strange?
-
ok, i have been doing some testing, and i found David Laronde’s method to be most useful.
I also did a test in After Effects with the sequence rendered with Continuous Rasterize ON, and Continuous Rasterize OFF – i’ve notice there is less flickering (or subsampling) while rasterize was OFF. I realised this when i zoomed in at 800% on each frame of the sequence, and noticed less fading around the edges of the letters – rather, they seemed to be more solid and consistent.
i hope that may help some people.
🙂
–
-
i will try out the math expression and see how it works, thanks.
continuous rasterize is on.. in fact, i thought this might be a problem, since after effects is recalculating pixels for antialiasing, so the pixels are not “fixed”?
i am working through the film director, so i do not see it on the client monitor, which is a bummer. i get the information through him.
thanks
–
-
i just read david laronde’s post on flickering – great stuff! i think i will try this out instead since it sounds alot like what the lab guys said about subsample pixeling, and it will give me control over the speed of the scrolling.
thanks
–
-
oh, i was also wondering if the flickering issue would also apply to horizontal, x-axis movement? in the opening credits of the same project im working on, i have slow moving horizontal text movement. i have a 16MB demo here:
https://www.defasten.com/files/LILI_A_GILLES/LILI_OPEN_2K_1_POST.mov
thanks again for any info
–
-
Hi Kevin
I just tested your preset, but it seems to shorten the length/speed the up the credits i have. is this normal? my credits run to 1min42sec, and after applying your preset/effects to my layer, it is now running at 1min19sec. is there a way to control the speed of the scrolling, and have the last frame of the end credits remain on screen?
if you would like to see my current version of the end credits, it’s available here:
https://www.defasten.com/files/LILI_A_GILLES/CREDITS_FINAL_2.mov
(1 min42sec, 45 MB)thanks alot for the response!
patrick–


