Bill Buchanan
Forum Replies Created
-
Most all previous drivers can be found on BMD’s web site.
Bill Buchanan
Buchanan Film Co. -
Matt/Baz:
I deleted, then re-conformed all audio in the project, saved and closed the project, restarted XP, reopened the project, put a clip on the timeline, no crash…then adjusted the length of the clip (by dragging one end of it) and,”Gotcha! A serious error has…” I reopened the project, and as usual no matter how fast I adjust, move, bring more clips, groups of clips, whatever, I can’t make it crash. As I mentioned before, sometimes I can get the crash after re-opening the project, but I don’t recall ever getting it after re-opening the project the third time.
Bill Buchanan
Buchanan Film Co. -
Nevermind about how to delete the pref file in 1.5. I remembered holding down the shift key, etc.
Bill
-
Baz:
No, I haven’t deleted the pref file to start afresh. I forget how to delete the Pref file in 1.5. I will give re-conforming the audio files a shot, though it’s beyond me why a corrupt file–audio or video–would cause an intermittent problem. Thanks again for your help and response.
Bill
-
Baz/Matt:
I hid all the folders, opened the project and did the “all offline” as you suggested.
Tried dragging any number of long and short clips/placeholders to the timeline, adjusted lengths, etc. I could not generate a crash.
Baz, as far as “slowly reintroducing clips” trying to find “corrupt media,” I really cannot do that since this project contains over 5,000 clips.
Also, the crashing is so random, so intermittent AND it only occurs (if at all) with the first, second or third clip put on the timeline. Typically, after I reopen the project the second or third time, I don’t get anymore crashes. Since I (and DKH Lai) experienced no crashes with V5.0, surely there must be something in the 5.1 to 5.2 drivers.
Are you suggesting that if only one or more media files are corrupt (out of hundreds or even thousands), crashing could occur? If so, is there any other way to seek out corrupt media files other than your first suggestion?
Bill Buchanan
Buchanan Film Co. -
Baz:
Watching PF usage (and all the other I-have-no-idea-what-they-mean readings) in Task Manager, there doesn’t seem to be anything unusual happening when the crashing occurs or when it doesn’t.
BTW, I increased the page file size setting to 1500megs initial and 4500 max, and still get the error on occasion.
Bill Buchanan
Buchanan Film Co. -
Adrian:
My setup: Two RAID 5 arrays across 2 8-channel Broadcom RAIDCore SATA controller cards tied to 14 300gb sata Seagates. It’s fast as hell, about 400mb/s read and 280mb/s write according to BMD’s disk speed utility. This setup is really overkill for even 10-bit uncompressed SD work, but provides ample storage for the size projects I typically shoot and cut. RAIDCore SATA controller cards are I believe one of the best if not the best available. In fact, BMD has them at the top of their list of approved cards for their SD line. And RAIDCore support folks are second to none.
Anyone doing long-form work, capturing enormous amounts of material, and not using RAID 5 or some other redundancy level, is in my view dancing with the devil. On two occasions within the last 6 months, I’ve had 3 drives go south–one at one time, and later, two at the same time, and because of raid 5, I didn’t lose a single file nor have any down time while the arrays rebuilt themselves. Faced with having to re-capture thousands of files TWICE had mine been a RAID O setup, I’m certain I would have done any number of controlled substances.
On the other hand, for those folks who really get off on capturing the same footage over and over, then RAID 0 is definitely the way to go.
Bill Buchanan
Buchanan Film Co. -
Matt/Baz:
A bit lengthy, but perhaps this description will help. As I mentioned before, the project at hand is huge in terms of the number of clips in the bins (over 5,000 clips). But at this point, the timeline is empty! So, Matt, I don’t know if sending you the project file will help you or not. If so, please send me your email address.
I’ve just finished capturing everything and am ready to begin cutting the show. The project file is just under 40 megs. A 10-bit ntsc project, every clip was captured via SDI at 10-bit uncompressed, using about 3tb of Raid 5 storage.
Coincidentally, I thought it might be a VM issue that had something to do with the crashing, and I’ve tried any number of VM settings all the way from “system managed” to as low as 100megs initial and max to as high as 1gb initial, 3gb max (my sys has 3gb RAM with the memory extension “switch” activated). None of these settings seemed to make a difference. With the 100/100, I did get the message window after a few minutes “Your VM is low and Windows is increasing it…” Often times with the 100/100 setting, I would wait until that message came and went before moving a clip to the timeline. Still, I would usually get the crash.
Again, the crash has only occurred ONLY after restarting the sys and opening the project. I usually don’t get the crash if I re-open the project without first restarting the sys. However, on occasion, I’ve gotten the crash the second or third time I re-open the project. If the crash does not occur when I move the first clip to the timeline, then I can work all day without another crash.
Another important point: Yesterday I uninstalled V5.2 and reinstalled V5.1 and 5.1.2. With those earlier versions, the crashing still happened. BUT, when I installed V5.0, NO crashes, and I tried everything to make it crash. Wouldn’t happen.
Back to the memory issue. With V5.0, in Task Manager, the PF Usage would level out at about 1.24gb after the project finished loading. But with V5.2, it levels out at about 970megs, then momentarily drops to about 700 (with no clip picons/thumbnails activated). When I start activating thumbnails in various bins, the PF Usage rises up to around 1.5gb, then momentarily drops down below 800gbs (apparently the memory they require is being moved to VM.
That the crashing it so intermittent, makes one crazy as an outhouse rat.
Bill Buchanan
Buchanan Film Co. -
Thanks, Matt. installed the fix, and you’re right. I solved the TC issue. Unfortunately, the “Sorry, a serious error has occurred…” is still with us.
Here’s how it played out: Following installation of your driver fix, I opened the project. Captured a clip, saw that the TC didn’t disappear. Good. Then, I pulled THAT clip over to the timeline. No crash. So far so good. Dragged some other clip over to the timeline, and the moment it hit the timeline, got that damned error message.
Prior to installing your fix, I had V5.0 installed and was unable to make the project crash, no matter how quickly I adjusted lengths of clips, moved them around.
Thanks again for getting the batch capture issue fixed. No doubt you guys will get whatever’s causing the crashing fixed soon, too.
Bill Buchanan
Buchanan Film Co. -
After re-installing 5.1.2, the “…serious error has occurred…” DID NOT go away.
Bill Buchanan