Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7513 discussions

by Mario Lang

Hi. In case anyone ever wanted to send OSC messages directly from within Emacs, you might want to take a look at this: http://delysid.org/emacs/osc.html Its rather rough right now, but it definitely works and delivers float, int and string arguments correctly. Watch the page for updates. -- CYa, Mario

20 years, 7 months

[linux-audio-dev] mux concept paper

by mimo

I have put online the beginngs of a concept paper for an audio program I have been wanting to write for quite a while now. I wondered whether you could give me some feedback on it and share some of your experiences with me. A while ago I decided to call this *mux* where the name stands for nothing in particular. I have tested a couple of similiar audio apps for linux recently, and then toyed around with libraries I found on the net. I might be reinventing the wheel once more, but that's up for discussion.. The paper is work in progress, I'm hoping to add to it tomorrow night. Looking forward to hear back from you and thanks for any input.. mimo PS.: the paper is here http://mimo.gn.apc.org/mux/

20 years, 7 months

[linux-audio-dev] linux.conf.au Audio Miniconf

by Conrad Parker

This is a reminder, as the closing date for submissions is soon. Please do not confuse this event with the Linux Audio Conference (LAC) in Karlsruhe, Germany, which is on during the same week. There may or may not be video streaming or teleportation between the two. There are kangaroos in Australia. ------------------------------------------------------------ CALL FOR PARTICIPATION Linux Audio Miniconf at linux.conf.au (LCA2005) April 2005, Canberra, Australia http://www.metadecks.org/events/lca2005/ This mini-conference is part of linux.conf.au (LCA2005), Australia's national Linux conference. Participants of this mini-conference must register for LCA2005; the conference web site is http://linux.conf.au/ The Audio Miniconf comprises technical sessions during the day, and an opportunity for jamming and musical demonstrations in the evening at a local pub. This call for participation is for the technical sessions. Suggested topic areas include: * Linux for Digital Audio Workstations and musical instruments * low latency and reliable audio in the Linux kernel and userspace * systems for connecting music, processing and control hardware * core Linux audio subsystems: Jack, ALSA, LADSPA, etc. * software synthesis and sequencing applications * recording, editing and mastering applications * audio file formats and codecs * streaming and network services for audio * telephony and speech technologies * usability of music and audio applications Presentations must relate to Free and Open Source software and/or open standards. The suggested duration of sessions is 60 minutes; this may be varied according to the needs of each topic. If you would like to present a technical session, please mail a brief abstract (100-300 words) to audioconf-cfp(a)metadecks.org by February 20 2005. This mini-conference is being arranged by Conrad Parker (Sweep project) and Erik de Castro Lopo (libsndfile, Secret Rabbit Code), with venue and other logistics provided by the organisers of LCA2005. Conrad.

20 years, 7 months

[linux-audio-dev] Job Opening

by Andreas Roedl

Hello! Yes, the following job has something to do with Linux and audio. Linux System Administrator in an audio company. :-) SYSTEM ADMINISTRATOR NATIVE INSTRUMENTS is the world's leading manufacturer of software synthesizers and samplers for standard processors and an established brand for music- and audio software. Founded 1996 in Berlin, Native Instruments was one of the first companies to use the possibilities for real-time sound synthesis on the Windows and Macintosh operating systems. On account of this early market presence and technological head start, NATIVE INSTRUMENTS plays a key role in the booming market for audio software. The products, designed for both professionals and hobbyists alike, have won practically every relevant award in the field. Native Instruments is looking for a versatile IT professional to support its IT Department located in Berlin. Responsibilities: - Administrating a complex Linux based server network. - Working with and developing LAN network monitoring tools. - Participate in rotating "on call" schedule with other members of the team. - Design and maintain Firewall, VPN and IDS infrastructure. - Assist with corporate windows/mac desktop support. Requirements: - Must have good LAN troubleshooting skills (net. device and system level). Thorough understanding of network security aspects, common problems and solutions (ACL, firewall filtering, and VPN). - Knowledge of network related protocols (e.g., TCP/IP, IPSEC, routing protocols, 802.1x, OSC). - Solid background in Unix Systems Administration topics (e.g. LDAP, Webservers, MTAs, DNS, virtual servers, cluster management, VoIP). - Familiarity with Unix system programming (C/C++) a plus. - Strong scripting skills (e.g., PERL, shell scripting, Python). - Experience in a high-volume or critical production service environment. - Proven technical troubleshooting experience. - Senior level Unix systems or database administration experience. - Experience with network change management control tools and policies. - Experience with several Network Monitoring and other network administration tools. - Excellent written and verbal communication skills. - Experience and flexibility regarding on-call responsibilities. - Ability to work independently. For immediate consideration, please send a text (ASCII) of your resume to andreas.roedl(a)native-instruments.com. Andi -- -> Andreas Roedl -> Senior IT Manager / Head of IT Dept. -> NATIVE INSTRUMENTS GmbH -> andreas.roedl(a)native-instruments.de -> Schlesische Strasse 28 -> http://www.native-instruments.de/ -> D-10997 Berlin -> Tel. +49-30-61 10 35-1711 -> Germany -> Fax +49-30-61 10 35-2711

20 years, 7 months

[linux-audio-dev] strange jack ringbuffer problem

by Hans Fugal

I've been banging my head against this one all evening. Now I'm going to go to sleep on it, but I throw it out for the wiser and more experienced to see if you can see my error. The code is at http://fugal.net/~fugalh/src/alex which you are welcome to refer to and critique. It segfaults on line 171 of jack.cc, but not if I comment out line 158 (or use 0 for the second argument). It seems to segfault once input_rb is nearly or completely to the end (not full, since it is being drained by the other thread; it's just as it would wrap around). The autopsy shows that it is segfaulting because output_rb and consequentially vec is completely hosed. What I don't understand is how jack_ringbuffer_write_advance(input_rb, something_plenty_small) could possibly hose output_rb. something_plenty_small is usually on the order of 160 bytes. I'm running jackd with a 512 byte buffer at 48000Hz. (gdb) bt #0 0xb7f91253 in src_short_to_float_array () from /usr/lib/libsamplerate.so.0 #1 0x0804a01c in Jack::jack_process (this=0xbffff300, nframes=512, arg=0xbffff300) at jack.cc:171 #2 0x08049d87 in Jack::jack_process_wrapper (nframes=512, arg=0xbffff300) at jack.cc:114 #3 0xb7fb255d in jack_stop_freewheel () from /usr/lib/libjack-0.80.0.so.0 #4 0xb7d639b4 in start_thread () from /lib/tls/libpthread.so.0 #5 0x00000000 in ?? () (gdb) up #1 0x0804a01c in Jack::jack_process (this=0xbffff300, nframes=512, arg=0xbffff300) at jack.cc:171 171 src_short_to_float_array((short*)vec[i].buf, buf, vframes); (gdb) p *output_rb $1 = {buf = 0xd0b0c860 <Address 0xd0b0c860 out of bounds>, write_ptr = 92858992, read_ptr = 88669736, size = 4291362712, size_mask = 13171512, mlocked = 3735008} (gdb) p vec $2 = {{buf = 0xd5f9c688 <Address 0xd5f9c688 out of bounds>, len = 4189256}, { buf = 0x804d028 "��", len = 0}} (gdb) p *input_rb $3 = {buf = 0x804d028 "��", write_ptr = 16266, read_ptr = 16266, size = 16384, size_mask = 16383, mlocked = 0} I hope someone can see what I'm doing wrong. Consider the code under the GPL. -- .O. Hans Fugal | De gustibus non disputandum est. ..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

20 years, 7 months

[linux-audio-dev] Native Buzz was: mux concept paper

by Jan Weil

There is an attempt to create a native and free replacement of Buzz at <http://www.buzztard.org>. The Status page suggests they could do with some help... -- Jan Weil http://linuxaudioblog.jawebada.de

20 years, 7 months

Re: [linux-audio-dev] Linux DSP Hardware?

by Peter Zubaj

Hi, >what if we want to experiment with h/w dsp? (e.g. the 1820m from creative professional aka emu) AFAIK emu1820 uses Audigy DSP - hw DSP effect are available only for 48 kHz. Correct me if I am wrong. Peter Zubaj ____________________________________ Vsetko o SuperStar http://superstar.atlas.sk

20 years, 7 months

[linux-audio-dev] [ANN] libDSP-5.0.1

by Jussi Laako

libDSP is a C++ library of digital signal processing functions with class and template interface. It also has a wrapper for C language. It also has assembler optimizations for x86 (E3DNow! and SSE2) and x86-64 platforms. Changes: - Assembler optimized version of complex multiply-add has been added. - Some makefile cleanups and fixes. Homepage: http://libdsp.sf.net http://www.sonarnerd.net/projects/libdsp/ Download: http://sourceforge.net/project/showfiles.php? group_id=25287&package_id=17119&release_id=305295 http://www.sonarnerd.net/projects/dlbins/ -- Jussi Laako (MiskaX || SonarNerd @ IRC) <jussi.laako(a)pp.inet.fi>

20 years, 7 months

[linux-audio-dev] X Error: BadWindow errors with qjackctl 0.2.15a

by Lee Revell

Every time I start qjackctl from a remote X session I get these errors at startup. I am using the Cygwin X server. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 Minor opcode: 0 Resource id: 0x3a X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 18 Minor opcode: 0 Resource id: 0x134 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x3a Then if I activate the Messages window and move the mouse back and forth between it and the qjackctl window I get tons of these. They seem to be associated with the tooltips popping up in the main qjackctl window. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 38 Minor opcode: 0 Resource id: 0x3a The latter are especially annoying as they spam the Messages window not the xterm I launched qjackctl from. Lee

20 years, 7 months

Re: [linux-audio-dev] X Error: BadWindow errors with qjackctl 0.2.15a

by eviltwin69＠cableone.net

Can you log in to the remote system using ssh -Y? This looks like one of the X11Forwarding problems. Jan On Thu, 17 Feb 2005 13:11 , Lee Revell <rlrevell(a)joe-job.com> sent: >Every time I start qjackctl from a remote X session I get these errors >at startup. I am using the Cygwin X server. > >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadAtom (invalid Atom parameter) 5 > Major opcode: 18 > Minor opcode: 0 > Resource id: 0x134 >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 7 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 7 > Minor opcode: 0 > Resource id: 0x3a > >Then if I activate the Messages window and move the mouse back and forth >between it and the qjackctl window I get tons of these. They seem to be >associated with the tooltips popping up in the main qjackctl window. > >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a >X Error: BadWindow (invalid Window parameter) 3 > Major opcode: 38 > Minor opcode: 0 > Resource id: 0x3a > >The latter are especially annoying as they spam the Messages window not >the xterm I launched qjackctl from. > >Lee

20 years, 7 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-dev