Forum Replies Created

Page 8 of 16
  • Brian Mulligan

    January 16, 2012 at 6:59 pm in reply to: FCPx in local TV

    No one in Local News has time to keyword clips and database before they edit. Most broadcast editors edit visually.

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

  • Brian Mulligan

    January 12, 2012 at 12:08 am in reply to: FCPX Choking On .PNG?

    Make sure you export at SCREEN or 72 dpi form Illustrator.
    Sounds like you exported at 300 dpi, which will increase the 1920×1080 resolution to compensate.

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

  • Brian Mulligan

    January 8, 2012 at 3:53 am in reply to: FCX won’t import .mov captured files

    No video means its a codec issue. Your fcpx machine doesn’t have the same DV codec as your older machine. There must have been some change inthe QT DV codec from QT 7 to QT 10

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

  • Brian Mulligan

    January 7, 2012 at 5:40 pm in reply to: How do I achieve this flicker effect?

    If you want to match the beat of the music… like in the video, you can achieve the same thing through actual editing.

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

  • Brian Mulligan

    January 1, 2012 at 10:23 pm in reply to: What do you mean by Fast?

    Edius is not a editor you want to emulate. It’s pretty horrid.

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

  • Brian Mulligan

    December 27, 2011 at 9:39 pm in reply to: Export Settings to for iPad playback

    You should be able to just export a standard h.264 which get wrapped as an .mp4.

    h.264 can go 1080 on an ipad, but 720p would be fine. not sure why you would need or want the 640 size.

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

  • Brian Mulligan

    December 22, 2011 at 4:01 pm in reply to: Green Screen Question / Advice

    My first response for both would be “Yes, it’s possible, but it might look like crap.”

    I have no experience with FCPX as a keyer. In example #1, It would be difficult to maintain the shadows, and you would have difficultly with other fine detail and any other green objects in your scene.

    In Example 2. You would have to build a graphic that looked like 2 walls meeting. Again, you might have issues with fine detail on the item to the left on the shelf. Also, any camera movements, would look odd as your background would not be matching the move.

    If you are going to use green screen, you might wan tot go for more of an abstract set design. Not animated backgrounds but something simple.

    Compression of your video source like h.264 or HDV will also cause you great difficulties.

    Here is a link to some free green screen shots that you can test out.
    https://www.hollywoodcamerawork.us/greenscreenplates.html

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

  • Brian Mulligan

    December 19, 2011 at 4:25 am in reply to: New blog post from Philip Hodgetts. Worth the read.

    Being a local broadcast editor, I have learned to edit fast. I have gone a very non traditional route with editing systems. GVG Sabre linear editor, Lightworks nonlinear, and then Smoke. So I have never edited with Avid or FCP7 or X. I have tinkered with fcpx early on.
    Lightworks had a great interface and controller. It made looking at sources, choosing shots, and finessing trims as fat as I could think. Smoke is equally fast at editorial. I can look at 50 source clps at a single glance and scrub though them to make selections.
    Lightworks worked the same.

    Broadcat time frames are in hours and not days. I can cut a stylized promo like this…Graphics and all…

    https://vimeo.com/31300494

    …in 6 hrs from import to export. Or I can rough cut a feature story 3-4mins in 8 hrs and completely color grade and audio mix in 12 hrs. I have made a career at editing fast and maintaing quality.

    How fast your system works does matter. I don’t think I can edit as fast or as detailed in
    Premiere, the only other editor I have experience with. Right or wrong we all have had to do more with less….less money, less people and less time.

    Fcpx is faster than fcp7…. How could it not be. I honestly think people should not compare the two. I think source material evaluation and rough editing are some of the strengths of fcpx. But anything more than that, it’s weaknesses in trimming and finessing might become more apparent.
    I know I could not use it for my purposes.

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

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Brian Mulligan

    December 16, 2011 at 6:14 pm in reply to: FCPX Trumps Avid

    I am sure the Avid Editor is happy he/she didn’t have to deal with the iMovie project. So everybody IS a winner.

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

  • Brian Mulligan

    December 1, 2011 at 2:44 pm in reply to: Failing so hard

    [Shane Ross] “Good for them. They gave the masses the NLE they wanted”

    Now the rest of the world just needs to move on. Use it or don’t, but the FCP zealots just need to let it go.

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

Page 8 of 16

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