05-27-2008 04:01 PM - edited 05-27-2008 04:07 PM
DonRoth wrote:
I had the same problem with the bringing in the right number of data points using your I32 methodology.
05-27-2008 04:49 PM - edited 05-27-2008 04:50 PM
05-28-2008 06:49 AM - edited 05-28-2008 06:56 AM
05-28-2008 07:05 AM - edited 05-28-2008 07:05 AM
05-28-2008 10:40 AM
Of course it starts at 544. Setting it to 543 is just a quick&dirty way to induce a frameshift so we can see from what point on the data looks "normal" if we assume there is a missing bit somewhere. If we now insert a byte right at that point, all the data will look normal when read starting at 544.
DonRoth wrote:
When I use Hex Workshop, it appears to me that the data starts at 544.
After you atttach the image, you can right-click the link and do a "copy shortcut". Now edit the post (within 10 minutes of posting!) and insert them image by clicking on the "Insert an Image" button and pasting the link to the attached image.
DonRoth wrote:
Let me attach a screen shot (you guys have to tell me again how to insert picture in message if the picture is not on another server - I think there is a trick, right?)....Don
05-28-2008 11:38 AM - edited 05-28-2008 11:41 AM
05-28-2008 11:57 AM
DonRoth wrote:
On your code regarding reading the data stream (don't worry about the header), can you explain this small portion to me in greater detail soI understand why you did what you did?
05-28-2008 12:28 PM
05-28-2008 12:58 PM - edited 05-28-2008 12:59 PM
DonRoth wrote:
1) what was the missing piece of information that would allow the conversion to the floatY? You have uncovered it here with the subtraction of 32. I still don't know why you did that. I understand the 2^exponent portion. I don't understand the 2^32 factor. Why do we do this? Is there something in your experience of file decoding that led you to figure this out?
05-28-2008 01:23 PM