| 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 |
<html> |
| 3 |
<head> |
| 4 |
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| 5 |
<title>IceS v2.0 Documentation</title> |
| 6 |
<link rel="STYLESHEET" type="text/css" href="style.css"> |
| 7 |
</head> |
| 8 |
<body> |
| 9 |
<div class=boxtest> |
| 10 |
<h1>Frequently Asked Questions</h1> |
| 11 |
<table width="100%"><tr><td bgcolor="#007B79" height="10" align="center"></td></tr></table> |
| 12 |
<p> |
| 13 |
This for those questions people have asked as it wasn't covered |
| 14 |
in the documentation |
| 15 |
</p> |
| 16 |
<h4>Can ices play mp3 files</h4> |
| 17 |
<div class=indentedbox> |
| 18 |
<p> |
| 19 |
No, there hasn't been much interest in handling MP3 with ices 2. The older version ices |
| 20 |
0.x maybe of interest in such cases. If you really want to encode the Vorbis stream from |
| 21 |
non-vorbis files then you can play them with an external application, eg xmms, and use |
| 22 |
ices 2 to capture from the soundcard, but be aware that any conversion from one lossy format |
| 23 |
to another is bad so make sure the original material is high quality. |
| 24 |
</p> |
| 25 |
</div> |
| 26 |
<h4>How do I encode from Line-In</h4> |
| 27 |
<div class=indentedbox> |
| 28 |
<p> |
| 29 |
IceS will read from the DSP on the soundcard, but where that gets the |
| 30 |
audio from depends on the mixer settings. Use a utility like aumix/alsamixer to |
| 31 |
see the settings and change the capture or recording device. Usually the |
| 32 |
default is the Mic |
| 33 |
<p> |
| 34 |
</div> |
| 35 |
<h4>When I start ices 2 it seems to get stuck not doing anything</h4> |
| 36 |
<div class=indentedbox> |
| 37 |
If you are using live input, check to see if something else is holding the |
| 38 |
recording device (typically /dev/dsp) open. A good candidate is esd. What |
| 39 |
happens is that the driver only allows one application to have the device |
| 40 |
open at any one time, a second attempt will just block. |
| 41 |
<p>Some OSS drivers allow multiple opens but on ALSA you can configure a virtual |
| 42 |
device in asound.conf, type dsnoop/dmix, which allows access for multiple apps.</p> |
| 43 |
</div> |
| 44 |
<h4>Ices reports a message about failing to set samplerate on live input</h4> |
| 45 |
<div class=indentedbox> |
| 46 |
Some hardware/drivers are limited in the settings they support. Sometimes |
| 47 |
they only support one samplerate like 48khz. You have to experiment if the |
| 48 |
documentation for the device is not specific. |
| 49 |
</div> |
| 50 |
<h4>Can I do crossfading with the playlist</h4> |
| 51 |
<div class=indentedbox> |
| 52 |
Ices does not do much in the way manipulating the audio itself, resampling |
| 53 |
and downmixing are available as that has a direct effect on encoding an |
| 54 |
outgoing stream. Ices can still be used in conjunction with other |
| 55 |
applications such as xmms by making ices read from the say the dsp (eg |
| 56 |
oss, alsa etc), that way anything that is played by that other application |
| 57 |
is encoded and sent to icecast. |
| 58 |
</div> |
| 59 |
<h4>My player connects but I don't hear anything</h4> |
| 60 |
<div class=indentedbox> |
| 61 |
If you are getting data through to the player and the settings show like the |
| 62 |
samplerate and chnnels then it is probably the mixer settings which are set |
| 63 |
incorrectly and ices can only read silence. A common example, ALSA may have |
| 64 |
many levels in the mixer and by default they are all muted. |
| 65 |
</div> |
| 66 |
<h4>My player seems unable to play the stream</h4> |
| 67 |
<div class=indentedbox> |
| 68 |
If the stream looks to be getting to the player then it will be how the |
| 69 |
player is handling it. The usual causes of this are |
| 70 |
<ul>missing ".ogg" extension. Both ices and icecast do not care about the |
| 71 |
extension however some apps use the extension to determine which plugin to |
| 72 |
use.</ul> |
| 73 |
<ul>Missing Ogg Vorbis plugin. The winamp lite versions were known for |
| 74 |
this.</ul> |
| 75 |
<ul>Are you running Winamp 3. This is a discontinued product and had problems |
| 76 |
with the vorbis plugin, either use the later v2.9 series or v5.</ul> |
| 77 |
</div> |
| 78 |
<h4>The sound quality is poor</h4> |
| 79 |
<div class=indentedbox> |
| 80 |
<p> |
| 81 |
Ogg Vorbis is a lossy compression technology, so quality of the sound is |
| 82 |
reduced, however with live input the source of audio can be poor depending |
| 83 |
on the soundcard and the system it's in. As an initial test just record |
| 84 |
a wav file from the DSP (using eg rec, arecord etc) and listen to the |
| 85 |
quality of the audio recorded. If the source of audio is poor then encoding |
| 86 |
it to Ogg Vorbis is not going to improve it. |
| 87 |
</p> |
| 88 |
<p> |
| 89 |
The reasons for poor audio from the DSP can be difficult to resolve, search |
| 90 |
for information on audio quality. It could be driver related or maybe some |
| 91 |
interference from some other device. |
| 92 |
</p> |
| 93 |
<p> |
| 94 |
Here are some links where further information can be found: |
| 95 |
</p> |
| 96 |
<a href="http://www.djcj.org/LAU/guide/index.php">http://www.djcj.org/LAU/guide/index.php</a><BR> |
| 97 |
<a href="http://www.linuxdj.com/audio/lad/index.php3">http://www.linuxdj.com/audio/lad/index.php3</a> |
| 98 |
</div> |
| 99 |
</div> |
| 100 |
</body> |
| 101 |
</html> |