SoulStorm ARG - lsot.mp3 analysis -

Manco · #31 03-28-2016, 01:19 AM

I wouldn’t say that’s the conclusion we came to, we just agreed that focusing on the clear pieces of code was the best course of action.

So far the only solution that tactic has borne out is ED, which hasn’t gone any further since we found it. So now we need to explore additional options.

edit: I’ve added more interpretations to the wiki. 0:15 left channel is definitely ET, I don’t think there should be any doubt about that. 1:49 is definitely TE as well. 0:15 right channel sounds like ETN but it’s hard to make out for sure.

***Xavier*** · #32 03-28-2016, 06:44 AM

:

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.

Hold on... if the audio is reversed shouldn't we read the morse code in reverse too?

In that case we have:

D -> U
F -> L
E -> E
T -> T
G -> W

STM · #33 03-28-2016, 06:53 AM

e: wrong ARG thread.

SqueeglePoof · #34 03-28-2016, 12:22 PM

:

edit: I’ve added more interpretations to the wiki. 0:15 left channel is definitely ET, I don’t think there should be any doubt about that.

It seems like we have a lot of Es. Are you sure? There's just such an issue with spacing between codes in the audio that it's hard to tell when one ends and another begins.

:

1:49 is definitely TE as well.

Moot and I were just discussing that this code is a reversed version of 0:15. So the (rhetorical) question is, should we consider that the code here is TE, or it's "proper" re-reversed version ET? (Alternatively, N or A?)

Moot · #35 03-28-2016, 12:32 PM

This is starting to hurt my brain. Please end the suffering.

SqueeglePoof · #36 03-28-2016, 12:38 PM

Here, have a Soulstorm. On the house.

Manco · #37 03-28-2016, 01:06 PM

:

It seems like we have a lot of Es. Are you sure? There's just such an issue with spacing between codes in the audio that it's hard to tell when one ends and another begins.

It confused me at first, but eventually you can get an ear for where the spaces are. I can definitely identify spaces in 0:15L and 1:45.

:

Moot and I were just discussing that this code is a reversed version of 0:15. So the (rhetorical) question is, should we consider that the code here is TE, or it's "proper" re-reversed version ET? (Alternatively, N or A?)

Either way it doesn’t get us anywhere new. Whatever we’re looking for will probably be an anagram or cipher anyway, so I doubt the order will matter too much.

metalpowerhead199 · #38 03-28-2016, 02:17 PM

I did some research, and after going off the theory that the first and last set of beeps have been separated from each other, I got .-.-.

In Morse Code, .-.-. means "End of Message".

Varrok · #39 03-28-2016, 02:19 PM

That's great, I didn't know that!

metalpowerhead199 · #40 03-28-2016, 02:22 PM

This means there's something hidden in the message, and it's not in order. It could all be separated from each other, so we've gotta start putting stuff together, in any way possible.

Moot · #41 03-28-2016, 03:33 PM

By the way guys, try turning the lsot.mp3 into a lsot.txt, it says "FIND ME" and "LAME" but I'm not entirely sure there's anything else in it..

Varrok · #42 03-28-2016, 03:37 PM

LAME is an mp3 encoder

Moot · #43 03-28-2016, 03:51 PM

:

LAME is an mp3 encoder

I totes knew that. I'm just messing with you guys!!!

i didn't ):

Nepsotic · #44 03-28-2016, 03:58 PM

I suggested we do that but Varrok said it would not work the shit

SqueeglePoof · #45 03-28-2016, 05:26 PM

:

I did some research, and after going off the theory that the first and last set of beeps have been separated from each other, I got .-.-.

Do you have your modifications to the audio handy? As in, do you have a file you can share?

metalpowerhead199 · #46 03-28-2016, 06:43 PM

:

Do you have your modifications to the audio handy? As in, do you have a file you can share?

Yes, I do

lsot_mono.zip is the original file. It is the left and right channels merged into a mono channel. Unfortunately I cannot remember who originally uploaded the file but it was in the main thread for the ARG.

lsot_mono (1).zip is the reversed clip. I made the reverse clip, and used both as references. Using them both I got the morse code, but if anyone could double check and verify, that would be great.

Moot · #47 03-28-2016, 06:56 PM

I said this in the main ARG chat. It still holds.

:

I'm not entirely sure where to go anymore. How can the ED page just be a dead end? The only thing you could possibly take away from it, is the UI (the only non-strange letters in it, once you save the page as a .txt). The audio is literally gibberish, only ED prove significant.

I'm still combing through the audio, and I just tried combining the first R and L channels together, whcih gave me -- . or .. - or . .. (it's hard to tell the tones with the beat n the backround. Which gives us: ME IT EI being the three possibilities.

The only substantial thing I learned, was the MC at the very end was indeed reversed. Once I re-reversed it, you could hear the subtle drumbeat in its backround, so it does translate to: ET

Edit: I really dislike this stage of the ARG.

SqueeglePoof · #48 03-28-2016, 07:05 PM

:

I cannot remember who originally uploaded the file

It was me!

So how again did you arrive at .-.-.? I'm not quite seeing... er, hearing it.

Also, according to wikipedia, .-.-. is "+"
https://en.wikipedia.org/wiki/Morse_...code_tree3.png

metalpowerhead199 · #49 03-28-2016, 07:50 PM

:

It was me!

So how again did you arrive at .-.-.? I'm not quite seeing... er, hearing it.

Also, according to wikipedia, .-.-. is "+"
https://en.wikipedia.org/wiki/Morse_...code_tree3.png

I believe I took the first morse code beeps from the beginning and got ".-" That could be wrong though, the echo was insane, and I could've been incorrect. I put it together with what i thought was ".-." at the end.

Here's my source for the End of Message:
http://rumkin.com/tools/cipher/morse.php