I'm a new user, and after a few days my impression is that Avidemux is a powerful piece of software - it can do things no other editor (at least that I've found) can do. I speculate that some fairly trivial additions might make it useful to a (very much) larger group of people.
I distinguish two broad use cases:
1) One-off edits, including cuts: If you want something done one time, you can set up the filters/codecs etc. and get it done pretty effectively. For this kind of work the U.I. seems quite effective once you understand it conceptually.
2) Bulk conversions: This includes larger scale or repetitive operations you want to do on multiple files; generally conversions of some kind, not cuts.
To do even the simplest operation more than once without explicitly re-setting all of the settings requires the ability to program in python, and a willingness to learn the subset of it and new classes required. This is a *very* tall bar, and I would guess excludes a high percentage of potential users. I am a python programmer, but I'm living with the frustration of setting the filters over and over because it's still faster than digging in and learning the scripting interface.
Here are two very simple things that could fill the gap between casual users and power users:
1) Make Avidemux retain all of the settings/filters etc. between jobs, so that if you want to do something more than once, you don't have to re-enter them. This would be a big help even if (2) doesn't make the cut.
2) Allow selecting/specifying multiple input files, and implicitly queue them for identical processing. This would require some way to specify a template for output filenames, but if that's too complicated just using the input filename and appending an index if needed to avoid overwriting other files would be good enough (Windows can do this automatically, I believe).
Thanks again to the devs and all who support Avidemux.