Bill Buchanan
Forum Replies Created
-
Oops. Spoke too soon. Fired up the sys this morning, opened the project, placed a clip on the timeline and was immediately greeted by, “Ha Ha Ha, a serious error has…”
I’m going to uninstall 5.2 and re-install 5.1 to see what happens. Will post results later.Bill Buchanan
Buchanan Film Co. -
Matt:
I uninstalled and reinstalled 5.2 and Viola! I can’t make the app crash. So, all’s well at the moment. Also, no rendering problems whatsoever. RT effects, etc. work very well, too.
Bill Buchanan
Buchanan Film Co. -
Luke:
The project at hand has literally thousands of clips in the library (all 10-bit uncompressed), and am just starting to cut the show. So, at this point the timeline is virtually empty. The 39mb project file loads fine–takes about 7 minutes. The crashes occur a split second after I place a shot on the timeline. Or, if the crash doesn’t occur after the shot is placed, it will when I try to adjust its length. I might add that I have just booted up the system in the morning.(Now I am wondering whether my loading the project before the all the “processes” listed in Task Manager have finished loading might be the culprit)
When I re-open the project, it will usually crash again as before. But today, for example, after two or three times re-opening the project, it did not crash, and I’ve been working with it all day, without another crash.
Since all I was doing was capturing while V5.1 was installed, I don’t really know if the crashing would have happened with that driver or not.
I will uninstall/reinstall 5.2 and/or go back to 5.1 to see if that fixes the problem, since I recall doing that many months ago with a previous version with which I was getting lots of crashes, and that exercise seemed to fix the problem.
I will post the results of the uninstall/reinstall and other experiments shortly.
Bill Buchanan
Buchanan Film Co. -
I am aware that BMD does not recommend nor “supports” Matrox cards, but I’ve been running a 128mb Parhelia with no problems whatsoever since I installed a BMD Extreme many, many months ago.
Just for the hell of it, you might want to try the Parhelia.
Bill Buchanan
Buchanan Film Co. -
Thanks, Noah. After I posted the question, I looked at the charger, and it does indicate the voltages and cycles you noted.
Bill Buchanan
-
You might try uninstalling the BMD driver/software, then re-booting, then re-installing the BMD driver/software and so on? Once upon a time, that seemed to work for me. Apparently, the BMD driver can get screwed up somehow and cause the “…serious error…” thing. Wouldn’t hurt to give it a shot.
How large is your project? If you have a very large library and lengthy timeline, yours is probably a memory-related problem, BUT not necessarily because you have insufficient RAM installed in your box! PPro1.5, because of its well known limitations handling the memory required of large projects, either goes white (the interface) for several minutes or punks out with the “I am really, really sorry, but a serious error has occured…” message.
Dealing with only long-form projects with huge libraries, I’ve been on the phone with Adobe tech numerous times squawking about the very problems you’re encountering. Some techs have blamed it on PPro being limited to about 2GB of memory allocation (or whatever it’s called), before it goes weird, and/or Win XP being limited to 2GB of memory. I applied the “switch” thing so that XP could use up to 3 or 4GB or RAM, but that didn’t cure the problem. Surely, with all the long-form people screaming at them for so long, V2 will not have those problems.
Additionally, I believe we should pray to all the gods that PPro V2 is a 64-bit app. As I understand it, that will make long-form use of PPro not only possible but enjoyable.
Bill Buchanan
Buchanan Film Co. -
PPro, according to one of their techs I talked with recently regarding the issue you are dealing with (and I am dealing with), can only “address” so many “records”, like large numbers of clips in bins, sequences made up of many shots, thumbnails, etc. Doesn’t matter how much physical RAM you have over 2gigs. I have 3 and was considering bringing it up to 4, but the PPro tech guy said it won’t make any difference.
Apparently this horrendous shortcoming has something to do with it being a 32-bit app. Whenever PPro becomes 64-bit (along with all the hardware, drivers, OS, etc.), then those of us working in long form will longer have to put up with these issues.
So, if you’re approaching PPro’s infamous 1.8 or 1.9 gigs of pagefile or ram use or whatever the hell’s going on, the grit-your-teeth slowdowns, crashing, white interfaces, etc. begins. Meanwhile, I believe the workarounds that Adrian suggests are unfortunately the best you can do.
Surely, PPro v2 will be a 64-bit app if Adobe wants to continue marketing it as a truly professional-level editing solution.
Bill Buchanan
Buchanan Film Co. -
Don’t even need to restart it. Just minimize PPro into the tray, bring it back up and they’re gone. My questions are: Why are they there in the first place, and where have they gone when the interface returns from the tray?
Bill Buchanan
Buchanan Film Co. -
Marcelo:
I never could get SteadyMove to work very well. There was weird jittering, and the overall image degradation was quite noticeable. I never noticed it affected color, but then I was concentrating on other things. I tried it with both DV files and with uncompressed 8 and 10 bit SDI-sourced files, trying all sorts of field settings. No luck. I finally gave up. The folks at SteadyMove were very happy to refund my money. Perhaps they will soon perfect the app.
Bill Buchanan
Buchanan Film Co. -
Craig:
You are precisely right. I also think Tim’s explanation is clearly accurate on all accounts, unfortunately. In my original post I wondered if by chance someone had figured out a better way to fill up a 16:9 screen with unsqueezed 4:3 material than by current methods.
Admittedly, I knew all along what’s possible and what is not regarding this issue and why. It’s just that stuck with that damned square frame in a rectangular world, I feel like a monkey with a coconut.
Bill Buchanan
Buchanan Film Co.