David Cherniack
Forum Replies Created
-
[Tim Kolb] “The issues are “niggling” in the context of the engineering aspect of the software. I can’t see that a lot of them would be difficult to fix…but then I’m not an engineer.”
Weel, that’s not what was implied, nor is it really relevant to the discussion. If they’re not difficult to implement then there would be no reason for them not to have fixed them in 1.51, which was exactly a “cavalier” point update. Instead of plugging any of the functional holes in the software, all they chose to do was add HDV support, and fix a few unstated bugs. None of the MAJOR issues were addressed. That’s cavalier.
AFA as updating the entire suite I fail to see how fixing the stereo audio paradigm has anything to do with After Effects, Encore, or Audition. It could ‘easily’ have been implemented in 1.51, but wasn’t. So either they don’t get the need, or just don’t care enough to implement the solution in a way that’s helpful to their professional users.
[Tim Kolb] “I don’t think that Adobe is cavalier necessarily, but they are coming from a different core group of users, so the existing priorities don’t evaporate to make way for the new ones…they just pile on.”
I’ve always felt that they should have released two different levels of Premiere Pro, because one size does not fit all. A hobbyist has very different needs than a broadcast editor. I’ve put in an order for Axio, Tim, but not because I’m filled with confidence about Adobe’s committment to making this software truly professional. In fact I have my grave doubts based in their performance so far. As I’ve said 2.0 will likely tell the tale. If it doesn’t cut it, I’d hate to be the PPro product manager at the next NAB. The poor guy will be lucky to escape with any skin.
David
AllinOneFilms.com -
[Tim Kolb] “Many of us here work with Adobe on development and rest assured, we note the issues and make sure they get to where they need to be…”
Maybe you should take a sldgehammer along the next time you go talking to them 🙂 Because either you’re not saying the right things or they’re just not listening.
The “niggling little things in the workflow” as you put above it are more like gaping wide holes for most professionals. But above and beyond that there’s the cavalier attitude to point releases during the 18 month development cycle and the insistence on releasing updates to the entire video suite at the same time. People who work in production environments need updates sooner and bug fixes soonest. And they also need real support – (maybe Adobe didn’t realize that NLE’s have to interface with hardware?)
All in all PPro’s a fine product that needs to be taken to the next level if Adobe ever wants to establish a serious presence in the professional marketplace. We’ll see whether they’re committed to do that with version 2. After 18+ months the gaping holes better be all filled and a new attitude evident of listening to professional users. Otherwise watch the exodus to FCP by PC houses when the first Intel Macs come rolling off the assembly lines. It’ll be a stampede.
David
AllinOneFilms.com -
True. I forgot.
David
AllinOneFilms.com -
Baz, a couple of questions.
When you go to on-line doesn’t PPro re-capture all your clips – not just your trimmed versions? I understand that’s what it presently does(!?)
How do you manage the seperate audio track issue raised below in the “Except everything we need” thread – or because it’s animal planet the need to work with two recorded mono tracks in sync just doesn’t arise that much?
David
AllinOneFilms.com -
Announced at the Axio demo in Toronto on Tuesday
David
AllinOneFilms.com -
[Ron Shook] “If this isn’t fixed in version 2, No Way!”
“Shocking” is putting it way too mildly. That the head designer couldn’t see the sense in what Herb was trying to convey is just appalling beyond belief.
My guess is they didn’t really understand the needs of professional users when they designed the thing and either didn’t talk to any, didn’t listen if they did, or just talked to people who really had no idea about professional use. Sorry if any of this last group are hanging here but if so, you really ought to hang your heads in shame.
The paucity of built-in shortcuts requiring wasted time and energy, the miserably inefficient project window, this dumb stereo dictatorship of audio tracks that I wasn’t fully aware of until now, and dozens of other poor design choices I’ve come across that any working editor could have told them not to do that way all point to a management team that has a lot of waking up to do if they really hope to enter serious post facilities.
When I saw the capabilities of Axio, I said wow! But every time I start to seriously consider it or Cineform as solutions for my work I’m confronted by the glaring deficiencies of Premiere and I shy away like a fish from a poorly baited hook. For a year now, I’ve been thinking I’ll give them a shot with version 2. But let’s face it, with stories like what’s come down in this thread we’re not likely to see the core design issues fixed. Maybe after a hue and cry when 2 comes out, but then it could well be another two year wait.
David
AllinOneFilms.com -
[BazinoZ] “I do many doco’s for Animal Planet using Premiere 1.5 with some extremely busy timelines and it never chokes on me. Go ahead”
What do you think about Marisu’s observations – especially about the free disk space crashes?
David
AllinOneFilms.com -
[marisu fronc] “You also need to consider disk space – you need to leave as much free space as you use or risk crashing and burning, so if you have 200GB of media in the job you need at least 200GB free. This could be a serious consideration with the overhead HD requires.”
Hey, Marisu, I know about the scrolling Project manager blues – Gawd you really wonder who input on the design of the project window – but I’m not aware of the double your storage requirement. What’s with this? I also hate the audio conforming thing into a non-standard file format.
David
AllinOneFilms.com -
If batch export and re-designed project management/window are not in version 2.0 Adobe will lose a lot of potential users. I, for one, will be moving to either VelocityHD or, gasp, FCP, and waving a wistful goodbye to Axio and Cineform. It’s hard for me to believe that they won’t have these features in – it’ll have been 18 (or more!) months since 1.5, but, as I keep reminding myself, they’re Adobe and they march to their own drummer – and I’ve heard the musicians’ jokes about drummers and keeping time.
Maybe prayer will work.
I doubt it, though.
David
AllinOneFilms.com -
Hi Aaron,
I’m glad it works for you. OTOH there are many professional editors for whom the feature set and design of PPro is a brick load short of “Pro”.
Because of the product’s emergence into the marketplace as a potential powerhouse many of us would like to see it mature very quickly. If it doesn’t have full featured project management and an overhaul of the pathetically clumsy project window by version 2 very few of those users will start to use it.
The other major re-think for the Adobe mindset is to realize that professional users can’t tolerate bug fixes every 18 months. No beta test program will catch everything. Serious bugs have to be fixed quickly.
But I haven’t a clue whether Adobe realizes all this. I’m afraid they don’t but we’ll see. Version 2 should tell the tale.
David
AllinOneFilms.com