Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: MP3 file encoded by Google (Read 1011 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

MP3 file encoded by Google

What encoder Google used for this file?

Re: MP3 file encoded by Google

Reply #1
Lame 3.100
So does the file say.
Error 404; signature server not available.

Re: MP3 file encoded by Google

Reply #2
How did you find out?
Well, it's not that hard to find out: MP3 is dead & LAME is the only MP3 encoder available.


Re: MP3 file encoded by Google

Reply #4
You can open the file inside hex editor and you will see "LAME3.100"
gold plated toslink fan

Re: MP3 file encoded by Google

Reply #5
LAME writes LAME INFO tag into frame padding.
--------------------



Re: MP3 file encoded by Google

Reply #8
You can even call it it a lossy representation ...

Found 256 lame in the file - did google just remove it from the usual header to disguise what they are doing?
High Voltage socket-nose-avatar

Re: MP3 file encoded by Google

Reply #9
-t              disable writing LAME Tag
--------------------

Re: MP3 file encoded by Google

Reply #10
So -t disables writing LAME tag, but still writes LAME all over the headers elsewhere?
High Voltage socket-nose-avatar

Re: MP3 file encoded by Google

Reply #11
Disabling writing the LAME tag also disables writing gapless information.

 

Re: MP3 file encoded by Google

Reply #12
Not in headers but in unused space. Lame is also the only encoder that fills this space with alternating bit pattern 101010.