Alexander,
thanks for the link, I will certainly give it a try. It hurts to say so, but
I miss the audio restoration features built in Cool Edit Pro for M$ Windows
since I migrated 100% to linux; those tools were, IMO, as powerful as easy
to use. If you know of any tool out there which is similar to that, let me
know (gwc doesn't seem to work very well...).
Thanks!
Sergi
<Greetings,
<
<I'm sorry for this cross-posting.
<
<I've just figured out that there is a sound restoration plugin on
<LAOE (http://www.oli4.ch/laoe/). Its description is in the
<documentation which is distributable in SXW
<(OpenOffice.org/StarOffice) files.
<
<If interested ...
<
<--
<Alexandre Prokoudine
<ALT Linux Documentation Team
<JID: avp(a)altlinux.org
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
Hey, all. I thought of something today that I think would be of good use
to many folks.
I was wondering, is there a mailing list somewhere for people to talk to
and educate each other on such things as music production, software use,
micing technique, best drum kits, or anything in between?
If not, how useful do you think this would be to those of you on this
mailing list? I was also thinking it would be a good place to announce new
recordings of songs.
If enough people would like this, I have my domain on a new server with
mailing list software that's actually worth something, and I would be
willing to start and host it. Since this is just a mailing list, and those
are generally fairly low-maintenance, this would not foreshadow any of my
work on the Open Music Resource Library (such as it is right now).
Thoughts and opinions?
Regards,
Darren Landrum
Hallo,
I have a M-Audio Audiophile card (snd-ice1712) in my box, and for
month I cannot get alsaplayer to work with it in ALSA-mode. I
currently use
$ alsaplayer --version
alsaplayer 0.99.70
from the unstable Debian package.
But it didn't work with any prior version. Actually I like alsaplayer,
because it runs very stable without dropouts, but in my case it
doesn't deserve its name. This is the error I keep getting when
starting alsaplayer ("-d default", "-d hw:0" all give the same):
$ alsaplayer
error on set_periods (13)
Unavailable hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (11609 11610)
PERIOD_SIZE: 512
PERIOD_BYTES: 2048
PERIODS: [1 13)
BUFFER_TIME: (11609 148595)
BUFFER_SIZE: [512 6553]
BUFFER_BYTES: [2048 26212]
TICK_TIME: 10000
error on set_periods (7)
Unavailable hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (23219 23220)
PERIOD_SIZE: 1024
PERIOD_BYTES: 4096
PERIODS: [1 7)
BUFFER_TIME: (23219 148595)
BUFFER_SIZE: [1024 6553]
BUFFER_BYTES: [4096 26212]
TICK_TIME: 10000
failed to configure output device...trying OSS
Yeah, "trying OSS", you wimp! ;)
Has anyone with an Audiophile alsaplayer working?
ciao
--
Frank Barknecht _ ______footils.org__
Hello,
I am currently using alsa 0.9rc7 with oss emulation, oss sequencer, virmidi
and ens1371. I have a ens1371 soundcard. I would like to create my own
soundfonts using smurf and play them with iiwusynth. Does anyone have some
insight into the best way to proceed with this process (workflow, devices etc
etc). I am a little overwhelmed by the amount of options there are for doing
this.
Thanks!
-Levi
> > 0 'Timer '
> > 1 'Announce '
> >client 64: 'External MIDI 0' [type=kernel]
> > 0 'MIDI 0-0 '
> > 32 'MIDI 0-1 '
> >client 72: 'External MIDI 1' [type=kernel]
> > 0 'Midisport 2x2 Port 0'
> > 1 'Midisport 2x2 Port 1'
> > 2 'Midisport 2x2 Port 2'
> > 3 'Midisport 2x2 Port 3'
> >[mark@Godzilla mark]$
> >
> >
> > The above information is certainly a bit more readable, but it seems
> >to still be, at the least, inconsistent.
> >
> >1) For client 64, which is an HDSP 9652, there are two rawmidi ports.
> >However, the info above says they are labeled '0' and '32'. Should they
> >not be 0 & 1? If this is an error, then what needs to be fixed? The HDSP
> >9652 driver?
>
> no, the port numbers are 0 and 32, but in the name, its 0 and 1.
Well, OK, I guess I don't understand the meaning of 'ports' then. The HDSP
only has two sets of in and out connectors. Are these not ports? Or does the
Alsa spec think that each 'port' is somehow combination of a MIDI connector
and a channel or something? How is it that a single input uses up 32 port
number? (HDSP 9652 MIDI 1 seems to go from port 0 to port 31, and I guess #2
goes from 32-63.)
>
> >2) Why does the HDSP 9652 not tell me its name like the MidiSport does?
>
> its using a copy of some generic ALSA code that just calls the ports
> "MIDI C P" where C=card number and P=physical port number. i'll change
> this when i add the fixes for the mixer and the h/w names.
>
This would be very helpful. Thanks!
Before diving into my particular question, I want to say that planet CCRMA is
great! the documentation is superb - -
Just wondering if there is a quick, easy answer for this - the problem is that
after installing cmucl from planet CCRMA using apt-get, it doesn't run:
~ ~ ~
root@dhcp-25-2 root]# lisp
Could not open file "/usr/lib/cmucl/lisp.core".
Maybe you should run "update-alternatives --config cmucl-core" as root?
open: No such file or directory
[root@dhcp-25-2 root]#
~ ~ ~
[root@dhcp-25-2 root]# rpm -qa | grep cmucl
cmucl-3.1.4-1
[root@dhcp-25-2 root]# rpm -qi cmucl
Name : cmucl Relocations: (not relocateable)
Version : 3.1.4 Vendor: (none)
Release : 1 Build Date: Fri 20 Dec 2002
04:01:30 PM EST
Install date: Sat 15 Feb 2003 09:06:10 PM EST Build Host:
nando.stanford.edu
Group : Development/Languages Source RPM: cmucl-3.1.4-1.src.rpm
Size : 944001 License: see
/usr/share/doc/cmucl/copyright
Signature : (none)
Packager : Fernando Lopez-Lezcano <nando(a)ccrma.stanford.edu>
URL : ftp://http.us.debian.org/debian/pool/main/c/cmucl
Summary : The CMUCL lisp compiler and development system.
Description :
CMUCL is a free implementation of the Common Lisp programming language
which runs on most major Unix platforms. It mainly conforms to the
ANSI Common Lisp standard (http://www.cons.org/cmucl/)
This is the basis package for CMUCL. It contains the base
image with the compiler, PCL (CLOS), and the tty based
debugger.
~ ~ ~
Best Regards
Larry Troxler
Well, since my installation (mostly RedHat 7.1) was getting to be a big mess,
with bits and pieces from different places, I decided the best way to get a
working C++ compiler was to get a new drive and do a fresh redhat 8.0
installation :-)
My immediate question: is ext3 bad news for real-time work? I saw some
linux-audio-dev list messages from people who were having freezes using it.
Should I convert my filesystem back to ext2 (assuming there is a way) or not?
Which one in theory (assuming no bugs which seems to be the cause for the
freeze) should be better for low-latency work?
Thanks in advance!
Larry Troxler
Hi,
I'm having a great deal of confusion about how Alsa is handling my
MIDI hardware. This is spilling over into unintended consequences in
Rosegarden that I think none of us understand. Couple someone with some
background in this please explain? Thanks.
I have two 2-port MIDI devices on this system. One is an RME HDSP
9652 with two MIDI ports, and the other is a hot pluggable MidiSport
2x2. I attach two screen shots of kaconnect, one with and one without
the 2x2 plugged in.
My questions:
1) In the screen shot "without_2x2.png" I see two read ports and two
write ports. Please explain why they are called
64:0 External MIDI 0
64:32 External MIDI 0
Why is my HDSP given the apparent name '64'? Why the :0 and :32? I would
have thought :0 and :16 would make more sense from a channel numbering
point of view, or :0 and :1 from an interface point of view. What's
going on?
2) In the screen shot "with_2x2.png" I've plugged in the MidiSport 2x2.
New devices show up in kaconnect. However, instead of showing 2 read
ports and 2 write ports, I am getting 4 read ports and no write ports.
Please explain why the MidiSport is given the names
72:0 External MIDI 1
72:1 External MIDI 1
72:2 External MIDI 1
72:3 External MIDI 1
Shouldn't this be just :0 and :1 for both the read and write ports?
I get the feeling that BOTH of the drivers for these devices are hosed.
What's up with these things?
I do not understand why Alsa gives these devices numbers in the first
place, nor how the numbers are assigned.
How can I change the names that are displayed so that
"64:0 External MIDI 0" shows the name "HDSP 9652 Port 1"
"64:32 External MIDI 0" shows the name "HDSP 9652 Port 2"
"72:0 External MIDI 1" shows the name "MidiSport 2x2 Port A"
"72:1 External MIDI 1" shows the name "MidiSport 2x2 Port B"
Thanks very, very much in advance,
Mark
Hi all,
For the longest time I've had this problem and even though I've used
Linux for over 5 years, I never bothered figuring this out until now. So
it may sound kinda pathetic that I still don't know the solution to this
sort of a trivial problem, but here it goes anyhow:
Let's say I install an app from sources and the binary built depends at
runtime on some stuff found in the subdirs of the source package. So,
when I execute binary by doing ./binary-name inside its original dir
(where it was built), it works like a charm, but if I move the whole
install dir (with sources) to let's say /usr/local/ and then do
ln -s /usr/local/appname/binary /usr/local/bin/binary
(thus creating a soft link into a bin dir that's in my path)
the binary fails because the app now cannot find the needed subdirs any
more. Now, this is obviously not the case with the apps that have good
"make install" routines, but for some odd reason there is quite a number
of apps which when built simply give out this kind of a problem.
The apps that do exhibit this kind of issue are usually built by a
simple
./configure
make
make install (if available -- usually not)
So, my question is how do I make the binary aware where its stuff lies
if its config script ~/.config-file does not reveal such settings, and
if I don't want to put app's dir into my path which to me seems a bit
clumsy? In another words, how can I link it to a bin dir and still have
it work as it is supposed to (i.e. to be aware of what Windows refers to
being app's "working dir"?
Any help on this matter is greatly appreciated! Sincerely,
Ico
Thanks all for your kind replies, I'm on digest so please forgive me
for replying to them all at the same time.
> Message: 3
> Date: Thu, 13 Feb 2003 21:15:45 +0100
> From: Frank Barknecht <fbar(a)footils.org>
> To: "'linux-audio-user(a)music.columbia.edu'"
> <linux-audio-user(a)music.columbia.edu>
> Subject: Re: [linux-audio-user] Alsa with OPL3-SA2 on Asus Laptop
> Reply-To: linux-audio-user(a)music.columbia.edu
>
> Hallo,
> Chris Bray hat gesagt: // Chris Bray wrote:
>
> > I've been trying for a couple of days now to get
> > any sound from my laptop (rebadged Asus L7000,
> > Slackware 8.1, vanilla 2.4.20) and seem to be
> > getting nowhere fast.
> >
> > isapnp.conf contains all the settings that Windows
> > is using and everytime I try to get it running with
> >
> > modprobe snd-opl3sa2 (or snd-card-opl3sa2)
> >
> > I get
> > "Yamaha OPL3-SA Soundcard not found or device busy"
>
> Are you sure that you have an OPL3-chip inside?
> According to http://www.muenster.de/~akorves/asus_l7g_de.html (in
> German) the Asus L7000 has an Intel ICH 8x0, AC'97 Codec. You
> need the snd-intel8x0 module then.
>
> ciao
> --
> Frank Barknecht _ ______footils.org__
Sorry, it is an L7300, my bad. It's quite old and not listed
on the asus site anymore. (Celeron 400, 96mb, 10Gb, 13.3" TFT)
ISAPNP detects it as a OPL3SA2 and so does Win98.
>
> --__--__--
>
> Message: 4
> Date: Thu, 13 Feb 2003 19:35:09 -0500
> From: Dave Phillips <dlphilp(a)bright.net>
> To: linux-audio-user(a)music.columbia.edu
> Subject: Re: [linux-audio-user] Alsa with OPL3-SA2 on Asus Laptop
> Reply-To: linux-audio-user(a)music.columbia.edu
>
> Hi Chris:
>
> If you can access the machine's BIOS when you boot it up perhaps you
> can retrieve some more detailed information regarding the
> audio chipset
> and its configuration.
No, the bios is very basic, doesnt let you do anything with audio.
Not even turn it off.
>
> For completeness sake I have to ask: how did you configure
> ALSA ? Did
> you build and install the entire package ? Were there any
> problems with
> it ?
I used
./configure --with-isapnp=yes && make && make install
didnt specify any particular cards
is there anything else I should have done
>
> --__--__--
>
> Message: 5
> Date: Thu, 13 Feb 2003 19:55:39 -0500
> From: "Gustavo Zamorano S." <gzsuniq(a)cableonda.net>
> To: linux-audio-user(a)music.columbia.edu
> Subject: Re: [linux-audio-user] Alsa with OPL3-SA2 on Asus Laptop
> Reply-To: linux-audio-user(a)music.columbia.edu
>
>
> Chris:
> Did you run alsaconf that is under the alsa-driver-0.9.0rc6/utils
> directory ?. It should recognize what chip you have and modify
> /etc/modules.conf accordingly...
> GZS
>
No, I'll try that when i get back to the machine, I did run snddevices (?)
or something, as suggested in the README, but that didnt seem to make any
headway.