Hi Linux Audio Users
Just wanted to share with you the professional soundtrack I wrote
for a short movie, since there are no rights/contract avoiding me from this.
This was written and composed entirely under Linux, and contains songs
in several styles, like piano, orchestral, techno, funk.
Only Tools Used:
-Shaketracker (sequencer)
-Chionic (sampler)
-Rezound (sound editor)
-A custom/unreleased app (a 32-bands graphical multiband compressor of
mine, which i'll release when i have time to polish it)
External Hardware:
-Roland Xp30, for sampling some instruments, some are live.
Soundtrack:
http://www.reduz.com.ar/sisteria/
Cheers!
I hope this helps to prove the level of maturity of the above apps.
Juan Linietsky
I'm having an issue getting sound out of my Delta 44. As root I can use
JACK in RT mode to play to both my on-board soundcard and my Delta 44.
As a user in the audio group, I can use JACK in RT mode to play to my
on-board soundcard, but not my Delta 44.
So, I'm confident that realtime-lsm is working properly, and that my
ALSA config is fine for my on-board soundcard. The only way I can get
sound out of my Delta 44 is to have root run JACK or have a user in the
audio group use OSS mode.
If I use an application like XMMS, I cannot use the ALSA driver directly
to play on the Delta 44 as root or a user. I have to use either JACK as
root or OSS as a user. It seems like it may be an ALSA issue, but I'm
at a loss to figure out why. I've tried various .asoundrc configs, but
to no avail. Gettting rid of a .asoundrc altogether yeilds the same
result. I've tried turning off OSS emulation by not loading the
modules, but it makes no difference.
I'm using the Gentoo kernel 2.6.11-gentoo-r6 with realtime-lsm 0.8.5-r1.
Alsa is not built into the kernel. Here's some more info:
# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.8.
Compiled on Apr 15 2005 for kernel 2.6.11-gentoo-r6.
# cat /proc/asound/cards
0 [M44 ]: ICE1712 - M Audio Delta 44
M Audio Delta 44 at 0xa400, irq 5
1 [nForce2 ]: NFORCE - NVidia nForce2
NVidia nForce2 with ALC650F at 0xe9080000, irq 9
When I start JACK through qjackctl, I get the following:
22:16:43.707 Patchbay deactivated.
22:16:43.726 Statistics reset.
22:16:43.738 MIDI connection graph change.
22:17:00.735 JACK is starting...
22:17:00.735 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2 -i2 -o2
22:17:00.742 JACK was started with PID=19234 (0x4b22).
jackd 0.99.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 ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|
32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
ALSA: cannot set channel count to 2 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
22:17:00.753 JACK was stopped successfully.
22:17:02.829 Could not connect to JACK server as client.
The error seems to point to the channel count, but whether I specify 2
or the proper number, which is 4, it makes no difference. Permissions
and ownership:group in /dev/sound and /dev/snd appear to be fine.
Any suggestions would be greatly appreciated. I can go on with life
running JACK and Ardour as root, but I'd really rather not. Previously
installed instances of Gentoo I've pointed all applications to JACK
running as a user and everything is happy. This install has me
scratching my head.
Alan
I'd like to be able to make an iso of a complete install including my
own software and data for csound, with the aim being a back up for gigs
should something go wrong. So ideally this would:
- detect any likely sound card properly
- ditto for midi
- have a low latency kernel
- have jack & some other misc alsa stuff
- create a reasonably sized ram disk in case I need to make some last
minute adjustments at the show.
I'd like to have the ability to quickly make a new version before each
show, so I want to be able to easily drop in some of my custom gig
software, along with csound5 plus my data and samples, and burn the cd.
Csound should be able to either use data files burnt on the cd, or
stored on the ramdisk in case adjustments were needed.
There seem to be plethora of live cd options. Can anyone suggest the
best course for the above? I normally use gentoo, but for the gig cd I
don't really care what it is as long as it's fast and clean and easy to
make. ( Ie a quick task that is done in a half hour before a show as a
back up. ) I don't even need xwindows really, just booting into runlevel
3 is fine, so if the live cd or utility allows that customization that
would be cool too. Being able to run a small LAN or vncserver would be
slick as well so that multiple machines can share the same monitor.
Thanks
Iain
Hi,
Andreas Kuckartz wrote:
>Marije,
>
>my mail was automatically rejected by sc-users(a)create.ucsb.edu because I am not
>subscribed. Maybe you want to forward it to that list.
>
>
I posted to both lists, in order to get as many possible responses as
possible...
After I checked out which live cd works easiest, I'll probably post
something in the SC world (on the list or on the swiki) about this, to
promote it :)
I will try the Demudi live cd (seems it is still the same one as the one
distributed last year at the LAC?) and send an email about my experiences...
It would probably be nice to have a more up-to-date version, as there
have been quite a few improvements in SC since last year...
sincerely,
Marije
Hi,
as an SC course has started here in Berlin at the TU and a lot of people
seem to have PC laptops, I was wondering whether anyone knows about a
Linux live cd which has a working version of SuperCollider on it (with
the emacs interface).
As the windows version is still a bit unstable and doesn't have all the
options yet, I think, a linux live cd with SC might be an easy solution
for those students who want to play around with SuperCollider, but do
not (yet) want to install Linux on their computer (of course, they might
in the run of time).
thanks for any hints.
sincerely,
Marije
When I installed Planetccrma, I had a the onboard motherboard sound card working. When I put the Audiophile 2496 in, I installed it, let kudzu find it.
After bootup I edited /etc/modprobe.conf and moved the new lines for the audiophile in front of the ones for the onboard sound, and I also reversed the snd-card-0 snd-card-1 numbers so that the audiophile 2496 was seen as the default sound card.
After that I added a .asoundrc file for the audiophile 2496 to my home directory and a system wide one to /etc based on the directions at the alsa site:
http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Midiman%2…
Alan
----- Original Message -----
From: Michael Mossey <mpm(a)alumni.caltech.edu>
Date: Sunday, April 17, 2005 5:24 pm
Subject: Re: [linux-audio-user] audiophile 2496 with Fedora Core 3
>
> Hmm, when I went to the Planet CCRMA website, it said "Install
> Fedora Core
> 3. You should now have a properly configured and working sound
> card.
> Then install the CCRMA sound applications." What's wrong with this
> picture is that I don't have a properly configured and working
> sound card
> after doing the Fedora Core 3 install. It didn't recognize my
> Audiophile2496 as far as I can tell--it configured the onboard
> sound. Can you tell
> me more specifically what you did to get the Audiophile 2496 working?
>
> Thanks,
> Mike
>
>
hi all
this has taken me ages ... dog knows why ... ten years, in fact :)
http://www.machinehasnoagenda.com/downloads/diggin_a_hole_-_final.ogghttp://www.machinehasnoagenda.com/downloads/diggin_a_hole_-_final.mp3
first "verse" was written said ten years ago during a particularly
scummy inner-city/amphetamine/paranoia period of my life ... second
verse was just since i got it happening with linux audio (few months
back) ...
it used to be just the first verse and chorus, really ... since then
i've dragged out the latent sonic youth-isms into the outro and given it
some more interesting (i think) rhythmic melodies.
i got this finished now so's i could rehearse it with the "band" on the
weekend.
i used hydrogen for the drums, and ardour to record all else (except
that feedback you can hear floating over some of it - with two young
kids around, i haven't found time or place to record pure feedback from
my amp, so i got this from the Slayer 2 VST guitar plugin - it has
astoundingly good feedback that you can control like well!).
also, there's a bunch of ladspa plugins for reverb and tube preamp
emulation on some parts (i've only just recently discovered the TAP
Reverb Editor - wow, it rocks!)
hope you all enjoy ...
and now to check out the back issues of music made with linux :)
shayne
> Try the realtime-preempt kernel. It should work on AMD64 these days.
Guess not. I tried 2.6.11 patched with 2.6.12-rc2 and
realtime-preempt-2.6.12-rc2-RT-V0.7.45-01 with full preemption,
the lowest preemption setting, and with the desktop setting but
nothing worked.
Any ideas?
Thanks!
-thewade
Error output--------
CONFIG_PREEMPT_RT=y
CC init/main.o
In file included from include/linux/rwsem.h:38,
from include/linux/kobject.h:24,
from include/linux/module.h:19,
from init/main.c:16:
include/asm/rwsem.h:55: error: redefinition of `struct rw_semaphore\'
In file included from include/linux/rwsem.h:38,
from include/linux/kobject.h:24,
from include/linux/module.h:19,
from init/main.c:16:
include/asm/rwsem.h:79:1: warning: \"__RWSEM_INITIALIZER\" redefined
In file included from include/linux/spinlock.h:16,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from include/linux/module.h:10,
from init/main.c:16:
include/linux/rt_lock.h:295:1: warning: this is the location of the previous definition
In file included from include/linux/rwsem.h:38,
from include/linux/kobject.h:24,
from include/linux/module.h:19,
from init/main.c:16:
include/asm/rwsem.h:83:1: warning: \"DECLARE_RWSEM\" redefined
In file included from include/linux/spinlock.h:16,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from include/linux/module.h:10,
from init/main.c:16:
include/linux/rt_lock.h:298:1: warning: this is the location of the previous definition
include/asm/rwsem.h:86: error: syntax error before \"do\"
In file included from include/linux/kobject.h:24,
from include/linux/module.h:19,
from init/main.c:16:
include/linux/rwsem.h: In function `compat_down_read\':
include/linux/rwsem.h:56: warning: passing arg 1 of `__down_read\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_down_read_trylock\':
include/linux/rwsem.h:67: warning: passing arg 1 of `__down_read_trylock\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_down_write\':
include/linux/rwsem.h:79: warning: passing arg 1 of `__down_write\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_down_write_trylock\':
include/linux/rwsem.h:90: warning: passing arg 1 of `__down_write_trylock\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_up_read\':
include/linux/rwsem.h:101: warning: passing arg 1 of `__up_read\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_up_write\':
include/linux/rwsem.h:111: warning: passing arg 1 of `__up_write\' from incompatible pointer type
include/linux/rwsem.h: In function `compat_downgrade_write\':
include/linux/rwsem.h:121: warning: passing arg 1 of `__downgrade_write\' from incompatible pointer type
In file included from include/linux/proc_fs.h:6,
from init/main.c:17:
include/linux/fs.h: In function `lock_super\':
include/linux/fs.h:828: warning: implicit declaration of function `compat_down\'
include/linux/fs.h: In function `unlock_super\':
include/linux/fs.h:833: warning: implicit declaration of function `compat_up\'
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
CONFIG_PREEMPT_DESKTOP=y
CC arch/x86_64/kernel/init_task.o
arch/x86_64/kernel/init_task.c:17: warning: implicit declaration of function `__RWSEM_INITIALIZER\'
arch/x86_64/kernel/init_task.c:17: warning: missing braces around initializer
arch/x86_64/kernel/init_task.c:17: warning: (near initialization for `init_mm.mmap_sem\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem.activity\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.page_table_lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmlist\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.cpu_vm_mask\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.users\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait.lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait.task_list\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.ctx_lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx\')
make[1]: *** [arch/x86_64/kernel/init_task.o] Error 1
make: *** [arch/x86_64/kernel] Error 2
CONFIG_PREEMPT_VOLUNTARY=y
CC arch/x86_64/kernel/init_task.o
arch/x86_64/kernel/init_task.c:17: warning: implicit declaration of function `__RWSEM_INITIALIZER\'
arch/x86_64/kernel/init_task.c:17: warning: missing braces around initializer
arch/x86_64/kernel/init_task.c:17: warning: (near initialization for `init_mm.mmap_sem\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem.activity\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.page_table_lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmlist\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.cpu_vm_mask\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.users\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait.lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait.task_list\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.wait\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx.ctx_lock\')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx\')
make[1]: *** [arch/x86_64/kernel/init_task.o] Error 1
make: *** [arch/x86_64/kernel] Error 2