Linux-audio-user September 2006

linux-audio-user@lists.linuxaudio.org

165 participants
155 discussions

[linux-audio-user] Linux Rock Star blog...

by DCZX

Hello, I was just wondering if anyone had anything they would like to read about at Linux Rock Star, or any applications they would like announced... after a brief delay, I'm posting again at: http://linuxrockstar.blogspot.com thank you! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

18 years

[linux-audio-user] RME Digi96/8 PST, no S/PDIF out apparently

by Ismael Valladolid Torres

After some problems configuring jackd, I achieved making use of this card in the analog world, featuring 5ms of latency and superb audio quality. However, I tried to connect the optical output to the optical input on my minidisc and I am not being able to record anything. While listening to music using analog out, there's laser in the optical connector of the card. If I plug the cable there's laser in the other side of the cable. When plugged into the minidisc it says "NO SIGNAL". I read about lowering the mixer level to 0 in order to enable the S/PDIF out but that wasn't succesful here. Jack's running like this: $ jackd -R -dalsa -dhw:1 -r96000 -p256 -n2 I assumed that the same sound output was being forwarded to both the analog output and the optical output as S/PDIF, but I might be wrong. Any pointers welcome, thanks in advance. Cordially, Ismael -- Ismael Valladolid Torres "Il est vain de pleurer sur l'esprit, il suffit de travailler pour lui." Albert Camus http://digitrazos.info/ http://lamediahostia.blogspot.com/ OpenPGP key ID: 0xDE721AF4

18 years

[linux-audio-user] Ok, what about non firewire mobile cards?

by Iain Duncan

Ack, I guess it's premature for firewire mobile audio on a dual boot mactel. I really like the specs on the MOTU and RME firewire cards but don't want to wait an unknown length of time for drivers... =( Any suggestions on good alternatives for audio on a powerbook pro? How decent is the latency using a USB 2 solution and what are the top choices? Pros for me are: - at least one decent mic pre - at least one midi bus - hands on volume controls - lots of ins. Thanks Iain

18 years

[linux-audio-user] [PATCH] oss2jack for kernel => 2.6.17 (with patch)

by Salvatore Di Pietro

Ok, here is the patch :) ...And it is fusd-kor-1.10-11, not fusd-kor-1.10-10. Sorry, It's 2.13 AM and I'm almost asleep... ;) -- salvuz POST FATA RESVRGO Linux registered user #291700 | machine #174619 get counted on ---> http://counter.li.org/ <--- --- kfusd/kfusd.c 2006-09-26 00:57:19.000000000 +0200 +++ kfusd/kfusd.c.new 2006-09-26 00:58:43.000000000 +0200 @@ -67,7 +67,7 @@ #include <linux/mm.h> #include <linux/slab.h> #include <linux/vmalloc.h> -#include <linux/devfs_fs_kernel.h> +//#include <linux/devfs_fs_kernel.h> #include <linux/poll.h> #include <linux/version.h> #include <linux/major.h> @@ -85,7 +85,7 @@ #define STATIC /* Define this if you want to emit debug messages (adds ~8K) */ -#define CONFIG_FUSD_DEBUG +//#define CONFIG_FUSD_DEBUG /* Default debug level for FUSD messages. Has no effect unless * CONFIG_FUSD_DEBUG is defined. */ @@ -96,6 +96,8 @@ /* Define this to check for memory leaks */ /*#define CONFIG_FUSD_MEMDEBUG*/ +#undef CONFIG_DEVFS_FS + /* Define this to use the faster wake_up_interruptible_sync instead of * the normal wake_up_interruptible. Note: you can't do this unless * you're bulding fusd as part of the kernel (not a module); or you've @@ -2956,10 +2958,10 @@ cdev_del(fusd_control_device); cdev_del(fusd_status_device); - - devfs_remove(FUSD_CONTROL_FILENAME); - devfs_remove(FUSD_STATUS_FILENAME); - +#ifdef CONFIG_DEVFS_FS + devfs_remove(FUSD_CONTROL_FILENAME); + devfs_remove(FUSD_STATUS_FILENAME); +#endif class_destroy(fusd_class);

18 years

Re: [linux-audio-user] Re: ANN: bristol 0.9.5-60

by David Baron

On Tuesday 26 September 2006 11:05, linux-audio-user-request(a)music.columbia.edu wrote: > > MIDI works fine but one must specify the -mididev if this is not the > > first alsa/oss device. Mine being the second one, I have to give it > > /dev/midi1 in a OSS mode and hw129:0 in ALSA. I assume there is a way of > > (setting up for) using device names instead of this stuff. > > Please, David : > how did you make out the correct id (hw129) for your midi device ? > I also have a USB keyboard as my second soundcard, but I cannot make > out its id ... > It is listed in /proc/devices as KONTROL49, but that is not a correct > id for Bristol, obviously ... Works just fine either way. > > Also, to Nick : > would it be possible for Bristol MIDI connections to show up in > QJackctl or Patchage ? This would enable ignorants like me to patch > Bristol to their MIDI devices :-) Jack stuff should show up in Qjackctl connections and then the user could connect to whatever input and output he/she chooses (just like most other jack apps). It might be nice to have a little control window in Bristol to be able to dynamically connect rather than have to always do it on the command line but this is not necessary, especially if jack works and the connections show up!

18 years

[linux-audio-user] Re: ANN: bristol 0.9.5-60

by David Baron

Yes, Nice piece of work. However, I have the following problems on my Debian Sid box: 1. This new version seems to always load two instances of the requested synth: One without and one with the watermark. 2. After closing one synth and invoking another, the sounds of the previous one are still active. Cannot always get the new one to change. 3. Jack did not work. 4. Some of the synths get no sound. I may be I do not know how to use them. B3, Rhodes, Mini work out of the box. MIDI works fine but one must specify the -mididev if this is not the first alsa/oss device. Mine being the second one, I have to give it /dev/midi1 in a OSS mode and hw129:0 in ALSA. I assume there is a way of (setting up for) using device names instead of this stuff.

18 years

[linux-audio-user] Re: WINE and ASIO

by Stéphane Letz

> > Message: 1 > Date: Mon, 25 Sep 2006 15:50:23 -0400 > From: Dave Phillips <dlphillips(a)woh.rr.com> > Subject: Re: [linux-audio-user] WINE and ASIO > To: A list for linux audio users <linux-audio-user(a)music.columbia.edu> > Message-ID: <451832FF.80801(a)woh.rr.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Dave Phillips wrote: > >> FM7 still looks like it's working, but I still get no audio from >> it. :( > > Scratch that. For some reason the master volume gets set to 0 for each > patch. > > Demudi 1.3 Debian Etch, kernel 2.6.15 (homebrew) > WINE 0.9.21 patched for ASIO support. > WineCfg audio/MIDI set for ALSA. > JACK period size set to 1024 to accommodate apps' recommended ASIO > setting. > Audio and MIDI work nicely. I loaded a MIDI file demo, and I played > the > synth from an external MIDI keyboard. > > Potential interest should be modulated by the capabilities of Robert's > driver. Currently it supports only two channels and doesn't > self-configure via JACK (buffersize is hard-coded at 1024). Also, I > don't know how much more work Robert will put into the project. But > the > code is there, it's a good start, and it works. > > Best, > > dp > I think ideas (maybe code...) could be shared with similar projects that also does Jack <==> some other audio API connections, that is JackOSX/JackRouter that does the Jack <==> CoreAudio bridge on OSX and the ASIO JackRouter driver, part of jack on Windows implementation. - on both projects there is a notion of "virtual channel", basically the number of audio channels (that actually correspond internally to real jack ports) can be different from the number of jack ports the real hardware supports. This way jackified applications can use these additional audio channels to route whatever they need. This number of virtual channels typically needs to be managed in a global setup with a shared state visible by all jackified applications. - saving/restoring jack ports connections state: any Jack <==> some other audio API bridge has to map the jack client life cycle on the other audio API life cycle, so that each jack API call would correspond to one of the other audio API call. Although this mapping usually works well with most applications, one may have some that behave a bit stangely: for example jackified Max/MSP typically register a jack client the first time the DSP is set to on, but only *deactivate/reactivate* the jack client with its DSP is later set up off/on. When desactivated the jack client still appears in a connection tool, but cannot be connected anymore: when setting the DSP to on, the previous state of jack connection is just lost. In this case having an automatic saving/restoring jack ports connections state inside the bridge is very convenient.... Regards, SL

18 years

Re: [linux-audio-user] Linux-friendly portable music player?

by Paul Winkler

On Tue, Sep 26, 2006 at 12:14:33PM +0900, michael noble wrote: > If you are waiting for a declared stable release, you're missing out. I've > been running rockbox on 2 H140s here for probably 9 months and only had a > crash in the very early stages. I haven't had a single problem for about 6 > months now - it really is rock solid, and lightyears ahead of the default > firmware. That's very good to hear. What's your take on the usability of rockbox? How does it compare to the nightmare of long vs. short button press on the default firmware? -- Paul Winkler http://www.slinkp.com

18 years

[linux-audio-user] [PATCH] oss2jack for kernel => 2.6.17

by Salvatore Di Pietro

Hi all, As some may have noticed, fusd-kor-1.10-10 does not build anymore on kernel 2.6.17 and 2.6.18 (AFAICS in the latter because of removal of obsolete devfs), here's a patch I put together that makes it build again, in case someone other than me needs it. Kudos to Kor Nielsen for his nifty oss2jack! -- salvuz POST FATA RESVRGO Linux registered user #291700 | machine #174619 get counted on ---> http://counter.li.org/ <---

18 years

[linux-audio-user] WINE and ASIO

by Dave Phillips

Greetings: Recently I tested Robert Reif's ASIO driver for WINE. It works okay for some small test apps (asiosiggen and asiodump). I also tested it with NI's FM7, the app opens fine but I got no sound from it. I even loaded and played a MIDI file as a demo but still got no joy from the audio. I'm curious to try other ASIO-driven apps but I need some recommendations for light-to-middle weight programs for testing. Free/shareware is best, but feel free to suggest commercial apps too. I don't use Win/Mac music apps and I have no idea where to start. Best, dp

18 years

← Newer
1
2
3
4
5
6
7
8
...
16
Older →

Jump to page:

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 September 2006