-
Red Giant – Magic Bullet Looks 2.5 update problem
We updated our Red giant Magic Bullet Looks from 2.0 to 2.5, now all of our rendered files in Premiere CC are gone. Premiere reads the render files when loading. It does not give any error message that it cannot find them, they are just gone. MB Looks doesn’t seem to be backwards compatible with projects that were rendered with 2.0. Has anyone else encountered this?
On a 30 minute program with chroma key, scaling, color correction, and Looks this equates to 10 hours of render/export time, again. Not cool.
Bars & Tone
SALUTE! -
5 Replies
-
We’ve had the very same issue, and have abandoned MBLooks until they can get this sorted out. Had a 4 minute timeline encode overnight for 9 hours, and it still reported that it had 120 hours to go! Of course, it had actually stopped encoding, but hadn’t reported this to Premiere so that an error could be generated.
We’re using the opportunity to learn SpeedGrade. With SpeedGrade, you can put LOTS of color effects on a myriad of clips, and never get a red bar. I re-edited that 4 minute timeline, duplicating the looks that I’d had with MBLooks, and the encode time was less than 10 minutes – a bit faster than with MBLooks.
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions -
I’m having a slightly different problem. MBL is very quick while editing, my problems start with encoding.
I have tried different settings with H.264 output and it seems like pot-luck as to whether it succeeds.
When encoding, it locks up 90% of the time, then I have to click cancel, close Premiere, and then kill the Premiere background process to enable re-loading before I try again.Rendering Entire Work Area doesn’t help either.
I have Premiere Pro CC 7.2.2 (More reel), MBL 2.5 on Windows 8.1 64bit.
-
We work on the MAC platform. Our output workflow is; we render the preview files in ProRes 422, check all the renders on the timeline, then export a ProRes 422 file that matches the sequence settings. We export from Premiere (not to Media Encoder) using the Preview Files. This seems to give all the plugins a chance to work within the Premiere environment with very few surprises. It also gives us a solid ProRes Quicktime file to then convert to any file format we need.
For the original problem of MB Looks not being backwards compatible with the pre-upgrade renders, we just opened each timeline and re-rendered everything. It shouldn’t have happened with a plug-in upgrade, but it is done and we are moving ahead.
Bars & Tone
SALUTE! -
Thanks for reply.
I tried the same approach, but with uncompressed AVI.
All sorted now, I’m sure in future I’ll be encoding without the double-handling. -
I had the same problem. Check your render settings in the encoder. Apparently there is a problem
with GPU acceleration on the latest CC update. Make sure you are set to software only. After countless hours of trying to figure out why I could not encode my edit a friend who is a Mac-Adobe tech expert
solved my problem. Thanks Adobe for your updates…complete with bugs.
Reply to this Discussion! Login or Sign Up