Question about ZMV format

creaothceann · Post by **creaothceann** » Thu Mar 30, 2006 8:54 pm

Nach wrote:I had no idea what the old ZMV format was till I started making the new one

I wish you hadn't used reverse bit order for the new format.

Post by **Nach** » Fri Mar 31, 2006 12:21 am

creaothceann wrote:
Nach wrote:I had no idea what the old ZMV format was till I started making the new one
I wish you hadn't used reverse bit order for the new format.

Huh?

Aerdan · Post by **Aerdan** » Fri Mar 31, 2006 12:38 am

I think he means little-endian byte order.

As opposed to big-endian.

creaothceann · Post by **creaothceann** » Fri Mar 31, 2006 11:20 am

Yeah... but it doesn't matter that much now.

Btw. the first event in the event stream is a key input - am I right in thinking that this is the controller status from the moment the movie recording was started? This would also mean that the RLE destination would point to one frame further...

Post by **grinvader** » Fri Mar 31, 2006 12:26 pm

Nach wrote:
creaothceann wrote:I wish you hadn't used reverse bit order for the new format. :|
Huh?

I told you when we were making it that all your stuff was big endian, remember ?

Post by **Nach** » Fri Mar 31, 2006 12:59 pm

grinvader wrote:
Nach wrote:
creaothceann wrote:I wish you hadn't used reverse bit order for the new format.
Huh?
I told you when we were making it that all your stuff was big endian, remember ?

I looked at numconv.h looks like little endian to me.

creaothceann wrote: Btw. the first event in the event stream is a key input - am I right in thinking that this is the controller status from the moment the movie recording was started? This would also mean that the RLE destination would point to one frame further...

The first input is how it differs from the initial input. So odds are the first segment is RLE.

creaothceann · Post by **creaothceann** » Fri Mar 31, 2006 1:27 pm

Nach wrote:
grinvader wrote:
Nach wrote:
creaothceann wrote:I wish you hadn't used reverse bit order for the new format.
Huh?
I told you when we were making it that all your stuff was big endian, remember ?
I looked at numconv.h looks like little endian to me.

Take a look at the notes I made for myself (link) - the flags are starting with the last bit.

Nach wrote:
creaothceann wrote:Btw. the first event in the event stream is a key input - am I right in thinking that this is the controller status from the moment the movie recording was started? This would also mean that the RLE destination would point to one frame further...
The first input is how it differs from the initial input. So odds are the first segment is RLE.

In the short movie I recorded, the first event is Input. (pic)

The current code (link) has shows a blank line.

Post by **grinvader** » Fri Mar 31, 2006 1:31 pm

Nach wrote:I looked at numconv.h looks like little endian to me.

Not that, the bit stuff.

creaothceann · Post by **creaothceann** » Tue Jun 13, 2006 8:51 pm

*bump*

Still not decided how to display the file content in a way that is useful for speedrunners.

Anyway, here's a new build.

Post by **grinvader** » Wed Jun 14, 2006 11:13 am

My current parser has 3 modes: input for a set frame #, input changelog and input full log.
You don't really need anything else.