Jelly challenge: decode the chaotic messages

by James Thorniley

Whilst hyperflunking across the interdimensional quantum vibration matrix, your spaceship detects three jumbled up signals. They sound like random noise, but you suspect they are in fact secret messages from Glycerol Soap Bomb, the ruler and Maximal Liapunov Exponent of the planet Cholesky Decomposition. The messages can be downloaded from the following locations:

The signals have actually been coded using a similar technique to the chaotic message hiding method we have already discussed. However, Glycerol Soap Bomb has sneakily mucked about with the algorithm a little bit, so you will probably find the three messages progressively harder to reconstruct.

Nonetheless, feel free to make use of this Java code for the original Jellymatter chaotic encryption system as a starting point. The ChaoticTransmitter class takes a wav file with a message in and hides it in a chaotic signal in a new wav file. ChaoticReceiver reconstructs the original message from the chaotic signal.

To start you off, try decoding this message which was created using the above code, so you should be able to use the provided ChaoticReceiver as-is to reconstruct it easily:

Use any method you want to find the solutions though. I believe it should be possible to find the messages without using a chaotic receiver (though I haven’t done this myself yet), so feel free to do that if you want. Bonus marks though if you are able to determine exactly how the messages were created, or for solutions that produce clearer sounding reconstructions.

The prize for finding the answers is a feeling of smug superiority.

Feel free to stick answers or thoughts in the comments. I will post a follow up with the original messages and correct encryption methods after a sensible time delay…

UPDATE: 5.30pm: I put the wrong file up for signal 3, I’ve left it anyway, but the one I intended was this:

About these ads

6 Comments to “Jelly challenge: decode the chaotic messages”

  1. Message 1 received. Standing by.

  2. Message 2 received. Have you tried turning it off and on again?

    That one was quite a lot harder. I’ll write up a post on how I did it after I’ve either decoded the rest or given up…

  3. Original message 3 received, but the corrected one (signal4.wav) has me completely stumped. I can guess at what sort of thing it might be, but I don’t know how to deduce the details. I’ll probably give it another try another day.

  4. signal4.wav is in fact sort of a trick question. I don’t myself have a way of getting the signal out of it, but I think it should be possible (I am going to try at some point as well)

    • I suspected that – I’d be very surprised if you could extract a signal from that using the same technique as the others. If I can’t extract it by next weekend I’ll include something in my post about what I think it is and why it’s so much harder to get the signal out.

  5. I will be interested to know the particular approach you took for the others, obviously I have methods in mind but they might not be the same…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 483 other followers

%d bloggers like this: