Forum Replies Created

Page 2 of 4
  • Bryan Mailer

    November 28, 2012 at 3:53 pm in reply to: Doubting My Workflow Pattern…

    Do you mean Smoothcam? I started using Motion because I found the Smoothcam so difficult to work with. What submenu is Stabilize under?

    Thanks for the reply. And the tutorials.

  • Bryan Mailer

    November 28, 2012 at 12:56 pm in reply to: Basic Question… Convert to ProRes422?

    If I have Quicktime .MOV files and I am still running into these ridiculous re-renders, is there something else that can be done? Is .MOV the ideal format for heavy editing?

  • Bryan Mailer

    November 28, 2012 at 12:54 pm in reply to: Fill Text Face with Video?

    Hi,

    The text is moving, probably rotating. Is it not possible to have the video on the face of the text so it rotates as well?

    At the very worst, it ought to work with some sort of:
    – import the video / send it to motion
    – image mask it to a letter
    – 3d whatever the result of that is and replicate it as a Line with points
    – animate that result to move / rotate / whatever…

    ?

  • Bryan Mailer

    November 28, 2012 at 12:21 pm in reply to: Basic Question… Convert to ProRes422?

    Thanks for the advice. Will probably save me about five years of converting, compressing and rendering.

  • Bryan Mailer

    November 28, 2012 at 9:54 am in reply to: Basic Question… Convert to ProRes422?

    Would just opening the source file in QT and simply Ctrl-S (Save) do the trick? Is it necessary to Save As a new file? I have a number of clips, all 60 minutes long and if “Save” will work, it will be nice not to have to re-link all the editing files in FCP.

    Thanks for the tip.

  • Bryan Mailer

    November 28, 2012 at 8:54 am in reply to: Compression for Film Fest, and I’m in trouble now!

    Hope things went okay. You can tell them that Brian Mailer did it and he has been fired.

  • Bryan Mailer

    November 28, 2012 at 8:49 am in reply to: prores 422 hq vs prores 422 vs prores 444

    Wow. I opened a thread trying to figure out whether I should convert my AVI files to Prores422 for editing purposes…and a hockey game broke out!

  • Bryan Mailer

    November 28, 2012 at 3:47 am in reply to: Multiply all keyframed motion by a constant?

    The main reason is that I have been doing titling and effects at a higher resolution and it seems to make more sense to expand the video to the res of the Motion work, rather than shrink the Motion stuff down to 480, then maybe later on expand the combined project (with its lower res).

  • The titles and effects are much better designed than the quality of the original camera and in a couple ways have the potential to upgrade everything as a whole. Also, when I’ve shrunk them down to the resolution of the footage and exported, they haven’t held up terribly well.

    I have learned that 1620×1080 isn’t a common (or even existing) preset but the way I got to it was by taking the 720×480 footage and – assuming that it might be worth it to do titles and transitions in HD… Well, if I expand the 480×720 proportionately…I get 1620×1080. So I guess in the end I would end up with 1920×1080 but with narrow black “wings” on the sides… It seemed to make sense…

    Of course, none of the stuff developed in Motion has been developed with interlacing involved. Don’t know how well that will play out on a DVD or TV and if that will be an issue.

  • I guess I meant 720×480. I haven’t paid much attention to which axis is stated first, but I guess it is usually X.

    My titles and such are created in Motion, and I did so in HD. I chose 1920×1080 for design, and then, I figured I could crop out what I don’t want and apply them to something like 1620×1080 if I expand the DV footage.

    Because of the interlacing in the footage, should I leave it there for DVD authoring? I applied a de-interlace filter because it looks better on the computer screen while I’m working, but I can always remove it if necessary…

Page 2 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy