diff --git a/doc/FAQ.html b/doc/FAQ.html
index 16e1835d..0798f286 100644
--- a/doc/FAQ.html
+++ b/doc/FAQ.html
@@ -208,6 +208,28 @@ the developer of the anti-virus software. And, if they don't fix the problem, sw
+Why does application 'xyz' not open the Wave files created by LameXP?
+
+Some of the decoders used in LameXP will insert an additional 'JUNK' chunk into the Wave/RIFF file, right
+before the 'fmt' chunk ("Wave header"). There are technical reasons why this 'JUNK' chunk (placeholder) might
+be needed at the beginning of the file. The 'JUNK' type is a standard RIFF type and, by definition of the
+RIFF file format specification, any reading application must ignore/skip all 'JUNK' chunks it may encounter!
+Evidently most reading applications do so and thus will correctly open the Wave file. Unfortunately it was
+brought to our attention that there are a few broken(!) applications, which reject Wave/RIFF files with an
+additional 'JUNK' chunk in front of the 'fmt' chunk. It seems that these applications make false assumptions
+and expect the 'fmt' chunk to be located at a fixed postion, rather than actually parsing the RIFF structure.
+
+While it is evident that applications, which reject the Wave/RIFF file because of the extra 'JUNK' chunk, are
+broken with respect to the RIFF specification and should be fixed by the respective author, there is an easy
+workaround: Re-saving the Wave/RIFF file with SoX creates a file that even the broken applications seem to
+accept, as SoX apparently doesn't insert any 'JUNK' chunks (although it would be free to do so!) Re-saving
+your Wave file with SoX does NOT change the actual content at all, as long as no additional filters are used.
+
+You can use a command-line like this:
+