Topic: BOUNTY: Crack this value, get bitcoin (Read 681 times)
Any more takers?
Crack it and take it all, hahaha
Heh
, I'm trying, I'm trying... no luck though yet... Huh, that is quite helpful.
I'm glad to hear that. When this ends, I don't mind a tip, I have 2 addresses in my profile.
I'll keep thinking, maybe I get something more to get us closer; if I get anything new, I'll post.
Crack it and take it all, hahaha
Huh, that is quite helpful.
I'm glad to hear that. When this ends, I don't mind a tip, I have 2 addresses in my profile.
I'll keep thinking, maybe I get something more to get us closer; if I get anything new, I'll post.
I believe you're on the right track NeuroticFish. I just got this hint from a Serato developer: working the encoded stuff through base64 to ascii gives the cue points in a ms in a base 64 number
Base 64 number = int 64?
Base 64 number = int 64?
But, why would it need a transparency value in the colours? That's the confusing part.
It can be useful. Most applications now use some kind of transparency in their colours.
Fair enough! Just seems odd that Serato would use it - I assumed most lighting and DJ applications would only need RGB but having an alpha channel makes sense.
But, why would it need a transparency value in the colours? That's the confusing part.
It can be useful. Most applications now use some kind of transparency in their colours.
From my understanding, after each "word", there's a number composed of 5 bytes. Imho, that number should not be read in hexa. I'll explain:
After the first group (COLOR) the number is 4, meaning the following are 4 bytes of color: 00, 99, 99, 99 (an ARGB color).
Then the next group tells CUE. The magic number is 12. If I'd convert it to hexa it would do wrong, but if I read it as decimal 12, then it matches: the next 12 bytes are the useful data 00 00 00 00 00 19 00 CC 00 00 00 00. Maybe the first 8 bytes are some Time (int64 time_t?) and the rest of 4 bytes are an ARGB black.
I hope it helps somebody...
After the first group (COLOR) the number is 4, meaning the following are 4 bytes of color: 00, 99, 99, 99 (an ARGB color).
Then the next group tells CUE. The magic number is 12. If I'd convert it to hexa it would do wrong, but if I read it as decimal 12, then it matches: the next 12 bytes are the useful data 00 00 00 00 00 19 00 CC 00 00 00 00. Maybe the first 8 bytes are some Time (int64 time_t?) and the rest of 4 bytes are an ARGB black.
I hope it helps somebody...
Huh, that is quite helpful.
But, why would it need a transparency value in the colours? That's the confusing part.
EDIT: I had figured that the 12 was a control character, but everything else lines up with your theory.
From my understanding, after each "word", there's a number composed of 5 bytes. Imho, that number should not be read in hexa. I'll explain:
After the first group (COLOR) the number is 4, meaning the following are 4 bytes of color: 00, 99, 99, 99 (an ARGB color).
Then the next group tells CUE. The magic number is 12. If I'd convert it to hexa it would do wrong, but if I read it as decimal 12, then it matches: the next 12 bytes are the useful data 00 00 00 00 00 19 00 CC 00 00 00 00. Maybe the first 8 bytes are some Time (int64 time_t?) and the rest of 4 bytes are an ARGB black.
I hope it helps somebody...
After the first group (COLOR) the number is 4, meaning the following are 4 bytes of color: 00, 99, 99, 99 (an ARGB color).
Then the next group tells CUE. The magic number is 12. If I'd convert it to hexa it would do wrong, but if I read it as decimal 12, then it matches: the next 12 bytes are the useful data 00 00 00 00 00 19 00 CC 00 00 00 00. Maybe the first 8 bytes are some Time (int64 time_t?) and the rest of 4 bytes are an ARGB black.
I hope it helps somebody...
It's directly related to a MP3 id3v2.3 tag. There's an app called Serato that creates it's own data placed in a GEOB (General encapsulated object).
Let me explain:
Here's our string:
Decode the value to get the binary output. This tool proves useful: http://base64-encoding.online-domain-tools.com/
COLOR:
AQFDT0xPUgAAAAAEAJmZmU
First 8 chars are: ..COLOR. (Hex: 01 01 43 4f 4c 4f 52 00)
The next 8 chars are: ........ (Hex: 00 00 00 04 00 99 99 99)
The hex value "99 99 99" is the actual colour.
The next step is where I'm stuck and what the bounty is for. You can find the start of a CUE by finding the end of a colour value.
Hex: 43 55 45 (CUE). After this value, there should be values of Time, Colour, Text(START)
The difficulty is decoding the individual items (CUEs), not the object itself.
Let me explain:
Here's our string:
Quote
AQFDT0xPUgAAAAAEAJmZmUNVRQAAAAASAAAAAAAZAMwAAAAAU1RBUlQAQ1VFAAAAABMAAQAA
cbMAzIgAAABWT0NBTFMAQ1VFAAAAAA0AAgAAqoQAAADMAAAAQ1VFAAAAABMAAwABVPkAzMwA
AABEUk9QIDEAQ1VFAAAAAA0ABAABjcYAAMwAAAAAQ1VFAAAAABUABQAB/3MAzADMAABCdWls
ZHVwMgBDVUUAAAAADQAGAALp1AAAzMwAAABDVUUAAAAAEAAHAANbegCIAMwAAEVORABMT09Q
AAAAABUAAAADLGMAA0jL/////wAnquEAAABMT09QAAAAABUAAQAAABAAABx5/////wAnquEA
AQBCUE1MT0NLAAAAAAEAA
cbMAzIgAAABWT0NBTFMAQ1VFAAAAAA0AAgAAqoQAAADMAAAAQ1VFAAAAABMAAwABVPkAzMwA
AABEUk9QIDEAQ1VFAAAAAA0ABAABjcYAAMwAAAAAQ1VFAAAAABUABQAB/3MAzADMAABCdWls
ZHVwMgBDVUUAAAAADQAGAALp1AAAzMwAAABDVUUAAAAAEAAHAANbegCIAMwAAEVORABMT09Q
AAAAABUAAAADLGMAA0jL/////wAnquEAAABMT09QAAAAABUAAQAAABAAABx5/////wAnquEA
AQBCUE1MT0NLAAAAAAEAA
Decode the value to get the binary output. This tool proves useful: http://base64-encoding.online-domain-tools.com/
COLOR:
AQFDT0xPUgAAAAAEAJmZmU
First 8 chars are: ..COLOR. (Hex: 01 01 43 4f 4c 4f 52 00)
The next 8 chars are: ........ (Hex: 00 00 00 04 00 99 99 99)
The hex value "99 99 99" is the actual colour.
The next step is where I'm stuck and what the bounty is for. You can find the start of a CUE by finding the end of a colour value.
Hex: 43 55 45 (CUE). After this value, there should be values of Time, Colour, Text(START)
The difficulty is decoding the individual items (CUEs), not the object itself.
PM, please
Done. If you can give me a little more context I can elaborate, but without context that string can be a multitude of things, though they all revolve around the same architecture.
Is the answer 'Ê'?
PM, please
Would you like us to PM you with the 3rd CUE + an explanation, or would it be okay to publically share?
| f | f | |||||||||||||||||||||||||
Hey Folk,
Im tossing a 0.2 btc bounty to crack this value and explain it.
The value is here: http://pastebin.com/pskVC3Qu
First hint: the string is base64 encoded. Decode this and you'll discover hex values. Crack the pattern, provide the value of the third CUE, and the btc reward is yours... As well as an opportunity to be paid btc for your knowledge.
Im tossing a 0.2 btc bounty to crack this value and explain it.
The value is here: http://pastebin.com/pskVC3Qu
First hint: the string is base64 encoded. Decode this and you'll discover hex values. Crack the pattern, provide the value of the third CUE, and the btc reward is yours... As well as an opportunity to be paid btc for your knowledge.
Jump to: