Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Thu, Oct 23, 1997 at 04:45:14PM -0200, Nicola Bernardelli wrote: On Wed, 22 Oct 1997, Marcus Brinkmann wrote: 2.1.59 has that problem too, 2.0.29 too... it is just out of memory (I recently reduced swap partition from 33Mb to 8Mb as it nearly never worked - 32 Mb ram BTW - and when it worked it was 2-3 megs and I needed to collect disk space... [snip] 8MB swap is far to low, if you ask me. Although you have 32 MB, if you run out of memory, it can break you suddenly, and important work can be at loss. Sure, a risk. Depends on what you do. What is your mail reader? pine Try using mutt. It is good (very good) and I have no problems reading my backlog of debian bug reports (23 Megabyte so far - in one singel folder, maybe a few thousand messages). And I have only 16MB of memory. Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Ok, congrats for you nice keyboard. I heard a PSR-don'tRememberWhichNow
years ago and the sounds were nice. Don't get slave to gadgets though!
get Mark E. Boling, The jazz theory workbook, Advance Music... other
books if you want, one especially good for pianists. If you learn jazz you
can face anything.
Back to Debian now.
On Thu, 23 Oct 1997 [EMAIL PROTECTED] wrote:
It supports a sustain pedal, but I did not get one yet. When I get
more $$$ and I am more advanced I'll get one. I think they go for
about $20-$50US.
As soon as you can, I suppose you have better learn _with_ it.
I think games are very nice for an OS to be more widely used, and Linux
could support both the _very_powerful_solid_graphics kind of games and
the abstract_fast_X_fascinating_graphics kind, of course both with
astonishing sounds :-) maybe in part math-generated and graphics-related
(I still have to give a look at software such as kandinsky). Maybe one day
some Debian-original ultra-eye_ear_MIND-catching game...?
Hopefully some day...
Where do you play Doom, Linux or DOS? If Linux, does it need anything else
but a properly configured kernel in order to send to the external MIDI
synth?... Maybe a doom-specific sound server does anything? Is there a
Debian package?... I can't find one on the 1.3.1. CD... I had it on my
very first Linux install years ago (or the second one...) and will give a
look at some more recent CDs I have here. I tried abuse yesterday from the
Debian package [not the one with 1.2.4, sound broken to me {but SVGA}, the
one with 1.3.1 {but only X, not SVGA it seems}] and it looks very
interesting (more than recent demos I saw in (Win)DOG with sophisticated
3d-like graphics), and sounds give a _very_ interesting taste; it seems
they chose to have no music in it.
Right now, I play it in dos, but that is only because I haven't
actually gotten the chance to install Linux yet...hehe. In the dos
version, I was just able to change the doom configuration from SB16
to Midi Out. As for Debian packages, I am not sure. I know Doom and
Wolfenstein3D are both out for Linux, though.
Yes, no Debian packages almost on 1.3.1., will give a look at the ftp site
but think not. (This won't interest you, anyway I saw a couple of hours
ago that at Takashi Iwai's home page there is also stuff for Doom with
Linux, sound server and patches to use awe synth with it... A Debian
package of doom should put all that stuff together.)
Cheers,
Nicola
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Thu, 23 Oct 1997, Marcus Brinkmann wrote: Try using mutt. It is good (very good) and I have no problems reading my backlog of debian bug reports (23 Megabyte so far - in one singel folder, maybe a few thousand messages). And I have only 16MB of memory. THANK YOU, I _will_ try it... (faster if a Debian package exists of course). Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Nicola =)
Nicole,
A-ehm, NicolA is a male name in Italy, just think about Nicolas in the
USA.
Oops.. sorry about that! I think it was late when I wrote that
message
Yes, you're right, not nice being tied to the computer... not nice FM too
nor eating CPU cycles for soft synthesis if you want the CPU to do
something else... as you told you can use your synth-capable-keyboard for
General Midi sounds from games (though here you _are_ tied to the computer
and AWE is not bad in this case)... I think your Yamaha PSR-200 _is_
General Midi compliant by now, isn't it? How many octaves has the
keyboard, 4, 5 or 7? Did you have to buy a sustain pedal apart of it?
Yeah.. it is tied then, but I just stick it on a chair, plug in the
3 wires, and works well (two plugs for the midi connection, and a
third into my SB16's input jack, which puts it into the stereo
system along with the wave sounds).. The thing is 11 pounds, but I
guess one of those Grand Pianos would be much harder to move..hehe.
Yes, the PSR-220 (not 200), is General Midi compliant (a feature of
which it makes sure to mention many times in the manual..hehe). It
has 100 panel instruments, and a seperate GM mode for 128 more.
Well, it has 61 keys over about 5 octaves. However, you can also
adjust the whole keyboard up or down two whole octaves by changing a
simple setting (you could also split the keyboard between two
instruments and adjust each side by 2 octaves seperately).
It supports a sustain pedal, but I did not get one yet. When I get
more $$$ and I am more advanced I'll get one. I think they go for
about $20-$50US.
I think games are very nice for an OS to be more widely used, and Linux
could support both the _very_powerful_solid_graphics kind of games and
the abstract_fast_X_fascinating_graphics kind, of course both with
astonishing sounds :-) maybe in part math-generated and graphics-related
(I still have to give a look at software such as kandinsky). Maybe one day
some Debian-original ultra-eye_ear_MIND-catching game...?
Hopefully some day...
Where do you play Doom, Linux or DOS? If Linux, does it need anything else
but a properly configured kernel in order to send to the external MIDI
synth?... Maybe a doom-specific sound server does anything? Is there a
Debian package?... I can't find one on the 1.3.1. CD... I had it on my
very first Linux install years ago (or the second one...) and will give a
look at some more recent CDs I have here. I tried abuse yesterday from the
Debian package [not the one with 1.2.4, sound broken to me {but SVGA}, the
one with 1.3.1 {but only X, not SVGA it seems}] and it looks very
interesting (more than recent demos I saw in (Win)DOG with sophisticated
3d-like graphics), and sounds give a _very_ interesting taste; it seems
they chose to have no music in it.
Right now, I play it in dos, but that is only because I haven't
actually gotten the chance to install Linux yet...hehe. In the dos
version, I was just able to change the doom configuration from SB16
to Midi Out. As for Debian packages, I am not sure. I know Doom and
Wolfenstein3D are both out for Linux, though.
Shawn
[EMAIL PROTECTED]
http://www.the-spa.com/shawn.fumo/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, 22 Oct 1997, Marcus Brinkmann wrote:
Ok. Please mail me about PnP if you have new information. I will try the new
kernels for myslf some time (far away from now, I suppose... lot to do).
(I've sent another message to the list about it in the meantime.)
2.1.59 has that problem too, 2.0.29 too... it is just out of memory
(I recently reduced swap partition from 33Mb to 8Mb as it nearly never
worked - 32 Mb ram BTW - and when it worked it was 2-3 megs and I needed
to collect disk space...
[snip]
8MB swap is far to low, if you ask me. Although you have 32 MB, if you run
out of memory, it can break you suddenly, and important work can be at loss.
Sure, a risk. Depends on what you do.
What is your mail reader?
pine
-
Marcus, as you allowed me to do it, I forward this to the list, maybe of
interest.
On Wed, 22 Oct 1997, Marcus Brinkmann wrote:
Hehe, you can use 8MB Chaos bank with 4MB RAM!
What is the Chaos bank, something to have the card playing just like some
syntethizer out there? BTW, anything to have it playing similarly to the
Yamaha Clavinova or I ask too much with 4 megs ram?
Look at the bottom of the awedrv home page. Chaos are very good sfb's. huge
and from superb quality, I can mail you the adress sometime (are short in
time now).
(A-ehm, are you still working on 0.4.2c/sources? Did you think about
contacting the Debian awe-* packages maintainer and help update them using
the binaries...? Perhaps it is better to also have the sources compile
ok.)
I will take a look at the sources this week. University is first now, it is
really hard! Math and phyics the whole week.
-
On Wed, 22 Oct 1997 [EMAIL PROTECTED] wrote:
Nicole,
A-ehm, NicolA is a male name in Italy, just think about Nicolas in the
USA.
Ah, about that cheap MIDI (possibly mute) keyboard, I saw that
[EMAIL PROTECTED] was talking about it too, he was looking
for midi software packages and mainly for software synthesis.
Well, speaking of that, this is what I settled on. I turned out
getting a Yamaha PSR-220. It cost about $220US, and considering that
was not much more expensive than the keyboard with no sounds of its
own, was better to get that one. Including power supply, warrenty,
and midi camble, turned out costing about $300US total.
It has turned out working very well. It works fine in place of a
sound card (sounds MUCH better than FM Synthesis), and doesn't take
up the processor like soft. syn. does. (thus making it possible to
play games like Doom with it). It also works very well for inputting
into a sequencer, as it can sense how hard you hit keys, etc.
I'd say that for a midi-comp. keyboard, this is about as low as
you'd want to go. Instruments sounded much more realistic (in
general) than the Casio I tried. Has no pitch-wheel, but can play
pitch-bend commands (so you could always add that later in the
sequencer or something).
The only dumb keyboard with no sounds in it, looked fairly nice,
but I don't think it'd be worth it unless you found it for like
$100US. Otherwise, might as well pay a bit more for the Yamaha and
get a nice built-in synthesizer, and the ability to practice without
being tied to the computer...
Yes, you're right, not nice being tied to the computer... not nice FM too
nor eating CPU cycles for soft synthesis if you want the CPU to do
something else... as you told you can use your synth-capable-keyboard for
General Midi sounds from games (though here you _are_ tied to the computer
and AWE is not bad in this case)... I think your Yamaha PSR-200 _is_
General Midi compliant by now, isn't it? How many octaves has the
keyboard, 4, 5 or 7? Did you have to buy a sustain pedal apart of it?
I think games are very nice for an OS to be more widely used, and Linux
could support both the _very_powerful_solid_graphics kind of games and
the abstract_fast_X_fascinating_graphics kind, of course both with
astonishing sounds :-) maybe in part math-generated and graphics-related
(I still have to give a look at software such as kandinsky). Maybe one day
some Debian-original ultra-eye_ear_MIND-catching game...?
Where do you play Doom, Linux or DOS? If Linux, does it need anything else
but a properly configured kernel in order to send to the external MIDI
synth?... Maybe a doom-specific sound server does anything? Is there a
Debian package?... I can't find one on the 1.3.1. CD... I had it on my
very first Linux install years ago (or the second one...) and will give a
look at some more recent CDs I have here. I tried abuse yesterday from the
Debian package [not the one with 1.2.4, sound broken to me {but SVGA}, the
one with 1.3.1 {but only X, not SVGA it seems}] and it looks very
interesting (more than recent demos I saw in (Win)DOG with sophisticated
3d-like graphics), and sounds give a _very_ interesting taste; it seems
they chose to have no music in it.
There's also LISP stuff to draw enemies behaviour it
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, 22 Oct 1997, Nicola Bernardelli wrote: On Wed, 22 Oct 1997, Nicola Bernardelli wrote: On Mon, 20 Oct 1997, Nicola Bernardelli wrote: As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly detects size of memory on soundcard: AWE32-0.4.2c (RAM4096k) I tried installing it on top of the AWE support coming with kernel 2.1.55... it works! (So far I tried with pnp handled by isapnp and not by the kernel, but will try that too.) PNP handled by the kernel doesn't work. Anyway redoing it with isapnp succeeds, not that anything is stuck unreacheable. I've just ftp'ed and applied the small :-) patch files bringing from 2.1.55 to 2.1.59, pub/Linux/kernel/v2.1/patch-2.1.5[6-9].gz on a mirror of sunsite.unc.edu, less than 200k total. Good that I didn't rm that big linux-2.1.55.tar.gz! _Tomorrow_ I will configure 2.1.59, build and test PNP and use 2.1.59 to continue looking at SLab. As with 2.1.55, 2.1.59 PNP handling does not initialize properly the AWE64 Gold, nothing works, not only awe synth but also /dev/audio. Again, running isapnp both during boot or after boot_with_kernel_PNP_mis-handle results in anything working fine. Anyway I recompiled 2.1.59 without PNP (is it possible that the two zImage files have the same _identical_ size?!). I installed the 0.4.2c awe driver on top of 2.1.59, of course. Before reporting to the kernel mailing list the PNP problem I'll look for docs on PNP handling done by the kernel, maybe some config file is needed as well...? I read _nothing_ on the matter as that wasn't my main goal. (I could also try putting an #error directive in some PNP .c file and see whether that goes compiled or not.) On Wed, 22 Oct 1997, Nicola Bernardelli wrote: BTW2: I am just testing 2.0.30 last rebuild, I had to see some OSS/xmixer relations, and while writing this message I was also zcatting a 2552707 bytes .gz file to less -i doing a pattern search in it... and suddenly this error line started to appear 6-7 times per second on any console I went to look at: Unable to load interpreter. Typing ctrl-c where the zcat ... | less -i processes had been started allowed recover, and I'm finishing this message and going to send it without rebooting (but good that you suggested to switch back my default to 2.0.29 as the latest stable kernel). 2.1.59 has that problem too, 2.0.29 too... it is just out of memory (I recently reduced swap partition from 33Mb to 8Mb as it nearly never worked - 32 Mb ram BTW - and when it worked it was 2-3 megs and I needed to collect disk space), better run zgrep on that high-compression-ratio .gz file or almost :-) not load at the same time the debian-user mail folder (currently it is very big and is soon going to become another gzipped month-or-little-more debian-upTo97mmdd.gz file). Ah, about that cheap MIDI (possibly mute) keyboard, I saw that [EMAIL PROTECTED] was talking about it too, he was looking for midi software packages and mainly for software synthesis. Date: Sun, 14 Sep 1997 15:15:12 + From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: SB AWE 64 versus Soft. Syns. for making midi... Also, midi keybo Cheers. Nicola Bernardelli [EMAIL PROTECTED] --- Please use [EMAIL PROTECTED] for messages from any kind of robot, such as mailing lists. From that address no autoresponse messages will come, even when I am away for some days. --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, Oct 22, 1997 at 03:59:54PM -0200, Nicola Bernardelli wrote: As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly detects size of memory on soundcard: AWE32-0.4.2c (RAM4096k) I tried installing it on top of the AWE support coming with kernel 2.1.55... it works! (So far I tried with pnp handled by isapnp and not by the kernel, but will try that too.) PNP handled by the kernel doesn't work. Anyway redoing it with isapnp succeeds, not that anything is stuck unreacheable. I've just ftp'ed and applied the small :-) patch files bringing from 2.1.55 to 2.1.59, pub/Linux/kernel/v2.1/patch-2.1.5[6-9].gz on a mirror of sunsite.unc.edu, less than 200k total. Good that I didn't rm that big linux-2.1.55.tar.gz! _Tomorrow_ I will configure 2.1.59, build and test PNP and use 2.1.59 to continue looking at SLab. As with 2.1.55, 2.1.59 PNP handling does not initialize properly the AWE64 Gold, nothing works, not only awe synth but also /dev/audio. Again, running isapnp both during boot or after boot_with_kernel_PNP_mis-handle results in anything working fine. Anyway I recompiled 2.1.59 without PNP (is it possible that the two zImage files have the same _identical_ size?!). I installed the 0.4.2c awe driver on top of 2.1.59, of course. Ok, I understand. Before reporting to the kernel mailing list the PNP problem I'll look for docs on PNP handling done by the kernel, maybe some config file is needed as well...? I read _nothing_ on the matter as that wasn't my main goal. (I could also try putting an #error directive in some PNP .c file and see whether that goes compiled or not.) Ok. Please mail me about PnP if you have new information. I will try the new kernels for myslf some time (far away from now, I suppose... lot to do). On Wed, 22 Oct 1997, Nicola Bernardelli wrote: BTW2: I am just testing 2.0.30 last rebuild, I had to see some OSS/xmixer relations, and while writing this message I was also zcatting a 2552707 bytes .gz file to less -i doing a pattern search in it... and suddenly this error line started to appear 6-7 times per second on any console I went to look at: Unable to load interpreter. Typing ctrl-c where the zcat ... | less -i processes had been started allowed recover, and I'm finishing this message and going to send it without rebooting (but good that you suggested to switch back my default to 2.0.29 as the latest stable kernel). Huh? I missed this prior. Perhaps less is not the right thing to do with a gzipped file this big... although it should work. Strange! 2.1.59 has that problem too, 2.0.29 too... it is just out of memory (I recently reduced swap partition from 33Mb to 8Mb as it nearly never worked - 32 Mb ram BTW - and when it worked it was 2-3 megs and I needed to collect disk space), better run zgrep on that high-compression-ratio .gz file or almost :-) not load at the same time the debian-user mail folder (currently it is very big and is soon going to become another gzipped month-or-little-more debian-upTo97mmdd.gz file). 8MB swap is far to low, if you ask me. Although you have 32 MB, if you run out of memory, it can break you suddenly, and important work can be at loss. What is your mail reader? Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Nicole, Ah, about that cheap MIDI (possibly mute) keyboard, I saw that [EMAIL PROTECTED] was talking about it too, he was looking for midi software packages and mainly for software synthesis. Well, speaking of that, this is what I settled on. I turned out getting a Yamaha PSR-220. It cost about $220US, and considering that was not much more expensive than the keyboard with no sounds of its own, was better to get that one. Including power supply, warrenty, and midi camble, turned out costing about $300US total. It has turned out working very well. It works fine in place of a sound card (sounds MUCH better than FM Synthesis), and doesn't take up the processor like soft. syn. does. (thus making it possible to play games like Doom with it). It also works very well for inputting into a sequencer, as it can sense how hard you hit keys, etc. I'd say that for a midi-comp. keyboard, this is about as low as you'd want to go. Instruments sounded much more realistic (in general) than the Casio I tried. Has no pitch-wheel, but can play pitch-bend commands (so you could always add that later in the sequencer or something). The only dumb keyboard with no sounds in it, looked fairly nice, but I don't think it'd be worth it unless you found it for like $100US. Otherwise, might as well pay a bit more for the Yamaha and get a nice built-in synthesizer, and the ability to practice without being tied to the computer... Shawn [EMAIL PROTECTED] http://www.the-spa.com/shawn.fumo/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, 20 Oct 1997, Nicola Bernardelli wrote:
As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly
detects size of memory on soundcard:
AWE32-0.4.2c (RAM4096k)
I tried installing it on top of the AWE support coming with kernel
2.1.55... it works! (So far I tried with pnp handled by isapnp and not by
the kernel, but will try that too.)
Why did I retake up 2.1.55? Because I had it handy here...
(I'm too tired these days to wake up at 4-5 and watch a 3 hours ftp to
get 2.1.57 or newer [?]... hard life in Italy with our monopolist
telephone company! Great hopes for next years.)
... to test SLab with it.
I understand from SLab doc release.notes that it needs OSS/Free (nee:
VoxWare) drivers reved to something like 3.5.X., and this is what the AWE
install.sh script reports when fired...
...on 2.0.29 and 2.0.30 ...on 2.1.55
AWE 0.3.3e OSS/Free-3.5.0 (aka USS/Lite) OSS/Free-3.8b5 or newer
AWE 0.4.2c USS OSS-3.8b5 or newer
(Where does it get it? SOUND_INTERNAL_VERSION is defined in the kernel
header file /usr/src/linux/drivers/sound/soundvers.h, and the awe driver
install.sh script translates it in what it needs, which is not the mere
SOUND_VERSION_STRING also defined in that header.)
BTW: SLab starts quite fine now, the error message about SHMEM was
misdirecting investigation toward that point, but instead it was an
absolutely trivial environment problem, I attach a tiny patch for the
startup script not to be error prone in case of SLAB_HOME different than
the default, if anybody is interested (but I'm currently using another
script which eventually stops the Network Audio System before starting
SLab and restarts it after SLab exits, running on sh instead of csh just
because I'm not familiar to the latter). I'm also writing anything I find
in a report I'll mail to the author when I'm sure of the contents. I have
_just_ started trying with it and with the sound driver coming with 2.1.55
somethings seems to happen.
BTW2: I am just testing 2.0.30 last rebuild, I had to see some
OSS/xmixer relations, and while writing this message I was also
zcatting a 2552707 bytes .gz file to less -i doing a pattern search in
it... and suddenly this error line started to appear 6-7 times per
second on any console I went to look at: Unable to load interpreter.
Typing ctrl-c where the zcat ... | less -i processes had been started
allowed recover, and I'm finishing this message and going to send
it without rebooting (but good that you suggested to switch back my
default to 2.0.29 as the latest stable kernel).
--
xmixer: a channel with an ear icon appears when fired under 2.1.55, not
clear to me what that is (microphone monitoring volume?) and what the
igain/ogain (also appearing under 2.0.29 and 2.0.30) are when compared to
each source volume and to the master volume and to the ear cursor itself
(the Creative Mixer doesn't have any of these ear/igain/ogain...).
Marcus, alas I hadn't time to look at all those other mixers you mentioned
yet, so far I only saw those two, xmix and xmixer.
I am _very_ tired. Too may times went to sleep at 2-4 in the morning.
Nicola Bernardelli [EMAIL PROTECTED]
---
Please use [EMAIL PROTECTED] for messages from any kind of
robot, such as mailing lists. From that address no autoresponse
messages will come, even when I am away for some days.
---
--- startSLab.orig Sat May 3 18:14:48 1997
+++ startSLab Tue Oct 21 09:49:38 1997
@@ -7,7 +7,7 @@
setenv TCL_LIBRARY ${SLAB_HOME}/tcl.files
setenv TK_LIBRARY ${SLAB_HOME}/tcl.files
-set path = ( /usr/slab/bin /usr/slab/effects $path )
+set path = ( ${SLAB_HOME}/bin ${SLAB_HOME}/effects $path )
exec mixslab | cat /dev/null
Re: is the Creative Labs AWE64 GOLD Soundcard supported? (fwd)
On Mon, 20 Oct 1997, Marcus Brinkmann wrote: On Mon, Oct 20, 1997 at 12:41:36AM -0200, Nicola Bernardelli wrote: As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly detects size of memory on soundcard: AWE32-0.4.2c (RAM4096k) I'm lucky to hear this. So there was no need to put the information in the header file? Good. I'll include this in my HOWTO. Install was trivial, identical to 0.3.3e in the awe-drv package, just an install.sh script to call and then rebuild the kernel (of course every step is explained). Well I put the 600/3200 MAX_INFOS/MAX_SAMPLES (or the like) values by hand as the 0.4.2c install.sh does not ask for them as the 0.3.3e did. A minute anyway. I removed the Debian packages and I got and installed by hand everything I found in the binaries directory at Takashi Iwai's web/ftp site. Really Did you try to compile the sources? It don't work for me... maybe I should take a look at the debian patches. Yes, actually I fired somthing and had some errors (some macroes not previously defined, a matter of headers suppose) and _immediately_ turned to try the prebuilt binaries (as I'm already testing a lot of stuff), which work. nice, everything seems to work _very_ fine (expect that I'm not able to test the Netscape plugin yet... not that I'm suffering about it anyway). NOW (while I pop/send mail, but also tried a fly with ACM!... and was able to land safe of course) drvmidi is playing without any delay some of those sf2demo files... sending by itself the additional soundfont banks to bank1 once I've told it to. We must ask Takashi Iwai to put his photo in his homepage :-) ^ :-) , And about the MIDI keyboard: have to dig in my email backlog... I got a few tips, but please ask Britton, too (or is he CC'ed?) Yes he is. Maybe the tips were from him, some Roland... II, but I would go on a mute keyoard instead (and use the AWE synth)... if not, me too I can scan in the folder :-)... Of course I think the opposite than Britton, that is a weighted keys keyboard would be better to me, though I don't absolutely have any pianistic technique... it's just that I type on a computer keyboard already too much each day and don't look forward to take that taste with me when playing... Was it you or Toersten speaking of enjoying really making music... buy a guitar instead Yes, my trumpet is quite another thing that what comes out of the soundcard, not only the valves I mean but the sound!... and the control I have on it, on each note attack... it is a true instrument compared to a pseudo one. Anyway, back to the keyboard: in case I decide, the budget point will be quite relevant, + room + weight of the thing being that I have no room and I'll have to move it here and there. Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, 22 Oct 1997, Nicola Bernardelli wrote: On Mon, 20 Oct 1997, Nicola Bernardelli wrote: As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly detects size of memory on soundcard: AWE32-0.4.2c (RAM4096k) I tried installing it on top of the AWE support coming with kernel 2.1.55... it works! (So far I tried with pnp handled by isapnp and not by the kernel, but will try that too.) PNP handled by the kernel doesn't work. Anyway redoing it with isapnp succeeds, not that anything is stuck unreacheable. I've just ftp'ed and applied the small :-) patch files bringing from 2.1.55 to 2.1.59, pub/Linux/kernel/v2.1/patch-2.1.5[6-9].gz on a mirror of sunsite.unc.edu, less than 200k total. Good that I didn't rm that big linux-2.1.55.tar.gz! _Tomorrow_ I will configure 2.1.59, build and test PNP and use 2.1.59 to continue looking at SLab. Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
[EMAIL PROTECTED] wrote: [...] : Let me say that the awe driver package works just fine with a SB AWE32. : Don`t know about the 64 yet. Any people tried? I would suspect that it would work fine with the 64 as well. AFAIK, the AWE64 is the same as the 32, except for the extra 32 voices. Oh, and the extra 32 voices are done in software, not hardware, so unless the driver has support coded specifically for those 32 voices (which implies tying up the CPU to do this), you'll find you're stuck with the first 32 anyway. Fscking Windoze hardware.. (generic rant :) -- Running at a mere 104 billion instructions per second, the SX4 appears to be the only machine actually capable of running Office '97. -- ChipChat, Australian Personal Computer, September 1997 (paraphrased.) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, Oct 20, 1997 at 04:05:56PM +1000, Mr Stuart Lamble wrote:
[EMAIL PROTECTED] wrote:
[...]
: Let me say that the awe driver package works just fine with a SB AWE32.
: Don`t know about the 64 yet. Any people tried?
I would suspect that it would work fine with the 64 as well. AFAIK, the
AWE64 is the same as the 32, except for the extra 32 voices. Oh, and the
extra 32 voices are done in software, not hardware, so unless the driver
has support coded specifically for those 32 voices (which implies tying
up the CPU to do this), you'll find you're stuck with the first 32
anyway.
Hello! You are totally right. Everything you say is true.
About the AWE64: As Nicola and me found out, the AWE64 is working
flawlessly, but there are a few caveeats (mostly with isapnp).
Everything who is interested, should check out my HOWTO at
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/soundblaster.html
It does cover the SB [AWE] {32,64} [PnP].
Fscking Windoze hardware.. (generic rant :)
No comment. (My rant would get longer than yours :)
Thank you,
Marcus
--
Rhubarb is no Egyptian god.
Marcus Brinkmann
[EMAIL PROTECTED]
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
As you suggested (THANK YOU), Marcus, I got 0.4.2c and it correctly detects size of memory on soundcard: AWE32-0.4.2c (RAM4096k) Install was trivial, identical to 0.3.3e in the awe-drv package, just an install.sh script to call and then rebuild the kernel (of course every step is explained). - I removed the Debian packages and I got and installed by hand everything I found in the binaries directory at Takashi Iwai's web/ftp site. Really nice, everything seems to work _very_ fine (expect that I'm not able to test the Netscape plugin yet... not that I'm suffering about it anyway). NOW (while I pop/send mail, but also tried a fly with ACM!... and was able to land safe of course) drvmidi is playing without any delay some of those sf2demo files... sending by itself the additional soundfont banks to bank1 once I've told it to. We must ask Takashi Iwai to put his photo in his homepage :-) - BTW, I gave a look at old messages... have you and Britton selected a cheap midi keyboard then? As you know, me too I think I'll have to get one soon... Nicola On Sat, 18 Oct 1997, Marcus Brinkmann wrote: On Fri, Oct 17, 1997 at 09:04:14PM -0200, Nicola Bernardelli wrote: On Fri, 17 Oct 1997, Marcus Brinkmann wrote: #define AWE_DEFAULT_BASE_ADDR 0x620 /* base port address */ #define AWE_DEFAULT_MEM_SIZE 4096 /* kbytes */ Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) This is awkward. You should test it with the new version, too. awe-drv is actually at 0.4.2c (you can find the location in my HOWTO). Note that the sources coming with kernel 2.1.55 in the lowlevel directory are version 0.3.1! This is very old, and everything can break. Oh, one more: 0.4.2c does support dynamically loaded sample fonts, so you can use the 4 Megabyte bank with 2 Megabyte RAM on the card. Obviously, you can try the 8 MB with 4MB on card,... Ok, I'll get the latest awe-drv at a Debian mirror. Thank you Marcus! I would be surprised if you could find a debian package newer that 0.3.3c (I filed a bug report against this old version). get the 0.4.2c at: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Fri, Oct 17, 1997 at 09:04:14PM -0200, Nicola Bernardelli wrote: On Fri, 17 Oct 1997, Marcus Brinkmann wrote: #define AWE_DEFAULT_BASE_ADDR 0x620 /* base port address */ #define AWE_DEFAULT_MEM_SIZE 4096 /* kbytes */ Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) This is awkward. You should test it with the new version, too. awe-drv is actually at 0.4.2c (you can find the location in my HOWTO). Note that the sources coming with kernel 2.1.55 in the lowlevel directory are version 0.3.1! This is very old, and everything can break. Oh, one more: 0.4.2c does support dynamically loaded sample fonts, so you can use the 4 Megabyte bank with 2 Megabyte RAM on the card. Obviously, you can try the 8 MB with 4MB on card,... Ok, I'll get the latest awe-drv at a Debian mirror. Thank you Marcus! I would be surprised if you could find a debian package newer that 0.3.3c (I filed a bug report against this old version). get the 0.4.2c at: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/ Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, 18 Oct 1997, Marcus Brinkmann wrote: I would be surprised if you could find a debian package newer that 0.3.3c (I filed a bug report against this old version). get the 0.4.2c at: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/ Oh, nice of you, so I won't go arowing in hamm directories! Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Fri, 17 Oct 1997, Marcus Brinkmann wrote: #define AWE_DEFAULT_BASE_ADDR 0x620 /* base port address */ #define AWE_DEFAULT_MEM_SIZE 4096 /* kbytes */ Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) This is awkward. You should test it with the new version, too. awe-drv is actually at 0.4.2c (you can find the location in my HOWTO). Note that the sources coming with kernel 2.1.55 in the lowlevel directory are version 0.3.1! This is very old, and everything can break. Oh, one more: 0.4.2c does support dynamically loaded sample fonts, so you can use the 4 Megabyte bank with 2 Megabyte RAM on the card. Obviously, you can try the 8 MB with 4MB on card,... Ok, I'll get the latest awe-drv at a Debian mirror. Thank you Marcus! Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Tons of e-mail and attached files passed... Marcus and I spared those things to others, here's what survives of the message I had started writing for the list... On Sun, 12 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) Mmmh. Because it can't detect your soundcard correctly :) From /usr/src/INSTALL.awe: * Manual Installation... ... ok, I wait a moment... (it will be the last thing in this message). before you do it, could you test what happens if you load a lot of samples with sfxload (more than four meg)? You can load the same big samples in different banks with: sfxload -b1 name sfxload -b2 name ... I would be interested in the error message (if any). -- nick:~$ sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 nick:~$ sfxload -b1 /mnt/fat1/sb16/sfbank/2gmgsmt.sf2 [Loading Data 144] Error in loading data: No space left on device nick:~$ sfxload -x -b1 /mnt/fat1/sb16/sfbank/2gmgsmt.sf2 [Loading Data 144] Error in loading data: No space left on device nick:~$ sfxload -b1 /mnt/fat1/sb16/sfbank/2gmgsmt.sf2 [Loading Data 0] Error in loading data: No space left on device nick:~$ sfxload -b2 /mnt/fat1/sb16/samples/voiperpn.sf2 [Loading Data 0] Error in loading data: No space left on device nick:~$ then I restart from scratch... After all the tweakle-hours of this days/nights I want to listen to those demo files with drvmidi... while recompiling 2.1.55 (done it a lot of times these last days) nick:~$ sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 ^^ cleans any fonts in any bank and send this to the default bank, which is 0 nick:~$ sfxload -b1 /cdrom/sf2demo/flight.sf2 nick:~$ drvmidi /cdrom/sf2demo/flight.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/radiatn.sf2 nick:~$ drvmidi /cdrom/sf2demo/radiatn.mid this one has nice use of guitar samples!... Niko Boese... Let's cut the standard fonts and isolate the peculiar ones... nick:~$ sfxload -i -b1 /cdrom/sf2demo/radiatn.sf2 nick:~$ drvmidi /cdrom/sf2demo/radiatn.mid Very interesting groove (though not one of my favourite genres). And... Linux is always great, no delays at all, while recompilation of kernel 2.1.55 doesn't seem to slow down, and I have the rc5v2 client in the background too, though it has a lower priority I think... This isn't but a P90 single CPU. Linux is so robust and efficient that it may well catch more and more the artists' attention in the future, say professional hd recording + MIDI + CD mastering... maybe even AudioVideo offline editing one day. And you can bet on Debian I believe. nick:~$ sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 nick:~$ sfxload -b1 /cdrom/sf2demo/letmesay.sbk nick:~$ drvmidi /cdrom/sf2demo/letmesay.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/surprise.sf2 nick:~$ drvmidi /cdrom/sf2demo/surprise.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/riffmia.sf2 nick:~$ drvmidi /cdrom/sf2demo/riffmia.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/htonight.sf2 nick:~$ drvmidi /cdrom/sf2demo/htonight.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/awedigph.sf2 nick:~$ drvmidi /cdrom/sf2demo/awedigph.mid nick:~$ sfxload -x -b1 /cdrom/sf2demo/aweblown.sf2 nick:~$ drvmidi /cdrom/sf2demo/aweblown.mid not a MIDI file - broken also for Windog sequencers nick:~$ sfxload -x -b1 /cdrom/sf2demo/awegathr.sf2 nick:~$ drvmidi /cdrom/sf2demo/awegathr.mid Anything seems OK here! -- On Sun, 12 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: [snip] Each time I did these steps (staying inside /etc and after 'mount -r -t msdos /dev/sda1 /mnt/fat1' and after '/etc/init.d/nas stop'): rmmod sound modify isapnp.conf-poke and save it isapnp isapnp.conf-poke insmod sound sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 saytime drvmidi /mnt/fat1/sb16/samples/awe64/*.mid Please, could you also try the following: sfxload -b1 your-path/sample.sbk drvmidi your-path/sfx.midi If you don't have those files, I would be happy to mail them to you (and I hope I would not violate any copyrights :( ). It is important for me, because it didn't worked for me the day before, but now after recompiling with awedrv 0.4.2c it works. (sfx.midi uses some samples in bank 1) I have sample.sbk but not sfx.mid* Oh, there is another example like this coming with vienna: sfxload -b1 voiperpn.sf2 drvmidi zebraper.mid (you shouldn't hear any piano with this, but I do) Try replacing any previously loaded soundfonts and putting the new one in bank 0: nick:~$ sfxload -i /mnt/fat1/sb16/samples/voiperpn.sf2 nick:~$ drvmidi /mnt/fat1/sb16/samples/zebraper.mid I don't hear any piano
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Thu, 16 Oct 1997, Nicola Bernardelli wrote: On Sun, 12 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) Mmmh. Because it can't detect your soundcard correctly :) From /usr/src/INSTALL.awe: [snip] Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) _Now_ done also 2.0.29 and it is the same. - (BTW, forgot this: Steinberg Italy gave some advice about CubasisAudio and Windog 3.1, but that didn't work, so I'm enquiring Creative UK and hope _they_ will eventually contact Steinberg Germany, or I will.) Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Thu, Oct 16, 1997 at 09:33:40PM -0200, Nicola Bernardelli wrote: Tons of e-mail and attached files passed... Marcus and I spared those things to others, here's what survives of the message I had started writing for the list... Yupp. Now the fine work can begin - sorting out :) Oh, there is another example like this coming with vienna: sfxload -b1 voiperpn.sf2 drvmidi zebraper.mid (you shouldn't hear any piano with this, but I do) Try replacing any previously loaded soundfonts and putting the new one in bank 0: nick:~$ sfxload -i /mnt/fat1/sb16/samples/voiperpn.sf2 nick:~$ drvmidi /mnt/fat1/sb16/samples/zebraper.mid I will try it... Thank you. I don't hear any piano like this ^ , while I hear it if I do: nick:~$ sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 nick:~$ sfxload -b1 /mnt/fat1/sb16/samples/voiperpn.sf2 nick:~$ drvmidi /mnt/fat1/sb16/samples/zebraper.mid Notice that playing this mid file under Windog too, after loading _only_ gm35revc.sf2, resulted in _everything_ played with a piano sound. There's a MIDI control to select a bank to select a preset in, so if a midi file expects to have a peculiar font on a peculiar bank you have to put it there. What is required for zebraper.mid? Strange is, that I hear sometimes piano, sometimes the real samples. They are mixing up. Mmmh, have to do some testing here. -- On Sun, 12 Oct 1997, Marcus Brinkmann wrote: [snip] ... the (VERIFYLD N) command would be alot easier. As we said by private e-mail, this doesn't work with isapnptools-1.9-1; as my system is libc5 based I had to pick the source of 1.11 in order to be able to try with it (the Debian package depends on libc6) and rebuild the binaries, and IT WORKS (but both isapnp and pnpdump take 6 seconds here, while 1.9-1 took the time to press return). Yes. I contacted the author about it, waiting I am. /* * AWE32 card configuration: * uncomment the following lines only when auto detection doesn't * work properly on your machine. **/ /*#define AWE_DEFAULT_BASE_ADDR 0x620*/ /* base port address */ /*#define AWE_DEFAULT_MEM_SIZE 512*/ /* kbytes */ you should change to #define AWE_DEFAULT_BASE_ADDR 0x620 /* base port address */ #define AWE_DEFAULT_MEM_SIZE 4096 /* kbytes */ Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) This is awkward. You should test it with the new version, too. awe-drv is actually at 0.4.2c (you can find the location in my HOWTO). Note that the sources coming with kernel 2.1.55 in the lowlevel directory are version 0.3.1! This is very old, and everything can break. Oh, one more: 0.4.2c does support dynamically loaded sample fonts, so you can use the 4 Megabyte bank with 2 Megabyte RAM on the card. Obviously, you can try the ( MB with 4MB on card,... (Ok, Marcus, I still have to do it in 2.0.29... you had a message half an hour ago... Britton, my dear, you understand we were doing lot of tests bringing possibly to lot of things to be just discarded... that's why we didn't keep cc'ing to you... but of course the wonderful HOWTO of Marcus is available.) Thank you :) I also tried it in the 2.1.55 kernel, but there I think I should modify something else... awe support remains more or less broken there for me (I have a 12k text file with boot-time output of various tries I did, if you want it I think I have better send it to you by private e-mail), almost with the default config files, AWE_NEW_KERNEL_INTERFACE... Notice that the debian package when applied to 2.0.30 prompts for AWE_MAX_SAMPLES, AWE_MAX_INFOS... These questions do not appear in make config of 2.1.55... As stated above, the version with 2.1.55 is very old. The MAX questions arise not in version 0.4.2c anymore, because the memory is allocated dynamically (Yipie!). Thank you alot, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Thu, Oct 16, 1997 at 10:58:12PM -0200, Nicola Bernardelli wrote: On Thu, 16 Oct 1997, Nicola Bernardelli wrote: On Sun, 12 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) Mmmh. Because it can't detect your soundcard correctly :) From /usr/src/INSTALL.awe: [snip] Then it should work. Done, but I still get this with kernel 2.0.30: AWE32 Sound Driver v0.3.3e (DRAM 28672k) _Now_ done also 2.0.29 and it is the same. We should really file a bug report. It would be nice if you could test the version 0.4.2c of the awe-drv. Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) Mmmh. Because it can't detect your soundcard correctly :) From /usr/src/INSTALL.awe: * Manual Installation on USSLite-3.5.4c / OSS-Free-3.7 with Linux 2.[01].x - Copy awe_wave.c, awe_hw.h, awe_version.h, and awe_config.h onto /usr/src/linux/drivers/sound/lowlevel. Also, copy awe_voice.h on /usr/src/linux/include/linux. - Apply a patch on linux source directory, /usr/src/linux. This modifies Makefile, Config.tmpl and init.c on lowlevel directory, and add a help file for configuration, /usr/src/linux/Documentation/Configure.help - If your card can't be detected automatically, edit awe_config.h and supply memory size and base address for your machine. - Configure and make the kernel and modules as usual. - Note the third remark. I think you have to edit awe_config.h in the following way: /* * AWE32 card configuration: * uncomment the following lines only when auto detection doesn't * work properly on your machine. **/ /*#define AWE_DEFAULT_BASE_ADDR 0x620*/ /* base port address */ /*#define AWE_DEFAULT_MEM_SIZE 512*/ /* kbytes */ you should change to #define AWE_DEFAULT_BASE_ADDR 0x620 /* base port address */ #define AWE_DEFAULT_MEM_SIZE 4096 /* kbytes */ Then it should work. before you do it, could you test what happens if you load a lot of samples with sfxload (more than four meg)? You can load the same big samples in different banks with: sfxload -b1 name sfxload -b2 name ... I would be interested in the error message (if any). Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: On Fri, 10 Oct 1997, Marcus Brinkmann wrote: On Fri, Oct 10, 1997 at 05:25:56PM -0200, Nicola Bernardelli wrote: Ok, for you HOWTO, I have isapnp working fine now. I find it *really* odd that you have to rearrange the order of the entrys in the isapnp.conf. A *quick* and *dirty* hack, and I can't even think of including it i my HOWTO (I see lots of emails complaining about such an unsure statement :). I can give a hint about it (and I will do), but could you check if the PEEK thing from the faq works for you? Please do it for me, because the faq states, that the standard does not clearly specifiy if it should work without the PEEKS, means, that it is fully legitimate that you have to include the PEEKS. Please try it, thank you! Good news to you Marcus, your POKE way works fine here with the AWE64 Gold, I tried the devices in any of the following sequences always with success: I'm sorry to bother you so hard, but here is my begging: Could you check if the first way also works? You were right as you wrote that the (VERIFYLD N) command would be alot easier. I was damned blind as this point (i didn't even looked at the man page was VERIFYLD means). So, if you could try this config script (note the fourth line): (READPORT 0x0203) (ISOLATE) (IDENTIFY *) (VERIFYLD N) (CONFIGURE CTL009e/138029808 (LD 0 # ANSI string --Audio-- (INT 0 (IRQ 5 (MODE +E))) (DMA 0 (CHANNEL 1)) (DMA 1 (CHANNEL 5)) (IO 0 (BASE 0x0220)) (IO 1 (BASE 0x0330)) (IO 2 (BASE 0x0388)) (ACT Y) )) (CONFIGURE CTL009e/138029808 (LD 1 # Compatible device id PNPb02f # ANSI string --Game-- (IO 0 (BASE 0x0200)) (ACT Y) )) (CONFIGURE CTL009e/138029808 (LD 2 # ANSI string --WaveTable-- (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20)) (ACT Y) )) -- I would be really happy if it would work without the POKE's, but with the (VERIFYLD N). It would be whole damn easier for the Newbie. I'm sorry that I rely on you, but I don't encounter such problems, and you are the only person I know of (I'm happy that I have you :)# Thanks you A LOT! Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, Oct 11, 1997 at 10:14:40PM -0200, Nicola Bernardelli wrote: On Fri, 10 Oct 1997, Marcus Brinkmann wrote: On Fri, Oct 10, 1997 at 05:25:56PM -0200, Nicola Bernardelli wrote: Ok, for you HOWTO, I have isapnp working fine now. I find it *really* odd that you have to rearrange the order of the entrys in the isapnp.conf. A *quick* and *dirty* hack, and I can't even think of including it i my HOWTO (I see lots of emails complaining about such an unsure statement :). I can give a hint about it (and I will do), but could you check if the PEEK thing from the faq works for you? Please do it for me, because the faq states, that the standard does not clearly specifiy if it should work without the PEEKS, means, that it is fully legitimate that you have to include the PEEKS. Please try it, thank you! Good news to you Marcus, your POKE way works fine here with the AWE64 Gold, I tried the devices in any of the following sequences always with success: 0 1 2 1 0 2 1 2 0 0 2 1 2 0 1 2 1 0 Thank you, I'm happy to hear this. As I already said, I will include this in my HOWTO. Each time I did these steps (staying inside /etc and after 'mount -r -t msdos /dev/sda1 /mnt/fat1' and after '/etc/init.d/nas stop'): rmmod sound modify isapnp.conf-poke and save it isapnp isapnp.conf-poke insmod sound sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 saytime drvmidi /mnt/fat1/sb16/samples/awe64/*.mid Please, could you also try the following: sfxload -b1 your-path/sample.sbk drvmidi your-path/sfx.midi If you don't have those files, I would be happy to mail them to you (and I hope I would not violate any copyrights :( ). It is important for me, because it didn't worked for me the day before, but now after recompiling with awedrv 0.4.2c it works. (sfx.midi uses some samples in bank 1) Oh, there is another example like this coming with vienna: sfxload -b1 voiperpn.sf2 drvmidi zebraper.mid (you shouldn't hear any piano with this, but I do) Please try those, I have problems with them, they don't play correctly. BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) i don't know. This is a bug, I think. What versions of the awedrv do you have? Did you tried the latest version 0.4.2c? thank you for your effort, and keep going, we nearly made it! Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
In my previous posting, I forgot to attach the isapnp.conf file with the solution suggested by Marcus Brinkmann, here it is. Also, I mentioned kernel 2.1.55 - err... I _have_ problems building it at the moment - but forgot to say that I wanted to test it more for the IPC SHMEM kernel feature needed by SLab-1.0 than for pnp/awe I currently have running via isapnp/awe-debian-packages. SLab seems to be a very interesting package, as for the description... I'm attaching two small files about it, the .lsm file and the system requirements from the readme. Did anybody test this software with Debian (and possibly with an AWE 64 Gold)? Nicola Bernardelli [EMAIL PROTECTED] --- Please use [EMAIL PROTECTED] for messages from any kind of robot, such as mailing lists. From that address no autoresponse messages will come, even when I am away for some days. --- # $Id: pnpdump.c,v 1.8 1997/01/14 21:05:35 fox Exp $ # This is free software, see the sources for details. # This software has NO WARRANTY, use at your OWN RISK # # For details of this file format, see isapnp.conf(5) # # Compiler flags: -DREALTIME -DNEEDSETSCHEDULER # # Trying port address 0203 # Board 1 has serial identifier 7f 08 3a 2a f0 9e 00 8c 0e # (DEBUG) (READPORT 0x0203) (ISOLATE) (IDENTIFY *) # Card 1: (serial identifier 7f 08 3a 2a f0 9e 00 8c 0e) # CTL009e Serial No 138029808 [checksum 7f] # Version 1.0, Vendor version 2.0 # ANSI string --Creative SB AWE64 Gold-- # # Logical device id CTL0044 # (CONFIGURE CTL009e/138029808 (LD 0 # ANSI string --Audio-- (INT 0 (IRQ 5 (MODE +E))) (DMA 0 (CHANNEL 1)) (DMA 1 (CHANNEL 5)) (IO 0 (BASE 0x0220)) (IO 1 (BASE 0x0330)) (IO 2 (BASE 0x0388)) (ACT Y) (REG 7 (POKE 1) (PEEK)) # Set logical device 1, but no check # Logical device id CTL7002 # Compatible device id PNPb02f # ANSI string --Game-- (IO 0 (BASE 0x0200)) (ACT Y) (REG 7 (POKE 2) (PEEK)) # Set logical device 2, but no check # Logical device id CTL0023 # ANSI string --WaveTable-- (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20)) (ACT Y) )) # End tag... Checksum 0x00 (OK)Begin3 Title: SLab Recording Studio Software Version:1.0 Entered-date: May 12, 1997 Description:SLab Direct to Disk Recording Studio. Mixer 64-16-8-4-2 stereo/quadraphonic outputs. Includes WaveEditing, effects send busses, stereo bus groupings, dynamic digital filters (per track), TCL/TK based drag and drop user interface, stereo effects API, VU metering, DSP - echo, chorus, flange, phase, reverb, rotary, limitor, et al, Continuous controller recording (mixdown sessions). MultiProcessing/shared memory mix engine. Kernel requires: 2.1.24, OSS/FREE 3.5.X, SYSV_IPC. System requires: TCL_7.5/TK_4.1, at least the header files. Keywords: audio, mixer, DSP, effects, multitrack, TCL, TK, Linux direct-to-disk recording Author: [EMAIL PROTECTED] (Nick Copeland) Maintained-by: [EMAIL PROTECTED] (Nick Copeland) Primary-site: sunsite.unc.edu /pub/Linux/apps/sound/mixers 2553 kb SLab-1.0.tgz 2 kb SLab-1.0.lsm Alternate-site: Original-site: Platform: Linux - static ELF, binary distribution only. Copying-policy: Shareware End SYSTEM REQUIREMENTS --- This runs and was developed on a P133 16 MB system. Get gobs of disk space if you want to do some real recording, 16 tracks CD quality requires about 80MB a minute. Compression is not going to be available for a while, although if new songs are created with a minimum of predefined run time (5 or 10 seconds) then autoextension on the Linux filesystem will only write new track sections. The consequence is, if you define 16 track, but only ever use 8 simultaneously then the disk space requirements will only be half of the total (and processing capacity is spared). Session recording will allow you to fade tracks in and out as you need them. Linux: IPC SHMEM required in kernel. Software was compiled on a 2.1.24 kernel, and full duplex may require this kernel. OSS/Free 3.5-10b.
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Fri, 10 Oct 1997, Marcus Brinkmann wrote: On Fri, Oct 10, 1997 at 05:25:56PM -0200, Nicola Bernardelli wrote: Ok, for you HOWTO, I have isapnp working fine now. I find it *really* odd that you have to rearrange the order of the entrys in the isapnp.conf. A *quick* and *dirty* hack, and I can't even think of including it i my HOWTO (I see lots of emails complaining about such an unsure statement :). I can give a hint about it (and I will do), but could you check if the PEEK thing from the faq works for you? Please do it for me, because the faq states, that the standard does not clearly specifiy if it should work without the PEEKS, means, that it is fully legitimate that you have to include the PEEKS. Please try it, thank you! Good news to you Marcus, your POKE way works fine here with the AWE64 Gold, I tried the devices in any of the following sequences always with success: 0 1 2 1 0 2 1 2 0 0 2 1 2 0 1 2 1 0 Each time I did these steps (staying inside /etc and after 'mount -r -t msdos /dev/sda1 /mnt/fat1' and after '/etc/init.d/nas stop'): rmmod sound modify isapnp.conf-poke and save it isapnp isapnp.conf-poke insmod sound sfxload -i /mnt/fat1/sb16/sfbank/gm35revc.sf2 saytime drvmidi /mnt/fat1/sb16/samples/awe64/*.mid BTW, why does the sound module say what follows at each startup, when I have the default 4megs on the soundcard? (Sure, on some readme...) AWE32 Sound Driver v0.3.3e (DRAM 28672k) - As for the quick and dirty way I had found of just changing the order of the LDs (0 2 1 works fine as I told, and I didn't try any other), it was a mistake what I said of it working fine only once at boot time, in fact it works any time you recall isapnp, just with the steps above, and the AWE synth part always works fine: I was simply forgetting to reload the soundfonts. - I'm currently trying to build the 2.1.55 kernel, it should handle pnp and AWE (but I may have problems here with Debian 1.2.4... so far I just had to replace genksyms with the one from the 1.3.1 CD for the -k option to be accepted). Nicola Bernardelli [EMAIL PROTECTED] --- Please use [EMAIL PROTECTED] for messages from any kind of robot, such as mailing lists. From that address no autoresponse messages will come, even when I am away for some days. --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Fri, 10 Oct 1997, Marcus Brinkmann wrote: Perhaps there is a newer isapnp out there, that could help you? Did you read the isapnp-faq? Ah, by the time I was popping this message and the one you CCed to the list I was also sending you the workaround I found... OK I'm going to reply you also forwarding that very simple workaround (simple but not digging into problems of the isapnp version I'm using here... anyway those problems are probably solved with the version _you_ mentioned). On Fri, 10 Oct 1997, Marcus Brinkmann wrote: This problem is described in the isapnp-faq (it should really be included in the debian package). I quote it here (Nicola, does it work for you? Please tell me, for the HOWTO) - What does `Error occurred executing request 'LD 2' on or around line...'' mean ? This means that attempting to read back the logical device number failed. The specification is rather unclear on whether this is guaranteed to work, and in any event, it doesn't appear to work with some devices. There are two solutions: 1. Get isapnp version 1.10 or later which supports VERIFYLD. 2. Use direct register access to select the logical device. So instead of configuring each logical device as normal: [snip] The first looks prettier :-) than all those PEEKs, and the following too. another tip: --- The configuration file must end in WAITFORKEY. --- This is the most important hint: Make sure that your isapnp.con contains the two lines i marked with (CONFIGURE CTL0043/54664 (LD 2 # ANSI string --WaveTable-- (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) # (IO 2 (BASE 0x0E20)) # # End dependent functions (ACT Y) )) --- Yes, I took them from Toersten's postings (see also attachments to forwarded message where I found those addresses being correct also for the Gold), he was that suggested to go and look at the AWE driver homepage. Very nice thing to come for everybody your HOWTO, good idea Marcus! Below I forward that message with the workaround, bringing the attachments with itself. Nicola -- Forwarded message -- Date: Fri, 10 Oct 1997 17:25:56 -0200 (GMT+2) From: Nicola Bernardelli [EMAIL PROTECTED] To: Marcus Brinkmann [EMAIL PROTECTED] Cc: Britton [EMAIL PROTECTED] Subject: Re: is the Creative Labs AWE64 GOLD Soundcard supported? Ok, for your HOWTO, I have isapnp working fine now. - you may skip - - I gave a look in my DOS partion at \CTCM\CTPNP.CFG and found that the wavetable addresses (there they are!) that I was trying are correct, so I could forget worries about them and concentrate on isapnp. - I noticed that with an isapnp.conf containing only the wavetable section the MIDI internal synth worked fine; doing a two issues isapnp.conf-allButWaveTable + isapnp.conf-waveTable resulted in AWE synth working but not dsp anymore, so I had to succeed with an only call to isapnp. - I tried the sections in another order, first attempt succeeded, see 3rd attachment. Just curious: trying to redo it after it is succesfully done at boot results in AWE synth no more working (/etc/init.d/nas stop ; rmmod sound ; isapnp /etc/isapnp.conf ; insmod sound ; test with drvmidi). Maybe some other order... - As for Cubasis, I've found something I got ftp (didn't even remember, at what time in the morning did I that?), a multimedia driver... maybe it is already installed though... I'm just sending this then I'm going to Windog to check about that driver. Cheers. Nicola [PNP] ReadPort=20b BypassPnPOS=0 [EXCLUDE] Exclude_Port= Exclude_Irq= Exclude_Dma= Exclude_32Mem= [SB16] Disable=0 Csn=1 CardId=CTL009e Serial=083a2af0 LogDev=0 Port0=220 Port1=330 Port2=388 Irq0=5 Dma0=1 Dma1=5 [GAMEPORT] Disable=0 Csn=1 CardId=CTL009e Serial=083a2af0 LogDev=1 Port0=200 [AWE] Disable=0 Csn=1 CardId=CTL009e Serial=083a2af0 LogDev=2 Port0=620 Port1=a20 Port2=e20 # $Id: pnpdump.c,v 1.8 1997/01/14 21:05:35 fox Exp $ # This is free software, see the sources for details. # This software has NO WARRANTY, use at your OWN RISK # # For details of this file format, see isapnp.conf(5) # # Compiler flags: -DREALTIME -DNEEDSETSCHEDULER # # Trying port address 0203 # Board 1 has serial identifier 7f 08 3a 2a f0 9e 00 8c 0e # (DEBUG) (READPORT 0x0203) (ISOLATE) (IDENTIFY *) # Card 1: (serial identifier 7f 08 3a 2a f0 9e 00 8c 0e) # CTL009e Serial No 138029808 [checksum 7f] # Version 1.0, Vendor version 2.0 # ANSI string --Creative SB AWE64 Gold-- # # Logical device id CTL0044 # (CONFIGURE CTL009e/138029808 (LD 0 # ANSI string --Audio
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Lawrence [EMAIL PROTECTED] writes: No. I start the kernel module via /etc/modules. Just put sound in a line for its own. my /etc/modules is 'auto', what do you think? can I have 'auto' and 'sound' in the file? I don't think so. But with auto setting your sound module will be automatically loaded -- if configured correctly. Edit the file /etc/conf.modules and check if the following line is there: alias block-major-14 sound I load a lot of things using modules (lp, serial, sg, sound, ne) and it works fine. Torsten -- What a depressingly stupid machine The Restaurant at the End of the Universe PGP Public Key is available -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Excuse me Torsten, my mail to you should have gone to the list also, here is what I recall: On Wed, Oct 08, 1997 at 11:38:15AM +0200, Torsten Hilbrich wrote: Lawrence [EMAIL PROTECTED] writes: No. I start the kernel module via /etc/modules. Just put sound in a line for its own. my /etc/modules is 'auto', what do you think? can I have 'auto' and 'sound' in the file? I don't think so. But with auto setting your sound module will be automatically loaded -- if configured correctly. It is indeed possible. auto just launches kerneld, sound just installs the sound module, so that kerneld does not remove it automatically. This is a good idea if you have a post-install that takes a long time (e.g. loading sound font banks (up to 8MB!) or setting the mixer. Edit the file /etc/conf.modules and check if the following line is there: alias block-major-14 sound Can someone explains me the difference to the default alias char-major-14 sound, as modprobe -c tells me? /dev/audio shows me a (c) device. Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Tue, Oct 07, 1997 at 08:38:56PM +0300, [EMAIL PROTECTED] wrote: On Mon, 6 Oct 1997, Ed wrote: $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? I have an AWE 64 GOLD (ok, that's what reads on the box :)) and it works fine with the awedrv made by Takashi Iwai. You can get it from: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/;. And that's GPL'd. Oh, and it is debianized. There are awe-* packages in sound (extra). Just dpkg -i them, and then follow the instructions in my SB AWE HOWTO coming soon :-) I know, I know. Last I checked it was v. 3.3 something, while the newest in 'barbaric' format are 4. something. I couldn't get it working at the time (easily) and it was less than 5 minutes to apply the patches to my kernel, and do couple make;make installs /usr/local. Lazy me. Hmm. I think I saw an AWE HOWTO somewhere a few weeks back. BTW, there's an SB-Awe64 mini-howto in the recent doc packages. How far are you writing? (I'd be more than glad to help, if I can.) --j -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, Oct 08, 1997 at 09:58:36PM +0300, [EMAIL PROTECTED] wrote: On Tue, Oct 07, 1997 at 08:38:56PM +0300, [EMAIL PROTECTED] wrote: On Mon, 6 Oct 1997, Ed wrote: $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? I have an AWE 64 GOLD (ok, that's what reads on the box :)) and it works fine with the awedrv made by Takashi Iwai. You can get it from: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/;. And that's GPL'd. Oh, and it is debianized. There are awe-* packages in sound (extra). Just dpkg -i them, and then follow the instructions in my SB AWE HOWTO coming soon :-) I know, I know. Last I checked it was v. 3.3 something, while the newest in 'barbaric' format are 4. something. I couldn't get it working at the time (easily) and it was less than 5 minutes to apply the patches to my kernel, and do couple make;make installs /usr/local. Lazy me. i already filed a reminder about it to the bug report (no, I don't think it is a bug, just a reminder). Actually, awedrv is in ver 0.4.2c, the actual debian version is ver 0.3.3c Hmm. I think I saw an AWE HOWTO somewhere a few weeks back. BTW, there's an SB-Awe64 mini-howto in the recent doc packages. How far are you writing? (I'd be more than glad to help, if I can.) I have completed 3 chapters out of 4. It will cover installation, configuration and testing (perhaps a note about the apps). I will be announcing it tomorrow. Any help is welcome, and I am looking forward to the bulk of comments, feature requests and bug reports :-) Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Tue, 7 Oct 1997, Britton wrote: I have the awe driver working with the awe 64, I think. At any rate the module loads without any complaints and I can play sound. /dev/mixer is definately not working right, but this is probably something I'm doing wrong. I havn't actually been able to check the wave table device either (I don't really know how yet). I'm doing it just today, now I have it working with the awe 64 Gold (but still must pass via DOS and loadlin, see attachments for the problem I have here with isapnp; I don't have any other pnp cards; I have tried putting in the WaveTable section the two addresses suggested on the list by Torsten Hilbrich but I don't even know if he has the same card... I'll have to dig into the awe driver faq I suppose, where Torsten itself got the info if I didn't misunderstand, at http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/awedrv-faq.html). MIDI files coming from an old (DOS) version of Band-In-A-Box sound as if some events had sustain/last too long here, also after recompiling the kernel with the AWE_ACCEPT_ALL_SOUNDS_CONTROL macro defined in the /usr/src/linux/drivers/sound/lowlevel/awe_config.h header. Other MIDI files seem OK, drvmidi works very fine and so does xmixer (from the multimedia package; I find it more suitable than xmix, but I think the midi synth volume should go on it instead than on the drvmidi panel, it should just be as the Creative mixer... or perhaps Creative should gently... ok, see below). The Netscape plugin: I was not able to test it yet... Just opening a .mid file with Netscape does not seem to be the way. As for the test file /usr/doc/awe/netscape-test.html, I don't see the mentioned .mid files there... so should I just try connecting to any(?) WEB site sending midi music? (I heard nothing at the Creative WEB pages.) (Notice: I will NOT install M$ Internet Explorer nor Web Phone, Linux is too great to have the will to be running other things after quitting them one crash after another.) On Sun, 5 Oct 1997, Marcus Brinkmann wrote: The Awe driver supports a good part of the AWE32 stuff. AWE64 was never intended for other OS than Windows (Creative Labs says, there would be no market for Linux, I think the linux community should ignore SB, if they ignore us). On Mon, 15 Sep 1997 (Subject: Re: SB AWE 64 versus Soft. Syns. for making midi...), Marcus Brinkmann wrote: SB cares nuts about the linux community (they say, the market is not important enough; we will see...), so we are on our own. Yes, we'll see. Ok, we are on this thread because we have a SB or think about buying one... Since January... I was thinking NOT to buy it, but now my brother got married and he's going to take away his MIDI keyboard soon, and I use to learn jazz trumpet impro practicing on drones... (Of course I'll miss the keyboard anyway, useful to look for chords or voicings for some small things of my own, once in a while... better than with the guitar, apart that my first instrument is _classical_ guitar and I don't have many pre-built chords positions handy with it [and don't want to, yet].) I suppose lots of professional studioes currently go with MACs + DigiDesign Tools hardware or the like... I would NOT trust Windog to keep tracks recorded from professional (possibly great) musicians, and this opinion is shared by _some_ people _inside_ that job I could talk to (I met one of them from Detroit just last week and he invited me to his studio in Germany... and he's also interested on Linux, BTW!). Instead I think it is a gift _from_ the Linux community _to_ Creative Labs the chance to have Creative hardware/software running on such a fast/robust/flexible system as Linux is. And last, I think that a lot of Linux guys (me too apart from my brother's marriage) hearing about other guys spending hours and hours for the AWE64 Gold to play as an AWE32 will think twice before buying it, which is a pity because the card seems a nice product to me... not the same opinion about Windog. BTW, I still have 3.1 here, a wreck, but 95 seems to be at the same quality level (one friend of mine is still going home-shop after months she bought 95 and Office 97 planning to use that stuff for her work) so I refused to get it. The Steinberg Cubasis Audio software given with the AWE64 Gold can't work all right almost on Windog 3.1, it doesn't play/record audio tracks (the small Creative application does it fine... maybe it's better to start the recording _before_ than starting e.g. a MIDI playback with the media player, otherwise the Creative recorder [or some Windog DLL or whatelse] is pessimistic and says the card is used by another device... and so seems to do the Steinberg software, while the card has no problems in reproducing while recording, as anyway the Creative recorder/player and mixer prove). Well, I think I could put some money on the Steinberg software released for Linux... the complete
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Wed, 8 Oct 1997, Nicola Bernardelli wrote: Other MIDI files seem OK, drvmidi works very fine and so does xmixer (from the multimedia package; I find it more suitable than xmix, but I think the midi synth volume should go on it instead than on the drvmidi panel...) Sorry, didn't think AWE synth is equivalent to FM (it isn't as to the Creative doc files)... anyway there it goes on xmixer. Nicola -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, 6 Oct 1997, Ed wrote: $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? I have an AWE 64 GOLD (ok, that's what reads on the box :)) and it works fine with the awedrv made by Takashi Iwai. You can get it from: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/;. And that's GPL'd. Marcus --j -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Tue, Oct 07, 1997 at 08:38:56PM +0300, [EMAIL PROTECTED] wrote: On Mon, 6 Oct 1997, Ed wrote: $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? I have an AWE 64 GOLD (ok, that's what reads on the box :)) and it works fine with the awedrv made by Takashi Iwai. You can get it from: http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/;. And that's GPL'd. Oh, and it is debianized. There are awe-* packages in sound (extra). Just dpkg -i them, and then follow the instructions in my SB AWE HOWTO coming soon :-) Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Pete Harlan wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? The alternative to doing backflips getting this card to work under Linux is to pay $20 to 4front-tech for their commercial driver for Linux. It's hassle-free, works, and is good for five years of upgrades. But it's not as cool as getting it to work for free (though you'll need to spend the $20 anyway on a hat after you tear your hair out). $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, 6 Oct 1997, Ed wrote: Pete Harlan wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? The alternative to doing backflips getting this card to work under Linux is to pay $20 to 4front-tech for their commercial driver for Linux. It's hassle-free, works, and is good for five years of upgrades. But it's not as cool as getting it to work for free (though you'll need to spend the $20 anyway on a hat after you tear your hair out). $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? Marcus -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, 6 Oct 1997, Ed wrote: Pete Harlan wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? The alternative to doing backflips getting this card to work under Linux is to pay $20 to 4front-tech for their commercial driver for Linux. It's hassle-free, works, and is good for five years of upgrades. But it's not as cool as getting it to work for free (though you'll need to spend the $20 anyway on a hat after you tear your hair out). $30. 30 dollars, US, I tell you. If you read the fine print at 4front, you will find a 10 dollar surcharge for AWE 32/64 support. Let me say that the awe driver package works just fine with a SB AWE32. Don`t know about the 64 yet. Any people tried? I have the awe driver working with the awe 64, I think. At any rate the module loads without any complaints and I can play sound. /dev/mixer is definately not working right, but this is probably something I'm doing wrong. I havn't actually been able to check the wave table device either (I don't really know how yet). Marcus -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . Britton Kerin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Mon, Oct 06, 1997 at 07:49:34AM +1000, Lawrence wrote: Marcus Brinkmann wrote: How your isapnp.conf file looks like? can you send it to me? Just done a minute ago (anyone else?) You just have to install and congfigure isapnp, that it is (and add the sound module to the modules autoloaded at boot time, if you want. You can even load a sound font bank at boot time). do you mean to let kerneld to load the sound module? No. I start the kernel module via /etc/modules. Just put sound in a line for its own. You can even load a sound fount at boot time: Put in /etc/conf.modules: post-install sound /usr/bin/sfxload -i 2mbgmgs.sf2 or any other sound font bank in /usr/lib/awe/sfbank/ (version 1 or 2). Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Marcus Brinkmann wrote: On Mon, Oct 06, 1997 at 07:49:34AM +1000, Lawrence wrote: Marcus Brinkmann wrote: How your isapnp.conf file looks like? can you send it to me? Just done a minute ago (anyone else?) You just have to install and congfigure isapnp, that it is (and add the sound module to the modules autoloaded at boot time, if you want. You can even load a sound font bank at boot time). do you mean to let kerneld to load the sound module? No. I start the kernel module via /etc/modules. Just put sound in a line for its own. my /etc/modules is 'auto', what do you think? can I have 'auto' and 'sound' in the file? You can even load a sound fount at boot time: Put in /etc/conf.modules: post-install sound /usr/bin/sfxload -i 2mbgmgs.sf2 or any other sound font bank in /usr/lib/awe/sfbank/ (version 1 or 2). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? The alternative to doing backflips getting this card to work under Linux is to pay $20 to 4front-tech for their commercial driver for Linux. It's hassle-free, works, and is good for five years of upgrades. But it's not as cool as getting it to work for free (though you'll need to spend the $20 anyway on a hat after you tear your hair out). -- Pete Harlan [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sun, 5 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 04, 1997 at 11:28:24AM -0800, Britton wrote: On Sat, 4 Oct 1997, Paul Miller wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? It will act like a SB16 yes, but this is nothing wonderful, as the SB16 is quite pathetic. xmix is the only program I've run into with a line select (which you need since the SB 16 has no input mixer). And it should act like a AWE-32, because I have the suspicion, that they mostly enchanced the software driver, not the hardware. (I wouldn't be surprised, if the hardware is nearly the same. I have a AWE32 with the 64upgrade, and they say that I have a functionally AWE64, so it is another sort of Winsoundcard) What you want is awedrv, which is available as a debian source package. Trouble is, it won't compile as a module, which I think means you have to use initrd to run isapnp before it will work. I've read the initrd stuff, You HAVE to install it as a module, because isapnp must be started first, and then the sound module has to be installed. In fact, isapnp will be started automagically by the current initrd scripts, so you have just to install it, and add two entrys two the isapnp config file (mail me for more info). I believe I have isapnp.conf set up correctly in /usr/local as I needed to use it (and a modularized version of the SB 16 driver) to get any sound at all. However... When I selected the additional low level drivers option and then the awe driver option, and compile, I didn't find anything in /usr/src/linux/modules, where the sound module always showed up before. Have you actually found this file there? Whould the option for the awedrv even show up in 'make menuconfig' if there was a problem with the included patching script? (I assumed it would not, and the script did not report any problems). but havn't gotten around to trying it yet. Am I right in my understanding that you just need to copy over a rescue disk, isapnp, and possible bash (to write initrc with) into the initrd environment? Anyone done this? You just have to install and congfigure isapnp, that it is (and add the sound module to the modules autoloaded at boot time, if you want. You can even load a sound font bank at boot time). The awedrv does not support all the SB 64 capabilities, but from what I understand the extra channels are provided by software anyway. Yup. The Awe driver supports a good part of the AWE32 stuff. AWE64 was never intended for other OS than Windows (Creative Labs says, there would be no market for Linux, I think the linux community should ignore SB, if they ignore us). Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, Oct 04, 1997 at 04:35:21PM -0800, Britton wrote: On Sun, 5 Oct 1997, Marcus Brinkmann wrote: On Sat, Oct 04, 1997 at 11:28:24AM -0800, Britton wrote: What you want is awedrv, which is available as a debian source package. Trouble is, it won't compile as a module, which I think means you have to use initrd to run isapnp before it will work. I've read the initrd stuff, You HAVE to install it as a module, because isapnp must be started first, and then the sound module has to be installed. In fact, isapnp will be started automagically by the current initrd scripts, so you have just to install it, and add two entrys two the isapnp config file (mail me for more info). I believe I have isapnp.conf set up correctly in /usr/local as I needed to use it (and a modularized version of the SB 16 driver) to get any sound at all. However... When I selected the additional low level drivers option and then the awe driver option, and compile, I didn't find anything in /usr/src/linux/modules, where the sound module always showed up before. Have you actually found this file there? Whould the option for the awedrv even show up in 'make menuconfig' if there was a problem with the included patching script? (I assumed it would not, and the script did not report any problems). Mmmh. I use the kernelpackage, and it installed the file sound.o just under /lib/modules/2.0.29/misc, where it belongs to... no problems at all. Are you sure you choosed the awe driver as a module? Are you sure you did the kernel compile right? Try using the kernel-package from debian. Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
You HAVE to install it as a module, because isapnp must be started first, and then the sound module has to be installed. In fact, isapnp will be started automagically by the current initrd scripts, so you have just to install it, and add two entrys two the isapnp config file (mail me for more info). I believe I have isapnp.conf set up correctly in /usr/local as I needed to use it (and a modularized version of the SB 16 driver) to get any sound at all. However... When I selected the additional low level drivers option and then the awe driver option, and compile, I didn't find anything in /usr/src/linux/modules, where the sound module always showed up before. Have you actually found this file there? Whould the option for the awedrv even show up in 'make menuconfig' if there was a problem with the included patching script? (I assumed it would not, and the script did not report any problems). Mmmh. I use the kernelpackage, and it installed the file sound.o just under /lib/modules/2.0.29/misc, where it belongs to... no problems at all. The trick is not to forget to do 'make modules'. This was all a mistake on my part, you most certainly do not have to use initrd. Sorry if I have caused anyone any confusion. Are you sure you choosed the awe driver as a module? Are you sure you did the kernel compile right? Try using the kernel-package from debian. Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
Marcus Brinkmann wrote: On Sat, Oct 04, 1997 at 11:28:24AM -0800, Britton wrote: On Sat, 4 Oct 1997, Paul Miller wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? It will act like a SB16 yes, but this is nothing wonderful, as the SB16 is quite pathetic. xmix is the only program I've run into with a line select (which you need since the SB 16 has no input mixer). And it should act like a AWE-32, because I have the suspicion, that they mostly enchanced the software driver, not the hardware. (I wouldn't be surprised, if the hardware is nearly the same. I have a AWE32 with the 64upgrade, and they say that I have a functionally AWE64, so it is another sort of Winsoundcard) What you want is awedrv, which is available as a debian source package. Trouble is, it won't compile as a module, which I think means you have to use initrd to run isapnp before it will work. I've read the initrd stuff, You HAVE to install it as a module, because isapnp must be started first, and then the sound module has to be installed. In fact, isapnp will be started automagically by the current initrd scripts, so you have just to install it, and add two entrys two the isapnp config file (mail me for more info). but havn't gotten around to trying it yet. Am I right in my understanding that you just need to copy over a rescue disk, isapnp, and possible bash (to write initrc with) into the initrd environment? Anyone done this? How your isapnp.conf file looks like? can you send it to me? You just have to install and congfigure isapnp, that it is (and add the sound module to the modules autoloaded at boot time, if you want. You can even load a sound font bank at boot time). do you mean to let kerneld to load the sound module? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
is the Creative Labs AWE64 GOLD Soundcard supported?
How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? -Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, 4 Oct 1997, Paul Miller wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? It will act like a SB16 yes, but this is nothing wonderful, as the SB16 is quite pathetic. xmix is the only program I've run into with a line select (which you need since the SB 16 has no input mixer). What you want is awedrv, which is available as a debian source package. Trouble is, it won't compile as a module, which I think means you have to use initrd to run isapnp before it will work. I've read the initrd stuff, but havn't gotten around to trying it yet. Am I right in my understanding that you just need to copy over a rescue disk, isapnp, and possible bash (to write initrc with) into the initrd environment? Anyone done this? The awedrv does not support all the SB 64 capabilities, but from what I understand the extra channels are provided by software anyway. -Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: is the Creative Labs AWE64 GOLD Soundcard supported?
On Sat, Oct 04, 1997 at 11:28:24AM -0800, Britton wrote: On Sat, 4 Oct 1997, Paul Miller wrote: How well/is the AWE64 GOLD Sound card supported under Linux? ..or will it act/function like the SB16? It will act like a SB16 yes, but this is nothing wonderful, as the SB16 is quite pathetic. xmix is the only program I've run into with a line select (which you need since the SB 16 has no input mixer). And it should act like a AWE-32, because I have the suspicion, that they mostly enchanced the software driver, not the hardware. (I wouldn't be surprised, if the hardware is nearly the same. I have a AWE32 with the 64upgrade, and they say that I have a functionally AWE64, so it is another sort of Winsoundcard) What you want is awedrv, which is available as a debian source package. Trouble is, it won't compile as a module, which I think means you have to use initrd to run isapnp before it will work. I've read the initrd stuff, You HAVE to install it as a module, because isapnp must be started first, and then the sound module has to be installed. In fact, isapnp will be started automagically by the current initrd scripts, so you have just to install it, and add two entrys two the isapnp config file (mail me for more info). but havn't gotten around to trying it yet. Am I right in my understanding that you just need to copy over a rescue disk, isapnp, and possible bash (to write initrc with) into the initrd environment? Anyone done this? You just have to install and congfigure isapnp, that it is (and add the sound module to the modules autoloaded at boot time, if you want. You can even load a sound font bank at boot time). The awedrv does not support all the SB 64 capabilities, but from what I understand the extra channels are provided by software anyway. Yup. The Awe driver supports a good part of the AWE32 stuff. AWE64 was never intended for other OS than Windows (Creative Labs says, there would be no market for Linux, I think the linux community should ignore SB, if they ignore us). Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
