Note: for testing, it's easiest to use the video-export-rebased branch.

The video export plugin stil doesn't compile :(

The export dialog looks really overloaded :(

Why should the user think about the PNG options when he exports into MKV? The only interesting thing that might be interesting for him is 1) whether to save transparency or to which color to replace it; 2) whether to convert into sRGB. Why should he know about PNG at all? Probably, some tabbed GUI could solve the issue?

@scottpetrovic, could you make any suggestions about that GUI? How can we make it less frightening?

And here is a small bug in the writing of "FF&mpeg"

I will check that, but it's not a regression compared to master, because in master, the video export should be disabled because it breaks saving an unanimated gif image.

Hm, I don't think I'll managed to do coding this weekend, so I see three options:

• merge & fix the bugs during stabiliasation phase
• merge & disable the plugin
• wait four weeks

I would prefer the first option, of course.

My proposal for the layout is:

1. Stick every group into a tab instead, so it doesn't take up the whole screen.
2. Add big, fat, configuration load/save dialog at the top.
3. Add a 'convert whole animation to animated gif' preset.
4. Merge and let others who understand video come up with other presets. Make a test build if possible and a call for proposals.
5. Add those other proposals into master.

I have checked the latest version of the branch, and now it has only two minor issues:

1. If you change video type in the drop down, the file extension is not updated until you click on the "..." button.
   1. Select container type to MP4, make sure that the filename is something like "filename.mp4"
   2. Select container type to GIF
   3. See that the file extension is not updated

2. On Linux the plugin should automatically find the ffmpeg binary installed in the system. In my implementation QProcess could easily do it.

Except these two bugs, the branch is fine to be merged.

Results from testing on OSX with ffmpeg static build:

Works for the most part, except for a few occasional memory leaks. After you click OK in the dialog box, it just won't do anything and then everything gets disabled like in the autosave bug. Trace here:

.mp4 files are created with yuv444 pixel format by default. They don't work on OSX though, so you have to tell ffmpeg to use yuv420p so that they'll display properly in OSX. Not entirely sure if we should make an entire option for this or just use yuv420p anyways.

.mkv files don't seem to run with VLC, but will work with mpv.