On Monday 23 February 2004 01:09, linux-audio-user-request(a)music.columbia.edu
wrote:
> > I had added my alsa devices (not of the "autodetected" types) to
> > modprobe.conf where it says to do so. I added them to the /lib/modules
> > version as well--this may be the reason. The question is where is it
> > correct to do so?
>
> Ususally, alsa module options go into /etc/modprobe.d/alsa
>
> From /etc/modprobe.conf:
>
> # This line loads the part of the modprobe configuration managed with
> # update-modules(8) and built from the contents of /etc/modprobe.d/.
> include /lib/modules/modprobe.conf
Oh, I put them there as well! Should I get them out of /etc/modprobe.conf?
The USB is very problematic. The uhci-hcd module needed to have snd-usb-audio
work does not shot down correctly. Indeed, an attempt to modprobe -r on that
will not terminate. Shutdown requires the big red switch (which apprently,
2.6 sits on and does a little cleanup once this is momentarily pressed). I
have to exclude this module till I know what to do about it!
I'll chime in here, because I think Mark was actually responding to my
sugggestion about multi-sample imports in Specimen.
I really like Pete's Specimen program, and I find it very useful. I
think it's amazing that he's done it so quickly as a first project.
Please just leave him alone, OK? He's already spoken; let it go.
We all have complex reasons for choosing our projects, choosing our
profession, marrying a certain person, etc. There is no way someone
else can step in and understand all those complex reasons. When
someone says "No!" it usually means at least "No."
Perhaps I should add that I have myself had many bad experiences in
trying to "channel a small amount of time" into a project. For me,
this has never worked out. In fact, I consider that kind of talk to
be a warning sign not to get involved. The more desperate the plea,
the more likely there is doom ahead.
In reality, seems to be working just fine now. UBS works and can record notes
to Rosegarden.
On boot, BEFORE alsa start, restore mixer setting, etc., there is a bunch of
underfind snd_..... items. Apparently harmless.
I had added my alsa devices (not of the "autodetected" types) to modprobe.conf
where it says to do so. I added them to the /lib/modules version as
well--this may be the reason. The question is where is it correct to do so?
wigwamjam grows sounds using your decisions to drive the evolution of
genetically programmed synth functions.
wigwamjam is proof of concept for the moment, and not a fully blown audio tool
yet.
http://www.pawfal.org/Software/wigwamjam/
cheers,
dave
................................. www.pawfal.org/nebogeo
On Friday 20 February 2004 18:01, linux-audio-user-request(a)music.columbia.edu
wrote:
> > I added lines that were in modules.conf to modprobe.conf.
> > Now and mpu401 driven devices is active!
> > The USB still is not, though snd-usb-audio is registering on boot and
> > deregistering on shutdown.
>
> Does the USB device show up in /proc/bus/usb/devices?
I have a /proc/devices/usb
>
> Probably the OSS drivers ("usb-midi" or "audio") are loaded. Â If so,
> deactivate them or put them into /etc/hotplug/blacklist.
long time done.
No reason they should not work on Win98. Not all that different than Win95!
Linux? I go my sw60xg to work following a little trick recommended by Yamaha
before they had a y2k driver for this card: Use mpu401. Another possiblity
would be to experiment with existing alsa serial-midi stuff. This box should
be mostly sending raw midi events.
How does it work, just for playing synth-guitar? Unable to afford a Roland,
might be intereted in one of these.
BTW, bough a "music-star" controller for $40 on ebay. Should have taken more.
OK, no touch-sensitivity (did not expect it), but 10-note polyphony keyboard
for that price!?! Plugs into a gameport so bought a Roland UM1 to use it
through USB. Now to get the USB working again on 2.6 ....
On Sunday 22 February 2004 03:36, linux-audio-user-request(a)music.columbia.edu
wrote:
> I bought not one...but 2 of these damn things from Ebay. It was a hex
> pickup and propietary box with RS232 midi interface to PC. They went
> bust a few years ago but these things are still around.The last
> Windblowz driver support ended in the Win 95 era. Some have reported
> getting them to work on Win 98.
>
> Anyway, I got 2...Right now they make great paperweights! Anyone
> interested in taking a stab at some linux drivers for them? If it could
> be done somewhat easily by someone versed in that area, it would be a
> possible cheap Midi guitar option. These boxes float around on Ebay for
> between $25.00 to $50.00. If they work even half reasonably, thats a big
> difference to the next midi guitar option like the Roland unit. Hell,
> the pickup is $200.00!!
>
> Anyway, hands up whos interested! :)
>
> I would be willing to offer up the second unit to someone who can
> actually get this done...
I bought not one...but 2 of these damn things from Ebay. It was a hex
pickup and propietary box with RS232 midi interface to PC. They went
bust a few years ago but these things are still around.The last
Windblowz driver support ended in the Win 95 era. Some have reported
getting them to work on Win 98.
Anyway, I got 2...Right now they make great paperweights! Anyone
interested in taking a stab at some linux drivers for them? If it could
be done somewhat easily by someone versed in that area, it would be a
possible cheap Midi guitar option. These boxes float around on Ebay for
between $25.00 to $50.00. If they work even half reasonably, thats a big
difference to the next midi guitar option like the Roland unit. Hell,
the pickup is $200.00!!
Anyway, hands up whos interested! :)
I would be willing to offer up the second unit to someone who can
actually get this done...
R~
Hello All,
I haven't been able to get jack to start with a vxpocket V2.
I'm using the commandline "jackd -d alsa -d hw:1" and getting the
error:
jackd 0.94.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
loading driver ..
creating alsa driver ...
hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|rt|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 24bit samples trying 16bit instead
Sorry. The audio interface "hw:1" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
ALSA: cannot configure capture channel
cannot load driver module alsa
The alsa version is 1.0.2c on a powerbook running debian testing
/unstable with 2.4.24 kernel.
I got the impression from some others on this list that they have it
working. What's the trick?
Thanks for any help,
digger
Thanks to Clemens,I have 4 channel output from my
rp-u200 usb-audio "card"
The problem now is bad sound,that is,lots of kind of pops
or whatever it's named.Also there is sync
problem,sometimes the sound is kind of slowing down.
I played back sound with different applications:alsaplayer,
ecasound,fluidsynth,terminatorX.Always the same result:
When I run jack the sound is bad,but when do the same thing without jack
running,direct by alsa there are no obvious problems(except having
only 2 channels),so it can't be a hardware problem.
Any ideas about the origins of this disastrous sound?
I have jack 0.94.0,alsa-driver 1.0.2c,kernel 2.4.20-gentoo-r8.
Thanks for help,
Jaap van Geffen