5dtorgb for windows keeps crashing drivers#
5dtorgb for windows keeps crashing archive#
5dtorgb for windows keeps crashing pro#

5dtorgb for windows keeps crashing pro#

In addition to training, I also bought a new max spec 15' Macbook Pro Retina, G Tech Thunderbolt 8TB drive and a shiny new FCP X Logic Keyboard, so the investment has been reasonably committed. If I could switch off the magnetic malarkey, I'd probably head back - although the constant crashing when I tried to do certain things too quickly was an irritation. I guess I developed what the Apple Nazis would call 'bad habits' and these just don't work within the constraints of a magnetic 'my first pony' NLE. I also find the magnetic timeline a straitjacket - all the stuff I loved after being dragged kicking and screaming from Avid to FCP4, the feeling of being unconstrained, grabbing clips or groups of clips and bunging them anywhere I wanted, like Media 100 used to be. It was seriously slowing me down and constantly crashing. I gave up on it for the time being a couple of weeks back, just prior to doing the edit of my first C100 gig. Don't hesitate to contact me if you have any specific problems that I might be able to advise you on. I've never used FCPX to capture files and I edit by referencing files rather than importing them. Strangely enough, as you describe in your post, I still use FCP7 to capture files onto an external drive. Technically I've now got a really solid and extremely fast set up and feel very confident that I've made a good decision in sticking with FCPX. The biggest transformation for me was to buy the new (2012) 3.4Ghz 27' iMac with a fusion drive and 32Gbs of Ram ( I got tired waiting for the new MacPro) and also get a Gtech Thunderbolt drive. Things got so bad that I almost thought of getting Premier Pro! ( Adobe's a bunch of fun at the moment eh ) But I stuck with it and from vers 10.0.6 onwards I've not had any serious issues and now think it is how it should have been at launch. I've been using it since it was launched and had huge problems initially, constant crashes, spinning balls and getting used to a new way of working after 8 years of FCP7. What's up with you and FCPX? Is it working correctly on your setup or do you simply not like the way it works? Magnetic Timeline, compound clips etc etc ? Keep trying and let us know how you get on. I'm hanging around for my old friend, Lightworks, which I last used to cut Take That's final live concert for BBC1 in 1994. There's so much excited bollocks being spouted about FCP X and how wonderful it is, I find myself questioning my own sanity. That's the problem with being an old fart and established film editor. For me, it's absolutely and utterly crapulent for editing (and, believe me, I've tried to get on with it and spent £1000 on kit and one-to-one training in the process) - but useful for ingest and grading/captioning an exported Quicktime from FCP 7. That's one thing I've found very useful about FCP X.

5dtorgb for windows keeps crashing archive#

It means you can store AVCHD as your space-friendly archive format and, should you ever need to restore a project, you can re-ingest the AVCHD with FCP X, move the resulting PR422 clips to your FCP 7 Capture Scratch folder and the clip properties should all match up when you re-link media in FCP 7. That's a useful thing for long term storage and retrieval. It will give all the transcoded clips a UID, based on the time and date it was shot. *** ALTERNATIVELY *** use FCP X to ingest your material. It has been an FCP feature for years and is generally bullet-proof, not withstanding the fact that it doesn't give any kind of 'waiting' indicator while it's first looking at the SD Card and generating the thumbnails.

You shouldn't have issues with the L&T process at all.

5dtorgb for windows keeps crashing drivers#

Try ditching your FCP 7 preferences and have a look to see if any other camera drivers might be causing a clash. You mention that your system is crashing. Just don't change the clip names directly in the browser, as that breaks the link to the media. Nothing wrong with that - you can add logging notes in the browser later on, if you want to. Now is the time to add any metadata you'd like - otherwise, the clips will default to Clip 1. Your spanned clips should go in without any missing frames. Select them all (FCP defaults to ProRes 422 transcode from AVCHD - but you can double check in the cog setting, Preferences.) All of your clips will be sat as thumbnails in the L&T list. FCP will appear to be doing nothing.Ĭome back after a couple of minutes. Point it at the SD Card (called 'Canon') and hit return. You already have everything you need to do this properly, without any missed frames. Sorry - I'm a little bemused by this thread and talk about Clipwrap.