- Posts: 107
- Thank you received: 0
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
10.08 crashing a lot
Is it mainly to do with the USB2 drive being too slow? The crashes seem to happen when I'm working fast and there's a bit of background rendering going on. If I wait for each change to render, it crashes less.
Any advice?
Please Log in to join the conversation.
Please Log in to join the conversation.
My computer was working really well using multicam shoot then the software suddenly crashed. I've re opened FTPX but the footage is now runing slow.
It's driving me mad and my client needs the footage by 5pm this eve.
I'm taking the footage directly from the hard drive.
Any ideas on how to solve this.
My computer about 2 weeks old and is a
mac mini
Processor 2.6 GHz Intel Core i7
Memory 16GB
Intel HD Graphics 4000 768mb
and presumed it word be fast enough when I bought it ?
Neil
Please Log in to join the conversation.
- TrixTrax9000
-
- Offline
- Platinum Member
-
- Posts: 1213
- Thank you received: 142
Please Log in to join the conversation.
TrixTrax9000 wrote: The FCPX software needs to be on the same hard drive as the OS Operating System, all media, projects & events on a DIFFERENT Hard Drive which is at least Firewire 800 7200 rpm, or preferably ThunderBolt.
Why different drives, I don't under stand this ?
Neil
Please Log in to join the conversation.
If you really are using a USB 2 drive, that is not ideal. Probably want to get a usb3 or thunderbolt drive after this job.
Please Log in to join the conversation.
Video editing software runs several streams of live video and audio to and from the hard drive. Hard drives have limited data bandwidth, just like your Internet connection. Video editing can eat up all that bandwidth really fast.
The OS and apps need a certain amount of free bandwidth so the overall system runs smoothly, also.
Putting all of that on one drive eats up the bandwidth, slows down the system, and can cause other symptoms such as apps locking up, apps unexpectedly quitting, and system crashes. Very similar to what can happen when a drive becomes too full (all drives need 10-15% of their capacity as free space).
So we put Projects and Events on a secondary drive, so that that media has plenty of bandwidth to stream. Then the OS and apps have plenty of bandwidth to work properly.
USB 2.0 is too slow for video editing. You can physically use it to a point, but it will give you problems in the long run. There is nothing that will fix it short of finding a drive that is capable of proper video editing speeds, such as FW800, USB 3.0, Thunderbolt. Also, all spinning disk drives MUST be 7200rpm for video editing, as the read/write speed needs to keep up with the speed required for streaming all of that video and audio.
RAID enclosures can be even faster.
Bear in mind that an unrendered timeline, each clip is a separate stream. The purpose of rendering is to write it all to one video and two audio streams, giving better playback, not to be multiple video and several audio streams at one time.
Please Log in to join the conversation.
- cinemaloha
-
- Offline
- Elite Member
-
- Posts: 163
- Thank you received: 36
I have done all the necessary maintenance processes: trash prefs, disk warrior, repair permissions, trash renders, etc.
I run a late-2012 iMac, 32GB RAM, 2GB VRAM, 3TB Fusion, Media/Projects/Events on a Pegasus R6 12TB Thunderbolt RAID5. My system drive has 1TB free space & the R6 has 7.9TB free space. It doesn't matter how fast my system is, FCPX will halt my workflow especially when in the zone. I love FCPX but also hate it.
In the OP's situation, USB2.0 is too slow but even when you have the latest greatest machines, FCPX will throw a wrench in and crash or slow down. I believe .8 has a multicam bug.
Please Log in to join the conversation.
For what it is worth, one large problem we have had with FCPX, as well as many other apps (Latest Creative Suite seems to crash very frequently, but Photoshop has no autosave), are corrupted fonts and font caches. You might want to try something that would clear you font caches. Just a shot in the dark.
Please Log in to join the conversation.
- Scott Markowitz
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 31
If it's larger than 100mb, then create a new event, and move some of your collections into the new event.
Please Log in to join the conversation.
- cinemaloha
-
- Offline
- Elite Member
-
- Posts: 163
- Thank you received: 36
I've come across other posts saying it's the fonts, corrupted clips in the timeline, prefs, corrupt renders, etc - so it's hard to know which one is actually causing an error. At any rate, I send all my crash reports with comments stating what I was doing and how I arrived to a crash. I hope Apple sorts this out.
Please Log in to join the conversation.
It can be hard to troubleshoot sometimes as troubleshooting in general is time consuming. Any chance you are using broadcast monitoring? I did have problems with my Matrox and crashing a while back. I have the same setup except I have a Thunderbolt to esata RAID, and I'm having zero problems with multicam.
If you want to figure this out a bit more contact me through my company web site, onecreative.net. You can perhaps send me some logs and I can give you some more ideas.
Please Log in to join the conversation.
So while I've noticed more issues on the Lion and 10.0.8, I can't really say that those are the reasons for the crashes, I just know that overall, this computer is not as awesome as my personal workstation.
But I would also jump on the bandwagon and say that you're gonna go bald if you keep editing with USB 2.0.
Please Log in to join the conversation.
Please Log in to join the conversation.

