So? No problem at all. ;) Then I'd just let the program call itself again (with a special secret command-line option) which does nothing but check for OpenGL support. The return value would be the message, but a crash is a return value too :)
It's not too technical for me, but even I would be stumped at first when encountering that error. My first instinct would be to search for a readme.txt file, but BizHawk doesn't ship with documentation. The project page mentions the config file, so that's good, but there's no documentation of the command-line options. Only when you go to the Google Code project page (which will be gone next year) there's a link at the bottom of the page, and it doesn't mention --gdi either.
I'm not saying that it's an unsolvable problem at all because the solution is available, but it doesn't seem like the user-friendliest and most straight-forward way to go. I'd add a check before loading OpenGL DLLs (or when they return an error); when that check fails I'd just switch to GDI+ automatically. If that's not possible I'd pop up a message box describing the problem and the solution. If that's not an option for some reason I'd put it in the readme (a properly formatted one - lsnes' documentation makes my eyes and head hurt).
How big is the file? Maybe you just downloaded a server error message or something.
You could also try looking into it with a hex editor and see if the first bytes look similar to other ROMs.
IMO (!) an encoder should also have a bit of familiarity with the tools being used, so even if I wouldn't know why an encode failed I'd be able to debug and possibly rewrite the encoding script.
A = AVISource("movie.avi", "movie_02.avi")
B = AVISource("movie.avi", "movie_02.avi")
ConvertToRGB32()
"ConvertToRGB32()" has an empty parameter list, so effectively it becomes "ConvertToRGB32(clip=last)", but last was never set because you assigned the video to A and B instead.
Anty-Lemon wrote:
pastebin
Seconded. It even has an Avisynth syntax highlighting preset.