4 ms·

At the time of me writing this, you missed a space between the ");" and the url for the dosbox codec. For people on mobile/lazy: https://wiki.multimedia.cx/ind

At the time of me writing this, you missed a space between the ");" and the url for the dosbox codec. For people on mobile/lazy: https://wiki.multimedia.cx/index.php/DosBox_Capture_Codec https://wiki.multimedia.cx/index.php/DosBox_Capture_Codec ----- For those interested in an even deeper dive: Decoder: https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/zmbv.c https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/zmbv... Encoder: https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/zmbvenc.c https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/zmbv... This implementation was written almost immediately after dosbox added the codec.

mkesper 7y ago
How hard would it be to let dosbox emit a newer container format? I remember AVI being quite bad re overhead.
- tracker1 7y ago
  Is it the write overhead and/or read overhead... I don't know in this case, but it can really vary. Also, depending on the hardware and what's running inside dosbox, most current hardware for at least half a decade should be able to keep up fine. More so on SSD.
- akx 7y ago
  I think AVI is being used because it's apparently _very_ easy to write a valid AVI file without extra libraries: https://github.com/svn2github/dosbox/blob/acd380bcde72db74f3b476253899016f686bc0ef/src/hardware/hardware.cpp#L132 https://github.com/svn2github/dosbox/blob/acd380bcde72db74f3...
  - naikrovek 7y ago
    Old image and video formats are great if you want something quick and dirty.
akx 7y ago
Ah, sorry about that. Seems I also missed the window for editing my post. Thanks for the correct link!