Bill Buchanan
Forum Replies Created
-
That 10-bit files resulting from effects applied to 10-bit files are not possible with XP is not good news.
Does anyone know whether or not the 64-bit version of XP features this limitation?
Bill Buchanan
Buchanan Film Co. -
Hey Luke:
Got me! When I wrote that message, I believed my crashing problems were related to the Parhelia. But, after temporarily replacing it with a nVidia 5200, the crashing continued. Also, with the 5200 I was unable to monitor (to TV) a DV project I was cutting at the time. BTW, I never experienced the black flashes others were having.
So, I reluctantly reinstalled the Parhelia. Matrox has updated their drivers any number of times since then, and perhaps you’re right that now their cards do work well with BMD cards. Apparently mine does and has all along.
That said, I’m considering swapping the Parhelia for a nVidia 6600 or 6800 to take advantage of Magic Bullet’s faster rendering feature. And, since I’m not cutting any DV projects, I don’t need Matrox’s monitoring feature.
You guys might want to run some tests with the Parhelia. Who knows, they might work just fine, like mine.
Cheers,
Bill Buchanan
Buchanan Film Co. -
Stewart:
I’ve been using a Parhelia 128mb AGP since installing a Dklnk Extreme with no (graphics card-related) problems whatsoever. With PPro, the monitoring feature it provides and that you want is a real plus.
I have yet to learn from BMD or from other users exactly why Matrox cards are not recommended or “supported.”
Bill Buchanan
Buchanan Film Co. -
Geoff:
Thanks for posting this question. Unfortunately, only 2 or 3 people on this particular planet know the answers and no one knows who they are. After experimenting with about every conceivable setting, I think checking the “system managed size” is the best way to go (and keeping the page file on your system drive).
Bill Buchanan
Buchanan Film Co. -
I wish someone would respond to Adrian’s inquiry, since having access to the safe action and title feature is important to many of us.
Bill Buchanan
Buchanan Film Co. -
Matt:
Thanks for the Happy Thanksgiving wishes. Yes, Andrew did send me a beta cut that cured the crashing problem. Because of him and the developers who worked it up so quickly, I now have a reason to live.
Bill Buchanan
Buchanan Film Co. -
A follow-up: Just for the hell of it, I again reinstalled BMD V5.0 yesterday and could not make that same ‘huge’ project crash.
I noted in Task Manager that PF Usage numbers were different with V5.0 and V5.2.2. After loading that project with V5.0 installed, PF Usage was about 1.20gb. But with 5.2.2 installed, it was only 720mb.
Obviously, the two drivers govern differently how PPro handles memory, and because of 5.2.2, I’ve spent a great deal of valuable time staring at my monitors while reloading this project along with spewing copious amounts of profanity when that farging “…serious error…” message appears.
Though V5.0 doesn’t offer the RT, etc. features that 5.2.2 does, it does allow work to continue on this very large project. I’m hopeful the engineers at BMD will have addressed this issue in their next release.
BTW, I also installed one of the recommended nVidia cards to determine if my (not supported) Matrox Parhelia card might have been the culprit. Nope. The project crashed like crazy with the nVidia, just like it does with the Parhelia.
Bill Buchanan
Buchanan Film Co. -
The crashing continues. However, yesterday I loaded a huge project and edited all day without a crash.
BUT, after closing it, then reloading it, it crashed any number of times. Only after I reloaded the project about 3 times was I able to place a clip on the timeline without the “…serious error…” appearing. Sometimes the error message appears when I diminish the interface.
This leads me to believe that as the project loads something does not get loaded properly everytime. As I’ve mentioned before, PPro doesn’t like huge projects, because I believe of some memory-allocation/whatever issue. I’m working on smaller projects (smaller libraries and timelines) that never crash. Go figure.
Bill Buchanan
Buchanan Film Co. -
You should check each drive with Iometer. It’s very likely one or more of the drives in your array is excessively slow, and that will gum up the works, which includes getting inconsistent speed readings. Had a similar problem, and that’s what it turned out to be. Replaced the slow drives; problem cured.
Bill Buchanan
Buchanan Film Co. -
Matt:
No doubt Baz knows his stuff. Since there are a relative few having the crashing problem, I wonder if all or most of us are working with long-form projects with many hundreds or thousands of clips in the bins (and/or on the timeline)? Well known for its sorry memory-handling ability, I’m convinced my PPro 1.5 problems are somehow memory-related, since the project that’s giving me all the grief features a 40mb project file and over 5,000 clips in the bins.
As a test, I created a New Project with the same settings (10-bit Uncmprsd, NTSC, etc) and imported 100 or so clips. Tried everything I could think of the make it crash and couldn’t.
I continue to beseech all the gods that PPro 2.0 will be 64-bit and your BMD drivers would quickly support it. Perhaps only then will those of us working in long-form be allowed to join the rapture.
Bill Buchanan
Buchanan Film Co.OS: WinXP Pro, sp2
MB: SM x5da8
RAM: 3gb (with 3gb extended memory switch enabled)
CPUs: Xeon 3.06
Graphic: Matrox Parhelia 128
Video Cap: BMD Extreme
Sound Card: None
RAID Controllers: 2 RAIDCore 4852
Video Arrays: 2 RAID-5 (1.7tb ea)
Sys Drive: 80gb WD eide
Audio Drive: 120gb WD eide