Photoshop crash when i use Magic Bullet Looks

Hello, good, I need help because I have been dating a message to start photoshop, which tells me card graphics is not supported, and attempting to open a plugin, such as Magic Bullet Looks, to put ok, shut me photoshop, and this had not happened to me before, what can i do?
i have WIN 7
Intel core (TM) i7 2.00 GHz
6 gb of ram
64 bits

I did a quick google search for "Magic Bullet Looks plugin" The first one I found does not even seen to be a Photoshop Plug-in Is this the plug-in your trying to use in Photoshop? Seems to be for video editing software. Photoshop can do limited video editing but is not listed as supported by this plugin.
Red Giant - Products - Magic Bullet Quick Looks Free 1.4
System Requirements
Quick Looks Free works with:
Adobe After Effects CC, CS6, CS5.5, CS5
Adobe Premiere Pro CC, CS6, CS5.5, CS5
Apple Final Cut Pro 6, 7

Similar Messages

After Effects CC crashes during prerender using Magic Bullet Looks [was: Help me Please!]

im using MBL for effects and CC and outting it on a adjustment layer. everytime i try to prerender it crashes! help me plz!

You want some help from us? Then we need some help from you:
FAQ: What information should I provide when asking a question on this forum?

When ever i try to use magic bullet looks it says that it could not complete the command because of a problem with the filter module interface what do i do to fix that please help

i dont know what the problem is everything else works my photoshop runs really well its just when i try to use magic bullet looks then it gives me the error message

Contact Red Giant and see if they have an update to the plugin that fixes the bugs in the plugin that are preventing it from working correctly.

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?

I am not able to use Magic Bullet Looks with the After Effects trial

Jeff,
I am having troubles with downloading a trial. I am currently trying to find ways to edit videos using Magic Bullet Looks. I have found many ways, but when I go to download the Magic Bullet looks, it says After Effects cs6. For some reason it does not install even though I have the trial version of After Effects. So when I open After Effects, and go to the effects tab, it does not show up. I have looked on tutorials and many other ways.
I also tried downloading the trial of After Effects at, http://prodesigntools.com/adobe-cs6-direct-download-links.htmlrfer
Please Help,
- jhsurfer

If you're having difficulty installing or using Magic Bullet Looks, then I recommend asking the folks who make that plug-in, Red Giant:
http://www.redgiant.com/products/all/magic-bullet-looks/

Photoshop crashes when I use the marquis tool.

Photoshop crashes when I use the marquee tool. As soon as I make a selection it crashes my computer (every time!) by either rendering the screen black or sometimes all white. I have to force shut down and restart. I'm using MacBook Pro OS 10.6.8 with Photoshop CS6. I am not in a position to update OS at this time. Is there anything I can do to work around this problem? It's extremely time-consuming and infuriating.
Here's the crash report, if anyone is able to make sense of this, I'd sure appreciate knowing what the problem is.
Interval Since Last Panic Report: 335913 sec
Panics Since Last Report:          3
Anonymous UUID:                    A9EE1760-D467-49BB-B2EC-A100E2095A2E
Mon Dec 30 15:09:00 2013
panic(cpu 0 caller 0x9d4c9b): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0x7f494000 0x0a5480a2, D0, P3/4
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x5c922188 : 0x21b837 (0x5dd7fc 0x5c9221bc 0x223ce1 0x0)
0x5c9221d8 : 0x9d4c9b (0xbea28c 0xc5a800 0xbf8e60 0x0)
0x5c922278 : 0xaef608 (0x8f97c04 0x9338004 0x100 0xcb42b6)
0x5c9222c8 : 0xae6601 (0x9338004 0x100 0x5c9222f8 0x9c4778)
0x5c9222f8 : 0x16d49a6 (0x9338004 0x100 0x438004ee 0x5c922308)
0x5c922438 : 0xb0e2b5 (0x9338004 0x9337004 0x0 0x0)
0x5c922478 : 0x9dde7c (0x9338004 0x9337004 0x0 0x0)
0x5c922518 : 0x9da55b (0x0 0x9 0x0 0x0)
0x5c9226c8 : 0x9dc58f (0x0 0x600d600d 0x702b 0x5c9226f8)
0x5c922798 : 0xc9feae (0xc1d0004d 0xbfef0033 0xbfef0034 0x857c)
0x5c922808 : 0xcaf734 (0xa1a5a00 0x1473ec80 0x8 0x0)
0x5c922828 : 0xcd4322 (0x1473ec80 0xb 0x5c922848 0x89e0)
0x5c922858 : 0xcd4b3d (0x986c000 0x0 0x5c92287c 0x0)
0x5c922888 : 0xcb4d79 (0x986c000 0x77890080 0x0 0x33)
0x5c9228d8 : 0xc76d0c (0x4651a000 0x0 0x0 0x3)
0x5c922948 : 0xc7640f (0x4651a000 0x0 0x2 0x3)
0x5c922978 : 0xc6c05f (0x4651a000 0x0 0x2 0x46255000)
0x5c922ab8 : 0xca55d8 (0x46255000 0x1 0x5c922bcc 0x5c922bc8)
0x5c922b68 : 0xc67fe1 (0x46255000 0x1 0x5c922bcc 0x5c922bc8)
0x5c922be8 : 0x56da06 (0x46255000 0x0 0x5c922e3c 0x5c922c74)
0x5c922c38 : 0x56e2a5 (0xcf6720 0x46255000 0x8981a88 0x1)
0x5c922c88 : 0x56eb59 (0x46255000 0x10 0x5c922cd0 0x0)
0x5c922da8 : 0x286638 (0x46255000 0x10 0x8981a88 0x1)
0x5c923e58 : 0x21dbe5 (0x8981a60 0x1103d5a0 0x1fd7e8 0x5d43)
0x5c923e98 : 0x210a86 (0x8981a00 0x0 0x954dc70 0x98d6620)
0x5c923ef8 : 0x216f84 (0x8981a00 0x0 0x0 0x0)
0x5c923f78 : 0x295c57 (0x8cc0188 0x0 0x0 0x0)
0x5c923fc8 : 0x2a256d (0x8cc0184 0x1 0x10 0x0)
      Kernel Extensions in backtrace (with dependencies):
         com.apple.GeForce(6.4.0)@0xc5c000->0xd12fff
            dependency: com.apple.NVDAResman(6.4.0)@0x96e000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
         com.apple.nvidia.nv50hal(6.4.0)@0x159e000->0x19b2fff
            dependency: com.apple.NVDAResman(6.4.0)@0x96e000
         com.apple.NVDAResman(6.4.0)@0x96e000->0xc5bfff
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 4671247742528
unloaded kexts:
com.apple.driver.AppleUSBUHCI    4.2.0 (addr 0x1431000, size 0x65536) - last unloaded 114471438805
loaded kexts:
com.apple.driver.AppleHWSensor    1.9.3d0 - last loaded 45127423025
com.apple.driver.IOBluetoothA2DPAudioDriver    2.4.5f3
com.apple.driver.AppleMikeyHIDDriver    1.2.0
com.apple.driver.AGPM    100.12.31
com.apple.driver.AppleHDA    2.0.5f14
com.apple.driver.AppleUpstreamUserClient    3.5.7
com.apple.driver.AppleMCCSControl    1.0.20
com.apple.driver.AppleMikeyDriver    2.0.5f14
com.apple.driver.AudioAUUC    1.57
com.apple.driver.AppleIntelHDGraphics    6.4.0
com.apple.driver.AppleIntelHDGraphicsFB    6.4.0
com.apple.driver.SMCMotionSensor    3.0.1d2
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AudioIPCDriver    1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin    4.7.0a1
com.apple.GeForce    6.4.0
com.apple.driver.AppleGraphicsControl    2.10.6
com.apple.driver.AppleLPC    1.5.1
com.apple.kext.AppleSMCLMU    1.5.2d10
com.apple.filesystems.autofs    2.1.0
com.apple.driver.AppleUSBTCButtons    201.6
com.apple.driver.AppleUSBCardReader    2.6.1
com.apple.driver.AppleUSBTCKeyboard    201.6
com.apple.driver.AppleIRController    303.8
com.apple.iokit.SCSITaskUserClient    2.6.8
com.apple.BootCache    31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.iokit.IOAHCIBlockStorage    1.6.4
com.apple.driver.AppleFWOHCI    4.7.3
com.apple.driver.AppleUSBHub    4.2.4
com.apple.driver.AppleEFINVRAM    1.4.0
com.apple.driver.AppleSmartBatteryManager    160.0.0
com.apple.driver.AppleAHCIPort    2.1.7
com.apple.driver.AirPortBrcm43224    428.42.4
com.apple.iokit.AppleBCM5701Ethernet    3.0.5b8
com.apple.driver.AppleUSBEHCI    4.2.4
com.apple.driver.AppleACPIButtons    1.3.6
com.apple.driver.AppleRTC    1.3.1
com.apple.driver.AppleHPET    1.5
com.apple.driver.AppleSMBIOS    1.7
com.apple.driver.AppleACPIEC    1.3.6
com.apple.driver.AppleAPIC    1.4
com.apple.driver.AppleIntelCPUPowerManagementClient    142.6.0
com.apple.security.sandbox    1
com.apple.security.quarantine    0
com.apple.nke.applicationfirewall    2.1.14
com.apple.driver.AppleIntelCPUPowerManagement    142.6.0
com.apple.driver.DspFuncLib    2.0.5f14
com.apple.driver.AppleProfileReadCounterAction    17
com.apple.driver.AppleProfileTimestampAction    10
com.apple.driver.AppleProfileThreadInfoAction    14
com.apple.driver.AppleProfileRegisterStateAction    10
com.apple.driver.AppleProfileKEventAction    10
com.apple.driver.AppleProfileCallstackAction    20
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.iokit.IOFireWireIP    2.0.3
com.apple.iokit.IOSurface    74.2
com.apple.iokit.IOBluetoothSerialManager    2.4.5f3
com.apple.iokit.IOSerialFamily    10.0.3
com.apple.iokit.IOAudioFamily    1.8.3fc2
com.apple.kext.OSvKernDSPLib    1.3
com.apple.driver.AppleHDAController    2.0.5f14
com.apple.iokit.IOHDAFamily    2.0.5f14
com.apple.iokit.AppleProfileFamily    41
com.apple.driver.IOPlatformPluginFamily    4.7.0a1
com.apple.driver.AppleSMBusPCI    1.0.10d0
com.apple.driver.AppleBacklightExpert    1.0.1
com.apple.driver.AppleSMC    3.1.0d5
com.apple.nvidia.nv50hal    6.4.0
com.apple.NVDAResman    6.4.0
com.apple.iokit.IONDRVSupport    2.2.1
com.apple.iokit.IOGraphicsFamily    2.2.1
com.apple.driver.BroadcomUSBBluetoothHCIController    2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController    2.4.5f3
com.apple.iokit.IOBluetoothFamily    2.4.5f3
com.apple.iokit.IOSCSIBlockCommandsDevice    2.6.8
com.apple.iokit.IOUSBMassStorageClass    2.6.7
com.apple.driver.AppleUSBMultitouch    207.7
com.apple.iokit.IOUSBHIDDriver    4.2.0
com.apple.driver.AppleUSBMergeNub    4.2.4
com.apple.driver.AppleUSBComposite    3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice    2.6.8
com.apple.iokit.IOBDStorageFamily    1.6
com.apple.iokit.IODVDStorageFamily    1.6
com.apple.iokit.IOCDStorageFamily    1.6.1
com.apple.driver.XsanFilter    402.1
com.apple.iokit.IOAHCISerialATAPI    1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily    2.6.8
com.apple.iokit.IOFireWireFamily    4.2.6
com.apple.iokit.IOUSBUserClient    4.2.4
com.apple.iokit.IOAHCIFamily    2.0.6
com.apple.iokit.IO80211Family    320.1
com.apple.iokit.IONetworkingFamily    1.10
com.apple.iokit.IOUSBFamily    4.2.4
com.apple.driver.AppleEFIRuntime    1.4.0
com.apple.iokit.IOHIDFamily    1.6.6
com.apple.iokit.IOSMBusFamily    1.1
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    6
com.apple.driver.DiskImages    289
com.apple.iokit.IOStorageFamily    1.6.3
com.apple.driver.AppleACPIPlatform    1.3.6
com.apple.iokit.IOPCIFamily    2.6.5
com.apple.iokit.IOACPIFamily    1.3.0

That is not an application crash - that is a kernel panic, which means there is a hardware defect, a bug in the OS or a bug in a low level driver (like parts of the video driver). Kernel panics are not caused by applications, but by defective hardware or bugs in the OS and drivers.
Resetting prefs may avoid the settings that triggered the crash - but the cause remains in the hardware, OS, or driver code.
Since Apple is not going to update the drivers in 10.6.8, your best bet is to update the OS when you can, and hope the new drivers are in better shape. Unfortunately, it is also possible that you just have a bad GPU or video RAM - and fixing that would require replacing the video card or system (in the case of laptops or all-in-one machines).

FCP Crashes while using Magic Bullet Looks

Hi All,
We have recently installed Magic Bullet Looks onto our main edit machine. However, using it causes FCP to crash with really annoying regularity. It seems to be related to either auto save or thumbnails (opening a sequence with Looks applied and it will crash while loading the thumbnails onto the timeline for example - that could be a coincidence as it crashes in many other situations as well but always when working with MBL))
I've tried the usual preference trashing things but can't stop it happening. Anyone had any similar issues that they've been able to resolve? We aren't yet running Snow Leopard but I may try that as a potential solution.
If it matters - the machine is dual 3.2 quad core with 6GB of RAM running FCP 7. It also has a Blackmagic Extreme card (tried turning external video off - no difference)
All thoughts greatly appreciated,
Regards and a happy new year to all,
Richard

Couldn't agree more Jim - hence why I'm not using Snow Leopard yet as I had a nightmare in the early adoption of an older operating system. As for MBL, there seem to be many using it without problems so I don't think it's an issue with the product per say and it really is a very good plug-in. (That view will change to excellent once the problems go away) I just need to get to the bottom of which square peg is destined for which round hole and I'm hopeful that all will be well. I've also submitted a support question to Magic Bullet so will update if I get a solution. I like the CleanApp idea. I'll try that as well. (and I may even give Snow Leopard a go!)
R

Final Cut Pro 7 crashes while using Magic Bullet Look, any idea why this is happening?

everytime i open the filter, final cut pro 7 crashes, anybody else having this issue?

Angel,
You may have better luck posting in the Final Cut Pro forum. This is a general iMac forum, not many users on this forum use FCP.
Good luck!

Photoshop crashes when I use Edit in Photoshop CC 2014 from Lightroom 5.6

I have Adobe Lightroom 5.6. Whenever I try to Edit in Photoshop CC (2014) when Photoshop has not been started, Photoshop immediately crashes with a message of:
Adobe Photoshop CC 2014 cannot be opened because of a problem.
This happens regardless of what option I choose to Edit in: 1) Copy with Lightroom adjustments, 2) Copy, or 3) Original
If Photoshop is already open, I don't have this problem.
I am running Mac OS X Mavericks. Everything is up to date.
How can I correct this?

That is not an application crash - that is a kernel panic, which means there is a hardware defect, a bug in the OS or a bug in a low level driver (like parts of the video driver). Kernel panics are not caused by applications, but by defective hardware or bugs in the OS and drivers.
Resetting prefs may avoid the settings that triggered the crash - but the cause remains in the hardware, OS, or driver code.
Since Apple is not going to update the drivers in 10.6.8, your best bet is to update the OS when you can, and hope the new drivers are in better shape. Unfortunately, it is also possible that you just have a bad GPU or video RAM - and fixing that would require replacing the video card or system (in the case of laptops or all-in-one machines).

Photoshop crashes when I use adjustment layer HUE

Every time I use adjustment layer for HUE/Saturation. I put the eye dropper on a specific color and move it right or left and it crashes. Wants me to reopen and try again

I have a cloud account with Adobe 214.2.1
Mac ver 10.10 Yosemite
Adjustment layer Hue/Saturation open Holding down command key to use Hue slider. When I release it crashes
Thank you for taking the time
Izzy

100% cpu AE7 using Magic Bullet Look Suite 2.0

Hi
My pc is over 2Ghz and has 2 gigs of Ram and a high speed hard drive. My video is onboard but usually does very well with video rendering.
The only problem I seem to have is with Look Suite 2.0. I dont bother trying out the latest because it doesnt work with onboard video.
Anyway, 2.0 used to work perfectly fine for the 2 weeks I was rendering. But, recently it started giving me the "unknown exception caught by look suite" error. There does not seem to be a real fix for this.
But I monitored task manager for awhile while compiling projects. Loading effects filters like Curves, Twixtor and others didnt phase the CPU a bit. But after loading Look Suite and going through the presets, all of suddent the cpu went 100% and never came back down as long as AE7 is open. Even if I disable the plugins nothing changes.
So I tried saving the project with the plugins disabled in the composition. Then closed AE and reopened the project. Instant 100% cpu. Next, I deleted the Look Suite plugin from the composition. Reopened the project and everything was perfectly fine.
LOOK SUITE has some kind of incompatibility issue either with AE7 or another plugin that was running. I cannot be sure.
But the bottom line is this. Who's responsible? Adobe or Red Giant?
Red Giant doesn't seem to have a clue what to do. I dont want to upgrade to a version that works only with higher end graphics. I tried changing memory settings in AE and it really isnt needed. I am guessing the "unknown exception" is caused from the CPU overload because it pegs out the cpu while rendering and uses more and more of the page file as it runs, until it finally fails. But if Looks Suite wasn't already loading up on the cpu I would not have a problem. And, a week ago it wasn't hogging the resources. SOmething went snap.
Sorry for the long rambling.

Nope, CPU usage and RAM usage are more or less unrelated. CPU usage is merely dependent on the number of threads/ sub-threads/ handles fired by a program and since the Celeron D only handles a limited number of them, it is quite predictable that it will frequently peak an queue requests it cannot process immediately, when e.g. on a Xeon the same operation would barely register. Updating the processor may improve performance, but it mostly depends on the kind of effects you are using. If they are not particularly computationally intensive like several color correction effects, the benefits will be minor. if on the other hand you use a lot of Blurs and Glows for instance, the speedup may be considerable. Regardles of this, having lots of RAM and processing power is never a bad idea ;-)
Mylenium

Adobe premiere pro cc 2014 freezing with magic bullet looks

Hi-
I'm running windows 8 with this software and I'm getting intermittent crashing when trying to work on any project when I'm also using magic bullet Looks on it. The frustrating thing is that it used to work fine in premiere Pro CC, but using the 2014 version is very unstable. Also, I cannot go back to using the non-2014 version because the file format is incompatible with the older version and I don't have another version saved. I've already done hours and hours of editing in 2014 only to keep having crashes.
Is anyone looking into this or has any recommendations so I can get work done.
Thanks!
-Lok

I don't use magic bullet Looks but is that a 3rd party plugin?
If yes, have you checked with the vendor to see if it needs to be updated for the new structure of CC 2014?
http://blogs.adobe.com/jkost/2014/06/installing-the-2014-release-of-creative-cloud.html

Magic Bullet Looks Error in After Effects CC 2014 (Latest)

My PC specs:
Windows 7 Home Premium
Processor: Intel(R) Core(TM) i3-2350M CPU @ 2.30Hz 2.30Hz
RAM: 4.00GB
System Type: 64-Bit
This is for Adobe(R) After Effects(R) CC - 2014.1.1 Release (Version 13.1.1.13
I didn't get this issue when i was using Adobe After Effects CC (Version 12.2) instead of After Effects CC 2014 (Version 13.1.13)
Here is the issue:
When i add Magic Bullet Looks onto my clip and then press edit:
Gyazo - a978019a26d81a694b2eb7c7b222c333.png
It brings up the "Looks Builder" window:
Gyazo - 0c5413ac656bc4f251053331b455f635.png
After i hover over or click on a preset from the "Looks" tab and then after effects says "Not Responding" and I also get an error message saying "After Effects error: crash occured while invoking effect plug-in "Magic Bullet Looks.":
Gyazo - d20bd9ad8215288401e7194ccc2e75d4.png
Please respond as soon as possible
Thank you,
Thifyan123

By the way i am extremely sorry for my the name "Jimmy Savile" it was my friend who did it . And I don't know how to change it. I'm sorry if it offends you.

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.

Adjustment layer and Magic Bullet Looks corruption

I often find using the adjustment layers to apply colour correction an easy trick and therefore love the concept.
However, I've recently noticed that PP CS6.0.2 does not like MB Looks to be applied to adjustment layers all that well.
On two recent projects, the primary sequence has become corrupt (PP loads and quits immediately) and I have to recover the edit by copying the none adjustment layer tracks to a new sequence and then relinking the media.
Today, I spent 4 hours recovering another complex sequence and wanted to know if any other person has had a similar experience applying MB Looks to an adjustment layer?
A word of warning to others who might be thinking of the same 'trick'.
Perhaps I am expecting too much of the adjustment layer concept.
Thanks for any responses.
J.

I found myself here because... I was trying to open last saved project and it just crashes.
I did use Magic Bullet "Looks" and "Cosmo" on both footage and adjustment layers.
"Panic... Drink Coffee" !!!!! idea !!!!
Uninstall Magic Bullet
Launch CS6APP
Open same project file warning you don't have plugins installed.
Delete the "Adjustment Layers" (you won't be able to get the adjustment layer settings back but, you will get the edit back
Save project "new name"
Re-install plugins
Re-open CS6APP
"new name" project file opens fine without the adjustment layers.
But wait!!! Why should you uninstall Magic Bullet?????
Open a new project
Import entire project file into new project
Go to media bin and delete the "adjustment layers"
Find last Sequence that had the adjustment layers and you can go back to working
We put finishing effects on entire or even sections of full edit
1. Select edit < New Sequence from clip... apply effects on new sequence
2. Not "adjustment layers" BUT!!
2. Right now I found this just be an issue with RedGiant plugins I'm going to pass this post along to them..
This is a link to our project we had this happen too. (Sound tweaking)
Superfine Bakery : Who we are on Vimeo
CS6APP 6.0.5
MacBookPro Retina 16 gigs of ram
Thunderbolt 2 drive with source
USB 3 drive writing scratch
(2) external monitors attached

Photoshop crash when i use Magic Bullet Looks

Similar Messages

Maybe you are looking for