-
Vista 64 and premiere
-
And crashes apparently. You might want to consider that some of your problems are Matrox based.
Steven
https://www.stevengotz.com -
[Steven L. Gotz] “You might want to consider that some of your problems are Matrox based”
Most assuredly some are but in the sense that Axio has intensive resource usage, as well. Mostly though, they’re Premiere based flakiness that necessitates a restart. Matrox gives Axio a little memory based utility that allows the monitoring of memory use by PPro. It’s a steady climb as you work.
David
AllinOneFilms.com -
-
Hi David,
OMG, you’re a marketing genius who can definitely get the buzz going with your forum posts! Your post really made my day and again reiterated why it’s soooo nice to be a retired software development and marketing manager. OTOH, my praise to Adobe for holding off on the 64 bit implementation. Can you imagine the wasted rework cost having rewritten their code 5 years ago when Microsoft was supposed to have released the XP replacement? Unfortunately, a 32 to 64 bit OS rewrite isn’t simply recoding header directives and variables in the code – one has to wait for Microsoft to release (and document) the APIs to the OS, to say nothing about re-writing applications to conform and take advantage of new features associated with the OS. Then there are changes in OS utilities, debugs/traps, diagnotics, error messages, dependencies on software development tools yet to be developed,… you get the idea.
Actually, an Adobe executive would have the heads of software or marketing managers who attempted recoding an application that wouldn’t have a payback for over 5 years (to say nothing about trying to hit a moving target of OS API specs) when they could be adding current features/function/bug fixes in the short term to keep ahead of the competition. And even today, I’m sure Adobe’s marketing and product management is doing a careful cost/benefit analysis vis-a-vis the competition in prioritizing the release of a 64 bit Vista release of Premiere Pro. We’ve recently seen a resegmented spin-off of Audition to SoundBooth and Adobe has recently acquired Serious Magic (including the awesome DV Rack) so perhaps there’s still more important fish to fry then a 64 bit Vista port – at least for some of us!
Perhaps I’m among the dumb fools, but having managed and made the “software sausage,” I’d be the last to judge Adobe harshly.
Warm Regards, Michael
Happy Trails to you, until we meet again
-
[MoonLitNite] “Actually, an Adobe executive would have the heads of software or marketing managers who attempted recoding an application that wouldn’t have a payback for over 5 years (to say nothing about trying to hit a moving target of OS API specs) when they could be adding current features/function/bug fixes in the short term to keep ahead of the competition. And even today, I’m sure Adobe’s marketing and product management is doing a careful cost/benefit analysis vis-a-vis the competition in prioritizing the release of a 64 bit Vista release of Premiere Pro. We’ve recently seen a resegmented spin-off of Audition to SoundBooth and Adobe has recently acquired Serious Magic (including the awesome DV Rack) so perhaps there’s still more important fish to fry then a 64 bit Vista port – at least for some of us!
Perhaps I’m among the dumb fools, but having managed and made the “software sausage,” I’d be the last to judge Adobe harshly.”
Hi Michael,
While you make some informed points about software development there remains the issue of whether Adobe should be judged harshly for the development path of Premiere Pro.
The present state of affairs, from the perspective of someone doing effects intensive, large projects, for broadcast, is that Adobe have engineered a product that systematically crashes under WinXP32 for lack of resources – a product that is almost impossible to use for such projects without substantial, inefficient, workarounds.
Perhaps, as you point out, it would have been unfeasable for them to have had a development path that made it easy to provide a 64 bit solution, but given that they almost certainly knew the strain that the product would create on XP32 bit resources, was it then irresponsible of them to release it into the market and claim that it was for professional users, without any caveats whatsoever? Or is my assumption that they were aware of it’s resource useage weaknesses incorrect? Either way I believe they can be held accountable as the resources problems surfaced with 1.0 and two major releases later, they have not been properly addressed. That fact alone inclines me to believe that they hope to sidestep the fix with a 64 bit version. Either that or perhaps they hope to migrate us to the Mac version, which, I’m told, will not suffer the same resources problem as under XP32. It seems to me that no matter which way you cut it they have not yet shown any real concern for the numbers of users like myself who suffer from their engineering decisions.
Not judged harshly? Tell someone that after a day of having to restart PPro 15-20 times in front of a client. As for me? I learned, painfully, how to reduce my restarts to under 5 a day, and my lost time to under a half hour. But I still regularly join the chant of users turning the air blue in Adobe’s direction on a daily basis. If the energy behind all those invectives could be harnassed you could probably run a small city.
David
AllinOneFilms.com -
Rehi David,
I’m sorry to hear you’ve been suffering numerous crashes on your project – we all know how awful it feels to lose work and have seen this on any number of programs. In fact, have you noticed how programs that emply an auto-save “feature” are typically the ones more likely to crash? All great software development comapanies with marketing prowess can turn a bug into a feature!
On the serious side, I’m unaware of the factual basis that PP throughput is limited by a 32 bit OS architecture and that a 64 bit sytem would resolve your constant crashing problems. Since most of the rest of us seem to have better luck, perhaps the problem isn’t entirely a 32-vs-64 issue. However, for folks like yourself that are unable to resolve the performance requirements associated with high-end application, I’m sure Adobe loses some mind and market share. And since you feel constrained to wait for a 64 version of PP, let’s hope it both arrives soon and the new architecture magically fixes your system crashes.
Warm Regards, Michael
Happy Trails to you, until we meet again
-
[MoonLitNite] ” I’m unaware of the factual basis that PP throughput is limited by a 32 bit OS architecture”
Adobe is well aware of it. The main problem seems to be how the app uses memory. Matrox provides a utility for monitoring PPro’s memory use. It gobbles ram with time and doesn’t give it all back. The limit of 3GB per app in XP becomes a problem fairly quickly with complicated projects. A 64 bit OS would only solve the existing problem by throwing more than 3GB of ram at it.
David
AllinOneFilms.com -
David
I’m having the same problems as you with the 15 to 20 crashes a day on complex stuff, it is so embarrasing to have clients ask if you should “upgrade” when you are up to date. I don’t care if Adobe releases a 64 bit version, I just want the 32 bit version more stable.
Shane
Reply to this Discussion! Login or Sign Up