Audacity Forum

You're a saint, Steve. I'd buy you a beer if I could. Thanks!

Right. That was a stupid question. So is this more correct? So, when we import NTOSKRNL.exe as a sound file into Audacity, we are interpreting the binary code that it contains as if we were interpreting any other audio file. For example, say we cull these two arbitrary bytes/16 bits from the file: 0...

Wouldn't that mean the each channel was playing something different?

Steve, Would you mind verifying my understanding (based on 16 bit PCM, 44.1k, little endian): So, when we import NTOSKRNL.exe as a sound file into Audacity, we are interpreting the binary code that it contains as if we were interpreting any other audio file. For example, say we cull these two arbitr...

So, just to clarify... Any and every file is just hex/binary. It's the header that interprets how it's read. So when imported as raw data, the header is ignored and the binary in this case is read as if it were a .wav file (or whatever is selected). Thus, what I'm really trying to undertand is just ...

Awesome. Thanks, Steve. I think I need to read a bit more into sample rate. I may have some more questions down the line

Thanks again. Now, off to the reading

Awesome. Thanks so much.

So, each byte is interpreted, i.e., amplitude "decided," in isolation from each other? What about frequency? Where is the connection there?

Hi! New to the board. I've been using audacity for a while now but I've finally gotten around to joining the forums. So, I'm sure a good amount of you have tried importing an .exe or .jpg as raw data. It's a lot of fun if you haven't :-) What I want to know is why this happens. Where does this glitc...