| 1 |
<!-- X-URL: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/awedrv-faq.html --> |
| 2 |
<BASE HREF="http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/awedrv-faq.html"> |
| 3 |
|
| 4 |
<title>AWEDRV FREQUENTLY ASKED QUESTIONS</title> |
| 5 |
<body> |
| 6 |
|
| 7 |
<hr size=10> |
| 8 |
<p> |
| 9 |
|
| 10 |
<center> |
| 11 |
<h1>AWEDRV FREQUENTLY ASKED QUESTIONS</h1><p> |
| 12 |
FAQ ver.1.24<p> |
| 13 |
Takashi Iwai |
| 14 |
(<a href=mailto:[email protected]> |
| 15 |
<i>[email protected]</i></a>) |
| 16 |
</center> |
| 17 |
<p> |
| 18 |
|
| 19 |
Original site: |
| 20 |
<a href=http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/awedrv-faq.html> |
| 21 |
<i>http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/awedrv-faq.html</i></a> |
| 22 |
<p> |
| 23 |
|
| 24 |
<hr size=10> |
| 25 |
<dl> |
| 26 |
<dt><a href=#Q1> |
| 27 |
1. GENERAL NOTES |
| 28 |
</a> |
| 29 |
<dl> |
| 30 |
<dt><a href=#Q1.1> |
| 31 |
Q1.1: What is awedrv? What can I do with this? |
| 32 |
</a> |
| 33 |
<dt><a href=#Q1.2> |
| 34 |
Q1.2: From where can I download AWE32 sound driver for Linux and FreeBSD? |
| 35 |
</a> |
| 36 |
<dt><a href=#Q1.3> |
| 37 |
Q1.3: Does awedrv work on my AWE64 card? |
| 38 |
</a> |
| 39 |
<dt><a href=#Q1.4> |
| 40 |
Q1.4: How can I play my midi files using awe driver? What configuration is necessary? |
| 41 |
</a> |
| 42 |
<dt><a href=#Q1.5> |
| 43 |
Q1.5: How can I play my .MOD files using awe driver? What configuration is necessary? |
| 44 |
</a> |
| 45 |
</dl> |
| 46 |
|
| 47 |
<dt><a href=#Q1> |
| 48 |
2. INSTALLATION |
| 49 |
</a> |
| 50 |
<dl> |
| 51 |
<dt><a href=#Q2.1> |
| 52 |
Q2.1*: How to install awedrv on my linux kernel? |
| 53 |
</a> |
| 54 |
<dt><a href=#Q2.2> |
| 55 |
Q2.2*: What options should be set to configure sound module for AWE32 on linux? |
| 56 |
</a> |
| 57 |
<dt><a href=#Q2.3> |
| 58 |
Q2.3*: The linux sound driver can't detect my SB32-PnP card. Why? |
| 59 |
</a> |
| 60 |
<dt><a href=#Q2.4> |
| 61 |
Q2.4*: I installed ISA PnP tools, but still awedrv says "can't detect AWE32". |
| 62 |
</a> |
| 63 |
<dt><a href=#Q2.5> |
| 64 |
Q2.5*: Can I load my GM file automatically on the sound driver module? |
| 65 |
</a> |
| 66 |
<dt><a href=#Q2.6> |
| 67 |
Q2.6*: I can't install properly on my linux-2.0.0 from Slackware 96. |
| 68 |
</a> |
| 69 |
<dt><a href=#Q2.7> |
| 70 |
Q2.7+: How to install awedrv on my FreeBSD kernel? |
| 71 |
</a> |
| 72 |
<dt><a href=#Q2.8> |
| 73 |
Q2.8+: How to use my PnP card on FreeBSD system? |
| 74 |
</a> |
| 75 |
</dl> |
| 76 |
|
| 77 |
<dt><a href=#Q3> |
| 78 |
3. PLAYING MIDI FILES |
| 79 |
</a> |
| 80 |
<dl> |
| 81 |
<dt><a href=#Q3.1> |
| 82 |
Q3.1: I can't hear anything using drvmidi or playmidi. Why? |
| 83 |
</a> |
| 84 |
<dt><a href=#Q3.2> |
| 85 |
Q3.2: I have no DRAM in my card - can I still play midi files with it? |
| 86 |
</a> |
| 87 |
<dt><a href=#Q3.3> |
| 88 |
Q3.3: How can I play midi files using the default ROM fonts that come with |
| 89 |
my card? |
| 90 |
</a> |
| 91 |
<dt><a href=#Q3.4> |
| 92 |
Q3.4: I have a midi file with a specified SBK file. How can I listen to |
| 93 |
it? |
| 94 |
</a> |
| 95 |
<dt><a href=#Q3.5> |
| 96 |
Q3.5: Drvmidi plays strange sounds when I use an addtional SoundFont file. |
| 97 |
</a> |
| 98 |
<dt><a href=#Q3.6> |
| 99 |
Q3.6: I changed chorus and reverb modes using drvmidi, but nothing |
| 100 |
changed. Why? |
| 101 |
</a> |
| 102 |
<dt><a href=#Q3.7> |
| 103 |
Q3.7: Many clicking noises can be heard in some midi files. |
| 104 |
</a> |
| 105 |
<dt><a href=#Q3.8> |
| 106 |
Q3.8: Sounds are too loud! |
| 107 |
</a> |
| 108 |
<dt><a href=#Q3.9> |
| 109 |
Q3.9: I have GUS patch files. Can I use these samples? |
| 110 |
</a> |
| 111 |
<dt><a href=#Q3.10> |
| 112 |
Q3.10: A strange piano sound is heard instead of drum (or other) sounds. |
| 113 |
</a> |
| 114 |
<dt><a href=#Q3.11> |
| 115 |
Q3.11: Drum sounds seem smaller than Windows sound. |
| 116 |
</a> |
| 117 |
<dt><a href=#Q3.12> |
| 118 |
Q3.12: What is "dynamic loading" of drvmidi? |
| 119 |
/a> |
| 120 |
<dt><a href=#Q3.13> |
| 121 |
Q3.13: I want to set up default options. |
| 122 |
</a> |
| 123 |
<dt><a href=#Q3.14> |
| 124 |
Q3.14: Can I play a GS midi file for Roland SC88? |
| 125 |
</a> |
| 126 |
<dt><a href=#Q3.15> |
| 127 |
Q3.15: Can I play a midi file with Yamaha XG format? |
| 128 |
</a> |
| 129 |
<dt><a href=#Q3.16> |
| 130 |
Q3.16: The tone of ver.0.4.3 seems different from others.. |
| 131 |
</a> |
| 132 |
<dt><a href=#Q3.17> |
| 133 |
Q3.17: What is a virtual bank file? |
| 134 |
</a> |
| 135 |
</dl> |
| 136 |
|
| 137 |
<dt><a href=#Q4> |
| 138 |
4. PROGRAMMING & MISCELLANEOUS |
| 139 |
</a> |
| 140 |
<dl> |
| 141 |
<dt><a href=#Q4.1> |
| 142 |
Q4.1: The sounds of module player are very weird. Why? |
| 143 |
</a> |
| 144 |
<dt><a href=#Q4.2> |
| 145 |
Q4.2*: How can MIDI files be played from Netscape? |
| 146 |
</a> |
| 147 |
<dt><a href=#Q4.3> |
| 148 |
Q4.3: I'm planning to write a music player for AWE32. How can I control |
| 149 |
the AWE32 driver from my program? |
| 150 |
</a> |
| 151 |
</dl> |
| 152 |
|
| 153 |
</dl> |
| 154 |
The questions with asterisk(*) indicate the Linux specific problems. |
| 155 |
The questions with plus(+) indicate the FreeBSD specific problems. |
| 156 |
The minus(-) indicates the obsolete questions spefic for v0.3 or older driver. |
| 157 |
<p> |
| 158 |
|
| 159 |
<!----------------------------------------------------------------> |
| 160 |
|
| 161 |
<p><hr size=10><p> |
| 162 |
|
| 163 |
<h2><a name=Q1> |
| 164 |
1. GENERAL NOTES |
| 165 |
</h2> |
| 166 |
|
| 167 |
<h3><a name=Q1.1> |
| 168 |
Q1.1: What is awedrv? What can I do with this? |
| 169 |
</h3><p> |
| 170 |
|
| 171 |
Awedrv is the sound driver extension to OSS/Free (aka USS-Lite or VoxWare) |
| 172 |
for AWE32 and its compatible wave synthesizer cards (SB32 and AWE64 series) by |
| 173 |
CreativeLabs. |
| 174 |
This driver provides a basic way to control Emu8000 chip on AWE32 |
| 175 |
board through <code>/dev/sequencer</code> and <code>/dev/sequencer2</code> |
| 176 |
devices as well as other |
| 177 |
synth drivers like FM-OPL3 and GUS wave drivers. |
| 178 |
Also from driver v0.3, awedrv behaves as a GUS compatible driver, too. |
| 179 |
(The module players use this feature.) |
| 180 |
You can play midi and module files using some sequencer programs |
| 181 |
listed below. |
| 182 |
<p> |
| 183 |
|
| 184 |
The current driver is distributed both as a lowlevel driver to |
| 185 |
OSS/Free with Linux 2.1.x, 2.0.x kernels, and as a patch to OSS/Free-3.0.x |
| 186 |
(aka VoxWare) with Linux 1.2.x kernels and FreeBSD. |
| 187 |
Both environments are confirmed to work fine. |
| 188 |
However a little attention is necessary to use this driver on PnP cards. |
| 189 |
See <a href=#Q2.3>Q2.3</a>, <a href=#Q2.4>Q2.4</a> and |
| 190 |
<a href=#Q2.8>Q2.8</a> for installation on PnP cards. |
| 191 |
<p> |
| 192 |
|
| 193 |
The programs supporting awedrv are: |
| 194 |
<ul> |
| 195 |
<li> MIDI Sequencers |
| 196 |
<ul> |
| 197 |
<li> <a href=http://bahamut.mm.t.u-tokyo.ac.jp/~awedrv/#MIDI>drvmidi</a>, |
| 198 |
MIDI player program (<code>awemidi-0.4.x.tar</code>) |
| 199 |
<li> <a href=http://playmidi.openprojects.net/>playmidi</a>, |
| 200 |
supported officially from v2.4 |
| 201 |
<li> <b>Jazz</b> works without any patch (but not perfectly yet) |
| 202 |
<li> <b>Rosegarden</b> works using MIDI emulation device on awedrv-v0.4.3. |
| 203 |
</ul> |
| 204 |
<li> Games |
| 205 |
<ul> |
| 206 |
<li> <a href=http://bahamut.mm.t.u-tokyo.ac.jp/~awedrv/#Others>DOOM musserver</a> with a patch file |
| 207 |
(<code>musserver+awe0.4.diff</code>) |
| 208 |
</ul> |
| 209 |
<li> Module Players |
| 210 |
<ul> |
| 211 |
<li> <a href=http://puma.inf.ufpr.br/~claudio/xmp/>xmp</a>, |
| 212 |
officially supporting the AWE driver. |
| 213 |
<li> <a href=http://www.nyx.net/~arobinso/xgmod.html>gmod</a>, |
| 214 |
module player (supporting AWEDRV officially from v3.1) |
| 215 |
</ul> |
| 216 |
<li> Others |
| 217 |
<ul> |
| 218 |
<li> <a href=http://bahamut.mm.t.u-tokyo.ac.jp/~awedrv/#Others>Netscape 3.0 MIDI Plug-in</a> |
| 219 |
<li> <a href=http://bahamut.mm.t.u-tokyo.ac.jp/~awedrv/#Sequencers>vkbd</a>, |
| 220 |
a virtual keyboard on X |
| 221 |
<li> <a href=http://www.interlog.com/~gray/groove.html>super groove</a>, |
| 222 |
a unique sequencer program |
| 223 |
<li> <a href=http://www.wi.leidenuniv.nl/home/jwittema/awe/awe.html>AWEWavePlayer</a>, |
| 224 |
playing wave samples through Emu8000 |
| 225 |
<li> <a href=http://www.floot.demon.co.uk/sfvbm/index.html>SFVbm</a>, |
| 226 |
the soundfont and virtual bank manager |
| 227 |
</ul> |
| 228 |
</ul> |
| 229 |
<p> |
| 230 |
|
| 231 |
<p><hr><p> |
| 232 |
|
| 233 |
<h3><a name=Q1.2> |
| 234 |
Q1.2: From where can I download AWE32 sound driver for Linux and FreeBSD? |
| 235 |
</h3><p> |
| 236 |
|
| 237 |
You can download from my web page: |
| 238 |
<center> |
| 239 |
<a href=http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/index.html> |
| 240 |
<i>http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/index.html</i></a> |
| 241 |
</center> |
| 242 |
<p> |
| 243 |
|
| 244 |
Also the following mirroring sites are available: |
| 245 |
<ul> |
| 246 |
<li> UK - Linux Sources - |
| 247 |
(<a href=http://www.lpsg.demon.co.uk/awe32.html> |
| 248 |
<i>http://www.lpsg.demon.co.uk/awe32.html</i></a>) |
| 249 |
<li> Brasil - Mirror of this page - |
| 250 |
(<a href=http://www.brasil.enemy.org/~claudio/awedrv> |
| 251 |
<i>http://www.brasil.enemy.org/~claudio/awedrv</i></a>) |
| 252 |
<li> Free BSD port - |
| 253 |
(<a href=http://multiverse.com/~rhh/awedrv/> |
| 254 |
<i>http://multiverse.com/~rhh/awedrv/</i></a>) |
| 255 |
</ul> |
| 256 |
<p> |
| 257 |
|
| 258 |
<p><hr><p> |
| 259 |
|
| 260 |
<h3><a name=Q1.3> |
| 261 |
Q1.3: Does awedrv work on my AWE64 card? |
| 262 |
</h3><p> |
| 263 |
|
| 264 |
Yes. It works as a AWE32 compatible driver, but the software synthesizer |
| 265 |
is not supported. So only 32 voices (30 voices when DRAM is on board) |
| 266 |
are available. |
| 267 |
<p> |
| 268 |
|
| 269 |
<p><hr><p> |
| 270 |
|
| 271 |
<h3><a name=Q1.4> |
| 272 |
Q1.4: How can I play my midi files using awe driver? What configuration is necessary? |
| 273 |
</h3><p> |
| 274 |
|
| 275 |
To play a sound using awedrv, you need awesfx utility to load samples on the driver, |
| 276 |
and midi player programs which support awedrv. |
| 277 |
Basically, awedrv doesn't have any sound information in it at beginning. |
| 278 |
So, users must prepare their own SoundFont files |
| 279 |
using sfxload program (included in awesfx utils). |
| 280 |
This procedure is necessary even for ROM sounds |
| 281 |
(see <a href=#Q3.3>Q3.3</a>). |
| 282 |
Awesfx utility can be downloaded also from the web site above |
| 283 |
(<a href=#Q1.2>Q1.2</a>). |
| 284 |
<p> |
| 285 |
|
| 286 |
To load the SoundFont file onto the AWE driver, |
| 287 |
use sfxload utility. |
| 288 |
For example, to load your GM SoundFont file <code>synthgm.sbk</code>, |
| 289 |
<pre> |
| 290 |
% sfxload synthgm |
| 291 |
</pre> |
| 292 |
Note: when you're using the older version of driver and utilities |
| 293 |
than ver.0.4, the additional option '<code>-i</code>' is required. |
| 294 |
This option means to remove all samples on the driver |
| 295 |
before loading this sample. |
| 296 |
<p> |
| 297 |
|
| 298 |
Now you can hear your midi files by a midi player like |
| 299 |
drvmidi (distributed in awemidi package). |
| 300 |
<pre> |
| 301 |
% drvmidi sample.mid |
| 302 |
</pre> |
| 303 |
See <a href=#Q3.4>Q3.4</a> to how to use specified SBK or SF2 files |
| 304 |
with a midi file. |
| 305 |
<p> |
| 306 |
|
| 307 |
The new drvmidi (v0.4.0) has a function of "dynamic loaindg" of samples |
| 308 |
on demand. This enables to play most of MIDI files with 2MB GM/GS soundfonts |
| 309 |
on only 512kB DRAM soundcards. |
| 310 |
<pre> |
| 311 |
% drvmidi -L 2mbgmgs sample.mid |
| 312 |
</pre> |
| 313 |
See <a href=#Q3.12>Q3.12</a> and <a href=#Q3.13>Q3.13</a> for details. |
| 314 |
<p> |
| 315 |
|
| 316 |
<p><hr><p> |
| 317 |
|
| 318 |
<h3><a name=Q1.5> |
| 319 |
Q1.5: How can I play my .MOD files using awe driver? What configuration is necessary? |
| 320 |
</h3><p> |
| 321 |
|
| 322 |
So far, some module players are available (see <a href=#Q1.1>Q1.1</a>). |
| 323 |
Both xmp and gmod support awedrv as default. |
| 324 |
See the installation instruction for more details. |
| 325 |
<p> |
| 326 |
|
| 327 |
Note: both programs watches read selection of the sequencer device. |
| 328 |
To support this, |
| 329 |
you need to activate MIDI input interface on SB16 driver |
| 330 |
when configuring the sound module. |
| 331 |
<p> |
| 332 |
|
| 333 |
<!----------------------------------------------------------------> |
| 334 |
|
| 335 |
<p><hr size=10><p> |
| 336 |
|
| 337 |
<h2><a name=Q2> |
| 338 |
2. INSTLLATION |
| 339 |
</h2><p> |
| 340 |
|
| 341 |
<h3><a name=Q1.6> |
| 342 |
Q2.1*: How to install awedrv on my linux kernel? |
| 343 |
</h3><p> |
| 344 |
|
| 345 |
See <code>INSTALL.awe</code> file in awedrv source package for details. |
| 346 |
Basically, you only need to run <code>install.sh</code> script |
| 347 |
on the awedrv source directory as root user. |
| 348 |
<pre> |
| 349 |
% su |
| 350 |
# sh ./install.sh |
| 351 |
</pre> |
| 352 |
Then, reconfigure the kernel options. |
| 353 |
See <a href=#Q2.2>Q2.2</a> about which options to be set. |
| 354 |
<pre> |
| 355 |
# cd /usr/src/linux |
| 356 |
# make xconfig |
| 357 |
<i>or</i> |
| 358 |
# make menuconfig |
| 359 |
</pre> |
| 360 |
Now, remake and install the kernel and modules. |
| 361 |
<pre> |
| 362 |
# make |
| 363 |
# make modules; make modules_install |
| 364 |
</pre> |
| 365 |
<p> |
| 366 |
|
| 367 |
<p><hr><p> |
| 368 |
|
| 369 |
<h3><a name=Q2.2> |
| 370 |
Q2.2*: What options should be set to configure sound module for AWE32 on linux? |
| 371 |
</h3><p> |
| 372 |
|
| 373 |
Basically, to configure awedrv, say <i>Yes</i> only to |
| 374 |
"lowlevel sound driver support" and "AWE32 wave synth". |
| 375 |
(If you're using OSS/Free-3.0.x (aka VoxWare), only the latter question will appear.) |
| 376 |
On AWE32 board, all transfers are done through I/O ports (not DMA), |
| 377 |
and awedrv probes these I/O ports automatically, so no need to specify |
| 378 |
any address or IRQ at configuration. |
| 379 |
<p> |
| 380 |
|
| 381 |
Of course, you may want other functions of SoundBlaster |
| 382 |
like playing and recording digital sound, FM synthesizer, and mixer support. |
| 383 |
Awedrv is only an enhancement to control Emu8000 synthesizer, and |
| 384 |
such functions are supported by other SB drivers. |
| 385 |
So better to keep <i>Yes</i> for all other SB16 options as well. |
| 386 |
<p> |
| 387 |
|
| 388 |
In my case, the sound part of <code>.config</code> file looks like: |
| 389 |
<pre> |
| 390 |
# |
| 391 |
# Sound |
| 392 |
# |
| 393 |
CONFIG_SOUND=m |
| 394 |
# CONFIG_PAS is not set |
| 395 |
CONFIG_SB=y |
| 396 |
CONFIG_ADLIB=y |
| 397 |
# CONFIG_GUS is not set |
| 398 |
# CONFIG_MPU401 is not set |
| 399 |
# CONFIG_UART6850 is not set |
| 400 |
# CONFIG_PSS is not set |
| 401 |
# CONFIG_GUS16 is not set |
| 402 |
# CONFIG_GUSMAX is not set |
| 403 |
# CONFIG_MSS is not set |
| 404 |
# CONFIG_SSCAPE is not set |
| 405 |
# CONFIG_TRIX is not set |
| 406 |
# CONFIG_MAD16 is not set |
| 407 |
# CONFIG_CS4232 is not set |
| 408 |
# CONFIG_MAUI is not set |
| 409 |
CONFIG_AUDIO=y |
| 410 |
CONFIG_MIDI=y |
| 411 |
CONFIG_YM3812=y |
| 412 |
SBC_BASE=220 |
| 413 |
SBC_IRQ=7 |
| 414 |
SBC_DMA=1 |
| 415 |
SB_DMA2=7 |
| 416 |
SB_MPU_BASE=300 |
| 417 |
SB_MPU_IRQ=-1 |
| 418 |
DSP_BUFFSIZE=65536 |
| 419 |
CONFIG_LOWLEVEL_SOUND=y |
| 420 |
# CONFIG_ACI_MIXER is not set |
| 421 |
CONFIG_AWE32_SYNTH=y |
| 422 |
</pre> |
| 423 |
<p> |
| 424 |
|
| 425 |
BTW, please do not copy these values directly to your kernel. |
| 426 |
IRQ and DMA numbers of SB card may be different on each machine. |
| 427 |
In usual cases, MPU base address may be 0x330. I set this value as different |
| 428 |
one to avoid confliction between SCSI card. |
| 429 |
(The setting in <a href=#Q2.3>Q2.3</a> is 0x330 because this is Neal's machine.) |
| 430 |
<p> |
| 431 |
|
| 432 |
<p><hr><p> |
| 433 |
|
| 434 |
<h3><a name=Q2.3> |
| 435 |
Q2.3*: The linux sound driver can't detect my SB32-PnP card. Why? |
| 436 |
</h3><p> |
| 437 |
|
| 438 |
This is a problem in PnP initialization. |
| 439 |
Because the original Linux kernels don't support initialization of PnP cards yet, |
| 440 |
some special treatment is necessary before loading sound driver. |
| 441 |
There're a couple of ways to solve this: |
| 442 |
<ol> |
| 443 |
<li>use Linux PnP driver |
| 444 |
<li>use PnP utilities like ISA PnP Tools. |
| 445 |
<li>initialize PnP card on DOS and use <code>loadlin</code> to boot linux. |
| 446 |
</ol> |
| 447 |
<p> |
| 448 |
|
| 449 |
The Linux PnP driver enables to configure the PnP devices from kernel. |
| 450 |
This driver has been originally developed by Tom Lees. |
| 451 |
The current awedrv (0.4.3) includes the PnP driver interface so that |
| 452 |
no patch is necessary. |
| 453 |
See the PnP driver project homepage for more details, |
| 454 |
<center> |
| 455 |
<a href=http://www-jcr.lmh.ox.ac.uk/~pnp/> |
| 456 |
<i>http://www-jcr.lmh.ox.ac.uk/~pnp/</i></a> |
| 457 |
</center> |
| 458 |
<p> |
| 459 |
|
| 460 |
Neal Sanche (<i>[email protected]</i>) summarizes the procedure to |
| 461 |
install on PnP card by ISAPnP tool that: |
| 462 |
<p> |
| 463 |
|
| 464 |
<h4>Setting up SoundBlaster 32 PnP under Linux</h4> |
| 465 |
|
| 466 |
The SoundBlaster 32 PnP, like all plug and play devices, requires |
| 467 |
initialization before the Linux device driver is loaded in order to |
| 468 |
function properly. This means that some form of initialization is |
| 469 |
required to hear sound. Currently many PnP projects (one at |
| 470 |
<a href=http://www.redhat.com/linux-info/pnp> |
| 471 |
<i>http://www.redhat.com/linux-info/pnp</i></a>) are being developed. |
| 472 |
I use a simple tool called ISAPnP. It is available at: |
| 473 |
<center><a href=http://www.redhat.com/linux-info/pnp/other.html> |
| 474 |
<i>http://www.redhat.com/linux-info/pnp/other.html</i> |
| 475 |
</a></center> |
| 476 |
<p> |
| 477 |
|
| 478 |
The steps you need to do in order to get sound working: |
| 479 |
<ol> |
| 480 |
<li> Compile your Linux kernel with module support, and compile the |
| 481 |
sound driver as a module. This is important because you must load |
| 482 |
the module <i>after</i> initializing your PnP card under Linux. |
| 483 |
|
| 484 |
<li> Somewhere in your startup scripts (in <code>rc.local</code>, or |
| 485 |
<code>rc.modules</code> in |
| 486 |
a recent version of RedHat) you must initialize your sound card |
| 487 |
with some tool. ISAPnP is easy to configure and seems very reliable. |
| 488 |
|
| 489 |
<li> Load the sound module. Set your mixer settings. |
| 490 |
</ol> |
| 491 |
<p> |
| 492 |
|
| 493 |
For example, this is how I initialize the SB32 PnP in my startup |
| 494 |
scripts. |
| 495 |
<pre> |
| 496 |
#!/bin/sh |
| 497 |
|
| 498 |
# initialize PnP devices |
| 499 |
if [ -x /sbin/isapnp ]; then |
| 500 |
echo "Configuring PnP devices" |
| 501 |
/sbin/isapnp /etc/isapnp.conf |
| 502 |
fi |
| 503 |
|
| 504 |
echo "Loading sound module" |
| 505 |
/sbin/modprobe -a sound |
| 506 |
</pre> |
| 507 |
<p> |
| 508 |
|
| 509 |
ISAPnP is quite an easy program to configure. Here is a copy of my |
| 510 |
<code>isapnp.conf</code> file. I used all of the defaults (from the SB manual) |
| 511 |
for ports and IRQ settings.<br> |
| 512 |
<b>DON'T FORGET TO ADD TWO I/O PORTS, 0xA20 and 0xe20, for WaveTable! |
| 513 |
These ports are never detected by pnpdump, but must be initialized. |
| 514 |
(See <a href=#Q2.4>Q2.4</a>) |
| 515 |
</b> |
| 516 |
<pre> |
| 517 |
(READPORT 0x0273) |
| 518 |
(ISOLATE) |
| 519 |
(IDENTIFY *) |
| 520 |
|
| 521 |
# Card 1: (serial identifier 6d 00 0e b0 52 44 00 8c 0e) |
| 522 |
# CTL0044 Serial No 962642 [checksum 6d] |
| 523 |
# Version 1.0, Vendor version 1.0 |
| 524 |
# ANSI string -->Creative SB32 PnP<-- |
| 525 |
# |
| 526 |
# Logical device id CTL0031 |
| 527 |
# |
| 528 |
# Edit the entries below to uncomment out the configuration required. |
| 529 |
# Note that only the first value of any range is given, this may be changed if required |
| 530 |
# Don't forget to uncomment the activate (ACT Y) when happy |
| 531 |
|
| 532 |
(CONFIGURE CTL0044/962642 (LD 0 |
| 533 |
# ANSI string -->Audio<-- |
| 534 |
(INT 0 (IRQ 5 (MODE +E))) |
| 535 |
(DMA 0 (CHANNEL 1)) |
| 536 |
(DMA 1 (CHANNEL 5)) |
| 537 |
(IO 0 (BASE 0x0220)) |
| 538 |
(IO 1 (BASE 0x0330)) |
| 539 |
(IO 2 (BASE 0x0388)) |
| 540 |
|
| 541 |
(ACT Y) |
| 542 |
)) |
| 543 |
|
| 544 |
# Logical device id CTL0021 |
| 545 |
# |
| 546 |
# Edit the entries below to uncomment out the configuration required. |
| 547 |
# Note that only the first value of any range is given, this may be changed if required |
| 548 |
# Don't forget to uncomment the activate (ACT Y) when happy |
| 549 |
|
| 550 |
(CONFIGURE CTL0044/962642 (LD 2 |
| 551 |
# ANSI string -->WaveTable<-- |
| 552 |
(IO 0 (BASE 0x0620)) |
| 553 |
(IO 1 (BASE 0x0a20)) |
| 554 |
(IO 2 (BASE 0x0e20)) |
| 555 |
(ACT Y) |
| 556 |
)) |
| 557 |
|
| 558 |
# Logical device id CTL7001 |
| 559 |
# |
| 560 |
# Edit the entries below to uncomment out the configuration required. |
| 561 |
# Note that only the first value of any range is given, this may be changed if required |
| 562 |
# Don't forget to uncomment the activate (ACT Y) when happy |
| 563 |
|
| 564 |
(CONFIGURE CTL0044/962642 (LD 3 |
| 565 |
# Compatible device id PNPb02f |
| 566 |
# ANSI string -->Game<-- |
| 567 |
# Logical device decodes 16 bit IO address lines |
| 568 |
# Minimum IO base address 0x0200 |
| 569 |
# Maximum IO base address 0x0200 |
| 570 |
# IO base alignment 1 bytes |
| 571 |
# Number of IO addresses required: 8 |
| 572 |
# (IO 0 (BASE 0x0200)) |
| 573 |
# (ACT Y) |
| 574 |
)) |
| 575 |
|
| 576 |
# Logical device id CTL0051 |
| 577 |
# |
| 578 |
# Edit the entries below to uncomment out the configuration required. |
| 579 |
# Note that only the first value of any range is given, this may be changed if required |
| 580 |
# Don't forget to uncomment the activate (ACT Y) when happy |
| 581 |
|
| 582 |
(CONFIGURE CTL0044/962642 (LD 4 |
| 583 |
# ANSI string -->StereoEnhance<-- |
| 584 |
# Logical device decodes 16 bit IO address lines |
| 585 |
# Minimum IO base address 0x0100 |
| 586 |
# Maximum IO base address 0x03f8 |
| 587 |
# IO base alignment 8 bytes |
| 588 |
# Number of IO addresses required: 1 |
| 589 |
(IO 0 (BASE 0x0108)) |
| 590 |
(ACT Y))) |
| 591 |
</pre> |
| 592 |
<p> |
| 593 |
|
| 594 |
That's all there is to it. In the future, the Linux kernel source will |
| 595 |
directory support Plug and Play, and there will be no need for the |
| 596 |
isapnp tool. |
| 597 |
<p> |
| 598 |
|
| 599 |
<p><hr><p> |
| 600 |
<h3><a name=Q2.4> |
| 601 |
Q2.4*: I installed ISA PnP tools, but still awedrv says "can't detect AWE32". |
| 602 |
</h3><p> |
| 603 |
|
| 604 |
Check WaveTable entries in your <code>/etc/isapnp.conf</code> file. |
| 605 |
AWE32 uses three I/O ports, normally 0x620, 0xa20, and 0xe20, |
| 606 |
but in the default ouput from <code>pnpdump</code> is |
| 607 |
lack of the last two pots (0xa20 and 0xe20). |
| 608 |
In such a case, you have to add them manually. For example, |
| 609 |
<pre> |
| 610 |
# Logical device id CTL0021 |
| 611 |
(CONFIGURE CTL0044/962642 (LD 2 |
| 612 |
# ANSI string -->WaveTable<-- |
| 613 |
(IO 0 (BASE 0x0620)) |
| 614 |
(IO 1 (BASE 0x0A20)) |
| 615 |
(IO 2 (BASE 0x0E20)) |
| 616 |
(ACT Y) |
| 617 |
)) |
| 618 |
</pre> |
| 619 |
<p> |
| 620 |
|
| 621 |
See the ISA PnP FAQ page |
| 622 |
(<a href=http://www.roestock.demon.co.uk/isapnptools/isapnpfaq.html> |
| 623 |
<i>http://www.roestock.demon.co.uk/isapnptools/isapnpfaq.html</i> |
| 624 |
</a>) |
| 625 |
for details. |
| 626 |
<p> |
| 627 |
|
| 628 |
<p><hr><p> |
| 629 |
|
| 630 |
<h3><a name=Q2.5> |
| 631 |
Q2.5*: Can I load my GM file automatically on the sound driver module? |
| 632 |
</h3><p> |
| 633 |
|
| 634 |
Yes. You can specify the command to be executed after loading modules |
| 635 |
in your <code>/etc/conf.modules</code> file with <code>post-install</code> |
| 636 |
command. |
| 637 |
For example, |
| 638 |
<pre> |
| 639 |
post-install sound /usr/local/bin/sfxload synthgm |
| 640 |
</pre> |
| 641 |
Similary, it's possible to set the mixer volume automatically, |
| 642 |
<pre> |
| 643 |
post-install sound /usr/local/bin/setmix -f /etc/mixrc;\ |
| 644 |
/usr/local/bin/sfxload synthgm |
| 645 |
</pre> |
| 646 |
<p> |
| 647 |
|
| 648 |
<p><hr><p> |
| 649 |
|
| 650 |
<h3><a name=Q2.6> |
| 651 |
Q2.6*: I can't install properly on my linux-2.0.0 from Slackware 96. |
| 652 |
</h3><p> |
| 653 |
|
| 654 |
Slackware 96 initially installs Linux-2.0.0 system. |
| 655 |
The AWE driver doesn't support this version of sound driver. |
| 656 |
So please update the kernel version to the newer one. |
| 657 |
Sorry for incovenience... |
| 658 |
<p> |
| 659 |
|
| 660 |
<p><hr><p> |
| 661 |
|
| 662 |
<h3><a name=Q2.7> |
| 663 |
Q2.7+: How to install awedrv on my FreeBSD kernel? |
| 664 |
</h3><p> |
| 665 |
|
| 666 |
See the document <code>INSTALL.frbsd</code> in awedrv source package |
| 667 |
for details. |
| 668 |
Also, if you're using a PnP sound card like SB32 PnP or AWE64, |
| 669 |
refer to <a href=#Q2.8>Q2.8</a>. |
| 670 |
<p> |
| 671 |
|
| 672 |
<ol> |
| 673 |
<li> Copy all source files to the system directory |
| 674 |
<code>/usr/src/sys/i386/isa/sound</code>. |
| 675 |
<li> Edit <code>awe_config.h</code> if necessary.<br> |
| 676 |
If you're using awedrv ver.0.4 or newer, |
| 677 |
you don't need to touch <code>AWE_MAX_SAMPLES</code> and |
| 678 |
<code>AWE_MAX_INFOS</code>. |
| 679 |
<li> Append an entry to kernel configuration file. |
| 680 |
<pre> |
| 681 |
device awe0 at isa? port 0x620 |
| 682 |
</pre> |
| 683 |
<li> Recompile and install a new kernel. |
| 684 |
</ol> |
| 685 |
<p> |
| 686 |
|
| 687 |
<p><hr><p> |
| 688 |
|
| 689 |
<h3><a name=Q2.8> |
| 690 |
Q2.8+: How to use my PnP card on FreeBSD system? |
| 691 |
</h3><p> |
| 692 |
|
| 693 |
See the how-to document by Takuya Koumoto (<i>[email protected]</i>) |
| 694 |
for more details (written in Japanese). |
| 695 |
<p> |
| 696 |
|
| 697 |
<ol> |
| 698 |
<li> Get FreeBSD PnP package |
| 699 |
(<code>FreeBSD-ISA_PnP_June8.tar.gz</code>) |
| 700 |
<li> Run a program <code>pnpinfo</code> in it. |
| 701 |
You may have an output like following: |
| 702 |
<pre> |
| 703 |
Checking for Plug-n-Play devices... |
| 704 |
Trying Read_Port at 203 |
| 705 |
Trying Read_Port at 243 |
| 706 |
.. (snip) .. |
| 707 |
Card assigned CSN #1 |
| 708 |
Board Vendor ID: CTL009d |
| 709 |
Board Serial Number: 10005fdc |
| 710 |
PnP Version: 1.0 |
| 711 |
Vendor Version: 32 |
| 712 |
Device Description: Creative SB AWE64 PnP |
| 713 |
Logical Device ID: CTL0042 (42008c0e) |
| 714 |
Device Description: Audio |
| 715 |
Start Dependent Function |
| 716 |
.. (snip) .. |
| 717 |
</pre> |
| 718 |
Remember the serial number of your sound card in the message. |
| 719 |
In this example, it's <code>10005fdc</code>. This value must be different |
| 720 |
on each sound card. |
| 721 |
<li> Applay a patch (<code>kernel.patch.2.2-current</code>) included in |
| 722 |
the package to kernel source tree. |
| 723 |
<pre> |
| 724 |
# cd /usr/src/sys |
| 725 |
# patch -p0 < kernel.patch.2.2-current |
| 726 |
</pre> |
| 727 |
<li> Edit <code>/usr/src/sys/i386/isa/pnp.c</code>:<br> |
| 728 |
Replace the line 34 |
| 729 |
<pre> |
| 730 |
#include "pnp.h" |
| 731 |
</pre> |
| 732 |
with |
| 733 |
<pre> |
| 734 |
#include "i386/isa/pnp.h" |
| 735 |
</pre> |
| 736 |
and the part from line 50 to 103 with the following |
| 737 |
<pre> |
| 738 |
{ |
| 739 |
0x10005fdc, /* Serial Number */ |
| 740 |
2, /* Logical Device Number */ |
| 741 |
{ |
| 742 |
{ -1, -1 }, /* Primary IRQ Number, Type */ |
| 743 |
{ -1, -1 } /* Second IRQ Number, Type */ |
| 744 |
}, |
| 745 |
{ -1, -1 }, /* DRQ Number */ |
| 746 |
{ |
| 747 |
0x620, /* Ports 1 */ |
| 748 |
0xa20, /* Ports 2 */ |
| 749 |
0xe20, /* Ports 3 */ |
| 750 |
-1, /* Ports 4 */ |
| 751 |
-1, /* Ports 5 */ |
| 752 |
-1, /* Ports 6 */ |
| 753 |
-1, /* Ports 7 */ |
| 754 |
-1, /* Ports 8 */ |
| 755 |
}, |
| 756 |
{ |
| 757 |
{ -1, -1, -1 }, /* Memory desc0 - base, ctrl, range */ |
| 758 |
{ -1, -1, -1 }, /* Memory desc1 - base, ctrl, range */ |
| 759 |
{ -1, -1, -1 }, /* Memory desc2 - base, ctrl, range */ |
| 760 |
{ -1, -1, -1 } /* Memory desc3 - base, ctrl, range */ |
| 761 |
} |
| 762 |
} |
| 763 |
</pre> |
| 764 |
Please put the serial number of your card on the first item. |
| 765 |
<li> Copy source files of awedrv. |
| 766 |
Do it as well as in <a href=#Q2.7>Q2.7</a>. |
| 767 |
<li> Edit kernel config file. |
| 768 |
Append both |
| 769 |
<pre> |
| 770 |
controller pnp0 |
| 771 |
</pre> |
| 772 |
and |
| 773 |
<pre> |
| 774 |
device awe0 at isa? port 0x620 conflicts |
| 775 |
</pre> |
| 776 |
</ol> |
| 777 |
<p> |
| 778 |
|
| 779 |
<!----------------------------------------------------------------> |
| 780 |
|
| 781 |
<p><hr size=10><p> |
| 782 |
|
| 783 |
<h2><a name=Q2> |
| 784 |
3. PLAYING MIDI FILES |
| 785 |
</h2><p> |
| 786 |
|
| 787 |
<h3><a name=Q3.1> |
| 788 |
Q3.1: I can't hear anything using drvmidi or playmidi. Why? |
| 789 |
</h3><p> |
| 790 |
|
| 791 |
The AWE driver itself doesn't have any sound information in it. |
| 792 |
You need to load the soundfont file at first. |
| 793 |
See <a href=#Q1.4>Q1.4</a> how to load soundfont files. |
| 794 |
<p> |
| 795 |
|
| 796 |
<p><hr><p> |
| 797 |
|
| 798 |
<h3><a name=Q3.2> |
| 799 |
Q3.2: I have no DRAM in my card - can I still play midi files with it? |
| 800 |
</h3><p> |
| 801 |
|
| 802 |
<i>Chris Wedgwood <[email protected]> answers:</i><p> |
| 803 |
|
| 804 |
Yes. You can use the default ROM fonts that are built into the card. |
| 805 |
However, it won't necessarily sound very good. |
| 806 |
<p> |
| 807 |
|
| 808 |
<p><hr><p> |
| 809 |
|
| 810 |
<h3><a name=Q3.3> |
| 811 |
Q3.3: How can I play midi files using the default ROM fonts that come with |
| 812 |
my card? |
| 813 |
</h3><p> |
| 814 |
|
| 815 |
<i>Chris Wedgwood <[email protected]> answers:</i><p> |
| 816 |
|
| 817 |
You have to load the ROM fonts into the card using sfxload. |
| 818 |
To do this you need a file called '<code>synthgm.sbk</code>' |
| 819 |
(or <code>synthgm.sf2</code>) which is installed under Windows95 |
| 820 |
and presumably Windows 3.1. |
| 821 |
<p> |
| 822 |
|
| 823 |
There always seems to be a copy in the 'windows system' |
| 824 |
directory, and often another copy amongst the other installed Creative Labs files. The windows system directory is usually <code>\WINDOWS\SYSTEM</code>. |
| 825 |
<p> |
| 826 |
|
| 827 |
For the 'purists' who don't have Windows installed - you will probably |
| 828 |
have to try and get this file from elsewhere, as it is not stored on the |
| 829 |
CDROM in any useful form. (At least not on mine). It appears to be |
| 830 |
archive in the <code>win95/sfbank/sfbank.lib</code> file |
| 831 |
- but I have no details on the format of this). |
| 832 |
<p> |
| 833 |
|
| 834 |
To load the ROM fonts type: |
| 835 |
<pre> |
| 836 |
% sfxload synthgm.sbk |
| 837 |
</pre> |
| 838 |
|
| 839 |
Note: you will have to prepend a path if <code>synthgm.sbk</code> |
| 840 |
is not in the current working directory or search path directories. |
| 841 |
If drum sounds are small, you can tune it via <code>-A</code> option |
| 842 |
(see <a href=#Q3.11>Q3.11</a>). |
| 843 |
<p> |
| 844 |
|
| 845 |
The size of the file is about 35k, it compresses down to about 14k, so |
| 846 |
obtaining it via FTP or email shouldn't be a big problem - although there |
| 847 |
maybe copyright issues involved. I wouldn't know, I'm not a lawyer. |
| 848 |
<p> |
| 849 |
|
| 850 |
<p><hr><p> |
| 851 |
|
| 852 |
<h3><a name=Q3.4> |
| 853 |
Q3.4: I have a midi file with a specified SBK file. How can I listen to |
| 854 |
it? |
| 855 |
</h3><p> |
| 856 |
|
| 857 |
Just load the SBK file after GM (or GS) presets. |
| 858 |
At first, load GM font. (For the older version (v0.3.x), the option <code>-i</code> is necessary.) |
| 859 |
<pre> |
| 860 |
% sfxload synthgm |
| 861 |
</pre> |
| 862 |
Then, append SBK font after it. |
| 863 |
If you've already loaded other samples, the additional option <code>-x</code> |
| 864 |
is required. |
| 865 |
<pre> |
| 866 |
% sfxload -b 1 foo.sbk |
| 867 |
</pre> |
| 868 |
Don't forget to add a command option "</code>-b 1</code>" |
| 869 |
in this case (see <a href=#Q3.5>Q3.5</a>). |
| 870 |
<p> |
| 871 |
|
| 872 |
Now you can hear your midi file. Enjoy. |
| 873 |
<pre> |
| 874 |
% drvmidi foo.mid |
| 875 |
</pre> |
| 876 |
<p> |
| 877 |
|
| 878 |
<p><hr><p> |
| 879 |
|
| 880 |
<h3><a name=Q3.5> |
| 881 |
Q3.5: Drvmidi plays strange sounds when I use an addtional SoundFont file. |
| 882 |
</h3><p> |
| 883 |
|
| 884 |
Most of user-defined SoundFont files are designed to be loaded on |
| 885 |
bank 1. Try the option <code>-b 1</code> of <code>sfxload</code> |
| 886 |
for such a sample (see <a href=#Q3.4>Q3.4</a>). |
| 887 |
<p> |
| 888 |
|
| 889 |
<p><hr><p> |
| 890 |
|
| 891 |
<h3><a name=Q3.6> |
| 892 |
Q3.6: I changed chorus and reverb modes using drvmidi, but nothing |
| 893 |
changed. Why? |
| 894 |
</h3><p> |
| 895 |
|
| 896 |
To activate chorus and reverb modes, you have to specify non-zero |
| 897 |
values for these effects at loading samples via |
| 898 |
<code>-c</code> and <code>-r</code> options of <code>sfxload</code>, |
| 899 |
respectively. |
| 900 |
<pre> |
| 901 |
% sfxload -c 30 -r 20 synthgm |
| 902 |
</pre> |
| 903 |
<p> |
| 904 |
|
| 905 |
<p><hr><p> |
| 906 |
|
| 907 |
<h3><a name=Q3.7> |
| 908 |
Q3.7: Many clicking noises can be heard in some midi files. |
| 909 |
</h3><p> |
| 910 |
|
| 911 |
If this happens when panning status changes, it is due to the |
| 912 |
restriction of Emu8000 chip. Try <code>-P</code> option with drvmidi. |
| 913 |
This option suppress the realtime pan position change. |
| 914 |
Otherwise, it may be a bug. |
| 915 |
<p> |
| 916 |
|
| 917 |
<p><hr><p> |
| 918 |
|
| 919 |
<h3><a name=Q3.8> |
| 920 |
Q3.8: Sounds are too loud! |
| 921 |
</h3><p> |
| 922 |
|
| 923 |
I think so, too... |
| 924 |
The total volume of the samples can be changed |
| 925 |
by using <code>-V</code> option at loading. |
| 926 |
<pre> |
| 927 |
% sfxload -V 40 synthgm |
| 928 |
</pre> |
| 929 |
The value is in percent with a default of 70%. |
| 930 |
<p> |
| 931 |
|
| 932 |
If you're using linux, the mixer volumes can be set at loading the module |
| 933 |
automatically (see <a href=#Q2.5>Q2.5</a>). |
| 934 |
<p> |
| 935 |
|
| 936 |
<p><hr><p> |
| 937 |
|
| 938 |
<h3><a name=Q3.9> |
| 939 |
Q3.9: I have GUS patch files. Can I use these samples? |
| 940 |
</h3><p> |
| 941 |
|
| 942 |
Yes. |
| 943 |
For example, to load a patch <code>gunshot.pat</code> onto preset #127, |
| 944 |
run |
| 945 |
<pre> |
| 946 |
% gusload -p 127 gunshot.pat |
| 947 |
</pre> |
| 948 |
<p> |
| 949 |
|
| 950 |
<p><hr><p> |
| 951 |
|
| 952 |
<h3><a name=Q3.10> |
| 953 |
Q3.10: A strange piano sound is heard instead of drum (or other) sounds. |
| 954 |
</h3><p> |
| 955 |
|
| 956 |
Some MIDI files use the channel 16 as a drum channel. |
| 957 |
while only the channel 10 is accepted as a drum in drvmidi |
| 958 |
as default. |
| 959 |
(In the case of GS file, it may vary according to system exclusive messages.) |
| 960 |
To change the drum state, |
| 961 |
use the option <code>-D</code>. |
| 962 |
The positive argument means to turn on the drum channel, |
| 963 |
but the negative argument means to turn off. |
| 964 |
For example, '<code>-D 16</code>' option specifies the channel 16 |
| 965 |
as a drum channel, |
| 966 |
and '<code>-D -10</code>' option |
| 967 |
reserves the channel 10 as a normal channel. |
| 968 |
<p> |
| 969 |
|
| 970 |
Another possibility is the problem of multi-part support. |
| 971 |
Drvmidi treats tracks over 16 as second MIDI part. |
| 972 |
This feature is suppressed using '<code>-T -1</code>' option with drvmidi. |
| 973 |
Then all tracks are assumed as one MIDI part. |
| 974 |
<p> |
| 975 |
|
| 976 |
<p><hr><p> |
| 977 |
|
| 978 |
<h3><a name=Q3.11> |
| 979 |
Q3.11: Drum sounds seem smaller than Windows sound. |
| 980 |
</h3><p> |
| 981 |
|
| 982 |
If you're using v0.4.2 driver and sfxload, try <code>-A</code> option of |
| 983 |
sfxload program. |
| 984 |
This is an option to control the sensitivity of attenuation level of each |
| 985 |
instrument, and it takes a positive (float) digit value. |
| 986 |
Generally, the smaller value makes drum sounds louder. |
| 987 |
I feel the value 2.0 is better than the default state, |
| 988 |
but to keep compatibility with older versions, it's set to 10.0 as default. |
| 989 |
<pre> |
| 990 |
% sfxload -A 2 synthgm.sbk |
| 991 |
</pre> |
| 992 |
<p> |
| 993 |
|
| 994 |
The v0.4.3 driver (and sfxload) uses different way of parameter calculation. |
| 995 |
It sounds more similar to DOS/Windows, but a little bit duller than the |
| 996 |
former version. The volume calculation method can be switched |
| 997 |
by <code>aweset</code> utility. |
| 998 |
<pre> |
| 999 |
% aweset newvolume off |
| 1000 |
</pre> |
| 1001 |
Note that drvmidi will change this switch by itself, so aweset doesn't affect |
| 1002 |
its sounds at all. The sound quality via playmidi will be influenced, though. |
| 1003 |
Also, there is a command option <code>-C</code> in sfxload |
| 1004 |
to keep the compatibility with the older versions. |
| 1005 |
<p> |
| 1006 |
|
| 1007 |
<p><hr><p> |
| 1008 |
|
| 1009 |
<h3><a name=Q3.12> |
| 1010 |
Q3.12: What is "dynamic loading" of drvmidi? |
| 1011 |
</h3><p> |
| 1012 |
|
| 1013 |
This is a new feature added from ver.0.4.0 to load the required fonts |
| 1014 |
in a soundfont file "on demand" for each MIDI file. |
| 1015 |
drvmidi looks up each instrument used in the file before playing, then |
| 1016 |
it invokes sfxload to load only the required samples. |
| 1017 |
This function enables us to to play with larger samples on samller soundcard |
| 1018 |
RAM size. |
| 1019 |
In most cases, you can play MIDI files via 2MB GM/GS soundfonts |
| 1020 |
(<code>2mbgmgs.sf2</code>) on 512kB DRAM. |
| 1021 |
Of course, it's possible to play 8MB fonts on 2MB DRAM, |
| 1022 |
or 12MB fonts on 8MB DRAM |
| 1023 |
(though it'll take a bit long time to load the fonts). |
| 1024 |
Many soundfont files are distributed on web sites. |
| 1025 |
I listed them up on the |
| 1026 |
AWE driver's web page, |
| 1027 |
<center> |
| 1028 |
<a href=http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/index.html#SoundFonts> |
| 1029 |
<i>http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/index.html#SoundFonts</i> |
| 1030 |
</a> |
| 1031 |
</center> |
| 1032 |
The 2MB font above is stored on Creative's web site, and on the AWE Hot Spot, too. |
| 1033 |
Also, there're 2MB and 4MB fonts are included in AWE64 distribution. |
| 1034 |
AWE64 users can try it. |
| 1035 |
<p> |
| 1036 |
|
| 1037 |
To use dynamic loading, the following precodure is necessary. |
| 1038 |
<ol> |
| 1039 |
<li> Load ROM fonts previously. (<b>DONT'T FORGET THIS!</b>) |
| 1040 |
<pre> |
| 1041 |
% sfxload synthgm |
| 1042 |
</pre> |
| 1043 |
<li> Specify the soundfont file to be used via <code>-L</code> (or <code>--dynamic</code>) option in |
| 1044 |
the command line of drvmidi. |
| 1045 |
<pre> |
| 1046 |
% drvmidi -L 2mbgmgs foo.mid |
| 1047 |
</pre> |
| 1048 |
</ol> |
| 1049 |
<p> |
| 1050 |
|
| 1051 |
Sometimes, drvmidi fails to load all samples due to out of memeory. |
| 1052 |
In such a case, the following message will appear: |
| 1053 |
<pre> |
| 1054 |
preload: couldn't load all fonts. |
| 1055 |
</pre> |
| 1056 |
drvmidi uses ROM fonts instead of the samples which are not loaded successfully. |
| 1057 |
<p> |
| 1058 |
|
| 1059 |
The dynamic loading fonts can be specified in the default setting file. |
| 1060 |
See <a href=#Q3.13>Q3.13</a>. |
| 1061 |
<p> |
| 1062 |
|
| 1063 |
<p><hr><p> |
| 1064 |
|
| 1065 |
<h3><a name=Q3.13> |
| 1066 |
Q3.13: I want to set up default options. |
| 1067 |
</h3><p> |
| 1068 |
|
| 1069 |
The command line options of sfxload and drvmidi can be specified |
| 1070 |
in the resource files in advance. |
| 1071 |
The resource file of sfxload are |
| 1072 |
<code>/etc/sfxloadrc</code> and <code>~/.sfxloadrc</code>, |
| 1073 |
and |
| 1074 |
those of drvmidi are |
| 1075 |
<code>/etc/drvmidirc</code> and <code>~/.drvmidirc</code>, |
| 1076 |
repsectively. |
| 1077 |
If both files are specified, the latter one is used. |
| 1078 |
<p> |
| 1079 |
|
| 1080 |
The sfxload resource file has the following format: |
| 1081 |
<pre> |
| 1082 |
fontname options.. |
| 1083 |
fontname options.. |
| 1084 |
</pre> |
| 1085 |
The first argument is the soundfont name, and the remaining arguments |
| 1086 |
are command line options to be specified. |
| 1087 |
The font name "<code>default</code>" is special, and means that the |
| 1088 |
default options to be used if any font name doesn't match the given soundfont. |
| 1089 |
Both short and long options are available. |
| 1090 |
For example: |
| 1091 |
<pre> |
| 1092 |
default --sense=10 --atten=32 -V100 |
| 1093 |
synthgm --sense=2 -V100 |
| 1094 |
</pre> |
| 1095 |
<p> |
| 1096 |
|
| 1097 |
The format of drvmidi resource file is similar to the above. |
| 1098 |
However, the valid font name is only "<code>default</code>". |
| 1099 |
Though drvmidi accepts both short and long options, the option editor |
| 1100 |
in tkmidi (featured from v0.4.2) can only handle long options. |
| 1101 |
For example: |
| 1102 |
<pre> |
| 1103 |
default --dynamic=2mbgmgs |
| 1104 |
</pre> |
| 1105 |
With this function, you can use dynamic loading without specifying |
| 1106 |
command line options at each time. |
| 1107 |
<p> |
| 1108 |
|
| 1109 |
<p><hr><p> |
| 1110 |
|
| 1111 |
<h3><a name=Q3.14> |
| 1112 |
Q3.14: Can I play a GS midi file for Roland SC88? |
| 1113 |
</h3><p> |
| 1114 |
|
| 1115 |
The new drvmidi ver.0.4.2 can emulate the SC88 specific controls; |
| 1116 |
a couple of sysex controls |
| 1117 |
including multi part, and some controls like TVF and EG. |
| 1118 |
As default, the sysex messages of multi-part mode and master volume control |
| 1119 |
are supported. |
| 1120 |
Regardless of received sysex status, you can turn on the multi part mode |
| 1121 |
by specifying the option <code>--multipart=on</code>. |
| 1122 |
<p> |
| 1123 |
|
| 1124 |
The effect controls to TVF, EG, etc. are not emulated as default status. |
| 1125 |
You need to add an option <code>--usefx=on</code> to drvmidi. |
| 1126 |
Note that this function is still experimental and inaccurate. |
| 1127 |
The sound effect varies with the soundfont file, so you should |
| 1128 |
adjust parameters for your using font file. |
| 1129 |
<p> |
| 1130 |
|
| 1131 |
Also, You can edit the options and effect parameters above |
| 1132 |
via the option editor in tkmidi. |
| 1133 |
<p> |
| 1134 |
|
| 1135 |
<p><hr><p> |
| 1136 |
<h3><a name=Q3.15> |
| 1137 |
Q3.15: Can I play a midi file with Yamaha XG format? |
| 1138 |
</h3><p> |
| 1139 |
|
| 1140 |
The new drvmidi (v0.4.2) accepts the bank control defined in XG format. |
| 1141 |
However, since the drum and sfx presets in XG format are partly different from |
| 1142 |
one in GS, some preset remapping is required to play back properly with |
| 1143 |
the usual GS soundfont file. |
| 1144 |
Drvmidi avoids this problem by assigning the XG drum and sfx presets to |
| 1145 |
the banks which are not used in GS. |
| 1146 |
To enable this feature, add the option <code>--xgmap=on</code>. |
| 1147 |
<p> |
| 1148 |
|
| 1149 |
To play back this new bank, the driver needs to duplicate the sounds |
| 1150 |
from original GS banks. |
| 1151 |
This can be solved easily using the preset mapping, |
| 1152 |
which is newly supported in awedrv-0.4.2. |
| 1153 |
For example, if you're using synthgs.sbk, load two bank files after it. |
| 1154 |
(These bank files are included in the awesfx / sfxload package.) |
| 1155 |
<pre> |
| 1156 |
% sfxload synthgs |
| 1157 |
% sfxload -b0 xgsfx.bnk |
| 1158 |
% sfxload -b0 xgdrum.bnk |
| 1159 |
</pre> |
| 1160 |
Then, the XG banks are mapped from the original GS fonts without |
| 1161 |
using any extra DRAM. |
| 1162 |
<p> |
| 1163 |
|
| 1164 |
The procedure above becomes easy by writing a <a href=#Q3.17>virtual bank file</a>. |
| 1165 |
For example, using the bank file (xgdefault.bnk) contains the following, |
| 1166 |
<pre> |
| 1167 |
default synthgs.sbk |
| 1168 |
include xgsfx.bnk |
| 1169 |
include xgdrum.bnk |
| 1170 |
</pre> |
| 1171 |
just load this bank file once, and all things above will be done. |
| 1172 |
<pre> |
| 1173 |
% sfxload xgdefault.bnk |
| 1174 |
</pre> |
| 1175 |
Also, you need to make the similar bank file to use the dynamic loading |
| 1176 |
function in drvmidi: |
| 1177 |
<pre> |
| 1178 |
default 2mbgmgs.sf2 |
| 1179 |
include xgsfx.bnk |
| 1180 |
include xgdrum.bnk |
| 1181 |
</pre> |
| 1182 |
By specifying this bank file in the option <code>--dynamic</code>, |
| 1183 |
drvmidi loads the appropriate fonts automatically even both for GS |
| 1184 |
and XG format. |
| 1185 |
<p> |
| 1186 |
|
| 1187 |
<p><hr><p> |
| 1188 |
<h3><a name=Q3.16> |
| 1189 |
Q3.16: The tone of ver.0.4.3 seems different from others.. |
| 1190 |
</h3><p> |
| 1191 |
|
| 1192 |
Yes, the latest version 0.4.3 uses the different volume parameter calculation. |
| 1193 |
Please refer to <a href=#Q3.11>Q3.11</a>. |
| 1194 |
<p> |
| 1195 |
|
| 1196 |
<p><hr><p> |
| 1197 |
<h3><a name=Q3.17> |
| 1198 |
Q3.17: What is a virtual bank file? |
| 1199 |
</h3><p> |
| 1200 |
|
| 1201 |
The virtual bank file is a text file describing the list of presets, banks |
| 1202 |
and notes from multiple soundfont files. |
| 1203 |
By using a virtual bank file, you can load a part of sounds from one soundfont |
| 1204 |
file and another part from other soundfont files without re-creating a whole |
| 1205 |
soundfont file. |
| 1206 |
On the other words, it enables to replace or add one instrument with other |
| 1207 |
sounds (even one note in drumset!). |
| 1208 |
<p> |
| 1209 |
|
| 1210 |
The format of virtual bank file is as follows: |
| 1211 |
<pre> |
| 1212 |
source:destination:file instr-name |
| 1213 |
</pre> |
| 1214 |
The source and destination are the instrument map |
| 1215 |
to specify the instruments to be replaced, and have the following format: |
| 1216 |
<pre> |
| 1217 |
preset/bank/keynote |
| 1218 |
</pre> |
| 1219 |
The preset is the MIDI program number (from 0 to 127), and the bank is |
| 1220 |
the MIDI bank number (from 0 to 128). The bank #128 is regarded as a |
| 1221 |
drumset. The keynote is the MIDI key note number (from 0 to 127). |
| 1222 |
If keynote is omitted, the whole instrument will be replaced. |
| 1223 |
If bank is omitted, all matching instruments with preset will be replaced. |
| 1224 |
If preset has an asterisk(*) or number -1, the matching bank will be replaced. |
| 1225 |
<p> |
| 1226 |
|
| 1227 |
The virtual bank will replace the instruments specified by source field |
| 1228 |
with the instruments by destination field. |
| 1229 |
The file field is a soundfont file name to be loaded. |
| 1230 |
Note that if you use the identical soundfont file several times in one virtual |
| 1231 |
bank file, you must give also the identical name here. |
| 1232 |
The files are searched through the path given to sfxload. |
| 1233 |
<p> |
| 1234 |
|
| 1235 |
The instr-name field is an optional field to specify the name of this |
| 1236 |
instrument. In the current version of sfxload, this field is ignored. |
| 1237 |
<p> |
| 1238 |
|
| 1239 |
The virtual bank file accepts also the following format: |
| 1240 |
<pre> |
| 1241 |
source:destination instr-name |
| 1242 |
</pre> |
| 1243 |
Unlike the previous case, this format includes no file field. |
| 1244 |
This enables the preset mapping (linking) and works like a symbolic link |
| 1245 |
of file operation. The source instrument is referred also as the destination |
| 1246 |
instrument. The actual destination instrument needs not exist. |
| 1247 |
<p> |
| 1248 |
|
| 1249 |
There are two special command directives: |
| 1250 |
<ul> |
| 1251 |
<li> <code>include filename</code><br> |
| 1252 |
This command simply includes the specified file in the current virtual bank |
| 1253 |
file. |
| 1254 |
<li> <code>default filename</code><br> |
| 1255 |
This command specifies the default soundfont file. |
| 1256 |
The default soundfont is referred when no matching instruments are found |
| 1257 |
in other virtual bank definitions. |
| 1258 |
</ul> |
| 1259 |
<p> |
| 1260 |
|
| 1261 |
<!----------------------------------------------------------------> |
| 1262 |
|
| 1263 |
<p><hr size=10><p> |
| 1264 |
|
| 1265 |
<h2><a name=Q4> |
| 1266 |
4. PROGRAMMING & MISCELLANEOUS |
| 1267 |
</h2><p> |
| 1268 |
|
| 1269 |
<h3><a name=Q4.1> |
| 1270 |
Q4.1: The sounds of module player are very weird. Why? |
| 1271 |
</h3><p> |
| 1272 |
|
| 1273 |
This happens when not enough DRAM is on the AWE32 card. |
| 1274 |
Please upgrade memories on your card. |
| 1275 |
<p> |
| 1276 |
|
| 1277 |
Also, the old drivers have a bug in sample loop addresses. |
| 1278 |
Please use the latest driver (v0.3.3e or later). |
| 1279 |
<p> |
| 1280 |
|
| 1281 |
<p><hr><p> |
| 1282 |
|
| 1283 |
<h3><a name=Q4.2> |
| 1284 |
Q4.2*: How can MIDI files be played from Netscape? |
| 1285 |
</h3><p> |
| 1286 |
|
| 1287 |
If you're using.. |
| 1288 |
<dl> |
| 1289 |
<dt> Netscape 3.0 |
| 1290 |
<dd> |
| 1291 |
The plug-in for Netscape 3.0 is now available. |
| 1292 |
Please install MIDI plug-in package, and check the helper list |
| 1293 |
in Options menu. See the document in this package for more details. |
| 1294 |
<p> |
| 1295 |
|
| 1296 |
The plug-in with MIDI control panel causes a bus error when displaying |
| 1297 |
the directory page (i.e. file://<i>directory</i>/). To avoid this, |
| 1298 |
you need to preload the plug-in file before starting Netscape. |
| 1299 |
It would be convenient to replace netscape as a wrapper script like |
| 1300 |
<pre> |
| 1301 |
#!/bin/sh |
| 1302 |
LD_PRELOAD=$HOME/.netscape/plugins/npmidi.so; export LD_PRELOAD |
| 1303 |
exec /usr/local/bin/netscape |
| 1304 |
</pre> |
| 1305 |
This bug doesn't appear on the plug-in without control panel window. |
| 1306 |
<p> |
| 1307 |
|
| 1308 |
Also, if you already add mime types as below, you should edit |
| 1309 |
these configuration files manually. Netscape only appends its list. |
| 1310 |
<p> |
| 1311 |
|
| 1312 |
<dt> Other browsers |
| 1313 |
<dd> |
| 1314 |
Add a new mime type for MIDI files by adding the following to your |
| 1315 |
<code>~/.mime.types</code> file: |
| 1316 |
<pre> |
| 1317 |
audio/x-midi exts=mid,midi |
| 1318 |
</pre> |
| 1319 |
Then specify the application for this type by adding to <code>~/.mailcap</code>: |
| 1320 |
<pre> |
| 1321 |
audio/x-midi; drvmidi %s |
| 1322 |
</pre> |
| 1323 |
Of course, you can choose your favorite MIDI players instead of this. |
| 1324 |
</dl> |
| 1325 |
<p> |
| 1326 |
|
| 1327 |
<p><hr><p> |
| 1328 |
|
| 1329 |
<h3><a name=Q4.3> |
| 1330 |
Q4.3: I'm planning to write a music player for AWE32. How can I control |
| 1331 |
the AWE32 driver from my program? |
| 1332 |
</h3><p> |
| 1333 |
|
| 1334 |
See <a href=awedrv-prog.html>the AWEDRV programming notes</a> |
| 1335 |
for control of awedrv device. |
| 1336 |
<p> |
| 1337 |
|
| 1338 |
From ver.0.2, awedrv accepts the GUS compatible patches and |
| 1339 |
hardware controls, so you can play module players using GUS driver |
| 1340 |
like gmod by a slight modification. |
| 1341 |
<p> |
| 1342 |
|
| 1343 |
For example, to use gmod for awedrv, just change the line 62 of |
| 1344 |
<code>Sequencer.c</code> for detection of synthesizer card to accept |
| 1345 |
subtype 0x20 like |
| 1346 |
<pre> |
| 1347 |
if (info.synth_type == SYNTH_TYPE_SAMPLE |
| 1348 |
&& (info.synth_subtype == SAMPLE_TYPE_GUS||info.synth_subtype==0x20)) |
| 1349 |
gus_dev = i; |
| 1350 |
</pre> |
| 1351 |
(<code>0x20</code> means <code>SAMPLE_TYPE_AWE32</code> defined in <code>awe_voice.h</code>.) |
| 1352 |
<p> |
| 1353 |
|
| 1354 |
<!----------------------------------------------------------------> |
| 1355 |
<p><hr size=10><p> |
| 1356 |
|
| 1357 |
</body> |