Re: Why Smoke may never export FCP7 XML, and what to do about it.

COW Forums : Autodesk Smoke 2013

VIEW ALL • ADD A NEW POST • PRINT

Respond to this post • Return to posts index • Read entire thread

Re: Why Smoke may never export FCP7 XML, and what to do about it.
by Brian Mulligan on May 28, 2012 at 2:45:16 pm

In Smoke 2013 your framestore does not have to be DPX as it once was. You can import and create project media as Prores and render as the same prores. So you can work with lesser hardware requirements.

Brian Mulligan
Senior Editor - Autodesk Smoke
WTHR-TV Indianapolis,IN, USA
Twitter: @bkmeditor

Posts Index

Read Thread

Current Message Thread:

Why Smoke may never export FCP7 XML, and what to do about it. by Juan Salvo on May 24, 2012 at 3:29:38 am
- Re: Why Smoke may never export FCP7 XML, and what to do about it. by Matt Penn on May 24, 2012 at 3:40:59 am
  - Re: Why Smoke may never export FCP7 XML, and what to do about it. by Juan Salvo on May 24, 2012 at 3:45:20 am
    - Re: Why Smoke may never export FCP7 XML, and what to do about it. by David Jahns on May 24, 2012 at 4:35:37 am
- Re: Why Smoke may never export FCP7 XML, and what to do about it. by Yevgeniy K'banchik on May 24, 2012 at 4:39:46 am
  - Re: Why Smoke may never export FCP7 XML, and what to do about it. by Juan Salvo on May 24, 2012 at 5:09:18 am
    - Re: Why Smoke may never export FCP7 XML, and what to do about it. by Brian Mulligan on May 24, 2012 at 5:57:16 am
  - Re: Why Smoke may never export FCP7 XML, and what to do about it. by walter biscardi on May 24, 2012 at 12:09:09 pm
    - Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 26, 2012 at 10:45:04 pm
      - Re: Why Smoke may never export FCP7 XML, and what to do about it. by walter biscardi on May 27, 2012 at 1:59:37 pm
      - Re: Why Smoke may never export FCP7 XML, and what to do about it. by Kevin Johnson on May 28, 2012 at 12:31:20 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 28, 2012 at 2:35:29 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Brian Mulligan on May 28, 2012 at 2:45:16 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 28, 2012 at 4:47:12 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Brian Mulligan on May 28, 2012 at 5:10:13 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 29, 2012 at 3:56:32 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Brian Mulligan on May 29, 2012 at 4:23:02 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 29, 2012 at 5:40:33 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Brian Mulligan on May 29, 2012 at 5:46:55 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Shawn Larkin on May 29, 2012 at 5:53:42 pm
        Re: Why Smoke may never export FCP7 XML, and what to do about it. by Jon Howard on Nov 9, 2012 at 8:09:15 pm


	LOGIN TO REPLY

FORUMS • TUTORIALS • MAGAZINE • STOCKYARD • VIDEOS • PODCASTS • EVENTS • SERVICES • NEWSLETTER • NEWS • BLOGS