6 ms·
As somebody who worked professionally with Adobe Premiere I think the criticism of its UI misses the point. Premiere was never meant for hobbyists (reflected by
by atoav 7y ago
As somebody who worked professionally with Adobe Premiere I think the criticism of its UI misses the point. Premiere was never meant for hobbyists (reflected by it's actual name: Premiere _Pro_).
The only valid point made here is that it is hard to learn for someone who never used any editing software at all. But it certainly isn't slow or "unfocused". That source monitor is on screen for a reason. Keyboard shortcuts will always be faster than moving your mouse around. And by the way: Premiere has a modular interface, so if you hate the clutter or don't need it, you can get rid of it.
If you are the person who just wants to edit some stuff together once a year Premiere _Pro_ is not for you. Turns out software interfaces that are meant to be used by people 8 hours a day for weeks at a time follow different design paradigms than stuff made for amateurs. I'd go completely insane if I had to edit a movie on anything simpler tho.
I like their TLI ideas, but I am honestly a bit alergic against designers who lack the phantasy of realizing that sometimes a UIs complexity is a reflection of the complexity of the problem it helps to solve in conjunction with the level of control you want to give to the user.
Steep learning curves should be avoided — sure — but sometimes they are necessary to shave of that extra second. Something that multiplies if you do it hundred times an hour.
Premiere is like vim: not for everybody, but if you wield it in the right way, there is not much that can beat it.
- k__ 7y agoI learned Photoshop, Flash, Final Cut Pro, Ableton Live and multiple IDEs. I found they were, like CLIs, all very similar.
- battery_cowboy 7y agoThat's because they were based on the original hardware for linear video editing, which had a metric shitload of buttons and knobs you'd have to know. I could see using a minimal CLI for something like this, but it wouldn't be useful for those guys who learned on linear equipment then had to switch to the nonlinear equipment, which already had a steep learning curve since they were used to a more linear process. I don't know why the author of the article picked Premiere as an example of a "bad UI", because it is pretty close to perfect for that particular time in video editing. Source: I am experienced in several nonlinear and linear video editing technologies from the 90's and early 2000's, since my father was in the videography business.
- ScottFree 7y agoIt would be useful for somebody who has no experience in video editing, but would like to cut together some footage taken on their phone. And yet, even the video editing software aimed at beginners and novices are crazy complicated.
- battery_cowboy 7y agoOh yea, today we can do so much more with less UI, but I'm not into video editing so I'm not sure of what's available. I'm sure there are simpler apps for regular people now.
- ScottFree 7y agoPlease let me know if you happen to stumble upon one. Every once in a while, I get the desire to take a small clip of a larger video to use as a gifv. I've yet to find a single video editing program that makes this very simple thing easy for somebody who has no idea what he's doing.
- mtrower 7y agoIn the past, QuickTime (Pro?) was excellent for this sort of thing; you could just mark the section you wanted right in the player window and export a new clip. I don't know what the present situation is with QuickTime, and obviously that's an Apple solution. There are basically two classes of editors: * "pro" editors, like Premier, and (old?) Final Cut Pro * "home" editors, like iMovie, Windows Movie Maker, OpenShot etc. You want something from the latter category. The general idea is: 1) Add your source video file to a new project 2) Drag that video onto your timeline 3) Edit the timeline to crop your video (various methods depending on user preference) 4) Export your new clip You haven't mentioned your platform, so lets give a simple example using the free, cross-platform OpenShot: 1) Add your source video file to a new project 2) Drag that video onto your timeline 3) Grab the edges of your video clip in the timeline, and drag them to crop your video 4) Export your new clip Short YouTube video (not mine) demonstrating this visually (you don't actually need to select the razor tool): https://www.youtube.com/watch?v=P8zmqfXXS60 https://www.youtube.com/watch?v=P8zmqfXXS60 --- Is this an easy enough method? I think to get any easier than that, you may be looking at a purpose-built tool to do only the simple thing you want, rather than a general purpose editing tool. --- edit: I didn't see your file format requirement. I honestly don't know anything about .gifv; it appears to not actually be a file format at all, but some tomfoolery that Imgur is engaging in? You'll have to export to an actual video format (say webm or mp4) and figure it out from there.
- tangert 7y agoyour point about UI complexity reflecting the complexity of the problem + level of control is totally true in regard to most tools - but one of the key points at replit is that we are trying to create a programming environment that appeals to both beginners and experts. we don't want to block out hobbyists. that's really the main point of comparison to Premiere- if someone is interested in learning about film production, you shouldn't have to go to iMovie and then "graduate" to Premiere (or Canva -> Photoshop, SketchUp -> Autocad). tools should grow with you (ideally)! complexity is always relative but I think the end point here is that there's always room for simplification and shallower learning curves, even for advanced/pro users.
- atoav 7y agoI agree that digital tools don't have to be one thing, as you said they can grow with you (or you change them, like going from textedit to vim or from notepad to sublime text). While there are solutions that both experts and beginners can benifit from (like Blenders 2.8 UI overhaul), everybody who has done every manual job ever might have learned that the optimized professional tool you used has a learning curve for a reason: when you know how to use it, it is literally faster and gets less in your way than the friendly intuitive and self explainatory variant of the tool. The kind of dynamic scaling you mentioned is always desireable, but not always possible without introducing considerable complexity into a software — especially in complex domains like editing, audio or 3D the hard thing usually is to develop a language of adjectives and verbs the user can throw onto the objects they work with. And learning this can feel like learning a new language for a reason. And like with languages a simple combination of grunts and gestures might be enough for certain communicative goals, but sometimes it pays off to learn the actual developed language to really express what you want. The most powerful software that gets in your way the least I ever learned had incredibly steep learning curves, but once you've got it, it felt like speeking a language you mastered. We are literally commanding machines here — and problems of high complexity paired with a high level of control usually demand a very precise communication. So while I could e.g. imagine an editing suite which interprets your grunt and edits a bunch of videos for you using AI, you are still losing a level of control there: because the computer has to assume what you are unable to tell it. There is literally no way around it. Ever wondered why the language used in the military, in an operation room or on a film set is so specialized and hard to understand for amateurs? It is because they need that level of control to communicate in order to get the desired result.
- mrbrowning 7y ago> I like their TLI ideas, but I am honestly a bit alergic against designers who lack the phantasy of realizing that sometimes a UIs complexity is a reflection of the complexity of the problem it helps to solve in conjunction with the level of control you want to give to the user. I think what's key here, and why I like the direction of the work in the linked post, is that none of the affordances of the UI they're augmenting -- the command line -- are being taken away,* merely made more visible based on context. I think that gets at a hole in the notion that UI complexity mirrors domain complexity -- in the case of Premiere, surely the entirety of what's on the screen doesn't mirror the complexity of the workflow you're executing right now, it's much closer to the sum total of everything you might ever do. Not that a UI based on progressive disclosure would be trivial or maybe even possible to implement effectively for something like a professional video-editing application, but it's worth considering whether something like that is merely a local maximum in the space of all possible UIs. * I guess in the case where you know exactly what you want to do and the added context might distract or slow you down, that's an affordance being removed, but I think it's outside the scope of what we're talking about here -- especially because, given the scope of the command line, you will inevitably have to do something with it that involves an invocation that isn't right at the tip of your fingers.
- atoav 7y agoI agree that they did the right thing for the domain of the TLI, as your comment captured. And existing editing GUIs might very well be a local maxima — however we designers need to be careful in quickly condemning existing solutions that we don't understand by calling them "unfocused", "slow" or "ugly". It is the responsibility of any designer to be more aware than the rest of tradeoffs like these — making it look good is merely a nice to have you can achieve as well. To decide that for a domain as complex as editing demands at least some degree of awareness of the common problems an editor needs to solve, as your software or UI will have to solve them as well. Sometimes this comes with a learning curve, as your user will have to learn how to tell the computer what they want. They will have to learn some language that allows them to express this, if they don't want the computer to take the wheel and just assume what they want. And that very language is what makes it complex and hard to learn, and there is not much way around it. Might there be a different language that lets you express more things with better ease while beeing easier to learn? Sure. But will it still be harder to learn a language which allows you to express a lot, compared to a language which allows you to express only little? Yes - as well. That beeing said: I they made all the right usability choices on their own thing there, my comment was more an aside stemming from my own values as a designer.
- vz8 7y agoXKCD's "Is it worth the time"[1] grid seems appropriate here. Amazing how often I keep coming back to it, and how it really does play out. [1] https://xkcd.com/1205/ https://xkcd.com/1205/
- atoav 7y agoA classic. However I like to note: sometimes it is also worth shaving something off that just annoys you, even if it doesn't take that much longer. Annoyances are a bit harder to quantify, but they also add up over the weeks.
- dspillett 7y agoAnnoyances have an effect beyond the time they take up: by definition they hang about taking a little bit of mental energy away from subsequent tasks.
- rijoja 7y agoyeah and humans short term memory is quite limited also automating away these small things reduces the risk of human error.
- lonelappde 7y agoTrivial annoyances can be fixed by CBT (fixing your brain to not overeact), without needing to spend time fighting the world.
- Cthulhu_ 7y agoIt's why I use intellij instead of e.g. vim at the moment, I can use a lot of the features and they provide a definite advantage over my previous editor, VS Code, which was also pretty densely packed with features (although it has a much cleaner UI). The other question is discoverability. I mean I'm sure vim is incredibly powerful, but none of the features are obvious and you have to trudge through two decades of websites to discover anything. I've been unable to find out (actually I haven't really looked) how to use vim as a software developing tool (with basic features like autocomplete/suggest and error reporting)
- mpfundstein 7y agoI'd arvise you to try vim again. Carve out two days, take your time, dive in and build the ide you want. I tried all modern ides, and while vscode is certainly awesome, i always go back to my vim :-)
- atoav 7y agoDiscoverability certainly is an issue with vim – but it isn't really with Premiere. What I was alluding to with vim was more the combinatoric aspect of powerful tools. Creating software that solves one specific problem with a beautiful UI isn't that hard – creating something that solves a very broad range of problems is infinitly harder, because you need to give the users a language in which they can tell the machine what they want. That "language" can be shortcuts and chainable commands like in vim or it could be graphical, using a timeline, context menues, drop downs, symbols etc. However: the more expressive this language has to be and the more problems you should be able to solve with it in precision, the steeper the learning curve will get. And as with spoken language, there are hard to learn languages that let you express certain aspects very precisely and there are simpler languages that might be easier to learn but make it harder to express certain things (e.g. "You" in English vs "Du"/"Sie" in German vs. all the formal variablity of Japanese).
- buzzkillington 7y ago>I've been unable to find out (actually I haven't really looked) how to use vim as a software developing tool (with basic features like autocomplete/suggest and error reporting) Vi is a text editor with an incredibly powerful language to edit text tied to keyboard keys. Emacs is a lisp interpreter that's optimized for text editing. They are not IDEs.
- blowski 7y agoYour comment reminds me of a conversation here about how some people confuse complexity and disorganisation, particularly when they don't have much expertise in what they're looking at. So they "organise" everything, but in the process remove all the power, and what they end up with is a beautiful white elephant.
- derefr 7y agoI once had a college HCI project where I designed the simplest possible TV UI (menus + on-display affordances + remote affordances.) I think I ended up with five buttons, and one menu. All the "settings" were automatic calibrations done during setup. You could re-trigger them by running the setup wizard again, but that's it. Now, I am probably not a "professional TV user"... but neither are 99% of people who use TVs. Even if most of the complexity of a TV is important to the few people who, say, install one as part of an IMAX-certified home-theatre setup, most people want a TV that "just works" and gets out of their way—even if it's working in a sub-optimal way! They want a remote that can 1. turn the thing on, 2. control volume on their TV and/or soundbar; 3. switch input sources; and 4. proxy through to menu around in the streaming boxes/game consoles/etc. they own; and that's it. You don't even need the setup button on there—you can get up and press that on the TV itself. The funny thing is, by default, TVs both have more functionality, but actually fewer desired features, than what I'm describing. People tend to have to buy a ridiculous 100-button (or digital touch-screen) Harmony remote just in order to get "turn on the TV" and "menu around in your streaming box" on the same remote. Why?
- nerpderp82 7y agoYou are not wrong, but criticism levied at Adobe products (and I haven't used them in 5 years) is often actually unbeknownst to the person making the criticism, about the lack of state control and visibility in the UI. You can mess up your UI state to such a level that the application is unusable. The undo/redo mechanism affects the data (movie, the image, the sound) but it has no effect on the state of the UI. Adobe did implement "reset workspace" or whatever it was called, this was a gift from the gods, but it did not go far enough. Tooling this complex needs to provide controlled methods for controlling state, both in the tooling and that tooling's impact on the data it is operating on.
- chubot 7y agoReminds me of a problem I just had with Eclipse's debugger (which sadly seems to be one of the most capable GUI debuggers on Linux). I set breakpoints and they were ignored. https://stackoverflow.com/questions/4388192/eclipse-doesnt-stop-at-breakpoints https://stackoverflow.com/questions/4388192/eclipse-doesnt-s... One time it was the top answer -- I had "skip all breakpoints" on. How it got on, I have no idea, since I did a fresh install of Eclipse pretty recently. Yesterday it was still ignoring my breakpoints even though that was NOT on. Why? I have no idea. So I still debug with gdb when the 'bt' command suffices. When I want to do more advanced stuff, I'll fire up Eclipse maybe, but I'm honestly loathe to do so.