Jason McDonald
May 8th, 2011, 08:34 PM
I merged the photos in Quicktime that gave me the large file. Imported it to Premier Pro in order to do some pans extra, just to see if it worked.
A problem I ran into was apply Magic Bullet Looks. The picture comes out black. I have to render it first then re-import, color and re-export. Is this normal for timelapse with photos? Or is it a memory problem with my PC?
Here it is:
YouTube - A taste (http://www.youtube.com/watch?v=KldhCiCpRFQ)
Jeff Troiano
May 11th, 2011, 07:03 AM
I'm not 100% about work flow from a PC stand point, as I use Mac. But once I make my time-lapse sequence in QuickTime, I don't save that file, and use it. I export as "QuickTime movie", and when the dialog box pops up, I can go in and select codec and so on. Then the time lapse is ready for import into my NLE. I have a pretty good Mac Pro (8 core), and the file QuickTime makes, before export, is pretty processor intensive, and labors my computer. Once its exported, works great (I export to Prores LT)
Hope this helps,
Jeff
Ted Ramasola
May 11th, 2011, 07:16 AM
I merged the photos in Quicktime that gave me the large file. Imported it to Premier Pro in order to do some pans extra, just to see if it worked.
A problem I ran into was apply Magic Bullet Looks. The picture comes out black. I have to render it first then re-import, color and re-export. Is this normal for timelapse with photos? Or is it a memory problem with my PC?
Here it is:
YouTube - A taste (http://www.youtube.com/watch?v=KldhCiCpRFQ)
I have encountered the same "quirk" in AE. What I did in AE was place an adjustment layer over the image sequence clip and placed effects on the adjustment layer instead of the clip itself. Dont know how it is in prem pro.
Jeff Murray
May 13th, 2011, 03:47 AM
This could also be the alpha channel from the Quicktime export - make sure to turn off the Alpha - its on by default in some codecs.
All the best
With regards
Jeff