Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Magic Bullet Looks MisFire not working with Premiere CS 6.0.1?

  • Magic Bullet Looks MisFire not working with Premiere CS 6.0.1?

    Posted by Tam Nguyen on August 23, 2012 at 5:50 pm

    I have a Windows 7 x64 Ultimate machine that has Premiere Pro CS 6.0.1 with Magic Bullet 11.4.1. I shoot with a Nikon D7000, which is 24fps at 1080p.

    Here’s my problem: when I apply the preset MisFire Dust or MisFire Splotches, I get an error during export that says “Error compiling movie. Unknown error.”

    I’ve tried everything this troubleshoot https://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-rendering-or.html suggests, no dice.

    I tried applying the preset with different settings, no help.

    Once I remove the MisFire Dust preset, I can export again. This leads me to believe there’s something wrong with the preset.

    Does anyone else have the same problem? If so, do you know how to fix it?

    One more thing: the MisFire Basic Scratches preset only works with low number or scratches (below 10 or something). If I raise it up, Premiere would freeze.

    Thank you very much!

    Nick Larry replied 12 years, 6 months ago 7 Members · 15 Replies
  • 15 Replies
  • Angelo Lorenzo

    August 23, 2012 at 7:22 pm

    I have the exact same problem. I don’t think it’s correctable without a bug fix because I can’t even render the timeline, let alone export the movie. This leads me to believe the issue is deep.

    But report for Red Giant I say.

    Angelo Lorenzo
    Fallen Empire Digital Production Services – Los Angeles
    RED transcoding, on-set DIT, and RED Epic rental services
    Fallen Empire – The Blog
    A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks

  • Tam Nguyen

    August 23, 2012 at 9:57 pm

    You wouldn’t happen to know an alternative to Magic Bullet for the time being, would you?

  • Michael Murphy

    August 24, 2012 at 2:20 am

    Try to apply in Photoshop or After Effects?

    Best,
    Michael

  • Tam Nguyen

    August 24, 2012 at 2:24 am

    That’s actually a very good point. Duh. I don’t have AE, but I have PS, which I’ll try and report back later.

    Thanks!

  • Tam Nguyen

    August 24, 2012 at 5:48 am

    So Photoshop was a no-go. I exported the sequence out to H264 using .mp4 container; Photoshop wasn’t able to read the file.

    I tried it with AE. Same problem: I wasn’t able to render the composition out; it failed after a few seconds. Export the project to AP didn’t work, as said something about preset not being available.

    /sigh

  • Ann Bens

    August 24, 2012 at 12:40 pm

    I have no trouble with misfire in 6.0.1.
    Change the extention of the nikon files form mov to mpg see if that will help

    File a bug report with RG.

    ———————————————–
    Adobe Certified Expert Premiere Pro
    Adobe Community Professional

  • Tam Nguyen

    August 26, 2012 at 12:40 am

    Nope, changing the file extension didn’t help 🙁

  • Michael Murphy

    August 26, 2012 at 2:29 pm

    Sorry, I have “Photo Looks”, but not “Looks” (great naming or what}? ;>)

    Can you open just any .mov or .jpg, etc., file in Photoshop and apply that look?

    What about Premiere? After Effects?

    If so, that starts to narrow it to a specific aspect of your composition in After Effects – an Effect, like “warp Stabilizer”. etc.

    Then you might see if you apply the “Misfire Look”, before you apply the “Effect”?

    If not, it sounds like you have a more global problem with your install, or some software component.

    I hope that makes sense?

    Good luck!

    Michael

    Best,
    Michael

  • Tam Nguyen

    August 27, 2012 at 4:08 am

    MisFire Dust doesn’t work even if the entire sequence consists of just one clip using one effect.

    My question was about Adobe Premiere using Red Giant Magic Looks. If I had use other software to apply the effect, I’d be running away from the problem instead of solving it. And no, it doesn’t work in AE either.

    The problem might be global 🙁

  • Michael Garske

    October 5, 2012 at 5:12 am

    Has anyone solved this issue? I’m running into the same issue in Premiere on my Winodws 7 x64 system with the 6.0.1 update.

    I’m moving to 6.0.3 now to see if it helps. Any suggestions would be appreciated.

Page 1 of 2

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