ok, i guess you can tell me the truth now: does anybody really understand
all those "items" appearing in alsamixer for the audiophile 2496 ? or am
i the only ignorant?
i only use the analog input and output, by the way. the card is simple
enough, and for me it "just works", but i really have no idea about these:
IEC958 --> you can switch between IEC958 I, Digital and H/W In from 0 to 7;
what's all that supposed to mean?
IEC958 Multi and IEC958 Multi 1 --> two sliders that don't do nothin' i can
see/hear...
IEC958 1 --> similar to the other one above, and equally mysterious.
DAC and DAC 1 --> well, at least i understand those two...
Deemphasis --> hmm... i don't understand this one either, but i don't care
much for whatever it is. i think.
H/W and H/W 1 --> switches between PCM Out0, H/W In 0 to 7, and IEC958 I; if
i choose H/W In 0 i can monitor while recording but no playback, choosing
PCM Out0 it's the opposite.
H/W Multi and H/W Multi 1 --> sliders, no idea what.
Multi to Multi 9 --> a series of sliders, also no idea.
Multi Track Internal Clock --> switches between different clock rates, don't
know what's its use.
Multi Track Peak, Multi Track Rate Reset, etc --> another set of sliders of
unknown nature.
as you can see, alsamixer is mostly a complete and obscure mystery for me.
could anyone explain what does all that mean? or point me to a document
where it's well explained?
what i would like to do, if possible, is:
- being able to monitor both while recording and playback without having to
change the mixer configuration
- record (with arecord, for example) from soundcard output; that is, capture
what's being reproduced.
- control analog input volume while recording (i can only see playback
volume).
please excuse me that i'm being so ignorant and stupid, but i've been using
linux for only six years, alsa for only five, and this card for only one
year, so i'm still a newbie.
best regards and thanks for your attention,
lj
--
Hi,
I have a synthesizer whose knobs send out NRPN data. They only have a
12-bit range (0 - 4095), not the usual 14-bit range.
I'd like to be able to turn one of these knobs, filter the NRPN data
into CC data (range 0 - 127), assign it to some arbitrary CC, and then
send it to either some running MIDI-capable software or out to my
CC-accepting drum machine, with as low latency as possible.
So far I've found Div's MIDI Utilities for Unix. Are these tools the
most appropriate for the job? Or are there other more recent things for
me to look at? It looks like I'd have to write some code to get what I
want with Div's utils, so I just want to check I don't do something
totally redundant. In windows, MIDI-Ox handled it fairly well, but I
don't need anything so complex, just a filter is fine.
http://www.sreal.com:8000/~div/midi-utilities-for-unix/
Cheers,
Chris
Hi all
Just wondering whether it is possible to change the inputs and outs to
either -10, consumer, or +4 in envy24 control, like you can with the
Windows delta control panel?
Thanks
Luke
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
Chris Pickett wrote:
> > Clemens Ladisch wrote:
> >>CONFIG_USB_MIDI is not the ALSA driver but the old OSS driver.
> >>You want to use CONFIG_SND_USB_AUDIO instead.
> >
> > Regardless of whether or not CONFIG_SND_USB_AUDIO is a module, I now
> > only get:
> >
> > usb 1-1: new full speed USB device using address 2
> >
> > in /var/log/messages. 'modprobe snd-usb-audio vid=0x0582 pid=0x0015'
> > doesn't help the situation. 'amidi -l' only shows me my Crystal
> > SoundFusion card.
> >
> >>The ALSA driver supports both driver modes.
>
> I tried switching the UM-880 back to the FPT mode, and it works now. I
> don't know if that's a regression, but in any case I'll try out patches
> for you if it's something you want to fix.
The "generic driver mode" descriptors aren't fully compliant with the USB MIDI
specification, because it doesn't have an AudioControl interface, which is
mandatory. You can say that an AudioControl interface is meaningless here
because the UM-880 has no audio function incorporated, only MIDI. That is
true, but in this case the class-specific AC interface descriptor will only
contain the header descriptor. Did you see a kernel/syslog complain about
"cannot find HEADER" or something like that?
The usb-midi OSS driver doesn't look for AC descriptor, so it can handle it.
But as Clemens said, that driver is not supported by Rosegarden.
Regards,
Pedro
Believe it or not, I've only just (bothered to) get ALSA working on my
system (Debian Sarge snapshot a couple of months old)
I have a M-Audio DiO 2448, and the primary reason for choosing it was
for S/PDIF digital input. That worked with the OSS drivers (paid for...)
- now how do I control the S/PDIF input with ALSA?
The driver module is snd-cmipci.
--
Anahata
anahata(a)treewind.co.uk -+- http://www.treewind.co.uk
Home: 01638 720444 Mob: 07976 263827
Hi Clemens (or others, if you can help),
I am trying to get my Edirol UM-880 to work with Rosegarden-4.0.9.7 and
alsa-1.0.4. This is a rackmount USB 8x8 MIDI interface. I have a
gentoo-2.6.5-r1 kernel with USB support compiled in.
------------------
/usr/src/linux # grep -i midi .config
CONFIG_SND_RAWMIDI=y
# CONFIG_SND_VIRMIDI is not set
CONFIG_USB_MIDI=y
------------------
The first thing I noticed is that it doesn't work with the default
Edirol driver, about which the manual says:
------------------
FPT technology will be used to perform high-speed MIDI transfer. We
recommend that you normally use this mode. FPT = Fast Processing
Technology of MIDI Transmission -- this optimizes MIDI data
processing by making efficient use of the USB bandwidth according to
the amount of MIDI data being transferred.
------------------
I get the following in /var/log/messages when I plug in a USB cable with
this driver enabled in the hardware:
------------------
usb 1-1: new full speed USB device using address 2
midi: probe of 1-1:1.0 failed with error -5
------------------
To change this, you have to follow the instructions in the manual to use
the generic driver mode. Ok, fine. I'm guessing Edirol isn't likely to
release specs for the fancy one, but I haven't gone about asking.
Now /var/log/messages shows me:
------------------
usb 1-1: new full speed USB device using address 3
usb-midi: Found MIDISTREAMING on dev 0582:0015, iface 0
usb-midi: Found MIDIStreaming device corresponding to Release 1.00 of spec.
usb-midi: Found IN Jack 0x10 EMBEDDED
usb-midi: Found IN Jack 0x11 EMBEDDED
usb-midi: Found IN Jack 0x12 EMBEDDED
usb-midi: Found IN Jack 0x13 EMBEDDED
usb-midi: Found IN Jack 0x14 EMBEDDED
usb-midi: Found IN Jack 0x15 EMBEDDED
usb-midi: Found IN Jack 0x16 EMBEDDED
usb-midi: Found IN Jack 0x17 EMBEDDED
usb-midi: Found IN Jack 0x18 EMBEDDED
usb-midi: Found IN Jack 0x20 EXTERNAL
usb-midi: Found IN Jack 0x21 EXTERNAL
usb-midi: Found IN Jack 0x22 EXTERNAL
usb-midi: Found IN Jack 0x23 EXTERNAL
usb-midi: Found IN Jack 0x24 EXTERNAL
usb-midi: Found IN Jack 0x25 EXTERNAL
usb-midi: Found IN Jack 0x26 EXTERNAL
usb-midi: Found IN Jack 0x27 EXTERNAL
usb-midi: Found IN Jack 0x28 EXTERNAL
usb-midi: Found OUT Jack 0x30 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x31 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x32 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x33 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x34 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x35 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x36 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x37 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x38 EMBEDDED, 1 pins
usb-midi: Found OUT Jack 0x40 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x41 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x42 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x43 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x44 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x45 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x46 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x47 EXTERNAL, 1 pins
usb-midi: Found OUT Jack 0x48 EXTERNAL, 1 pins
string descriptor 0 found (length = 4)
usb-midi: langid(0) 0x0409
usb-midi: langid(match) 0x0409
usb-midi: fetchString(2)
usb-midi: fetchString = 13
usbmidi: found [ EDIROL UM-880 ] (0x0582:0x0015), attached:
usbmidi: /dev/midi01: in (ep:81 cid: 0 bufsiz:64) out (ep:01 cid: 0
bufsiz:64)
usbmidi: /dev/midi02: in (ep:81 cid: 1 bufsiz:64) out (ep:01 cid: 1
bufsiz:64)
usbmidi: /dev/midi03: in (ep:81 cid: 2 bufsiz:64) out (ep:01 cid: 2
bufsiz:64)
usbmidi: /dev/midi04: in (ep:81 cid: 3 bufsiz:64) out (ep:01 cid: 3
bufsiz:64)
------------------
Which looks a lot more promising.
However, when I start rosegardensequencer, it doesn't show up:
------------------
Rosegarden 4-0.9.7 - AlsaDriver - alsa-lib version 1.0.4
JackDriver::initialiseAudio - JACK server not running
JackDriver::~JackDriver
JackDriver::~JackDriver: terminating buss mixer
JackDriver::~JackDriver: terminating instrument mixer
JackDriver::~JackDriver: terminating file reader
JackDriver::~JackDriver: terminating file writer
JackDriver: deleting mixers etc
JackDriver::~JackDriver exiting
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (WRITE ONLY)
[ctype 2, ptype 2, cap 99]
64,0 - (CS46XX - Rawmidi 0, CS46XX) (DUPLEX) [ctype
2, ptype 2, cap 127]
128,0 - (Rosegarden sequencer, Rosegarden) (WRITE ONLY)
[ctype 1, ptype 1048576, cap 99]
Creating device 0 in Play mode for connection 64:0 CS46XX (duplex)
Default device name for this device is MIDI external device
Creating device 1 in Record mode for connection 64:0 CS46XX (duplex)
Default device name for this device is MIDI hardware input device
Creating device 2 in Play mode for connection 128:0 Rosegarden (write)
Default device name for this device is MIDI software device
Creating device 3 in Play mode for connection 62:0 Midi Through Port-0
(write)
Default device name for this device is MIDI output system device
Current timer set to "system timer"
Record port set to (64, 0)
AlsaDriver::initialiseMidi - initialised MIDI subsystem
rosegarden (sequencer): RosegardenSequencer - started OK
------------------
I think I'm expecting to see another DUPLEX device, perhaps numbered
65,0. If I disconnect the USB cable, there is no change in the
rosegardensequencer messages. alsa-patch-bay doesn't show me the UM-880
either, and there is no change with or without the cable connected.
Finally, '/etc/init.d/alsasound restart' doesn't fix things.
So ... what am I missing here? I looked in various places but couldn't
find any information about what I need to do.
Cheers,
Chris
On my system, I using Planet CCRMA vintage March 2003. Realplay
version 8.0.3.421 and sfxload version 0.4.3; when I need to boot
my system, I must follow the procedure below to get realplay to
work when I load a soundfont to my sblive card. Today I had to
re-discover this sequence for the N-th time so I wrote it down.
I'm posting it here in hopes it will help someone; I don't
understand why it works, but it does, on my system.
How to get realplay to work after using sfxload to load a soundfont
to a SB-Live card. (Assume you've done a reboot of system, logged
in as a user to KDE.)
1-- Before using sfxload, start realplayer first.
Connect to internet and open a location such
as http://www.jazz.fm/liveg2.ra ; realplay
plays the stream.
1.1-- I usually start AlsaPatchBay and AlsaMixer at
this point; it doesn't seem to matter whether this
is done at this stage or later.
2-- While realplay is playing the stream, load the
soundfont; on my sys sfxload 4marv/soundfonts/FluidR3_20GM.SF2
On my sys, the stream must be playing. During the
loading of the soundfont the stream playing stops and
and realplay says "Buffering". After the font is loaded,
hit the stop button on realplay and re-connect to the location.
The stream will start playing again.
After this sequence, I can quit out of realplay and restart is
without getting the dread "cannot open the sound device..."
message.
If realplay is not up and actively playing a stream when
sfxload loads the soundfont, realplay will not find the
sound device. And my system must re-booted. Logging
out and back in, does not work. The soundfont load
does not survive the boot.
That's unfortunate but par for the course for some manufactures. Is there
an RME option that has s/pdif in/out only?
Matthew Polashek
> ----------
> From: Peter Lutek
> Reply To: plutek(a)infinity.net;A list for linux audio users
> Sent: Friday, May 14, 2004 11:38 AM
> To: A list for linux audio users
> Subject: Re: [linux-audio-user] Digital Audio Labs card
>
> On Fri, 2004-05-14 at 11:18, Polashek, Matthew wrote:
> > Anyone using any of these Digital Audio Lab cards with ALSA? Their
> status
> > is listed as unknown on the ALSA site.
>
> i've been in touch with the DAL people about this over the past few
> years. they have no intention of releasing the necessary programming
> data.
>
> don't hold your breath! i did for a few years, but finally just decided
> to jump to RME -- i don't think it's going to happen.
>
> -p
>
>
>
>
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
Michael D. Crawford wrote:
> Greetings,
> I just joined the list, so if you want to discuss my article here you
> don't need to copy to me separately.
> If you're thinking of translating my article, let me tell you some
> statistics that may be encouraging.
> The english version has been served to about 2000 unique hosts per day
> for the past two and a half months. It ranks #1 at Google for the query
....
> about one's opinions.
> Unfortunately that forbids such derivative works as translations. I
> tried to find a license that would suit me but would allow faithful
> translations, but I couldn't find any, and I don't think there's really
> any way one could be written. But I can grant separate permission to
> anyone who wishes to translate, and I'm willing to hold joint copyright
> with a translator.
> I welcome your discussion.
>--
>Michael D. Crawford
>GoingWare Inc. - Expert Software Development and Consulting
>http://www.goingware.com
>crawford(a)goingware.com
Michael,
Thank you for your article. If I can ever get myself to concentrate long
enough to get my own site online I will be linking to yours.
I've long felt that music should be something that everyone has the
right to _do_ themselves. The experience of making sounds happen seems
to me to be something everyone needs. So many people do not get this
experience. My knowledge of history may be a bit spotty, but in general
my understanding is that before the rise of the Music Business a far
greater percentage of the population actually participated in music
making fairly regularly rather than merely consuming entertaiment. Now
it seems to me that most people in the general population are afraid, or
can't even conceive, of making music themselves. The feeling I get is
that the average person (amongst the general population -- not the
average reader of this list :) ) is trained to think that if they can't
sell millions of albums they might as well not bother. This is a
horrible shame.
My personal hope is that the internet and free software can help to give
back to the individual the freedom to create and to enjoy the act of
creating. The world will be a better place for it.
Thank you again.
You have stirred me up a bit, definitely for the better :)
-Eric Rz.