SoulStorm ARG - lsot.mp3 analysis

[Xavier]

We're most likely missing something in the lsot.mp3 file:

http://www.oddworld.com/soulstorm/lsot.mp3

Here's what someone posted on the Wiki about it:

The audio file has hidden morse codes scattered through it in different time marks, as follows:

00:15, left audio channel -> . - (translated: ET)
00:15, right audio channel -> . --. (translated: EG)
01:11, both channels -> . -.. (translated: ED)
01:48, both channels -> - . (translated: TE)

The four codes translated, in order and together, spell: "ETEGEDTE", if we consider the left audio channel comes first, and "EGETEDTE", if we consider the right audio channel comes first.

Did we check if this was correct?

The "ED" led us to http://www.oddworld.com/soulstorm/ed/ but the meaning of the other codes is yet to be found.

Also, thinking of it, maybe we should use the following comment found in the html code:

!-- are you l/os/t

?--

EDIT: Probably not as the comment got removed from the page. It would probably still be there if it was put there to help us crack the mp3 file.

[Manco]

I think it’s interesting how they keep highlighting the O and S in “lost�:

• In the original HTML comment, the message was “are you l/os/tâ€�
• Then it was updated to “still lsot ? .mâ€�
• The filename itself is “lsot.mp3â€�

In each case, our attention is drawn to the O and S.

[SqueeglePoof]

I don't think it's correct.

Here's my theory: The beeps at 00:15 (let's call it A) and 01:48 (C) are the same as the beeps at 01:11 (B). It's just that A and C weren't successfully "transmitted."

My reasoning is that for A and C, you hear white noise around the beeps, as if some interference was experienced (hence the white noise). Also in A, you have strange echoing, and neither channel is consistent with each other; it's hard to tell what it is, and then static comes in. For C, you have white noise before and after the signal and it doesn't sound like a "full" message.

But with B, you have a distinct and clear message in both channels and no white noise, except for the very short segment that takes place just before it.

Additionally, I believe that the strange cut-off sine wave signals at 1:40 further indicate that "ED" was the message being sent. I pitched this section it up a couple octaves and listening to the spacing of the "beeps," I hear "E" and "D" and not "L." The signals at 1:28 seem to be the same as 1:40, only much shorter.

However, I'm not saying there isn't more to the file. I look at it from time to time to see if maybe other parts of the file can offer clues.

[Manco]

I don’t agree that they would repeat the same section of morse code like that, it would serve no purpose as solving one would solve both.

However, 0:15 is cut off at the end by static, and 1:45 is cut off at the beginning by static – what if they are supposed to be played as one longer message?

Also, discussing 0:15 with Moot and how the left and right channel are split for that one piece, we’ve come up with a possible theory – what if the key to solving this part is that the two channels are both parts of the same piece of code, and that to hear it properly we have to “re-align” them so they play together at the same time instead of slightly offset?

[FennecFyre]

Adding in my two cents: Manco might be onto something. Maybe the filename is misspelled for a reason--it could be a hint that the message sections are out of order.

[Moot]

Been analyzing with Manco, and the right channel is definitely not EG. It's really hard to tell (because there's a dang beat mixed in), but there are certainly at least three, or maybe four blips.

ET or E T, it sounded like R or IN at another. R and IN may be long shots though. I believe the last MC at the end is reversed. I'm also concerned about ED. Why was only it mentioned in the picture we got in the .txt file? Was it meant to take us to the ed page, and doesn't correlate to the audio at all? It's hard to tell..

Edit: There has been lsot and ME FIND, there's a good chance you guys are right.

[Manco]

I’m having real trouble figuring out how Audacity works, but it does sound to me like the two channels at 0:15 can be aligned. From what I’ve got it sounds something like .- -., which is AN, but I can’t say for sure.

[Moot]

i̠̞̹̺ c̴͙̙̰̬͙a͍̭n̘͚̜͖̻͔ ̺̮h҉̦̖̜͙e̶͓a̟̜̖̕r̶͓ ̩̹ͅy͜o̹̰̟͔u̢͉̼,̦͕͉͉͎̕ ̞̞j̗̼̮̠̥̥͍us̗t̩̺.̻̗ ͕̞̳̹̭̀ͅi̛t̰̯̙̣͖̟̙'̪̪̞̦̳̩s̕ ̩̬̗͖̻̖̀f̴̙͉͎̯̺a̫iṇ͚̞͢t̵͚̬͇̰͍̼ͅ,̬͕̹̖̩̮͜ͅ ̺͔͎͉̺̱b̸̝̰̬u̻͍̲̕t̪̼̮̣̫ ̮͕͎͍͡i̮̱͙ ͎̲̤̯c̷̺͓a̜̪̺ṉ̻̲̦̲̼̻͘ ̧̳̗̮̘̦͔h͏̪͎̬͔͎͍̗ȩ̤̞͖̬̘͕Ã*̺̭̭̼ŗ͈̳̠̤̳̗ ͏y̲͈̭̘̰͔͞o̢̗̳̘u͔̫͚͉.̩̼̠

If you look closely, in the words JUST and FAINTLY, the letters U and I aren't altered in any way.

Any ideas if this means anything?

[cleanshirtuk]

I shifted the timing of the channels so, from the waveform, the morse code matches up time wise. Interesting to note, this only applys to the first lot of more code, on checking the waveforms it appears the second and third part are already synced correctly. I ran it through a morse code translator and got 'f' however that could be my miosinterpereting it. Anyway, here's a link to the time shifted version:

https://soundcloud.com/cleanshirtuk/...hifted/s-B35GW

[SqueeglePoof]

I'd be happy to be proven wrong.

From what I’ve got it sounds something like .- -., which is AN, but I can’t say for sure.

I hear it, too. I think this is what you mean when you say aligned.

http://imgur.com/EuqSy6K
where 4 and 5 line up with 1 and 2. However, I don't feel that this really does anything. I can still hear .- -. in the right channel (3 4 5 6). Actually, it sounds more like .--. to me, which is P.

The left channel is much more clean than the right. With the right, it's hard to distinguish between . and - since it's not as clear.

[cleanshirtuk]

I think I've found something! Those low frequency parts? They look like morse code too! You can tell because the waves are so small (that might not make sense but see the pictures for more info). For example, the one right at the end is this:

http://imgur.com/EAKeTtR

Which in turn can be interpreted as .-..

before that is this:

http://imgur.com/AqKUGUK

which can be interpreted as ..

I think this should be investigated further, by some one more able to interpret morse code.

[SqueeglePoof]

I ran it through a morse code translator and got 'f'

Actually, I think you might be right. If we assume that the left channel aligns with the right, and that this is not two separate codes in two channels but only one in both channels, then I hear .- for the left channel. Which means the signal as a whole is ..-.

Also, has anyone else noticed that there are "drum" beats mixed in with the beeps? Could these clue us in as to what the code actually is?

[Manco]

I think I've found something! Those low frequency parts? They look like morse code too! You can tell because the waves are so small (that might not make sense but see the pictures for more info). For example, the one right at the end is this:

http://imgur.com/EAKeTtR

Which in turn can be interpreted as .-..

before that is this:

http://imgur.com/AqKUGUK

which can be interpreted as ..

I think this should be investigated further, by some one more able to interpret morse code.

If that’s the case, those would be L (.-..) and I (..).

This stuff is way beyond me and I’m getting frustrated trying to make progress. I’ll let you audio people figure this one out.

[SqueeglePoof]

http://imgur.com/EAKeTtR

Which in turn can be interpreted as .-..

I know what you mean. It looks like .-.., but I pitched that part up a couple octaves so I could hear the sounds (because it's too low frequency for anyone to hear). I am pretty sure that the first . is distinct from the -.. because there is more spacing between them, sound-wise. What I mean is, between . and -, there is more space than between the - and .

That equates to . -.., which is "ED." This is my interpretation.

before that is this:

http://imgur.com/AqKUGUK

which can be interpreted as ..

This is the one I'm unsure of. To me, it looks like .- (a) since the first wave is shorter than the second. Or, maybe they are separate. So, . (e) and - (t).

[JayDee]

I've tried once more for the past hour with lsot.mp3 but to no avail, my theory that I had was that the position of the static noise during the morse code could be used to place the order. With static on right being on the left, static on each side being in the middle, and static on the left being one the right. I tried this with the trouble issue of lsot l/os/t and figured it may mean the middle section is reversed. I tried my order with and without the middle reversed but didn't get anything significant, checking on soulstorm/ for any URL results.

Perhaps someone more capable than myself could try this method since I couldn't find the isolated morse code segments, and was doing the morse code by ear.

[Manco]

I figure that before we start worrying about order we need to get every piece of morse code translated first, including these supposed hidden ones. Then we can start worrying about whether they’re ciphered, out of order, or reversed.

[cleanshirtuk]

so there are 3 sections of low frequency morse code that I can see, the two I posted before, and another .-.., however, the wave in this never does a full cycle. Don't think this means anything but it's something to work with. Judging by all of this we are dealing with 6 different snippets of code. I'm still struggling to get my head around more code but its arranged as follows:

HIGH FREQ MORSE 1/HIGH FREQ MORSE 2/LOW FREQ MORSE 1 (. -..)/LOW FREQ MORSE 2 (.-)/LOW FREQ MORSE 1/HIGH FREQ MORSE 3

If you need any clarification let me know, There's so many different interpretations for this morse code stuff I have no idea how it translates.

[JayDee]

If someone who has the isolated morse code post it here in this thread, that would be pretty helpful. Or posting this low frequency morse code.

[SqueeglePoof]

HIGH FREQ MORSE 1/HIGH FREQ MORSE 2/LOW FREQ MORSE 1 (. -..)/LOW FREQ MORSE 2 (.-)/LOW FREQ MORSE 1/HIGH FREQ MORSE 3

I think this makes sense. However, I'm not sure that there are only six. There could other codes hidden. For example, I find it strange that there are drums playing at 0:25, with nothing before or after. And it even gets cut off suddenly.

[SqueeglePoof]

If someone who has the isolated morse code post it here in this thread, that would be pretty helpful. Or posting this low frequency morse code.

We should put this on the wiki. I can get it started.

[Moot]

I think I can accurately translate the first MC, which is split up in channel 1 and 2. Checking now.

[cleanshirtuk]

Hmmm. Low frequency morse 2 actually looks more like . -, which would mean ET.. Which would mean all together we could be looking at (with what we have so far) either:

ETEGEDETEDTE

or

FEDEDETEDTE

Which brings us back to square one. I'm so stumped.

[Moot]

14227

This is the right channel reversed. It's much easier to understand. What do you guys think it is? We can take the result, and turn it about, whcih should give us the answer.

Edit: I'm almost certain it's .-.. or .--.

Edit 2: I'm pretty sure it is .--. which is P, that's my conclusion. And sorry, no idea how to fix it ):

[SqueeglePoof]

I can't open the attachment.

[SqueeglePoof]

I added a section to the wiki for lsot.mp3.

Wasn't too sure about the format of the table, but I did my best. As for the last section at 1:49, I didn't know what, if anything, we thought the code might be.

[SqueeglePoof]

14227

This is the right channel reversed. It's much easier to understand. What do you guys think it is? We can take the result, and turn it about, whcih should give us the answer.

Edit: I'm almost certain it's .-.. or .--.

Edit 2: I'm pretty sure it is .--. which is P, that's my conclusion. And sorry, no idea how to fix it ):

So the signal in the right channel at 0:15, reversed, you think is P? To me it sounds more like --. as I can't hear the first . in .--.

Speaking of reversing, it seems as though the last signal at 1:49 is a reversed version of the signal in the left channel at 0:15. I lined them up and they match almost exactly. Can someone else confirm?

[Moot]

So the signal in the right channel at 0:15, reversed, you think is P? To me it sounds more like --. as I can't hear the first . in .--.

Speaking of reversing, it seems as though the last signal at 1:49 is a reversed version of the signal in the left channel at 0:15. I lined them up and they match almost exactly. Can someone else confirm?

I made the same comment when we first got the audio. So I can confirm! Notice how there's static too, which certainly helps it seem reversed.

Edit: The more I look at this audio, the more I feel like we were only supposed to find ED. I'm focusing myself on the ED page, to see what I can find. So far only the U I.

[Nepsotic]

Pretty sure I told people about the low frequency sine waves in the last thread. I thought we already came to the conclusion that they were dupes.

[SqueeglePoof]

Pretty sure I told people about the low frequency sine waves in the last thread. I thought we already came to the conclusion that they were dupes.

Could you explain again why you think so? I didn't seem to catch that conclusion. I feel like it's significant, even if it's redundant (tells us "ED" is the important stuff).

[Nepsotic]

Yeah just listen to them and it's pretty clear.

I've taken out the bits of what appear to be morse code and spliced them into one file. I'm not very good at morse code so I will explain what this audio file contains and then someone else can figure it out. I've also EQed out most of the unnecessary frequencies so you can hear the beeps more clearly.

The first clip is the first bit we hear, the second is the same thing but just the right channel and the third is the same again but just the left channel. This is because both channels contain different snippets of code, so I separated them.

After the silence there is another clip, this is the second piece of code we hear, nothing special here.

After that silence, there are two clips. The first is the next piece of code, but it's quite obviously reversed, so what you hear after that is it flipped round. I decided to put both in.

Now the last set of clips are a series of clicks I heard throughout the file, I pitched them up and it seems like they might be some more code. You guys figure it out. I'm actually thinking that last one is the same as the second one.