Thank you for replying. I thought it might be a silly question but it seems it never hurts to be 100% sure when it comes to final cut pro. I did a preference trash manually by going in to the fcp docs and finding the necessary folders and moving them to the trash, do you see any gain in letting the digital rebellion app do this again before I reinstall? I just got the fcp remover app and am going to use it. Back up is no problem, by paths I assume you mean where the project bin media is linked to the actual media folder and to keep an eye on where I set my capture scratch, render file folders etc when I reinstall. anything else?
The gamma shift has completely taken me by surprise and put my work load on hold. It started about a month ago but was in editing stages of a project so thought it might have been a box ticked in fcp that was not mean't to be or settings that were mismatched etc. but after careful analysis of settings it seems to happen regardless of what I do. It started when I was editing prores 422HQ footage that was a strange resolution 2048 x 871 I would apply an effect/plugin to the footage and the gamma curve would shift either making the footage contrasty or alternatively washed out. so from this I hypothesised that it was a data rate issue as I was editing 2k off a usb hdd. tryed it again this time editing from a firewire 800 Graid drive..same problem. decided to go back to basics, started editing 1920x1080 16.9 prores 422 footage originating from 8bit 420 material. when I add a effect/plugin as simple as the widescreen 2.35.1 and render that.. gamma shifts up, robbing the image of its colour accuracy and raising the blacks. My knowledge has only been able to take me so far as I feel this is bug related. the only things I can think about are in the past month I downloaded quicktime pro 7 which incidentally the latest version I have won't output prores 4444 but all other flavours, i installed Nvidia cuda graphics driver or at least I think I did in an attempt to get davinci resolve lite working and osx mavericks has come out, so keep asking my self is it a bug related with these and will a reinstall fix?