The only reason I use the rest of the switches, is that some of my devices could not read some MP3s on the CD compilations I made, or even directly off the hard disk.
So I went reading and found that the set for compliance and limits meant a lot.
lame --nohist --vbr-new -V2 -t -b64 -B320 -F --strictly-enforce-ISO -p
--nohist == No Histogram during encoding, thank you. (way optional)
--vbr-new == Use the new VBR encoding please. The old one surprisingly is not well supported in the "MP3 Device Industry" or at all in some cases.
-V2 == Please use the third largest algo set for encoding, or "please chop very litte info from the music program, but please remove the "ringing most MP3 encoders cause above 19K during encoding"
-t == disable writing LAME Tag (or encoded by LAME v3.blah in the comment tag)
-b64 == The absolute minimum bit rate lame can use. Many MP3 devices, surprisingly cannot read/decode below this bitrate, causing dropouts or skipping to the next song. My Sony "Xplod" Car Audio deck falls into the category.
-B320 == The absolute maximum bit rate lame can use. Some early MP3 devices were designed that "320Kbps" is all they will ever need... seems they were wrong. I have another Sandisk thumb drive that works as an MP3 player, storage and dictation recorder. Very early on in the MP3 device arena
-F == strictly enforce the -b option, for use with players that do not support low bitrate mp3
--strictly-enforce-ISO == comply as much as possible to ISO MPEG spec
-p == error protection. adds 16 bit checksum to every frame (the checksum is computed correctly). My Sony "Xplod" and my wife's mobile Sony CD/MP3 player both can do error correction on the fly.