Magic Bullet Frames Workflow

Does anyone have any experience, or a general feel, for the best workflow when using Magic Bullet Frames 1.1 from within PP5.5 with 24p conversion being the ultimate intended goal?
Using DV source material.
I have done a deartifact, a color treatment and a 24p-deinterlace (stacked in that order in the effects tree) in one pass/render.
But - I have also heard you should break up these steps and do them individually - so do a non-24p deinterlace as one render, dearticfact as another, and then color treat as a render, and then 24p convert on a fourth pass.
Also deartifact first or deinterlace? Can you do both at the same time on a render? pros cons?
Curious about the entire process really.
As an aside - if it is good practice to deinterlace footage straight away before doing anything else to it - when you later do a 24p conversion with MB, typically the final step in the process, arent you deinterlacing it a second time as MB 1.1 combines 24 and deinterlace as one action now. (though as i mentioned you can do just a deinterlace sans the 24p conversion).
Thanks.

This post isnt 24 hours old.
Yes I need your help - did you want to go private?
Basically I just need to know the order in which to apply the different techniques - and whether to do them all at once - or break them up separately.
Keep in mind Magic Bullet 1.1 hasnt been out "many years" nor has PP5.5 - so I'm not sure if that will affect your advice - there were some substantial changes to their usability in platforms.
Thanks!

Similar Messages

Premiere Pro and Magic Bullet Frames Help

I shot a wedding a few weeks ago using the Canon XHA1 and down converted in the camera into Adobe Premiere Pro CS3. I placed all of the edited clips on a 29.97 time line. Here is the question… There are some portions of the video that I want to apply Magic Bullet Frames to give it more of a cinematic look. From what I have read, it is best to place footage on a 23.976 timeline and then apply magic bullet frames (according to the magic bullet tutorial). How can I do this since I have placed all clips on a 29.97 time line. Should export the footage out to After Effects, apply the Frames effect on a 23.976 timeline and then re-import back into Premiere Pro (29.97)? Or is there a better way? Any help would be appreciated.
Thanks.

From what I have read, it is best to place footage on a 23.976 timeline and then apply magic bullet frames (according to the magic bullet tutorial).
Two things. First, I'd like to see that tutorial. To the best of my knowledge, Frames does not create actual 24p files, it adds back the proper pulldown so you still need to work in a standard 29.97 preset.
Second, dv2Film was created because products like Frames just weren't good enough. Give it a try at the link below. It's free, and creates the best looking film conversions yet.
http://www.dv2film.com/

Magic Bullet Frames vs Nattress

Hey,
I am trying to make my 1080i 60 footage look like 24p. I am wondering if any one can recommend one of these products over the other? Just wanting to de interlace and smooth out the motion.
AND was wondering if the render times are significantly different from on set of plug ins vs the other.,,?
thanks

Film Effects converts the 60i to 24p, but embeds it in 3:2 pulldown for playback on a normal 29.97fps timeline. Remember to set field orders to upper for HD. That will make the footage look like it was shot on 24p and transferred to video.
If you need 60i to 24p in a 24p timeline, it's a touch more tricky, but the Standards Conversion pack does that, and the look is great.
Graeme

Fcpx with magic bullet green and pink flash frames

Hi I'm using fcpx with magic bullet. all recent updates. an imac 3.4ghz 32gb ram 512ssd drive and 512mb card. I keep getting pink and green flash frames whenever i colour grade in magic bullet.
first 22 secs of project were fine, next day I added to it, flash frames everywhere throughout the entire project. tried everything. is it a bug?
cheers

This problem is completely averted, for me (and reportedly most others), by exporting using "Send to Compressor" rather than using any FCPX presets. That is, no flashes or green/purple/upside-down frames show up in the final output.
I would hardly have believed that the "engine" used in Compressor is different to FCPX - but that is obviously (simplistically) the case.
This is also some confirmation that the problem is with FCPX - not the plugin.

Magic Bullet "V" FCP Color

Anyone use both? Whats your thoughts, which is better? Heard that color is pretty hard to use??

Here is my thought.
Are you a colorist? Then don't use COLOR. Color is a highly professional color correction application. It isn't as simple as the 3-way, it requires a pretty strict workflow and set of codecs. It has a lot of settings internally that you need to do right. CAN you pick it up? Yes...I have, because I had to. I have two tutorial DVDs and I had a week to play and figure things out. I even had people I could call and have them help me figure out the more trickier aspects. And I STILL only use the PRIMARY room.
Are you just an editor that wants to produce great looking color corrected footage? Look at Magic Bullet COLORISTA. It has a very familiar looking interface (looks like the 3-way), allows you better control over the colors and allows you to push them to the extremes more that the 3-way allows. And you can color correct in FCP. You can monitor your timeline the way you normally would if DV via firewire. But if you are working with HD then yes, you need an HD monitor and HD capture card to see how you are REALLY affecting the colors.
MB Looks? That is GRADING software to give your footage a certain look. It does not allow you to view this footage on an external monitor (from what I have heard) so you cannot really tell what it looks like. Plus you can only see one frame, not the whole clip, so if the shadows and highlights change throughout the shot, then you can't see that to adjust. But you can use that to get a basic look, then tweak with the 3-way or Colorista.
Bottom line...if you are not wanting to be a colorist, I say avoid COLOR. Use Colorista or the 3-way.
(NOTE...Colorista still clamps anything over 100IRE down to 100IRE, so you need to adjust it down with the ProcAmp or 3-wa before you add Colorista).
My Humble Opinion. Color isn't simple to use, and isn't for everyone.
Shane

I just updated to new final cut pro x 10.1.1 and i am also on mavericks so but on my editing timeline i was trying to color grade using magic bullet looks but i am having problem with it. when it comes back to tcp x it's black.

I just updated to the new final cut pro x 10.1.1 and i am also on mavericks so but on my editing timeline i was trying to color grade using magic bullet looks but i am having problem with it. When i send a sample to MBL and color grade it , it comes back to final cut pro x all black even after render. By the way on the MBL i am using the GPU rendering, I used before like 4months ago and it was fine. And i don't like to use the CPU because it very slow.

What is the frame rate of the project? At what frame rate was the media recorded? What frame size?
What are the audio settings?
What are the specs of the machine, in particular how much RAM, how is the hard drive connected, etc.?
If possible, post screenshots of the inspector for the project.
It could be related to the audio frequency?

Problam with magic bullet instant hd advance

after i changed my sd video to 1080p and added magic bullet instant hd advance i set it so that it renders in h.264 codecs but every time i tryed i got this message.

The H.264 format only permits a limited, constrained set of frame sizes. In After Effects CS4, these constraints were communicated in the Comments field of the H.264 Export Settings dialog box, and you must follow those instructions or else get the error message that you got.
In After Effects CS5, if your settings don't match one of the sets of settings allowed by the H.264 specification, then a warning icon in the Output Module Settings dialog box appears, and After Effects tells you what it's going to do to make the video fit.
The F4V format (which contains video encoded using H.264) has a different set of constrained sizes, including the 1920x1080 size that you're looking for. And other formats (like QuickTime) aren't constrained in this way at all. So, you might have better success choosing a different output format, if you need that output frame size.

Magic Bullet Looks is fixed...

For those of you who use Magic Bullet Looks, you may have noticed that it didn't work so well with CS4 - no preview image. Well, Red Giant released an update today. So far, it works great. I did catch one little bug in that you need to have the play head over the clip you select to edit in Looks, otherwise the preview image will be where ever the play head is.
If you're like me, this is good news...I've really grown to depend on Looks.

Yeah I beta tested it Looks when it came out and they were pretty adamant about not being able to move the preview around. Evryone in the beta asked for it but they layed down the law and said: Basically, it's not gonna happen so stop asking. Guess it's in the coding or something.
Micah from Red Giant and Stu have said over and over that Colorista is for matching all your clips's color for a scene then Looks is meant to be applied as an over all correction for a scene. This would work better if Premiere had adjustment layers. It was never meant to be a single clip corrector, even though I find myself using the Lens effects (like the awesome swing/tilt, edge softness and grad) for single clips.
They did say that scrubbing in looksbuider might happen for version 2.0 but it's not in google color correction beta group right now. So I don't expect it to happen any time soon.
Eric, are you saying that it picks a random frame from the clip for your preview. That's not the way it's supposed to work. In fact doesn't that kinda negate the reason for keyframing looks?
It's always pulled up the frame the CTI is over. If the CTI isn't over the clip then it pulls up the first frame. Works the same way in AE. If it doesn't work that way for you there's some sort of problem. I'm looking at it right now on Premiere CS4 and it's working for me.

Magic Bullet Editors & Deinterlacing

hi all,
i just picked up Magic Bullet Editors for a big project i'm working on in FCP 5. my question is, what's the best stage to apply MBE and when to deinterlace?
a) in the main timeline, apply colour correction, MBE and deinterlace each shot?
b) in a nested sequence (after CC and MBE each shot), deinterlace entire subclip?
c) in Compresser, deinterlace using Frame Controls?
also, is the FCP Deinterlace filter the best way to go? what about Shift Fields, or one of Joe's Filter's?
FYI, the footage is from an old four year old Sony MiniDV camera (not my choice) and i'm working on a pretty tight budget, so i can't really afford any bigger, more expensive toys.
thanks in advance,
Craig

I too can confirm that MBE 2 works with FCP 6.
And as for FCE...you gotta ask that in the FCE forum.
Shane

Magic Bullet v2?

Anyone have the new Magic Bullet v2 for Editors along with the 7800 nvidia graphics card and can confirm real-time playback? Red Giant Software is claiming it runs magic bullet v2's look suite in real time with the 7800 nvidia card. Let me know if you got it. Thanks !!!

yeah ... I have the 6600 nvidia card and its pathetic My CPU usage is only at 25% cause its pushing all the workflow to the graphics card [thats how they coded magic bullet v2] and my card *****. I noticed it changes the look of your older magic bullet files.
Again .... if anyone has tested this please post.

Magic bullet looks for cs6

which version magic bullet looks is applicable for premiere pro cs6

The 2.0.8 update for Looks just fixed a bug in handling large frame buffers. 2.0.7 fixed the CS6 installer problem.
See the release notes table.

I am having problem when I am installing magic bullet look 1.4 please help

Hi, I am having an issue with my Red giant magic bullet look 1.4
When I am installing this plug ins I receive a message saying: your graphic card did not meet the minimum requirement but actually my graphic card did meet the requirement and I was looking at the requirement for this in website and my Gcard met the requirement. Why is it not installing?
please help me
I use premiere pro CS3
Win 7 OS 64bit
My graphic card is: NVIDIA GeForce 9800 GT (Microsoft corporation-WDDM v1.1)
The minimum requirements for the plug ins are: Magic Bullet Looks supports a wide range of cards from both ATI or NVIDIA. For ATI cards, we require a 9600 XT or greater, or an X series card starting with the X700 series. Cards with greater model numbers and at least 128 MB of RAM can run the Looks engine.
For NVIDIA cards, we support the 6600 model and higher or QuadroFX 1300 and up. Cards with higher model numbers and a minimum of 128 MB of RAM can run Looks. For users working with HD images, we require that the video card have at least 256 MB of RAM. In all cases, we suggest using the latest video drivers for your graphics card.
Please Note Since all media is processed at 32 bit, you will absolutely need a 256 MB graphics card or larger. For newer cards from ATI and NVIDIA, we recommend a minimum of 320 MB of RAM. For 2K projects, we recommend 512 MB or a larger amount of RAM on the graphics card.

Run this.
http://www.maxon.net/downloads/cinebench/cinebench-115.html
Report back the results.

Red line with Magic Bullet Looks

Magic Bullet Looks in the Video Effects panel shows as a 32 GPU accelerated effect.
However, when I add it to a clip in timeline one, two or three, I go from no lines (including yellow) to a red line above that clip.
If it's a GPU accelerated effect why am I seeing a red line above the clip when I add that effect?
My card is a 285 that works fine with everthing else.

Magic Bullit Looks is not a accelerated effect, so that is why you are seeing the red line.
Effects with the icon on the left are accelerated.

Blue Screen When using Magic Bullet Instant HD in Premiere Pro CC

When using Adobe Premiere Pro CC, using Magic Bullet Instant HD to convert a 720p video to a 1080p. The system will blue screen and the problem dll file seems to be hal.dll.
What is the cause of this?
and how to fix it?
System Specs:
OS: Win 7 Ultimate 64 bit
CPU: i7 3770k 3.5 Ghz
RAM: 16 GB
GRAPHICS: AMD Radeon HD 7700
MOTHERBOARD: ASRock Z77 Extreme6
STORAGE: 1 TB local disk, 3 2TB Expanded driver attached to 3.0 port
Wireless mouse and keyboard

Hi Kris,
I have checked all the three dumps, they all showed the same bugcheck 124.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8010821028, be200000, 21136}
Probably caused by : GenuineIntel
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010821028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Adobe Premiere
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
fffff880`0350ab58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`10821028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0350ab60 fffff800`035d6463 : 00000000`00000001 fffffa80`10817950 00000000`00000000 fffffa80`108179a0 : hal!HalBugCheckSystem+0x1e3
fffff880`0350aba0 fffff800`03413700 : 00000000`00000728 fffffa80`10817950 fffff880`0350af30 fffff880`0350af00 : nt!WheaReportHwError+0x263
fffff880`0350ac00 fffff800`03413052 : fffffa80`10817950 fffff880`0350af30 fffffa80`10817950 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0350ad50 fffff800`03412f0d : 00000000`00000008 00000000`00000001 fffff880`0350afb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0350ad90 fffff800`03406e88 : 000007ff`fda7f140 00000000`00000b40 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0350adc0 fffff800`034be4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0350adf0 fffff800`034be313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0350af30 00000000`0352f2c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`36c0cdd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x352f2c9
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
Information for Bugcheck 124:
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR.
Bugcheck 124, This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Which is probably caused by "GenuineIntel". Make sure we have updated the BIOS drivers, take a check with the hardware tool provided by the manufacturer, or you may take a check with them.
Best regards
Michael Shao
TechNet Community Support

PP CS4 crash - because of magic bullet stabilizer??

I'm using PP CS4 and I have a wedding video that I've been working on and it all of the sudden crashed on me. I used time machine to pull up an older version which opened fine but I lost the hours of work I put in. So I tried again to open the file that crashed and it worked. I sent it to the media encoder to render out but woke up to an "unknown error" message. I'm back to being unable to open the file with all the work.
My hunch is that the problem is an effect, more specifically Magic Bullet Stabilizer. This is only a guess but I remember it acting funny when I dropped it on the video layer. (It didn't seem to work and it would freeze up a little.) I could be wrong, other effects I'm using are Magic Bullet Denoiser and a bunch of standard color effects.
When I try to open the file I see what looks like chopped up pieces of an error message and my desktop background in the project window and then it crashes. I'm unable to do anything before PP crashes.
If anyone can help, please do...
Thanks...

Hi there,
I have seen crashes using Magic Bullet Denoiser in Premiere Pro CS5. Red Giant says Denoiser is currently unsupported for CS5, and I assume that goes the same for CS4. The Denoiser compatibility notes are here:
http://www.redgiantsoftware.com/products/all/magic-bullet-denoiser/compatibility/
Unfortunately, I don't have compatibility info on Magic Bullet Steady for CS4. I know it is discontinued for CS5. Perhaps you could contact Red Giant directly to ask them. Even better, if you could post back your results for other users who may have the same question.
Cheers,
Zac

Magic Bullet Frames Workflow

Similar Messages

Maybe you are looking for