Thanks for the new feature to allow a dump as input for DMDExt.exe.
The output processor video is supported for library only, not for the exe, so we cannot push a dump in and get a video out.
Video out would allow to reprocess a dump with the --colorize option and then fast forward through the video to verify if everything is colorized or a new color process is better than the previous.
And it would allow to produce a RGB24 colorized video, to produce snippets to feed a DMD Pinball clock.
I tried to do that myself by using your code from the library for the exe, but I failed to retrieve the gamename (which you get from the dump name?). If it is helpful I can do a pull request, but my code works only if the .ini is set with a video file name, not for video folder and using .ini is mandatory, as there is no option to specify a video file name and I did not wanted to make too much changes, producing too much differences.
Thanks for the new feature to allow a dump as input for DMDExt.exe. The output processor video is supported for library only, not for the exe, so we cannot push a dump in and get a video out.
Video out would allow to reprocess a dump with the --colorize option and then fast forward through the video to verify if everything is colorized or a new color process is better than the previous.
And it would allow to produce a RGB24 colorized video, to produce snippets to feed a DMD Pinball clock.
I tried to do that myself by using your code from the library for the exe, but I failed to retrieve the gamename (which you get from the dump name?). If it is helpful I can do a pull request, but my code works only if the .ini is set with a video file name, not for video folder and using .ini is mandatory, as there is no option to specify a video file name and I did not wanted to make too much changes, producing too much differences.