Main > Software Forum

MAME Movie Maker released

<< < (109/153) > >>

Kook:
This is a great tool. Nice job Bud. I do have one feature request... when using the automatic loop detection, it would be great if I could specify that I want my saved movies to start in the middle of the loop. Know what I mean? So if I have this option turned on, and let's say the detected loop consists of 300 frames, the AVI will have 300 frames, but the starting frame would be 151 and the ending frame would be 150. Thus when I use the movies as previews in my frontend, and I am scrolling up and down through my list of games, I will see mostly gameplay action in the movie previews instead of intro screens.

Kook

Silver:
Thats an interesting idea..... Might look a bit strange starting a random point.

I imagine it would be a lot easier to impliment simply starting the movie from a set point - a fraction of the way into the loop or something. ie miss out the first bit altogther... Not quite as nice, but if you are only after a quick glimpse (and some of the movies are very long) it may serve your purpose....

Having it loop round perfectly would probably require a load of file renaming or building of a script/list.....

Buddabing:
I've uploaded a test version which may address the "some videos are too long" issue.

This zip is 0.94u1, binary only.

I implemented -movieloops 4 for Kook. Basically, it detects the loop as normal, then takes half the length of the loop and keeps capturing frames until that many frames are captured.

So, the movie will contain the second half of the first loop and the first half of the second loop.

Another way to do it would be to shuffle the filenames around. For example, if the loop ran from frame 100 to frame 199, the filenames of the frames would be zoo00100 to zoo00199 (for zookeeper). Then the program would have to rename the files so that zoo00100 would be renamed zoo00150, zoo00101 would become zoo00151, and so forth, and zoo00150 would become zoo00100, zoo00199 would become zoo00149, etc. I chose not to implement it this way for simplicity, but it's the more accurate approach.

<OfficeSpace>Yeeeeah, if you guys would do some tests and see if it runs better, that would be great.</OfficeSpace>

If it does run better for you, I'll go back and change 0.92 and the official source.

2600:
Speaking of scripts, if anyone is interested I was messing around and have a script that adjusts the start and/or end times.  For example, I run the script in my batch file to remove the neogeo bios screens before virtualdub processes the files.

Let me know if anyone's interested and I'll put it in another thread.

2600:
Buddabing,
Did a quick test with the test release with the usual 3countb.  The video isn't too long, but something doesn't appear right.

If you take the output,(this changes between runs so don't worry if yours is different):
10-frame match detected between frame 316 and 10194
movie will run between frames 307 and 10185

A: The 10-frame match value is different than the actual run. You'd expect that for the second value under this circumstance, but the begining doesnt' make sense.

B: If you compare the png's the movies is clearly not being made between the two points it says the movie will run between. Looks like the "movie will run between" message is 10 frames too many at the begining and end.  And a quick look at my .vdb file, the addrange is 10175.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version