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.
Hi All;
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.
I've tried OSS/Free and Alsa (0.9.0rc2 and 0.5.12a)
and can't seem to get anything working.
OSS just hangs as I modprobe the module, no log entries
or anything I can find.
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"
Can anyone please help me as I'm getting to the end
of my patience!
I am a bit of a newbie so if anyone has any ideas what
I could have missed then please let me know.
Chris Bray
(Frustrated)
Hello
I'm almost as new to Debian and Linux as I am to DeMuDi, so I've kind of
dropped myself in at the deep end I guess.
I've successfully installed the demudi-2.4.18 kernel, which I must say was
remarkably smooth i.e. my system still works jus as well as it did before I
installed the new kernel. Well done to whoever packaged that up!
However, when I get to the point of configuring demudi-base it comes up with:
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*
and then it hangs. I'm confused. Where should I specify these modules?
Also my system can't find any opti92x module does this mean I have to go
find/download one? I've been running the bluepoint/OPTi soundcard with mad16
semi-succesfully up to this point. modprobe won't load seq-oss either which
makes me suspect I have conflicts with my modules (?) :-/
I will admit to being only about half-way through all the available
documentation, which _is_ mighty, _especially_ if I was compiling it.
I don't suppose anything like a straightforward demudi install HOWTO exists
just yet (I guess you're all flat out with current developments).
My eyes are going familiarly wiggly with on-screen reading, so I thought I'd
dash off a quick email just to see if the list could give me any obvious
pointers.
forgive me if I'm being an utter twink here. If so, even a brief RTFM
response would probably give me a significant clue. I include the results of
my most recent lsmod & dmesg just to illustrate the point.
yours hopefully
tim hall
tim(a)glastonburymusic.org.uk
********************************************************************************
Module Size Used by Not tainted
parport_pc 22056 1 (autoclean)
lp 6336 0 (autoclean)
parport 22976 1 (autoclean) [parport_pc lp]
serial 44064 0 (autoclean)
opl3 11112 0 (unused)
smc-ultra 5024 0 (unused)
8390 5920 0 [smc-ultra]
ipv6 123424 -1
mad16 7392 0 (unused)
ad1848 20896 0 [mad16]
isa-pnp 28168 0 [serial smc-ultra ad1848]
sb_lib 32480 0 [mad16]
uart401 6080 0 [mad16 sb_lib]
sound 52620 0 [opl3 mad16 ad1848 sb_lib uart401]
soundcore 3492 5 [sb_lib sound]
af_packet 11528 0 (unused)
rtc 5528 0 (autoclean)
ext2 30784 3 (autoclean)
ide-disk 6624 4 (autoclean)
ide-probe-mod 8080 0 (autoclean)
ide-mod 130892 4 (autoclean) [ide-disk ide-probe-mod]
ext3 56864 0 (autoclean)
jbd 35272 0 (autoclean) [ext3]
unix 13316 44 (autoclean)
Linux version 2.4.18-586-demudi (free@leporello) (gcc version 2.95.4 20011002
(Debian prerelease)) #1 Tue Oct 15 11:19:17 CEST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000003000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 12288
zone(0): 4096 pages.
zone(1): 8192 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=demudi ro root=301
Initializing CPU#0
Detected 133.637 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 266.24 BogoMIPS
Memory: 43976k/49152k available (808k kernel code, 4792k reserved, 196k data,
192k init, 0k highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
CPU: Before vendor init, caps: 000001bf 00000000 00000000, vendor = 0
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After vendor init, caps: 000001bf 00000000 00000000 00000000
CPU: After generic, caps: 000001bf 00000000 00000000 00000000
CPU: Common caps: 000001bf 00000000 00000000 00000000
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb210, last bus=0
PCI: Using configuration type 1
PCI: Probing hardware on bus (00:00)
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
Linux IP multicast router 0.06 plus PIM-SM
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 2580 blocks [1 disk] into ram disk...
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/done.
Freeing initrd memory: 2580k freed
VFS: Mounted root (cramfs filesystem).
Freeing unused kernel memory: 192k freed
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Journalled Block Device driver loaded
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller on PCI bus 00 dev 39
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:pio, hdd:pio
hda: ST31720A, ATA DISK drive
hdc: FX800S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 3331852 sectors (1706 MB), CHS=3305/16/63
Partition check:
hda: [PTBL] [826/64/63] hda1 hda2 < hda5 hda6 hda7 >
ext3: No journal on filesystem on ide0(3,1)
Adding Swap: 98748k swap-space (priority -1)
Real Time Clock Driver v1.10e
isapnp: Scanning for PnP cards...
isapnp: Card 'SMC EtherEZ (8416)'
isapnp: 1 Plug & Play card detected total
ad1848/cs4248 codec driver Copyright (C) by Hannu Savolainen 1993-1996
ad1848: No ISAPnP cards found, trying standard ones...
MAD16 audio driver Copyright (C) by Hannu Savolainen 1993-1996
CDROM Disabled.
Joystick port enabled.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
smc-ultra.c: Presently autoprobing (not recommended) for a single card.
smc-ultra.c: ISAPnP reports SMC EtherEZ (8416) at i/o 0x240, irq 10.
smc-ultra.c:v2.02 2/3/98 Donald Becker (becker(a)cesdis.gsfc.nasa.gov)
eth0: SMC EtherEZ at 0x240, 00 00 C0 D1 23 E0,assigned IRQ 10 programmed-I/O
mode.
YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI
ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Hello folks, think you all probably will find this of considerable
interest. AMI and Transmeta are planning to make chip that put content
control on your computer at the hardware level, in a way that lets
others turn things on and off on your computer, in a protected space
entirely outside your control. Many details below:
Seth Johnson
Stop Palladium and TCPA now!
Tell American Megatrends and Transmeta not to make chips that let others
control your computer!
Please use the following form to tell American Megatrends and Transmeta
not to produce their AMIBIOS8 and TM5800 chips, and that you will
boycott any technology that enables TCPA and Palladium technology on
your computer: http://www.nyfairuse.org/action/palladium/
What's Going On:
Last week, Intel, Microsoft, the RIAA and the MPAA announced their
intention to force Palladium and TCPA into every personal computer on
the planet. Palladium and TCPA are a different kind of DRM, worse than
even the most invasive of previously proposed "content control" systems.
Palladium and TCPA would hardwire your home computer so that these four
entities and their partners would be able to run processes on your
computer, entirely outside your control, indeed, without your knowledge.
Below we answer some questions about DRM, Palladium, TCPA, and the
boycott.
New Yorkers for Fair Use
What is DRM?
DRM is the political, legal, contractual, economic, hardware, and
software infrastructure designed and intended by a loose alliance of
cartels and monopolies to take away your right to own and privately use
a computer. No full DRM exists in the world today, though pieces of DRM
have been successfully enacted into law and tiny bits of DRM hardware
and software have been placed in some home movie playing and recording
devices. Every single piece of DRM is meant to help attain the objective
of the anti-ownership alliance: to get control of every personal
computer in the world.
Intel and Microsoft and RIAA and MPAA, by their own admission, have, to
date, spent billions of dollars to force universal DRM on the entire
world. Last week these four reiterated their intention to force DRM into
every personal computer on the planet:
http://www.nytimes.com/2003/01/15/business/15PIRA.htmlhttp://news.com.com/2100-1023-980671.html
For more on DRM see:
http://newsforge.com/newsforge/02/10/21/1449250.shtml?tid=19http://www.panix.com/~jays/what.is.drm.3
What is Palladium?
"Palladium" is Microsoft's name for its proposed DRM system. No
implementation of Palladium exists today, indeed no complete
specification of Palladium exists today, but certain hardware which a
Palladiated operating system requires is about to be placed in all
personal computers, unless we stop Microsoft and its hardware and vendor
partners, such as Intel, American Megatrends, Transmeta, Dell, and
CompUSA.
What will Palladium do?
Palladium will enable a few large corporations and governments to run
source secret, indeed, well-encrypted, code on home users' machines in
such a way that the home user cannot see, modify, or control the running
code. A Palladiated system is under the complete control of Microsoft at
all times. Microsoft might allow some of its partners to run code on
your machine, but no code will run on a Palladiated system without
Microsoft's consent. The mechanics are as follows: only code that has
been signed with a special Microsoft provided key will run. Microsoft
will retain at all times the power to revoke any other entity's keys. In
particular, no operating system will be able to boot without a key from
Microsoft. So if Palladium is forced into every home computer, there
will be no more free software.
Microsoft will be able to spy on each and every keystroke, and mouse
movement, and send encrypted messages from your machine to Microsoft
headquarters. Microsoft will also be able to examine every file on your
system. Your encryption programs will not work against Microsoft, or any
other entities which have full power keys from Microsoft.
But surely wily crackers and freedom-loving hackers around the world
will be able to defeat Palladium by breaking it?
No. Whether or not a few hackers are able to get around some versions of
Palladium, most people will not be able to. There are two reasons most
people will not be able to escape the All Seeing Eye and Invisible Hand
of Palladium. First, Palladium is not like the absurdly weak systems
called "DRM" today. Palladium is both hardware and software, and the
software is locked to the hardware in a manner completely different from
today's weak DRM systems. The design of Palladium allows for defense in
depth, and even one layer of Palladium is harder to crack than any DRM
ever seen before. Second, under the Digital Millennium Copyright Act of
the United States of America, it is illegal to try to see what Palladium
is doing. It is also illegal to modify the hardware of a Palladiated
system. And it is a felony to sell advice on how to disable Palladium or
its supporting hardware. It is hard enough today to get vendors to sell
computers with a free operating system already installed. Once Microsoft
and Intel have forced Palladiated hardware into every personal computer,
it will be impossible to run a free OS. The very act of booting a free
OS will be outlawed by application of the DMCA to a Palladiated
computer.
But there are no Palladium systems available today. So how can you
boycott Palladium?
We are boycotting the hardware that Palladium needs. Before Palladium is
rolled out, Palladium-enabling hardware must be placed in most of the
world's personal computers. Right now such hardware is being placed in
computers meant for home and business use without the buyer being told.
Our boycott is aimed at stopping Palladium-enabling hardware from being
secretly forced into every personal computer in world. We intend to stop
Palladium before we cease to own the computers in our own houses and
offices.
The main Palladium-enabling hardware is called a "TPM" for Trusted
Platform Module. The TPM hardware will support, in addition to
Palladium, many different systems which take control of the computer
away from the user and give control to large corporations and government
entities. The TCPA, the Trusted Computing Platform Alliance, is the
standards organization for the TPM. The founding Alliance members are
Compaq, HP, IBM, Intel and Microsoft. Since 1999, the year TCPA was
founded, about one hundred more companies have joined the TCPA. The
Alliance has published a formal specification of the TPM. The TCPA's FAQ
http://www.trustedcomputing.org/docs/Website_TCPA%20FAQ_0703021.pdf
seeks to allay the natural suspicions of computer buyers about what the
TPM does. Unfortunately the FAQ is inaccurate on the most important
issues. For example, the claim is made that a computer with a working
TPM will remain under the final, ultimate, and complete control of the
user. But, as explained above, this is simply untrue.
So what exactly are you doing?
We refuse to buy any computer with a TPM inside and we ask you to refuse
to buy any computer with a TPM inside. We use the term "TPM" to include
TPM-like devices, whether in a separate chip, in the BIOS chip, or even
in the cpu. This means that we ask buyers of personal computers to find
out whether the computer has a TPM or a TPM-like device inside. We will
shortly provide buyers of home computers with methods for telling
whether or not a computer has a TPM inside.
Is it possible to be more specific today?
Yes. We call for a boycott of the just announced American Megatrends
AMIBIOS8:
http://www.ami.com/ami/showpress.cfm?PrID=118http://www.ami.com/products/product.cfm?ProdID=127&CatID=6&SubID=14http://interviews.slashdot.org/article.pl?sid=03/01/09/166251&tid=99http://interviews.slashdot.org/article.pl?sid=03/01/17/1430214&mode=thread&…
and the just announced Transmeta TM5800 cpu:
http://siliconvalley.internet.com/news/article.php/1569201http://slashdot.org/article.pl?sid=03/01/14/1719220&mode=thread&tid=161
Where can I find out more about Palladium, TCPA, and DMCA?
For Palladium see:
http://www.cl.cam.ac.uk/%7Erja14/tcpa-faq.htmlhttp://wintermute.homelinux.org/miscelanea/TCPA%20Security.txthttp://discuss.microsoft.com/SCRIPTS/WA-MSD.EXE?A2=ind0301b&L=wmtalk&T=0&O=…http://www.theregus.com/content/4/25378.htmlhttp://www.counterpane.com/crypto-gram-0208.html#1http://www.ofb.biz/modules.php?name=News&file=article&sid=152
For TCPA and the TPM see:
http://www.trustedcomputing.org
For the DMCA see:
http://www.nyfairuse.org/analysis/dmca.must.be.repealed.xhtmlhttp://anti-dmca.orghttp://www.nyfairuse.org/dmca.xhtml
Hartmut Noack <symposion(a)onlinehome.de> wrote:
> Hi Bryan,
<CHOP>
> 1) try Soundblaster 1024 Live! Player ( NOT SB Live 501 !!)
> the card uses a professional EMU-Chip witch is formidably
> supported by alsa, so midi-functions should work properly...
> even though the cards D-A-Encoders are far from being excellent
> they work smooth enough to serve very well for demos in average
> HIFI-Sound. AND: the card should be available for less than $60,-
What would the main differences be in the (above) 2 cards. I have a SB Live! 5.1 and don't seem to have any problems with it. But if there is
any major differences, I would be curious what they are.
Thanks,
Rocco
__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
Hi,
I'm new to the list so... hi to all. I decided to migrate 100% to linux from
windows recently, just because I did't want to depend on commercial software
anymore. I checked those hundreds of projects at sourceforge / freshmeat,
and though that would fit my needs. I didn't say it would be easy though...
:-P Mainly, besides normal desktop applications (OpenOffice, internet
browser, and so on), I use my computer to transfer my old vynils to CD. My
soundcard is a Terratec DMX 6Fire 24/96, which is exactly what I need (high
resolution recording + preamplified phono input); the problem is that I
can't manage to find out how the envy24control and alsamixer work. I don't
know how to select the phono input for recording, and usually when I play
music (even a CD or mp3 using xmms) it sounds distorted, kind of too
"saturated".
Is anyone using the same card? Would anyone give me a hand please? Thanks!
Sergi
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
1. A short summary of changes
The JACK slave mode code has been completely rewritten. As a
new feature it is now possible to use libsamplerate for
resampling. Using JACK has been made more user-friendly as ecasound
can now automatically configure the runtime parameters to
match the current server settings. And thanks to build system
and signal handling updates, it's now possible to compile
ecasound for win32 under Cygwin.
---
2. What is ecasound?
Ecasound is a software package designed for multitrack audio
processing. It can be used for simple tasks like audio playback,
recording and format conversions, as well as for multitrack effect
processing, mixing, recording and signal recycling. Ecasound supports
a wide range of audio inputs, outputs and effect algorithms.
Effects and audio objects can be combined in various ways, and their
parameters can be controlled by operator objects like oscillators
and MIDI-CCs. A versatile console mode user-interface is included
in the package.
Ecasound is licensed under the GPL. The Ecasound Control Interface
(ECI) is licenced under the LGPL.
---
3. Changes since last release
* If configured with JACK-support, ecasound will now fetch the
correct buffer size and sampling rate parameters from the
JACK server when connecting a chainsetup with JACK inputs or
outputs. In other words you don't have to manually match
these settings between the JACK server and ecasound.
* Support for Erik de Castro Lopo's libsamplerate
resampling library added. If libsamplerate is not installed,
ecasound will fall back to the old resampling algorithm.
* Rewritten the code that handles JACK slave-mode operation.
Ecasound is now able to more quickly and reliably follow
transport state and position changes, as initiated by the
current JACK timebase master.
* Ecasound for Windows! :) With help of the Cygwin environment,
you can now compile win32 ecasound binaries straight from
the standard source package. As of 1.3.1, Cygwin also
contains basic /dev/dsp emulation, so even audio playback
works.
* Fixed many, more or less serious, bugs. The most annoying
ones were incorrect handling of the '-t' option, excessive
DBC warnings with JACK inputs and outputs and failing to
properly reset the terminal after a CTRL-C while in interactive
mode.
Full list of changes is available at
<http://www.wakkanet.fi/~kaiv/ecasound/history.html>.
---
4. Interface and configuration file changes
None.
---
5. Contributors
Patches
Junichi Uekawa (build system)
Kai Vehmanen (various)
Bug Hunting (items closed)
Janne Halttunen (2)
Eric Amundsen (1)
Antti Boman (1)
William Goldsmith (1)
Andrew Reilly (1)
Oliver Thuns (1)
---
6. Links and files
Web sites:
http://www.eca.cxhttp://www.eca.cx/ecasound
Source packages:
http://ecasound.seul.org/downloadhttp://ecasound.seul.org/download/ecasound-2.2.1.tar.gz
Related sites:
http://jackit.sf.net (JACK)
http://www.mega-nerd.com/SRC (libsamplerate)
http://www.cygwin.com
Distributions with maintained ecasound support:
Agnula - http://www.agnula.org
Debian - http://packages.debian.org/stable/sound/ecasound.htmlhttp://packages.debian.org/unstable/sound/ecasound2.2.html
DeMuDi - http://www.demudi.org
FreeBSD - http://www.freebsd.org/ports/audio.html
Gentoo Linux - http://www.gentoo.org
PLD Linux - http://www.pld.org.pl
PlanetCCRMA - http://www-ccrma.stanford.edu/planetccrma/software
SuSE Linux - http://www.suse.de/en
Contrib Packages for Distributions:
Mandrake - http://rpm.nyvalls.se/sound9.0.html
Note! Distributors do not necessarily provide packages for
the very latest ecasound version.
--
http://www.eca.cx
Audio software for Linux!
I want to build a small home studio. I'm planing to record
electrical and acoustical instruments (including voice).
I already do have an external mixer (with mic preamplifiers).
I do need MIDI and (maybe) SPDIF I/O.
While I do think that about 6 analog inputs will do, I know
that some more could become handy some day...
Looking around in the net I have got the impression that both
RME Hammerfall (PCI Interface + Multiface) and the Midiman Delta 1010
would be good (but expensive) choices and about equally supported
in Linux.
Do you think that these cards would be comparable regarding quality
and Linux compatibility? Are there other suggestions to consider?
I have seen some complaints about RME MIDI timing problems, but I
do not think it was the PCI Interface + Multiface combination.
Is that right?
BTW: how long is the cable between PC and Midiman Delta 1010?
How is the collaboration between M-audio/RME and the free software
community? (we should honour this ;-)
I know websites for Linux printer recomandations and such, but did
not find something similar for sound equipment. Pointers welcome.
Thank you for taking your time to share your experience,
Robert Epprecht