Re^13: pack/unpack binary editing

... the rest are off by a few bits.

The only way that can be true, is if

the sync mark itself is not meant to be on a byte boundary.

Ie. If it is meant be a few bits into each frame?

This is possible and easily dealt with.

Or the frames are themselves are "a few bits" longer than 960 bytes, which doesn't makes much sense.

Could you unpack the first 3 or 4 frames of the (raw) file to binascii and post them on your scratchpad?

Examine what is said, not who speaks.

Silence betokens consent.

Love the truth but pardon error.

Comment on Re^13: pack/unpack binary editing

Replies are listed 'Best First'.
Re^14: pack/unpack binary editing by tperdue (Sexton) on Feb 10, 2005 at 18:44 UTC
Sorry, the company would frown upon that. I think my problem is that I'm reading in the equivalent of 2 frames but have to discard so many bits to get to the sync. afterwhich I no longer have a frame left that's on a byte boundary. This is why I am currently writting the ascii-ized binary out to a file then reopening and going though the file to pack it back. I forgot I had changed that part of the code.	[reply]
Re^15: pack/unpack binary editing by BrowserUk (Patriarch) on Feb 10, 2005 at 19:00 UTC
If you are only discarding from the first (double) record, then if the original file is sync'd, the resultant file will be: Read \|------------\|------------\|------------\|------------\|---\| --------------------------------------------------------- ....\|s 7680 bits \|s 7680 bits \|s 7680 bits \|s 7680 bits \| --------------------------------------------------------- write <<<<\|s-------\|----s-------\|----s-------\|----s-------\|---\| \|s-------\|----s-------\|----s-------\|----s-------\|---\| ----------------------------------------------------- \|s 7680 bits \|s 7680 bits \|s 7680 bits \|s 7680 bits \| ----------------------------------------------------- [download] Anyway, good luck. Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error.	[reply] [d/l]
Re^16: pack/unpack binary editing by tperdue (Sexton) on Feb 11, 2005 at 12:27 UTC
Thanks for your help. I think I may open the first frame and prepend 0's until the sync is on a byte boundary and then work with everything as hex. Thanks again.	[reply]