Final Cut has it's pros but, at least to me, it's more for video editing (by which I mean not sourcing or finishing to film) and smaller projects (promos, commercials, shorts). I still have an old Lightwave controller sitting around that I've thought about hacking to work with the Avid.Ĭurrently we work on Avid Media Composer, since it remains the only true pro-level editing software. My dad (a film editor, now director) loves the Lightworks systems due to their natural and intuitive control systems. The first editing system I ever experienced when I was young was a Lightworks/Heavyworks system. If you find that this is the case, something is massively wrong, and unless the user is a complete and total idiot, it's probably the UI. To go back to your bicycle example, this is like not being able to figure out how to raise the kickstand in the first thirty minutes. You might not figure out every esoteric feature in thirty minutes, but you should be able to at least get most of the basics. That's not saying that you should be able to be a power user in thirty minutes. You really should not need to read a manual for such basic usage unless the UI is unintuitive, which makes it, by definition, bad software. Any software in which such functionality is difficult or undiscoverable is badly written software, period.
In a good user interface, the actions a user must take to perform any simple and common task should be both discoverable and simple. If I get into your car and can't figure out how to turn it on, pull out of the parking place and drive somewhere within thirty minutes, I conclude that the car is no good."īasic cut-and-splice video editing is a very simple process. It's probably more like, "I've been driving a car for twenty years. I assume none of those things is any good. Incidentally, I can't read, write, swim, drive or ride a bicycle. I have the same attitude with all products: if I can't figure it out in 30 minutes, without consulting a manual (see below), I just give up.
0 kommentar(er)
