Linux-audio-user October 2004

linux-audio-user@lists.linuxaudio.org

153 participants
223 discussions

[linux-audio-user] LAC 2004 recordings now online

by Joern Nettingsmeier

hi everyone! thanks to the work of stephan römer at zkm, the recordings of the linux audio conference 2004 are now completely edited and tagged. they are being uploaded as i type. you will find them at http://linuxaudiodev.org/contrib/zkm_meeting_2004/recordings/ , the corresponding slides are at http://linuxaudiodev.org/contrib/zkm_meeting_2004/slides/ . best regards, and sorry it took so long (my responsibility), jörn ps: if you have more photos, recordings or other lac memorabilia to share, throw them my way so that i can upload them. -- "90% of all networking problems are routing problems. 9 of the remaining 10% are routing problems, but in the other direction. The final 1% might be something else, but check the routing anyway." - Anthony Stone's networking words of wisdom Jörn Nettingsmeier Lortzingstr. 11, 45128 Essen, Germany http://spunk.dnsalias.org (my server) http://www.linuxaudiodev.org (Linux Audio Developers)

20 years, 3 months

[linux-audio-user] Re: [Jackit-devel] [Fwd: Re: Linux audio latency]

by Lee Revell

On Sat, 2004-10-02 at 17:49, John Hedditch wrote: > As you can see, the actual kernel latencies are pretty low, but I still get > big xruns - for example just starting hydrogen gives me 3 xruns ( 1.026, 0.188, and 4.895 msec respectively ). > > Also, Hydrogen seems to crash if I run with > jackd -R -p512 -t200 -dalsa -dhw:0 -r96000 -p64 -n2 -M Now that might be a hydrogen bug. On my system it sounds OK at 32 frames and 128 frames, but crackles terribly (no xruns though) at 64. In any case it crashes within a minute. Also, there is a known issue where starting a new jack client causes xruns. I don't remember what the status is. My theory is that the VP patches are exposing bugs in other apps. Lee

20 years, 3 months

[linux-audio-user] linux-2.6.9-rc3-mm1-s8 patch make error

by thewade

Hello all! Has anyone else had this problem? I patch 2.6.8.1 with 2.6.9-rc3, 2.6.9-rc3-mm1, and vp-2.6.9-mm1-s8. My machine is an AMD64 3400+ laptop running FC3t1 and gcc-3.4.1-2 When I make I get: CC kernel/irq/autoprobe.o In file included from kernel/irq/autoprobe.c:9: include/linux/irq.h:78: error: syntax error before \"wait_queue_head_t\" include/linux/irq.h:78: warning: no semicolon at end of struct or union include/linux/irq.h:80: error: syntax error before \'}\' token include/linux/irq.h:80: warning: type defaults to `int\' in declaration of `irq_desc_t\' include/linux/irq.h:82: error: syntax error before \"irq_desc\" include/linux/irq.h:82: warning: type defaults to `int\' in declaration of `irq_desc\' include/linux/irq.h:82: warning: data definition has no type or storage class In file included from kernel/irq/autoprobe.c:9: include/linux/irq.h:92: error: syntax error before \"irq_desc_t\" include/linux/irq.h:92: warning: function declaration isn\'t a prototype include/linux/irq.h:93: error: syntax error before \"irq_desc_t\" include/linux/irq.h:93: warning: function declaration isn\'t a prototype kernel/irq/autoprobe.c: In function `probe_irq_on\': kernel/irq/autoprobe.c:30: error: `desc\' undeclared (first use in this function) kernel/irq/autoprobe.c:30: error: (Each undeclared identifier is reported only once kernel/irq/autoprobe.c:30: error: for each function it appears in.) kernel/irq/autoprobe.c:31: warning: ISO C90 forbids mixed declarations and code kernel/irq/autoprobe.c:42: error: request for member `action\' in something not a structure or union kernel/irq/autoprobe.c:43: error: request for member `handler\' in something not a structure or union kernel/irq/autoprobe.c:80: warning: ISO C90 forbids mixed declarations and code kernel/irq/autoprobe.c: In function `probe_irq_mask\': kernel/irq/autoprobe.c:121: error: `desc\' undeclared (first use in this function) kernel/irq/autoprobe.c:122: warning: ISO C90 forbids mixed declarations and code kernel/irq/autoprobe.c: In function `probe_irq_off\': kernel/irq/autoprobe.c:163: error: `desc\' undeclared (first use in this function) kernel/irq/autoprobe.c:164: warning: ISO C90 forbids mixed declarations and code make[2]: *** [kernel/irq/autoprobe.o] Error 1 make[1]: *** [kernel/irq] Error 2 make: *** [kernel] Error 2 I dont know what to do. Thanks for the help! -thewade

20 years, 3 months

Re: [linux-audio-user] linux-2.6.9-rc3-mm1-s8 patch make error

by thewade

> Should I ask if the build target is amd64 specific? Yes, Im building for AMD64 3400+ laptop. Thanks! -thewade

20 years, 3 months

[linux-audio-user] Ardour working again & splitting files

by Greg Reddin

I updated planet and my Ardour transport is working again. It looks like some significant changes were made since I last used it so I'll give it more time before bailing off the deep end. So I found a session that was a live recording I did a year ago. I want to test Ardour by mixing down this session. But I'd rather split it into sections and mix each song separately. Should I do that outside of Ardour then reimport the tracks into separate sessions or is there a way to create separate song mixes within sessions and mix down to multiple wav files? What would you think is the best way to work with this session? Thanks, Greg _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com

20 years, 3 months

Re: [linux-audio-user] linux-2.6.9-rc3-mm1-s8 patch make error

by thewade

> > When I make I get: > > CC kernel/irq/autoprobe.o > > In file included from kernel/irq/autoprobe.c:9: > > You need to start with 2.6.8, not 2.6.8.1. There were probably some > rejects. Indeed I did start with 2.6.8.1 but I think I only had two rejects and one was just setting the minor/extra version in the make file. Im not sure of the other one, it flew by too fast. So I started with 2.6.8 this time but die at the same point. I then upgraded from gcc-3.4.1-2 to gcc-3.4.1-10 (the newest rpm I could find) but it dowent help any. I looked at the code and there is no obvious syntax problem. There may be a problem with struct task_struct *thread; but I couldnt tell you what it is, though Ive never seen a one line struct with no curly brackets... Thanks for the help! -thewade

20 years, 3 months

Re: [linux-audio-user] suggestions for USB/serial/PCMCIA MIDI interfaces ?

by Pedro Lopez-Cabanillas

On Monday 04 October 2004, Chris Cannam wrote: > On Monday 04 Oct 2004 12:25, Emiliano Grilli wrote: > > So, they are at the same price, offer the same functionality, one is easy > > to setup and does not involve the use of proprietary software, the other > > is "more difficult to get working", why should I choose the m-audio? > > The MidiSport 2x2 doesn't involve the use of proprietary software, as there > is the GPL firmware (which Pedro mentioned) that works fine. Same goes for > the 1x1, but not I think the 4x4 or 8x8. Yes, thanks. That is exactly what I mean. I think that he is confused about the meaning of "firmware". It is not a synonym of proprietary things. Quoting the Wikipedia (http://en.wikipedia.org/wiki/Firmware): "In computing, firmware is software that is embedded in a hardware device." > Nitpicking aside, I agree with you -- I have a 2x2, and I've found the > firmware situation just awkward enough to recommend getting something else > instead. Twice now I've managed to take it with me on the road only to > remember, when miles from an internet connection, that I'd upgraded the > laptop OS more recently than I'd last used the MidiSport and that I no > longer have a copy of the firmware. You are right here. If mobility is your first requirement then a device that requires firmware is not a good choice. And the USB devices are suitable companions for laptops. But there are several advantages with the loadable firmware. You can upgrade the functionality without modifying the device phisically. A bug in the device's logic is not forever. And if you use a GPL firmware, you can even customize the firmware to suit your needs. For instance, these are some differences using the Midisport2x2 with the proprietary firmwares, compared to the ezusbmidi functionality. 1. ezusbmidi is designed and works following the USB-MIDI standard specification, so you can use the interface with the ALSA driver or the OSS driver, or any other driver conforming the specification without the need of specific quirks. The proprietary firmware is not conforming with the standards, and can be used only with the ALSA drivers, because it has a quirk for it. Look at the USB descriptors shown by `lsusb -v` after loading each firmware if you are curious about this. 2. The proprietary firmware turns on the green leds for every MIDI event received, including the "Active Sensing" events (0xfe). The ezusbmidi firmware doesn't switch on the lights for the received active sensing events (it does so only for the outcoming ones). It is trivial to modify the sources to ignore completely these (or other) kind of events if you want. Thats your freedom. Regards, Pedro

20 years, 3 months

[linux-audio-user] Re: how videocard affects audio?

by Kjetil Svalastog Matheussen

Andrew Gaydenko: > > Hi, > > Saying "aidio", I mean jack/latency/allRealted area. I have rather ancient > videocard - some info is below. Is it worth to think about an upgrading in > concerning with audio work? If it's so - are there cheap decisions here? > Suggestions? > > Andrew > //////////////////////////// > # cat /proc/driver/nvidia/cards/0 > Model: GeForce2 MX 100/200 I think the videocard should be more than okey for audio use, but you might consider using the open-source nv driver instead of the closed-source nvidia driver to get less xruns and be able to run with lower latency settings. --

20 years, 3 months

[linux-audio-user] how videocard affects audio?

by Andrew Gaydenko

Hi, Saying "aidio", I mean jack/latency/allRealted area. I have rather ancient videocard - some info is below. Is it worth to think about an upgrading in concerning with audio work? If it's so - are there cheap decisions here? Suggestions? Andrew //////////////////////////// # cat /proc/driver/nvidia/cards/0 Model: GeForce2 MX 100/200 IRQ: 16 Video BIOS: 03.11.01.37.00 Card Type: AGP # cat /proc/driver/nvidia/agp/card Fast Writes: Not Supported SBA: Not Supported AGP Rates: 4x 2x 1x Registers: 0x1f000007:0x1f000104 r # cat /proc/driver/nvidia/agp/host-bridge Host Bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface Fast Writes: Supported SBA: Supported AGP Rates: 4x 2x 1x Registers: 0x1f000217:0x00000104

20 years, 3 months

[linux-audio-user] suggestions for USB/serial/PCMCIA MIDI interfaces ?

by Dave Phillips

Greetings: I'd like to gain some hands-on knowledge on setting up a MIDI interface from my laptop to external gear. eBay lists a lot of USB MIDI interfaces, but I'd like to know what users on the list recommend for an inexpensive 1x1 or 2x2 box. I'm also looking for a serial port interface, probably one of the Key Midiator boxes. There's one on eBay now, but I'm being outbid on it by someone who obviously wants it more than I do. If anyone has one to sell please let me know, and I'd also like to know of anyone's experience with the Midiator. Finally, is there such a beast as a PCMCIA MIDI interface card ? Audio cards I know about, but I don't recall ever seeing such a creature as a PCMCIA MIDI card. TIA! dp

20 years, 3 months

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 October 2004