📄 faq.htm
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
<TITLE>Bugs, features, and frequently-asked questions</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<OBJECT TYPE="application/x-oleobject" CLASSID="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
<PARAM NAME="Keyword" VALUE="FAQ">
<PARAM NAME="Keyword" VALUE="bugs">
<PARAM NAME="Keyword" VALUE="questions">
<PARAM NAME="Keyword" VALUE="Macintosh">
<PARAM NAME="Keyword" VALUE="IRC">
<PARAM NAME="Keyword" VALUE="hung machine">
<PARAM NAME="Keyword" VALUE="server, IRC">
<PARAM NAME="Keyword" VALUE="firewall">
<PARAM NAME="Keyword" VALUE="Internet, wrecking">
<PARAM NAME="Keyword" VALUE="interoperability with other programs">
</OBJECT>
<H2><A NAME="faq"></A>Bugs, features, and frequently-asked questions</H2>
<dl>
<dt><b>I have a high-bandwidth connection to the Internet. Why do I get pauses and
lost sound?</b>
<dd>Unlike file transfers, transmitting intelligible audio
requires not only adequate bandwidth but <I>consistent delivery
time</I>. If one packet of sound takes a tenth of a second to
arrive, the next two seconds, and the third half a second, not
only will be there an audible pause but they'll be received and
played out of order.
<P>Network congestion and moment-to-moment re-routing can cause
precisely this kind of inconsistent delivery time. If you're
using a public network, there's nothing you can do other than
try again later when there may be less traffic. Remember, the
Internet was never intended to transmit real-time data such as
audio; it's a miracle it works as well as it does.</P>
<p>
<dt><b>When I send, nobody can hear me / I can't hear anybody else.</b>
<dd><I>(The following was contributed by John Deters).</I> For
those of you who aren't particularily familiar with Windows
audio hardware but would like to use <i>Speak Freely</i>, here
are some hints that might help get you started.
<P>First, does your sound card play regular Windows sounds?
When you start Windows, do you hear the "Ta-Da"? If not, make
sure your speakers are plugged in to the "speaker" or "output"
jack coming from your sound card. While you're at it, make sure
your microphone is plugged into the "mic in" jack. If there is
a volume knob on your sound card, make sure it's turned up. If
your speakers have a power supply (such as batteries or a power
transformer) make sure you have power, such as fresh batteries
or the transformer is plugged into a live outlet. Make sure
your speakers are turned on. You may need to refer to your
sound card or speaker's documentation to get it set up
correctly.</P>
<P>Some sound cards come with the microphone input not "turned
on". What this means is that your sound card will not "listen"
to your microphone until you tell it to. Included with your
sound card was (probably) a "Mixer" application (if not, there
may be a volume control application in your Accessories
group.) Double click the Mixer to start it. With Sound
Blaster cards, the mixer appears as columns of sliding volume
knobs. Your sound card may have come with a different
mixer.</P>
<P>If there is a volume control labeled "Microphone", this
refers to how much of the sound from the microphone input will
come out through your speakers. For now, turn it on (by
checking the box or whatever) and set the volume to the same
level as the volume control marked "Wave". If you're not sure,
just turn it all the way up (you can always turn it down
later). Make sure the switch on your microphone is turned on,
and tap on it or talk in it. Do you hear yourself? If not,
you need to find the input side of the mixer.</P>
<P>Hunt around for a menu option or button called "Recording
Controls". When you select it, you'll see a similar looking
screen that lists all of the inputs to your system. Turn the
microphone input on by clicking the box, and if there is a
"gain", set it to its maximum setting. Now, try tapping on the
microphone. You should now hear the tapping coming from your
speakers. Speak into the microphone, and compare the level of
sound from your voice to that of the other sounds in your
system.</P>
<P>You want your voice to come out about the same loudness as
the "ta-da", and you want it to be intelligible. You may need
to adjust the gain downward a bit, or find the correct place to
hold your microphone. Some microphones need to be held almost
to your lips, while others meant for mounting on your monitor
need to be a foot away from your face before you sound good.
Experiment with this for a while until the sound coming out of
your speakers sounds good to you.</P>
<P>Once you have the microphone gain set, you should return to
the output side of your mixer by finding the menu option or
button labeled "Volume" or "Output". It might have opened a
second window called "Recording Control" or "Input" that you
will need to close. Once you get back there, you will probably
want to turn the microphone OFF by un-checking the box. This
will keep your side of the conversation off of your speaker,
preventing nasty feedback squeals. When you've done that, you
won't hear anything else from your microphone coming out your
speaker, but you now know that your microphone is set up for
recording your voice. (Special note to headphone users: if
you use headphones, leave the microphone <I>ON</I>. It will
help your voice sound better to you, and your conversations
will sound more natural. You might wish to adjust the
microphone volume setting.)</P>
<P>For a good test, use the "Sound Recorder" program found in
your "Accessories" group. You should be able to click on the
"Record" dot, say something, click on stop, then rewind, then
the play arrow, and hear yourself.</P>
<P>Once your audio hardware is correctly set up and working to
your satisfaction, you will probably find that <i>Speak
Freely</i> now works surprisingly well. You can use the <A
HREF="loopback.htm">local loopback</A> facility to verify
correct operation with <i>Speak Freely</i>, then proceed to
experimenting with an <A HREF="echo.htm">echo server</A>.</P>
<P>The <A HREF="audiomonitor.htm">Audio Monitor</A> display may
help in troubleshooting input and output audio settings.</P>
<p>
<dt><b>I tried to call you and nobody answered.</b>
<dd>Hundreds of thousands of people have downloaded <i>Speak
Freely</i>, and the first thing a depressingly large percentage
of them do is immediately try to call me to "see if it works".
If I allowed all these calls to interrupt me, development on
<i>Speak Freely</i> (and everything else) would immediately
cease. So while I occasionally accept calls, until and unless
people become more considerate of my time, I mute the speaker
whenever I'm doing serious work. Use one of the <A
HREF="echo.htm">echo servers</A> for testing; that way you
won't bother total strangers with unsolicited calls.</P>
<p>
<dt><b>My dial-up Internet connection gives me a different host name and IP address every time I
connect. How can other people find me when I'm on-line?</b>
<dd><A HREF="lwl_tell.htm">Publish your E-mail address</A> on a
Look Who's Listening server. People who wish to call you can
<A HREF="lwl_ask.htm">look you up on the server</A>, see if
you're currently connected and, if so, connect to the address
for this session. You can use the same procedure to locate
other users with dial-up connections. Since your E-mail
address is unique and does not change from session to session,
it allows others to find you regardless of how you are
currently connected to the Internet.
<p>
<dt><b>Why do I connect to a machine (like furry.zoo.org) instead of a user (like
panda@fuzzy.zoo.org)?</b>
<dd>Because the audio hardware belongs to the machine, not the
user. Think of it like a house with a single telephone; there
may be several people living there, but they all share the same
phone number and only one can use the telephone at a time.
Your host name or IP address is just like a telephone number,
and your computer the telephone. To find what host name a
given user is connected to at the moment, look up their E-mail
address on a <A HREF="lwl_ask.htm">Look Who's Listening
server</A>.
<p>
<dt><b>My machine hangs as soon as I try to transmit.</b>
<dd>This is usually the result of failing to set a <A
HREF="compresswhy.htm">compression mode</A> appropriate for the
speed of your Internet connection. What should happen in this
case is that sound that can't be sent in time is just
discarded, but some implementations of WINSOCK seem to hang the
machine when a program tries to send data faster than the
network can accept it. In many cases (assuming you have a fast
enough computer), setting Options/GSM Compression will cure the
problem.
<p>
<dt><b>Is there / when will there be a Macintosh version?</b>
<dd>As soon as somebody makes one. I have neither the
knowledge nor the hardware to port <i>Speak Freely</i> to the
Macintosh myself, but it would be a relatively straightforward
project for a Mac developer experienced in both network and
audio programming, I believe. The compression and encryption
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -