Hey everyone,
I'm currently looking into a computer upgrade, including new
disks. As everyone here knows, more space is well worth it.
Unfortunately, money isn't unlimited ::-(.
Previously, I've always kept my disks in mirrored pairs to
ensure the death of one disk didn't cost me any data. But looking
around, I'm not sure if I wanna spring the $200 for a pair of 120G+
drives. But we all know I'll regret getting something smaller.
Does anyone here have some other clever solutions to getting
reliable archives of recordings? My ardour sessions, even for demos
quickly outpace what will reasonable fit on to CDs. DVD burners are
still way out of my price range. I'm plum out of ideas.
Thanks for any tips!
--
Ross Vandegrift
ross(a)willow.seitz.com
A Pope has a Water Cannon. It is a Water Cannon.
He fires Holy-Water from it. It is a Holy-Water Cannon.
He Blesses it. It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it. It is a Wholly Holy Holy-Water Cannon.
He has it pierced. It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official. It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive. He shoots them.
Not that many of you live in Korea but I am playing a live ambient set
tomorrow night using only my computer.
http://www.djcj.org/shevaka
The software I will be using: spiralsynthmodular x1, alsaplayer x3,
jackeq x1, and jack timemachine to hopefully record it all.
I also have been working for the past month with ardour and audacity
creating a lot of the samples which I will inject into the soundscape
with alsaplayer.
This will be my first real gig performing my music. Not just djing other
peoples cuts (which I have been enjoying doing for the past 3 years).
It wouldn't be possible for me to accomplish this without the awesome
assistance from Steve Harris who designed the djeq plugin and dj flange.
I'm also relying heavily on the latest cvs version of ssm as it has
improvements to the jack plugin and echo plugin among other things which
I will be thrashing heavily :).
I feel this is important to let y'all know about because I have worked
(and I mean work) for the past 4 years to get to this position and in
the process I had a lot of fun with and help from many of you to get here.
I chose not to invest in windows or mac apps 5 years ago and I am
pleased that my gamble and investment in time and energy has paid off.
Big ups to all the people who are following the dream through to concept
through to reality.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
Mark Constable wrote:
>
> http://alsa.opensrc.org/index.php?action=find&find=envy24control
>
> Probably more exciting info somewhere but the above may help.
Thank you. There is some information about installing and OSS emulation,
but unfortunately nothing helpful about how to use envy24control.
Anahata wrote:
>
> Does this have something to do with Audacity only working with OSS sound
> drivers?
>
> I think it can be made to work, either by later versions of Audacity
> having ALSA support or by using ALSA's OSS emulation, but as you can
> probably tell, I haven't tried this. I am using Audacity with OSS,
> which works fine for my purposes, including recording via S/PDIF input.
Harald Milz wrote:
>
> man arecord maybe.
In the meantime I tried to use arecord (which unfortunately does not
provide man pages) to avoid OSS emulation problems:
arecord -f dat test.wav
produces mute files again. However it works with
arecord -f S16_LE -r 48000 test.wav
*but* this results in a mono file with too low signal level.
I also did not succeed in playing around with the
recording/muting/volume settings of alsamixer. :-(
HippiE
I'm trying to use the Gate plugins (from the swh plugin collection) with
Ardour. Seems like that isn't quite the right place for them - there
seems to be no place for the non-audio input / output?
So what other app could I use them in?
thanks
John
Jan Depner wrote:
>
> Try changing /dev/dsp to /dev/dsp0. Usually /dev/dsp is a link to
> /dev/dsp0 but not always.
This link is okay.
> Also, can you see the signal in envy24control?
Yes, I can see it an route it - directly or via the mixer - to the
analog outputs.
> I was under the impression that there might be a problem with
> the SPDIF inputs on the envy24 chipset cards with ALSA but I could be
> wrong.
I do not think so because I can mix, DA and output the signal.
HippiE
tim hall wrote:
>
> Why are you using such an old version of alsa?
> Perhaps this is the way SuSE does it (?:-)
Right, this is part of SuSE 8.2.
>>But how can I record the data?
>
> What do you mean by 'data'? If you just want the data, surely there is some
> kind of way of 'mounting' the tape drive directly - As if it was a Tape
> ARchive and then using standard tools to copy it where you want it - 'dd' ?
Mounting the DAT recorder?! Sounds interesting... ;-)
> You probably haven't read enough, and my experience is that it's easy to
> overcomplicate matters. There may be a simpler solution. Oh yeah, and you
> need to ask clearer questions.
What I want to have is a 1:1 copy of the audio data of a DAT deck. For
this I use its SPDIF-out and plug it to the SPDIF-in of the Audiophile.
Using envy24control I can route the signal to the cards internal mixer
or to its outputs. But how can I record it to an audio file?
Recording with Audacity results in a mute file. In its preferences I
found the sole option /dev/dsp as recording device.
I am determined to read more about it if you can tell me *what* to
read...
Ciao,
HippiE
Hi there,
I still try to record a DAT signal. In the meantime I installed a
M-Audio Audiophile 2496 as card 0. I can configure it using
envy24control (alsa 0.9.0) and route the signal to the mixer or directly
to the outputs.
But how can I record the data? Programs like Audacity or krecord do not
"hear" it. What do I do wrong?
Ciao,
HippiE
> -----Original Message-----
> From: Dave Phillips [mailto:dlphilp@bright.net]
>
> PlanetCCRMA is definitely has the more current apps versions, but
> AGNULA Demudi is really quite nice too. I have both systems installed
> here, and I must say that I'm impressed by the AGNULA core system. Yes,
> it's not pretty (yet), but it's well designed where it counts, and the
> 1.1 release promises to bring the system into a more up to date
> condition.
I will 3rd (or 4th?) the Agnula recommendation. I had originally installed
ccrma (which is fantastic for those who want to just get up and go!) but I
wanted to do a lot of stuff with PD that wasn't yet supported under ccrma,
but was supported under debian out of the PD CVS. I installed a base woody
system, then set all of my apt stuff to testing, and used the Agnula disks
to get the sound stuff set up. After some initial X and mouse problems with
agnula (now being tracked in their bug databse) I was good to go.
> I'm not sure when AGNULA 1.1 will be ready for release but
> I'm sure it's Real Soon Now. ;)
January 15th according to some recent posts of the Agnula list.
> Next month's column for the Linux Journal On-line will briefly
> describe my experiences with PlanetC and AGNULA.
Cool. By the way Dave GREAT article in CMJ. I just got back from vacation,
checked the mail, and saw the cover! Having just jumped into the Linux world
I was happy to see the article. (A month or 2 to late for me, but I'm sure
it will help a lot for others!)
m.
Mark,
Set state the way you want it then do alsactl store to save it. On reboot do alsactl restore and it will reset. The easiest way to do this is to add something to your rc.local script (wherever that is depending on distribution). On RH the best thing to do is add a file to /etc/rc.d/init.d that uses chkconfig (look at some of the other files in there). On start/boot it should do alsactl restore. On stop/halt it should do alsactl store. If you set it up like some of the other scripts in /etc/rc.d/init.d you should be able to turn it on by entering chkconfig FILENAME on.
Jan
-----Original Message-----
From: "linux-audio-user-bounces(a)music.columbia.edu" <linux-audio-user-bounces(a)music.columbia.edu> on behalf of "Mark Constable" <markc(a)renta.net>
Sent: Tue, 30 Dec 2003 21:39:21 +1000
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Subject: [linux-audio-user] Using alsactl to preserve volume state
On the Wiki there is this advice and the following statement so
would anyone happen to know what the correct way to preserve
state across reboots for 2.6 is ?
# load/unload the volume settings on startup/shutdown
post-install snd-driver-name /usr/sbin/alsactl restore
pre-remove snd-driver-name /usr/sbin/alsactl store
This doesn't seem to work with a 2.6.0-test kernel. modprobe
simply ignores lines with these statements. Update to this
section would be appreciated.
--markc
On the Wiki there is this advice and the following statement so
would anyone happen to know what the correct way to preserve
state across reboots for 2.6 is ?
# load/unload the volume settings on startup/shutdown
post-install snd-driver-name /usr/sbin/alsactl restore
pre-remove snd-driver-name /usr/sbin/alsactl store
This doesn't seem to work with a 2.6.0-test kernel. modprobe
simply ignores lines with these statements. Update to this
section would be appreciated.
--markc