Hello,
I would like to do some simple WAV editing. Actually, minimum
pre-mastering of an audio CD: normalizing, cutting out pieces, dividing
into tracks, altering volume in some places.
My problem is, at this point alsa drivers are not working for me. And in
itself this is not a problem. The audio source is not the sound card, so
I don't do realtime audio capture. And as I only want simple editing, I
don't care about playback latency.
Which WAV editor should I use? I'd like it to be able to work with OSS
(perhaps via jack-oss?).
Yours, Mikhail Ramendik
Kai Vehmanen wrote:
> Hello all,
> this year's first stable Ecasound release is now out!
> And while I'm at it, here are some recent interesting Eca-related
> links and news items:
> * http://4ms.org/influx9/
> * http://www.agnula.org/documentation/dp_tutorials/no-x/
> * http://emi.thevtek.com/
> But now, back to the 2.3.3 release. CVS is tagged with 'v2_3_3' as usual,
> and here are the details...:
> 1. Summary of changes
I'm having trouble compiling ecasound, but I can't compile 2.3.2 now
either, so I think there's something wrong with my system. I'm just
wondering if anyone else is having problems with this.
make fails like this:
PROCEDURE_TIMER::to_string() const':
kvu_procedure_timer.cpp:147: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [kvu_procedure_timer.lo] Error 1
make[2]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3/kvutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3'
make: *** [all] Error 2
System details below.
Thanks,
Eric Rz.
asus a7v8x-x
athlon XP 2800+ (2071.203 MHz)
1.5GB PC2700 RAM
12GB / /dev/hda2 (actually a 40G disk)
160GB /mnt/audio/ /dev/hdc1
2GB swap /dev/hda1
(onboard via8235 -- disabled)
ice1712 M-Audio Delta-66 w/omni i/o
ymfpci guillemot maxisound fortissimo -- midi only
debian testing (sarge)
2.6.5 (pre-empt on -- kernel.org sources compiled via make-kpkg)
drives tuned in kernel config
alsa-1.0.4rc2 drivers compiled in kernel tree
realtime-0.0.4 lsm (insmod'ed since make install screws things up)
alsa-1.0.4 (lib, envy24control, tools)
libsndfile-1.0.9 from tar.gz
libsamplerate-0.1.0 from tar.gz
jack-0.98.1
./configure --enable-capabilities --enable-optimize
--with-default-tmpdir=/dev/shm --disable-portaudio --disable-oss
ecasound-2.3.3
./configure --enable-pyecasound=c --disable-oss --disable-arts
--with-largefile
Taybin Rutkin wrote:
>What is the problem with JACK and AMD cpus? I haven't heard of one.
>
>
>
Not so long ago a release of qjackctl in Planet C failed due to (IIRC)
JACK getting compiled with an SSE call (or calls) that killed it
completely on my Duron. The problem was simply and quickly solved, and
I'm perhaps off-base accusing JACK but that's where the problem came
from. Maybe it was a bad make ?
Anyway, if it's the opinion of the LAD developers that AMD is OK then
that's what I need to know. As I stated, I've had only that one
difficulty with AMD and Linux audio software, so I think I'm just being
paranoid.
Best,
dp
Hi all,
Initially posting on Tim Orford's Linux VST Compatibility Page, my quest has
been to test all Win-only FreeVSTi's featured on the K-v-R database under Linux
thanks to some of Kjetil Matheussen's apps and to report the way they work in my
language, to speed up things a bit!
I've posted the list on the K-v-R forum:
http://www.kvr-vst.com/forum/viewtopic.php?t=42640
Because that's where i've found most of the plugins:
http://www.kvr-vst.com/get.php
Alternatively, until the nodes change while I update my bookmarks, you can
browse all links to devs there:
http://theremin.free.fr/hunchback/index.php?nodes=|0|461|897|1098|1103|/
Let me quote one of the first answers to the thread: "The stuck notes in some SE
VSTi are most likely due to CK's Unison modules that are a little twitchy."
Have your copy saved on a text file, so that you can emulate a database search.
Ex: getting all interesting working plugins among all plugins stored on a text
file named "VSTi":
cat VSTi | grep ': W!'
NB:
Do you want to practise your french?
http://fr.audiofanzine.com/apprendre/mailing_forums/index,idtopic,60705.html
Cheers,
Mr°Freeze
Using a Turtle Beach Santa Cruz card or should I say experimenting...on
the 2.6.5mm-2 kernel from Thac's repository.
I'm curious if I can get some additional discrete outputs in jack via
the good ol' mystery .asoundrc file? I have wondered with all of these
supposed 5.1 cards that have a rear and front as well as center channels
as to why this is not possible? The one thing I see different about the
Santa Cruz is that it seems to show dedicated pcm slots for center and
rear in /proc/asound/pcm?
Having 4 discreet outs on a 5.1 card would be usefull for some things me
thinx.
R~
Hi Steven:
Forgive me for this late reply, I was in Karlsruhe when your message
arrived.
For the most part I had already discovered the answers to my original
queries, but read on... ;-)
>As Juan indicated, this behavior is supported by run "scons -c".
>A number of other software packages that are beginning to use SCons set
>up an alias in their SConscript files so you can still type "scons clean"
>at the command line.
>
That would be good. We autotoolers are quite familiar with the 'make;
make install; make clean' process...
>> 3. No man pages, that sucks on a UNIX/Linux platform. The GNU
>>autotools have them, SCons should have them too.
>>
>>
>
>How are you installing SCons? We do have a very thorough man page, but
>it sounds like you've stumbled into a hole in the process that prevents
>it from being installed. Can you help me understand what it is so we
>can fix it? Is this from one of the SCons packages you downloaded, or
>is it from the scons/ or scons-local/ package shipped internally with
>CT or CSound?
>
This is an odd one. Apparently the install step is not installing the
man page by default (someone else mentioned that they manually placed it
in /usr/local/man). I downloaded, built, and installed the SCons package
available from the home site, and I *think* I followed the instructions
exactly. At any rate, SCons itself works perfectly. :)
>> 4. No 'scons uninstall' ?? Again, if I'm missing it, please inform
>>me how it's invoked.
>>
>>
>
>As Juan indicated, this is something the SConscript writer has to supply.
>
I guess that's okay. I'd be happy if it were de rigeur for autotools too...
>> CT and Csound are now the only two apps on my system that use SCons.
>>The maintainers of Csound couldn't make the autotools work for
>>themselves, so now you must add downloading and installing SCons (and an
>>up-to-date Python)
>>
>>
>
>SCons itself is very intentionally written to run on an old Python version
>(1.5.2) so you don't have to install an up-to-date Python to use it.
>CT and Csound may require later versions of Python to handle Python 2.x
>code they've put in their SConscript files, though.
>
Mea culpa, sorry about that. Now it needs to become a de facto component
in all significant distros.
>Although SCons has been around a while now, it's only just now beginning
>to reach the sort of critical mass that makes all of the distro owners
>sit up and take notice. The more voices that request it of other distros
>(such as RH), the easier this will get...
>
>In the meantime, we're trying hard to continue to make SCons as easy as
>possible for both software developers and end users to use, so I'm very
>glad to receive the feedback. Thanks for posting your questions/comments,
>and if there are other ways SCons can be improved to make this sort of
>transition a little easier, please don't hesitate to let me know.
>
Thanks, Steven. Your response is much appreciated, and I'll be sure to
contact the SCons team if/when I run into any major difficulties.
Best regards,
Dave Phillips
Sorry for cross-posting.
Hi all,
now that my new website is online I'd like to let you know that I
recently added a 'Linux Audio' path to my weblog.
This is meant as an offer to all those who find themselves continuously
struggling with lots of postings to LA* & Co.
Of course this can only stand for my point of view and I won't claim for
completeness.
http://www.jawebada.de/index.cgi/blog/lad
Regards,
Jan
Hy there,
i fooled around with getting my rme hdsp card to work under my 2.6.4 kernel in
debian.
There is some information i collected and i am confused somehow...
If anyone has an idea to help me out I'd be glad to hear!!
Current status: I am able to address my hdsp-multiface f.e. with the app
hdspmixer, after having my box booting Win2k and doing a warm-reboot into
debian running 2.6.4 kernel.
This i found on the net:
If you have a recent hdsp-card or if you are using a recent (December, 2002)
driver in windows or macOS, you might have the wrong firmware installed.
In order to make alsa-hdsp recognize the hdsp you have to downgrade the firmware
of your card(bus) to revision 10 (0xa hex).
(by klingt.org)
Q: Is this still so? I'm using my Multiface with different computers, running
Win2k, Mac OSX and Debian, so I'd like to be able to use the latest drivers
(which also implies using the latest firmware i guess)
Q: Where to get the firmware??
Q: Has the firmware get loaded via hdsploader after loading the modules, and how
do you do it? a script?
Anyway, i get:
bigh:~/alsa-tools-1.0.4/hdsploader# ./hdsploader
hdsploader - firmware loader for RME Hammerfall DSP cards
Looking for HDSP + Multiface or Digiface cards :
Card 0 : RME Hammerfall DSP + Multiface at 0xdfdf0000, irq 18
Upload firmware for card hw:0
Unable to open file
'/usr/local/share/alsa/firmware/hdsploader/multiface_firmware_rev11.bin' for
reading
There is no alsa directory in: /usr/local/share/
I just compiled a 2.6.4 kernel and I don't feel i have to apt-get-install alsa
since i'm glad to have alsa in my kernel finally... :-)
(btw: if i'd install alsa via apt-get, would that overwrite crucial
settings/files created by my 2.6.x kernel?)
Thanks if anyone has time to help me out!!!
Peter~
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
Hello all,
I have finally made the choice in a card for my laptop, and got a VXPocket
440.
Does anyone have any advice on using this card?
The literature and specs from evrywhere I look says that it can use all 4
inputs, but when I fire up a mixer, I only see 2. Is this the case, of can
that be modified?
Any help would be great!
Thanks,
Wade
Having seen the recommendations for gcdmaster, and because my partner
has lots of tapes she wants to archive to CD, I installed it on her
(recent Debian snapshot) system.
It worked very nicely for about 5-10 minutes and then crashed with a
segfault, whilst editing track marks. Repeatedly.
Anyone know what environmental factors can affect this? Somebody must
have it running more stable than that to abe able to use it. The version
of gcdmaster seems to be the latest - 1.1.7
Hardware: AMD Duron 1300, 512M RAM, onboard CMI sound chip,
run-of-the-mill IDE drive. Lots of USB devices (printer,
mouse, KB, scanner)
Software: Kernel 2.4.25, Gnome 2.4 desktop.
If it doesn't work we'll be back to doing it the hard way with Audacity,
which at least works.
I might try with a small enough audio file to fit all in memory, in case
it's a VM problem. And better check there is a swap partition - I'm sure I
installed one....!
Any suggestions gratefully welcomed.
PS just seen that version 1.1.8 is available. Better try that too...
--
Anahata
anahata(a)treewind.co.uk Tel: 01638 720444
http://www.treewind.co.uk Mob: 07976 263827