Commit 06d2d79b authored by Josh Coalson's avatar Josh Coalson
Browse files

move submit-a-bug to project section

parent b32b82bc
...@@ -115,9 +115,6 @@ ...@@ -115,9 +115,6 @@
<LI> <LI>
<A HREF="#general__lowest_bitrate"><B>What is the lowest bitrate achievable with FLAC?</B></A> <A HREF="#general__lowest_bitrate"><B>What is the lowest bitrate achievable with FLAC?</B></A>
</LI> </LI>
<LI>
<A HREF="#general__submit_bug"><B>How do I submit a bug report?</B></A>
</LI>
</UL> </UL>
</P> </P>
...@@ -169,6 +166,9 @@ ...@@ -169,6 +166,9 @@
<LI> <LI>
<A HREF="#project__lists"><B>Where are the mailing lists, forums, discussion areas, etc.?</B></A> <A HREF="#project__lists"><B>Where are the mailing lists, forums, discussion areas, etc.?</B></A>
</LI> </LI>
<LI>
<A HREF="#project__submit_bug"><B>How do I submit a bug report?</B></A>
</LI>
</UL> </UL>
</P> </P>
...@@ -270,12 +270,6 @@ ...@@ -270,12 +270,6 @@
<P> <P>
With FLAC you do not specify a bitrate like with some lossy codecs. It's more like specifying a quality with Vorbis or MPC, except with FLAC the quality is always "lossless" and the resulting bitrate is roughly proportional to the amount of information in the original signal. You cannot control the bitrate and the result can be from around 100% of the input rate (if you are encoding noise), down to almost 0 (encoding silence). With FLAC you do not specify a bitrate like with some lossy codecs. It's more like specifying a quality with Vorbis or MPC, except with FLAC the quality is always "lossless" and the resulting bitrate is roughly proportional to the amount of information in the original signal. You cannot control the bitrate and the result can be from around 100% of the input rate (if you are encoding noise), down to almost 0 (encoding silence).
</P> </P>
<P>
<A NAME="general__submit_bug"><B>How do I submit a bug report?</B></A>
</P>
<P>
First, <A HREF="http://sourceforge.net/tracker/?group_id=13478&atid=113478">visit the bug tracking page</A> and do a little searching of both open and closed bugs to see if yours is already there. If you have something truly new, <A HREF="http://sourceforge.net/bugs/?func=addbug&group_id=13478">submit a new bug</A>. <B>Make sure</B> to monitor the bug or include your email address in the description. Include as much information as possible: the version of FLAC that you are running, the name and version of any frontend you are running, your operating system and version, your CPU type and speed, the amount of memory you have, where you downloaded FLAC from, the exact error message (if any) copied from the console, and anything else you may think will help.
</P>
<H2> <H2>
<B>Tools</B> <B>Tools</B>
...@@ -305,7 +299,7 @@ ...@@ -305,7 +299,7 @@
<A NAME="tools__hardware_prob"><B>I compressed a file to FLAC with verify on, and flac said "Verify FAILED!" Why?</B></A> <A NAME="tools__hardware_prob"><B>I compressed a file to FLAC with verify on, and flac said "Verify FAILED!" Why?</B></A>
</P> </P>
<P> <P>
Every single report of this has turned out to be caused by a hardware problem, usually aggressive over-clocking or bad RAM. The best indicator of this is that the verify failure does not always happen in the same place for the same file. First, read the comments in <A HREF="http://sourceforge.net/tracker/index.php?func=detail&aid=595858&group_id=13478&atid=113478">this bug report</A>. Then, if you have a file that fails verification in the same place every time, <A HREF="#general__submit_bug">submit a new bug</A>, uploading a sample according to <A HREF="http://sourceforge.net/tracker/index.php?func=detail&aid=585158&group_id=13478&atid=113478">the instructions found at the bottom of this bug report</A>. Every single report of this has turned out to be caused by a hardware problem, usually aggressive over-clocking or bad RAM. The best indicator of this is that the verify failure does not always happen in the same place for the same file. First, read the comments in <A HREF="http://sourceforge.net/tracker/index.php?func=detail&aid=595858&group_id=13478&atid=113478">this bug report</A>. Then, if you have a file that fails verification in the same place every time, <A HREF="#project__submit_bug">submit a new bug</A>, uploading a sample according to <A HREF="http://sourceforge.net/tracker/index.php?func=detail&aid=585158&group_id=13478&atid=113478">the instructions found at the bottom of this bug report</A>.
</P> </P>
<P> <P>
<A NAME="tools__wave_flac_wave"><B>I compressed a WAVE file to FLAC, then decompressed to WAVE, and the two weren't identical. Why?</B></A> <A NAME="tools__wave_flac_wave"><B>I compressed a WAVE file to FLAC, then decompressed to WAVE, and the two weren't identical. Why?</B></A>
...@@ -353,6 +347,12 @@ ...@@ -353,6 +347,12 @@
<P> <P>
There are a few places. The main discussions happen on <A HREF="http://sourceforge.net/mail/?group_id=13478">the official FLAC mailing lists</A>. Eventually we will be transitioning over to <A HREF="http://xiph.org/archives/">the lists on Xiph.org</A>. Also, there is a lot of discussion relating to FLAC on <A HREF="http://www.hydrogenaudio.org/">Hydrogen Audio</A>. There are a few places. The main discussions happen on <A HREF="http://sourceforge.net/mail/?group_id=13478">the official FLAC mailing lists</A>. Eventually we will be transitioning over to <A HREF="http://xiph.org/archives/">the lists on Xiph.org</A>. Also, there is a lot of discussion relating to FLAC on <A HREF="http://www.hydrogenaudio.org/">Hydrogen Audio</A>.
</P> </P>
<P>
<A NAME="project__submit_bug"><B>How do I submit a bug report?</B></A>
</P>
<P>
First, <A HREF="http://sourceforge.net/tracker/?group_id=13478&atid=113478">visit the bug tracking page</A> and do a little searching of both open and closed bugs to see if yours is already there. If you have something truly new, <A HREF="http://sourceforge.net/bugs/?func=addbug&group_id=13478">submit a new bug</A>. <B>Make sure</B> to monitor the bug or include your email address in the description. Include as much information as possible: the version of FLAC that you are running, the name and version of any frontend you are running, your operating system and version, your CPU type and speed, the amount of memory you have, where you downloaded FLAC from, the exact error message (if any) copied from the console, and anything else you may think will help.
</P>
</FONT> </FONT>
</TD></TR> </TD></TR>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment