Linux-audio-user April 2005

linux-audio-user@lists.linuxaudio.org

163 participants
185 discussions

Re: [linux-audio-user] audiophile 2496 with Fedora Core 3

by aljordan＠maine.rr.com

I would highly recommend using the planetccrma fedora core 3 packages. See http://ccrma.stanford.edu/planetccrma/software/ I just started using the Audiophile 2496 along with the onboard sound of my motherboard and the planetccrma kernel and packages work flawlessly. They have a package called envy24control or something like that which works very well with the 2496. Hope this helps, Alan ----- Original Message ----- From: Michael Mossey <mpm(a)alumni.caltech.edu> Date: Saturday, April 16, 2005 11:47 pm Subject: [linux-audio-user] audiophile 2496 with Fedora Core 3 > Hello, > I'm new to the Linux sound world. I'm trying to get an Audiophile > 2496 to > work on Fedora Core 3. I was able to install the OSS driver; > however, it > isn't putting sound out the SPDIF output, which is what I want. I > triedto run alsamixer but got a message > > alsamixer: function snd_ctl_open failed for default: No such device or > address > > Searching the web I see many people claim to get the Audiophile 2496 > working but they describe how they did it in very general terms > that I > don't understand. > > Can anyone help, or point me to the right forum if this isn't it? > > Thanks so much, > Mike > >

20 years, 1 month

[linux-audio-user] Core Audio Format

by Netserva Desktop User

Anyone know more about the details of this (kind of looks like an ogg or avi wrapper for audio) audio format and whether we can interoperate with it ? . Core Audio Format is the latest addition to the . dozens of audio formats supported natively in Mac . OS X. Developed by Apple, Core Audio Format (CAF) . combines virtually infinite capacity with rich . support for metadata in an optimized-for-audio . package. As a 64-bit file format, you can record . a thousand channels of audio for a thousand years . in a single file. And it can store any audio data, . whether uncompressed PCM or compressed such as AAC. . Application support for these files is available . today in QuickTime 7. http://www.apple.com/macosx/features/coreaudio/ --markc

20 years, 1 month

[linux-audio-user] S/PDIF Clock Problem

by Steven Tonge

I have been having problems with the internal clock on my system ever since I connected my S/PDIF input to an eyernal sound source. I have tried changing the "Multi Track Internal Clock" in both alsamixer and envy24control. Anyone know how to fix this? I am using alsa 1.0.8-7 with an M-Audio Delta 1010LT on a DeMudi based system. Thanks Steven

20 years, 1 month

RE: [linux-audio-user] audiophile 2496 with Fedora Core 3

by Henry Camacho

If I remember correctly you must use ossxmix, and configure the interface to use SPDIF. In my configuration I provide Sync from a MOTU 1296. It works really well. If you are still running into problems email me directly and I will send you configurations of my current setup. HFC -----Original Message----- From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-user-bounces@music.columbia.edu] On Behalf Of Michael Mossey Sent: Saturday, April 16, 2005 10:48 PM To: linux-audio-user(a)music.columbia.edu Subject: [linux-audio-user] audiophile 2496 with Fedora Core 3 Hello, I'm new to the Linux sound world. I'm trying to get an Audiophile 2496 to work on Fedora Core 3. I was able to install the OSS driver; however, it isn't putting sound out the SPDIF output, which is what I want. I tried to run alsamixer but got a message alsamixer: function snd_ctl_open failed for default: No such device or address Searching the web I see many people claim to get the Audiophile 2496 working but they describe how they did it in very general terms that I don't understand. Can anyone help, or point me to the right forum if this isn't it? Thanks so much, Mike

20 years, 1 month

[linux-audio-user] audiophile 2496 with Fedora Core 3

by Michael Mossey

Hello, I'm new to the Linux sound world. I'm trying to get an Audiophile 2496 to work on Fedora Core 3. I was able to install the OSS driver; however, it isn't putting sound out the SPDIF output, which is what I want. I tried to run alsamixer but got a message alsamixer: function snd_ctl_open failed for default: No such device or address Searching the web I see many people claim to get the Audiophile 2496 working but they describe how they did it in very general terms that I don't understand. Can anyone help, or point me to the right forum if this isn't it? Thanks so much, Mike

20 years, 1 month

[linux-audio-user] Re: Freesound (Comparisonics copyright)

by ix＠replic.net

On Sat, Apr 16, 2005 at 11:58:20PM +0200, martin pichlmair wrote: > > i often use: > > http://www.findsounds.com/ > > also features graphic + audio preview. but you don't know if you break > a copyright. Comparisonics is definitely trademarked, or copyright or whatever its called, but i guess only in the US? in any case, id love for more people besides Samplitude to use the weighted peak spectrum to color their waveforms, it makes editing much faster..

20 years, 1 month

Re: [linux-audio-user] recording WAV files from a midi file played through alsamodularsynth

by mrmoo1231＠ahooyay.omcay

>From: Kevin Cosgrove <kevinc@email-addr-hidden> >Date: Sat Apr 16 2005 - 20:23:57 EEST >If you're not picky about your patches, then you can use >this: >timidity -OwS -s 44100 -U -o outfile.wav infile.mid Thanks, yes, I've used that without problems. In this case I have a tweaked ams patch I particularly wanted to use for a fugue voice. I used timidity with some downloaded soundfonts so I know how to do /that/, and even output the wav file. In another posting, you'll see that I've finally succeeded in getting an output wav file, but the tempo is too fast for some unknown reason... Thanks for everyone's help. The Village Idiot (Mark) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

20 years, 1 month

Re: [linux-audio-user] recording WAV files from a midi file played through alsamodularsynth

by mrmoo1231＠ahooyay.omcay

--- "mrmoo1231(a)ahooyay.omcay" <mrmoo1231(a)yahoo.com> wrote: > >> It does not depend on your soundcard, so it's not > > >> necessary to set anything in the mixer. > > >> Did you set the gain and volume in the > PCM-out-module of ams? > > Yes, still no joy. :-\ > > -Mark Okay, revised version: It *did* work once I shut down alsamodularsynth, which freed up the device. (I loaded the resulting foo.wav into audacity to see if there was anything other than flat-line, and there was, but it also gave me the message that I couldn't access the i/o device. I took care of this by closing AMS). But now, the tempo of the foo.wav file is 2x as fast as it should be, even though the pitches are correct, as far as I can tell. If I use timidity to play the same file, I get the right tempo. Unless somehow I accidentally doubled the tempo last time I loaded the file into muse or rosegarden4... -Mark __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/

20 years, 1 month

Re: [linux-audio-user] recording WAV files from a midi file played through alsamodularsynth

by mrmoo1231＠ahooyay.omcay

>> It does not depend on your soundcard, so it's not >> necessary to set anything in the mixer. >> Did you set the gain and volume in the PCM-out-module of ams? Yes, still no joy. :-\ -Mark __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail

20 years, 1 month

Re: [linux-audio-user] Help tracking down xruns

by thewade

> Try the realtime-preempt kernel. It should work on AMD64 these days. Nope. 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

20 years, 1 month

← Newer
1
...
6
7
8
9
10
11
12
...
19
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user April 2005