FORUMS: list search recent posts

Lock'n'Load and FCP 7 on OS X Mountain Lion

COW Forums : CoreMelt Plug-ins

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Christopher Mann
Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 16, 2012 at 2:25:32 pm

Lock and Load used to work fine on my Mac Pro with FCP7 until I updated the OS to Mountain Lion from Snow Leopard.

Since then I have had many issues with the plugin either refusing to track the motion (on very simple clips, in a timeline with only one video layer), or when it's tracked the motion using very exaggerated zoom factors (thousands of percent in some cases).

I've tried uninstalling and reinstalling Lock N Load but with no benefit. However, today I discovered what I think may be the cause - FX Factory. I decided to remove all my FCP plugins in case one of them was conflicting with LocknLoad, and after I reinstalled the latest update of FX Factory the crazy behaviour of Lock n Load started again. I just uninstalled FX Factory, and LnL seems to be OK again.

So my advice to anyone still using FCP7 is to get rid of FX Factory if you need to use Lock n Load.


Return to posts index

Roger Bolton
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 16, 2012 at 3:03:40 pm

which version of FxFactory did you have installed? We're not aware of any conflict, we'll investigate

-
CoreMelt V2 plugins


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 16, 2012 at 3:05:58 pm

I originally had FX Factory 3.0.4 - I also tried installing 3.0.6 and then the latest version 4.0 which has just been released - same issues with both.


Return to posts index


Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 17, 2012 at 12:34:55 pm

Well so much for that - thinking I had solved the issues with Lock'nLoad - no such luck.

I copied and pasted some clips that I had stabilized successfully in one sequence, into a new sequence. Same FCP7 project, video format etc (ProRes 422LT 1080p 25).

Now when I use LnL Frames I get the same problem of a zoom factor of over 1000% and the message "consider reducing stabilization strength". This is on a shot that worked fine in the other sequence, and in any case only needs a small amount of stabilization (it's a gentle Steadicam shot).

The Lock'n'Load X plugin seems to work OK, just not LnL Frames. I prefer to use Frames as it generally works a bit quicker and I don't have to wait for the "exporting XML data..." message which often gets to 99% and then stops for several seconds before the tracking actually starts.

It seems to me that Lock & Load has changed for the worse in being updated to work with FCP X and Premiere. While I understand that software moves on, it seems bizarre that an update should break something that was working fine.

Unless there is some conflict with something else that I'm missing.


Return to posts index

Eberhard Ammelt
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 17, 2012 at 2:10:16 pm

Hello Christopher,

it's not possible that Lock & Load Frames got worse because we support Premiere Pro and FCP X as well, because these are different plugins.

Inappropriate strong zooms are mostly due to tracking problems, which can be caused by frame reading issues. Lock & Load Frames uses FCP's plugin api to read frames while Lock & Load X reads the videos frames directly from the clip.
According to your observations it's likely that FCP 7 sometimes provides wrong video frames to Lock & Load Frames during motion tracking.
One reason for this problem could be a low memory condition.
Can you please check the log file for possibly related error messages?
Also, can you try to temporarily delete FCP 7's preferences? In some cases this has helped to fix the problem.

Regards, Eberhard


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 17, 2012 at 2:22:49 pm

By "check the log file" do you mean the Apple system log (via Console)?

I found the following errors in the system log from earlier this morning - hope you can make sense of them!

Nov 17 11:10:24 mac-pro.home Final Cut Pro[5045]: Error loading /Library/Plug-ins/FxPlug/Lock & Load FCP X.fxplug/Contents/MacOS/Lock & Load FCP X: dlopen(/Library/Plug-ins/FxPlug/Lock & Load FCP X.fxplug/Contents/MacOS/Lock & Load FCP X, 265): no suitable image found. Did find:
/Library/Plug-ins/FxPlug/Lock & Load FCP X.fxplug/Contents/MacOS/Lock & Load FCP X: mach-o, but wrong architecture
Nov 17 11:10:26 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class RGRegDialogSession2 is implemented in both /Library/Plug-ins/FxPlug/Cosmo.fxplug/Contents/MacOS/Cosmo and /Library/Plug-ins/FxPlug/Colorista_II.fxplug/Contents/MacOS/Colorista_II. One of the two will be used. Which one is undefined.
Nov 17 11:10:26 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class RGSerialNumberTransformer is implemented in both /Library/Plug-ins/FxPlug/Cosmo.fxplug/Contents/MacOS/Cosmo and /Library/Plug-ins/FxPlug/Colorista_II.fxplug/Contents/MacOS/Colorista_II. One of the two will be used. Which one is undefined.
Nov 17 11:10:28 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class libCompressorKit is implemented in both /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Plugins/Transcoder.bundle/Contents/MacOS/Transcoder and /Library/Application Support/ProApps/SharedA/Frameworks/Motion/Ozone.framework/Ozone. One of the two will be used. Which one is undefined.
Nov 17 11:10:28 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class objCWrapper is implemented in both /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Final Cut Pro and /Library/Application Support/ProApps/SharedA/Frameworks/Motion/Ozone.framework/Ozone. One of the two will be used. Which one is undefined.
Nov 17 11:10:28 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class LicenseObject is implemented in both /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Final Cut Pro and /Library/Application Support/ProApps/SharedA/Frameworks/Motion/Ozone.framework/Ozone. One of the two will be used. Which one is undefined.
Nov 17 11:10:42 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class ImageSequenceMedia is implemented in both /Library/Application Support/ProApps/Bundles/Soundtrack Pro Integration.bundle/Contents/MacOS/Soundtrack Pro Integration and /Library/Frameworks/AECore.framework/Versions/A/AECore. One of the two will be used. Which one is undefined.
Nov 17 11:10:42 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class MotionDocumentInfo is implemented in both /Library/Application Support/ProApps/Bundles/Soundtrack Pro Integration.bundle/Contents/MacOS/Soundtrack Pro Integration and /Library/Frameworks/AECore.framework/Versions/A/AECore. One of the two will be used. Which one is undefined.
Nov 17 11:10:42 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class OZTimeMarker is implemented in both /Library/Application Support/ProApps/Bundles/Soundtrack Pro Integration.bundle/Contents/MacOS/Soundtrack Pro Integration and /Library/Frameworks/AECore.framework/Versions/A/AECore. One of the two will be used. Which one is undefined.
Nov 17 11:10:42 mac-pro.home Final Cut Pro[5045]: objc[5045]: Class LicenseObject is implemented in both /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Final Cut Pro and /Library/Frameworks/Qmaster.framework/Versions/A/Frameworks/SwampTypes.framework/Versions/A/SwampTypes. One of the two will be used. Which one is undefined.
Nov 17 11:10:42 mac-pro.home qmasterqd[5054]: Using "localClusterAdminKey" admin key


Return to posts index


Eberhard Ammelt
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 17, 2012 at 3:15:51 pm

The log is right, but the messages are not related.
Are there any further messages printed during motion tracking?

Eberhard


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 17, 2012 at 3:17:20 pm

I will have to reload the project in FCP7 and try it again to see if there are any other messages - I am rendering and burning the DVD right now but will test again after that...


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 26, 2012 at 11:25:43 am

Okay I had an opportunity to try this again and I am still experiencing issues.

I created a fresh sequence (1080p Prores 422LT 25 fps) and dropped in a clip from a Panasonic GH1 on a Steadicam. Not a very shaky clip, just in need of some minor smoothing.

So new sequence, one clip on the timeline.

LockNLoad Frames gives me the same problem - excessive auto-zoom (up to several hundred percent).

LockNLoad X gives me the error "No motion tracker app proxy".

This is what's in the system.log (via Console):

Nov 26 11:17:43 mac-pro.home DictationIM[5953]: IMK Exception in client(wrapper):[0x7fafa940f7e0] InputController:[0x7fafa940f1d0]
Nov 26 11:17:47 mac-pro.home spindump[5774]: Client side error: Connection interrupted
Nov 26 11:17:47 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5920 [coresymbolicatio]
Nov 26 11:17:47 mac-pro com.apple.launchd[1] (com.apple.coresymbolicationd[5920]): Exited: Killed: 9
Nov 26 11:17:48 mac-pro com.apple.launchd.peruser.501[259] ([0x0-0x14c14c].com.apple.inputmethod.ironwood[5953]): Exited: Killed: 9
Nov 26 11:17:48 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5953 [DictationIM]
Nov 26 11:17:48 mac-pro.home Mail[337]: The contentValues and content bindings need to be bound to the same observable object
Nov 26 11:17:50 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5956]): Exited: Killed: 9
Nov 26 11:17:50 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5956 [SleepServicesD]
Nov 26 11:17:58 mac-pro com.apple.launchd[1] (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[5950]): Exited: Killed: 9
Nov 26 11:17:58 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5950 [xpcd]
Nov 26 11:18:04 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5966]): Exited: Killed: 9
Nov 26 11:18:04 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5966 [SleepServicesD]
Nov 26 11:18:04 mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.A6B3D950-D556-412C-B280-6F4090DFBC19[5960]): Exited: Killed: 9
Nov 26 11:18:04 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5960 [QuickLookSatelli]
Nov 26 11:18:22 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5973]): Exited: Killed: 9
Nov 26 11:18:22 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5973 [SleepServicesD]
Nov 26 11:18:22 mac-pro com.apple.launchd.peruser.501[259] (com.apple.tccd[5971]): Exited: Killed: 9
Nov 26 11:18:22 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5971 [tccd]
Nov 26 11:18:23 mac-pro com.apple.launchd.peruser.501[259] ([0x0-0x14f14f].com.apple.inputmethod.ironwood[5969]): Exited: Killed: 9
Nov 26 11:18:23 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5969 [DictationIM]
Nov 26 11:18:24 mac-pro com.apple.launchd.peruser.501[259] (com.apple.pbs[5959]): Exited: Killed: 9
Nov 26 11:18:24 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5959 [pbs]
Nov 26 11:18:34 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5978]): Exited: Killed: 9
Nov 26 11:18:34 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5978 [SleepServicesD]
Nov 26 11:18:34 mac-pro com.apple.launchd.peruser.89[451] (com.apple.distnoted.xpc.agent[456]): Exited: Killed: 9
Nov 26 11:18:34 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 456 [distnoted]
Nov 26 11:18:43 mac-pro com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[4029]): Exited: Killed: 9
Nov 26 11:18:43 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 4029 [cfprefsd]
Nov 26 11:18:47 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5982]): Exited: Killed: 9
Nov 26 11:18:47 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5982 [SleepServicesD]
Nov 26 11:19:34 mac-pro com.apple.launchd.peruser.501[259] (com.apple.tccd[5994]): Exited: Killed: 9
Nov 26 11:19:34 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5994 [tccd]
Nov 26 11:19:36 mac-pro.home distnoted[5999]: # distnote server agent absolute time: 9284.725816357 civil time: Mon Nov 26 11:19:36 2012 pid: 5999 uid: 89 root: no
Nov 26 11:20:20 mac-pro com.apple.launchd.peruser.488[6011] (com.apple.cfprefsd.xpc.agent[6013]): Exited: Killed: 9
Nov 26 11:20:20 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6013 [cfprefsd]
Nov 26 11:20:21 mac-pro com.apple.launchd.peruser.89[5996] (com.apple.cfprefsd.xpc.agent[6000]): Exited: Killed: 9
Nov 26 11:20:21 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6000 [cfprefsd]
Nov 26 11:20:21 mac-pro com.apple.launchd.peruser.501[259] ([0x0-0x151151].com.apple.inputmethod.ironwood[5991]): Exited: Killed: 9
Nov 26 11:20:21 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5991 [DictationIM]
Nov 26 11:20:22 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[5989]): Exited: Killed: 9
Nov 26 11:20:22 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5989 [SleepServicesD]
Nov 26 11:20:23 mac-pro com.apple.launchd.peruser.501[259] (com.apple.pbs[5979]): Exited: Killed: 9
Nov 26 11:20:23 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 5979 [pbs]
Nov 26 11:20:36 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[6062]): Exited: Killed: 9
Nov 26 11:20:36 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6062 [SleepServicesD]
Nov 26 11:20:53 mac-pro.home spindump[5774]: Saved hang report for Final Cut Pro version 7.0.3 (7.0.3) to /Library/Logs/DiagnosticReports/Final Cut Pro_2012-11-26-112052_Mac-Pro.hang
Nov 26 11:21:12 mac-pro com.apple.launchd.peruser.501[259] (com.apple.tccd[6075]): Exited: Killed: 9
Nov 26 11:21:12 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6075 [tccd]
Nov 26 11:21:13 mac-pro.home mdworker[6069]: Unable to talk to lsboxd
Nov 26 11:21:14 mac-pro kernel[0]: Sandbox: sandboxd(6078) deny mach-lookup com.apple.coresymbolicationd
Nov 26 11:21:17 mac-pro com.apple.launchd.peruser.501[259] ([0x0-0x156156].com.apple.inputmethod.ironwood[6070]): Exited: Killed: 9
Nov 26 11:21:17 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6070 [DictationIM]
Nov 26 11:21:18 mac-pro com.apple.launchd[1] (com.apple.sleepservicesd[6063]): Exited: Killed: 9
Nov 26 11:21:18 mac-pro kernel[0]: memorystatus_thread: idle exiting pid 6063 [SleepServicesD]
Nov 26 11:21:19 mac-pro com.apple.launchd[1] (com.apple.coresymbolicationd[5967]): Exited: Killed: 9


Return to posts index


Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 26, 2012 at 11:44:24 am

I restarted FCP7, removed and reapplied LocknLoad Frames, and it worked fine this time.

So I don't know what to make of this problem. It seems to come and go.

FWIW I've also noticed that if I have moved a project to a different drive, then LnL is more likely to throw errors - even though the scratch disks are reset to the new drive and the media is correctly linked.


Return to posts index

Eberhard Ammelt
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 26, 2012 at 12:30:35 pm

The log doesn't contain related messages, except for the FCP hanging event. Are you sure you've looked at the correct time and you've chosen "All Messages"? FCP usually writes some messages when launching, loading a project and when rendering.

Lock & Load Frames does not directly work with video files, this is all handled by FCP. So, if you notice problems when you move a project to a different drive this can only be caused by FCP.
Did you try to reset FCP's preferences?
Also, I'd try to check for problems/repair of the volume and file permissions.

If Lock & Load X shows the error message "No motion tracker app proxy", this could be to due to sandbox in OS 10.8. What are your security settings? Can you try this again with less strict security settings (All all applications to launch)?

Eberhard


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 4:06:33 pm

Thanks for the suggestions Eberhard - I started with a new FCP7 Project and had the same problems - however, trashing the FCP7 preferences seems to have solved it - LockNLoad Frames is working now.

So maybe it was just a Preferences issue.

Thank you for your help - I will let you know if I see the problem again! :)


Return to posts index


Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 4:41:15 pm

Well I thought that might turn out to be too good to be true...

I saved and closed the project and quit Final Cut - then relaunched it and reopened the project. The last clip that I stabilized was now showing excessive zoom - over 3000% - without me having done anything except close and reopen FCP7.

This is a new project containing only one 20-minute sequence; the stabilized clips are right at the beginning of the sequence.

I opened the clip in the Viewer, and LnL reports "no tracking data". I click "Track Motion" and it gives me this error:

Please set viewer size to 100 percent and try again. If Digital Cinema Desktop is enabled, please switch it off during motion tracking.
If the problem persists, please contact support@coremelt.com and provide this information:

'Expected: 1920, 540; Actual: 637, 179'
[Error: -1, Tracker: 904253168]

The following errors appear in the system.log file:

Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 0
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 16
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 32
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 48
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 64
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 80
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 96
Nov 28 16:39:03 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 29, 112
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 0
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 16
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 32
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 48
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 64
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 80
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 31, 96
Nov 28 16:39:32 Mac-Pro.local Final Cut Pro[12020]: Frames missing in Tracker: 29, 112


Digital Cinema Desktop is not enabled. Setting the Viewer size to 100% makes no difference.

I am at my wits end with this - I rely on LocknLoad to smooth out my Steadicam shots and this is really screwing up my workflow. Any suggestions you have would be appreciated.


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 4:48:28 pm

Okay here's another weirdness for you guys to investigate.

I removed LockNLoad Frames from the last Steadicam clip and tried LnL X. That worked.

However, I have a dissolve transition between the preceding clip (stabilized with LnL Frames) and the last clip (stabilized with LnL X). As soon as the transition starts, the magnification of the outgoing clip jumps by a factor of about 200%, ruining the cross-dissolve.

So it seems your two plugins are not compatible with each other?! I guess I could replace all the instances of LnL Frames with LnL X...


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 4:50:34 pm

....no - I just replaced LnL Frames with LnL X on a clip that was previously OK, and I am now back to excessive zoom factors (190%).


Return to posts index


Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 5:10:02 pm

...and finally: I quit Final Cut 7, restarted and opened the project, removed all the LnL filters and reapplied LnL Frames to the clips - and it all worked fine.

So maybe there is some weird memory issue.

But it's frustrating that the problem is so unpredictable.


Return to posts index

Eberhard Ammelt
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 7:29:04 pm

This all sounds like the problems are mainly caused by getting incorrect video frames from FCP for motion tracking. E.g. , as you report, the provided frames can have wrong image size.
If resetting FCP's preferences doesn't help permanently, it's difficult to give further suggestions.
If your projects are complex, FCP might run out of memory, which can cause this kind of failure too, but you would see related error reports in the log.

The problem appeared only after updating to OS 10.8, right? We're not aware that such problems occur more often on OS 10.8, nor is there any known incompatibility between Lock & Load X and Frames.

Did you install other plugins recently? If yes, could you try to disable them temporarily?

Eberhard


Return to posts index

Christopher Mann
Re: Lock'n'Load and FCP 7 on OS X Mountain Lion
on Nov 28, 2012 at 8:41:12 pm

Thanks Eberhard,

The previous project was quite complex, but this was a new one with just one 15-minute sequence, 3 video tracks and two audio tracks, and all the stabilized clips were on one track right at the beginning of the timeline. So I don't think FCP is running out of memory.

I did previously try removing all plugins except LocknLoad but that didn't make any difference if I recall correctly.

Right now I have just the Magic Bullet suite installed alongside LocknLoad. It could be a factor, but I used it for a long time alongside LocknLoad without problems.

As you say, I have only started to have problems since upgrading to Mountain Lion. I guess one option is to do a completely fresh install of the OS, applications and plugins, but I don't really have time for that right now!

Anyway thanks for your help - I will let you know if I get any other messages that might help solve the question.


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 CreativeCOW.net All Rights Reserved
[TOP]