MM? Marble Madness?

Anyway, an interesting thing perhaps is that -mngwrite (though not producing any output) has major impact on the max. unthrottled emulation speed, whereas -aviwrite (also not producing any output) has not.

I don´t think so.

YES

Maybe it´s on Aaron to fix it.

Done

+ QCHDman update

I just found out that -mngwrite & -aviwrite actually DID produce output, just not where it was told to do it: for example, I used "-mngwrite /home/rene/test.mng", but it produced the output in "$PWD/snap/home/rene/test.mng" ($PWD = current working directory), which IMHO is wrong, but may be intentional!

Your posting is not clear for me.
Beside the folder/direction problem, the outout file (.avi as example) itself is ok?

-mngwrite and -aviwrite work out of the snap directory, yes. That's intended behavior as far as I'm aware.

The movie files itself are ok, so I was looking in the wrong folder before.

Without defined output path, the snap folder will be used as default.

With defined output path, nothing will be saved (c:\temp\) or I can´t find (neither in the snap folder nor in the working directory).


The current solution on QMC2 is, to put in the file name for the movie without using the OpenFileDialog.
The movie file will be saved in the snap folder by default.
Don´t forget to remove the entry if you no more need it, otherwise the recording will not stop (if you use the same driver), even you restart QMC2 or not (setting will be saved).

Correct me if I`m wrong.

Yeah, that's the way it's working here as well, but I find it pretty confusing that when an absolute path is given MAME/MESS either produces nothing (Windows OSD) or a file with the specified path below the $PWD/snap folder gets created (SDL OSD), which is weird... I could understand producing the movie file below the $PWD/snap folder when no path is explicitly given, though. Well, anyway, I can't change this from QMC2, but knowing how it works makes it possible to circumvent this confusion once I build a "create video" dialog .