I'll change the way the inputs are stored to something more efficient so the size limit shouldn't be an issue.

The idea with a dialog sounds good. Long term it would be nice to get another dialog so you could browse for missing files.

Quote:

What happens if you try to replay the capture on another MSX, or if there's slight differences like a different ROM? (Or is that all in the save state?)

I don't consider replay on a different MSX a valid case because I see the replay as an exact copy of when it was recorded. So the way I look at it, there isn't such a thing as replaying it on a slightly different machine. I know openMSX looks at it differently though but then you'll get problems like the replay won't look the same as when it was recorded.

The blueMSX capture contains two things:
1. A save state when the capture was started (this includes the entire machine configuration)
2. The input events that happened after the capture was started.

The save state is also needed because the capture can be started at any time, not only during system startup. So the events alone is not enough information.

Quote:

I'll change the way the inputs are stored to something more efficient so the size limit shouldn't be an issue.

RLE should dramatically decrease raw size. (that is, if the player isn't a robot )

*edit* While you're updating capturing, how about adding a feature that allows you to add 'bookmarks' inside the capture (technically these would just be savestates). erm ;p .. let me clarify it with an example: you're recording Contra, and add a bookmark before every cool bossfight. If you're replaying the capture, instead of waiting, you can quickly jump to any bookmarks to see the bossfights. (that's not exactly a clear clarification is it? ;p )

dvik: openMSX *currently* allows you to play any file, but in the end it will have to check that the sytem is the same indeed, as it will definately mess up

Was I correct about the files?

@manuel: Yes I think you were right. the capture file is just a standard save state + the capture log (and its just a regular zip but with different extension). In fact you can run the .cap file by loading it as a save state. So inside the emu the capture file is equal to a save state. It just contain a little bit more info.

Yeah, I also just read it on the manual page that mars pointed me to Ah well. Nice toys, input logs I loved watching BiFi play MoG at very high speed (Or watch myself play Space Manbow at max speed

Quote:

While you're updating capturing, how about adding a feature that allows you to add 'bookmarks' inside the capture (technically these would just be savestates). erm ;p .. let me clarify it with an example: you're recording Contra, and add a bookmark before every cool bossfight. If you're replaying the capture, instead of waiting, you can quickly jump to any bookmarks to see the bossfights. (that's not exactly a clear clarification is it? ;p )

I think I understand. Its actually a pretty cool feature. With a save state for each bookmark, its even possible to create a nice index with screenshots. Its probably not too hard to implement. I need to add support for save states inside captures. Currently I support captures within save states, so it shouldn't be too hard to support the other (especially considering that save states and captures are the same thing).