Audigy1 MIDI input, wavetable support?

Audigy1 MIDI input, wavetable support?

[Mark J Roberts]

I am trying to load a soundfont into my Audigy1's wavetable and play
it with a MIDI keyboard. I am using kernel 2.5.64.

MIDI output verifiably works. However, MIDI input does not. The
cable and keyboard are not the problem--I've tried them with an
es1371, and I easily got MIDI input working.

My procedure with the Audigy1:

	cat /dev/snd/midiC0D0
	watch /proc/interrupts
	watch /proc/asound/Audigy/midi0

No interrupts occur and no bytes are read. I have also tried using
aconnect to connect the inputs. Does anyone else see this behavior?

I've got one more question. What program should I use to configure
the wavetable and load the soundfonts? I found a couple versions of
"awesfx", neither of which was compatible with my ALSA.


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: Audigy1 MIDI input, wavetable support?

[Josh Green]

On Fri, 2003-03-07 at 07:44, Mark J Roberts wrote:
> I am trying to load a soundfont into my Audigy1's wavetable and play
> it with a MIDI keyboard. I am using kernel 2.5.64.
> 
> MIDI output verifiably works. However, MIDI input does not. The
> cable and keyboard are not the problem--I've tried them with an
> es1371, and I easily got MIDI input working.
> 
> My procedure with the Audigy1:
> 
> 	cat /dev/snd/midiC0D0
> 	watch /proc/interrupts
> 	watch /proc/asound/Audigy/midi0
> 
> No interrupts occur and no bytes are read. I have also tried using
> aconnect to connect the inputs. Does anyone else see this behavior?
> 
> I've got one more question. What program should I use to configure
> the wavetable and load the soundfonts? I found a couple versions of
> "awesfx", neither of which was compatible with my ALSA.
> 
> 

I know that ALSA contains support for the wavetable of the EMU8k and
EMU10k series of cards (AWE 32/64 and Live! respectively). I'm not
absolutely sure whether the wavetable on the Audigy is also supported,
but chances are it is. The SoundFont loading API is OSS based, but ALSA
uses it so awesfx (sfxload utility, etc) should work (provided the API
is actually there for the Audigy).
I'm convinced that software synthesis is the way to go. It allows for
easier routing of the synthesized data (via Jack for example) and
supports any sound card. This is the approach I have gone with with
Swami (http://swami.sourceforge.net) the successor to the Smurf
SoundFont Editor which was based on the OSS awesfx API. Swami uses
FluidSynth (http://www.fluid-synth.org - was previously called
iiwusynth) to do software synthesis of SoundFont files. Using software
synthesis gives us these additional features over current Linux
supported hardware solutions:

- Modulator support, allowing for real time modulation of effects with
MIDI controllers (or with GUI controls from Swami)
- Customizable Reverb/Chorus (EMU10k doesn't have support for these
effects in Linux)
- Routing of audio via Jack, opening up a whole world of audio
processing, effects, etc.

The downside is of course the CPU usage, so in the future I will likely
be re-adding support to Swami for the hardware wavetable OSS API.

If you want to check these projects out, you can either wait a few days
for FluidSynth 1.0 to be released which a release of Swami will follow
shortly after, or you can get Swami CVS and FluidSynth CVS. Cheers.
	Josh Green



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: Audigy1 MIDI input, wavetable support?

[Mark J Roberts]

Josh Green:
> If you want to check these projects out, you can either wait a few days
> for FluidSynth 1.0 to be released which a release of Swami will follow
> shortly after, or you can get Swami CVS and FluidSynth CVS. Cheers.

Thanks for all the help. Savannah CVS is giving me unexpected EOFs
at the moment, so I just tried iiwusynth 0.2.1. I'm very impressed.
It worked right out of the box.

Do you have support in the works for DLS/Gigastudio format? I'd be
thrilled if I could get that working.


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: Audigy1 MIDI input, wavetable support?

[Manuel Jander]

Hi,

I would like to comment something about that Software / Hardware 
wavetable issue:

-Most today soundboards use software wavetable anyway. So having one generic
wavetable engine should work for all of them. The idea is to share the 
effort; one for all.

-Some soundcards if not all of them use multiple PCM channels using a 
hardware mixer
and sometimes some hardware efects (modulation on the trident for 
example). I think,
a good approach would be a software wavetable engine that makes use of 
as many hardware
PCM channels as avaiable, and allows some kind of hardware effects 
through callbacks to set
hardware effect parameters. If the driver developer lets them empty, 
just nothing happens
or a software fallback is used.

Best Regards

Manuel Jander.

Josh Green wrote:

>On Fri, 2003-03-07 at 07:44, Mark J Roberts wrote:
>  
>
>>I am trying to load a soundfont into my Audigy1's wavetable and play
>>it with a MIDI keyboard. I am using kernel 2.5.64.
>>
>>MIDI output verifiably works. However, MIDI input does not. The
>>cable and keyboard are not the problem--I've tried them with an
>>es1371, and I easily got MIDI input working.
>>
>>My procedure with the Audigy1:
>>
>>	cat /dev/snd/midiC0D0
>>	watch /proc/interrupts
>>	watch /proc/asound/Audigy/midi0
>>
>>No interrupts occur and no bytes are read. I have also tried using
>>aconnect to connect the inputs. Does anyone else see this behavior?
>>
>>I've got one more question. What program should I use to configure
>>the wavetable and load the soundfonts? I found a couple versions of
>>"awesfx", neither of which was compatible with my ALSA.
>>
>>
>>    
>>
>
>I know that ALSA contains support for the wavetable of the EMU8k and
>EMU10k series of cards (AWE 32/64 and Live! respectively). I'm not
>absolutely sure whether the wavetable on the Audigy is also supported,
>but chances are it is. The SoundFont loading API is OSS based, but ALSA
>uses it so awesfx (sfxload utility, etc) should work (provided the API
>is actually there for the Audigy).
>I'm convinced that software synthesis is the way to go. It allows for
>easier routing of the synthesized data (via Jack for example) and
>supports any sound card. This is the approach I have gone with with
>Swami (http://swami.sourceforge.net) the successor to the Smurf
>SoundFont Editor which was based on the OSS awesfx API. Swami uses
>FluidSynth (http://www.fluid-synth.org - was previously called
>iiwusynth) to do software synthesis of SoundFont files. Using software
>synthesis gives us these additional features over current Linux
>supported hardware solutions:
>
>- Modulator support, allowing for real time modulation of effects with
>MIDI controllers (or with GUI controls from Swami)
>- Customizable Reverb/Chorus (EMU10k doesn't have support for these
>effects in Linux)
>- Routing of audio via Jack, opening up a whole world of audio
>processing, effects, etc.
>
>The downside is of course the CPU usage, so in the future I will likely
>be re-adding support to Swami for the hardware wavetable OSS API.
>
>If you want to check these projects out, you can either wait a few days
>for FluidSynth 1.0 to be released which a release of Swami will follow
>shortly after, or you can get Swami CVS and FluidSynth CVS. Cheers.
>	Josh Green
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
>for complex code. Debugging C/C++ programs can leave you feeling lost and 
>disoriented. TotalView can help you find your way. Available on major UNIX 
>and Linux platforms. Try it free. www.etnus.com
>_______________________________________________
>Alsa-devel mailing list
>Alsa-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
>.
>
>  
>




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: [linux-audio-dev] Re: Audigy1 MIDI input, wavetable support?

[Josh Green]

On Fri, 2003-03-07 at 15:29, Mark J Roberts wrote:
> Josh Green:
> > If you want to check these projects out, you can either wait a few days
> > for FluidSynth 1.0 to be released which a release of Swami will follow
> > shortly after, or you can get Swami CVS and FluidSynth CVS. Cheers.
> 
> Thanks for all the help. Savannah CVS is giving me unexpected EOFs
> at the moment, so I just tried iiwusynth 0.2.1. I'm very impressed.
> It worked right out of the box.
> 
> Do you have support in the works for DLS/Gigastudio format? I'd be
> thrilled if I could get that working.

Actually, yes :) I'm currently working right now with DLS support (like
within the last few days). I have put a lot of work into getting the
archetecture in place in Swami to support different patch formats.
DLS2/Gigastudio is the first other format I am adding (I have not yet
researched what additional info is added by Gigastudio, if any). I
currently have all the run time objects defined as well as the DLS
loader, just haven't tested it yet. This is all with the new Swami
branch, which is not quite ready for public consumption. FluidSynth is
most likely going to stay SoundFont based, which isn't really a problem,
since it has a nice API that allows for other formats to be synthesized
(within the scope of a SoundFont of course). If you would like to know
when this stuff is available, you could join the swami-devel list
(http://lists.sourceforge.net/lists/listinfo/swami-devel) it currently
has very little traffic, so no worries there. I'm really excited about
where Swami is going, its somewhat of a slow process, but it is
definately getting there :) Cheers.
	Josh Green



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: Audigy1 MIDI input, wavetable support?

[Takashi Iwai]

At Fri, 7 Mar 2003 09:44:02 -0600,
Mark J Roberts wrote:
> 
> I am trying to load a soundfont into my Audigy1's wavetable and play
> it with a MIDI keyboard. I am using kernel 2.5.64.
> 
> MIDI output verifiably works. However, MIDI input does not. The
> cable and keyboard are not the problem--I've tried them with an
> es1371, and I easily got MIDI input working.
> 
> My procedure with the Audigy1:
> 
> 	cat /dev/snd/midiC0D0
> 	watch /proc/interrupts
> 	watch /proc/asound/Audigy/midi0
> 
> No interrupts occur and no bytes are read. I have also tried using
> aconnect to connect the inputs. Does anyone else see this behavior?

which midi connector are you using?

audigy have two MPU401 connectors.
the first one is assigned to the gameport and the second one to the
connect on the audigy-drive.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Audigy1 MIDI input, wavetable support?

[Mark J Roberts]

Takashi Iwai:
> which midi connector are you using?
> 
> audigy have two MPU401 connectors.
> the first one is assigned to the gameport and the second one to the
> connect on the audigy-drive.

I tried the gameport on the audigy1, since I don't have an audigy1
drive.

I _do_ have an audigy2 drive (at the moment my config is audigy2 +
es1371, which is the only card I've got that will do midi in) and
like I posted before I've tried both the gameport and the drive
midi, and they have the same output-only behavior.

I wonder if anyone has working audigy midi in...


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf