Linux-audio-dev April 2005

linux-audio-dev@lists.linuxaudio.org

107 participants
90 discussions

Re: [linux-audio-dev] 3D fft analysis program

by Downer

> I'm hoping that you're thinking of a realtime display, in which the > peaks roll off to create a true waterfall effect. Baudline (http://www.baudline.com) is a fantastic viewer that does fft cascade. I've used it for a couple of years, and it is great for figuring out how different sounds "work", and it has an oscilloscope-type display as well. Cheers, Jason Downer

18 years, 6 months

[linux-audio-dev] Drum synth

by Dmitry Baikov

Hello. I finally started making my pet music project and realized I need a drum synth to make some cool sounds. psindustrializer is good but also need some tr-909-style sounds. I remeber from my old windoze days I used a nice piece of software called Stomper. Does anybody know any software for linux with comparable capabilities? Or we need to write one? Stomper does not work under wine :( Thanks.

18 years, 6 months

[linux-audio-dev] Re: Drum synth

by Juhana Sadeharju

Hello. I had a couple of articles on drum synths. Check ftp://ftp.funet.fi/pub/sci/audio/devel/lad/drumsynth/ I built the circuit in a00*.jpg at the time when this article was fresh. The article b00*jpg mentions an earlier article. I will check that out at library. Hmm.. I coded a drum synth for Commodore VIC-20 at the time. VIC provided an audio chip with three oscillators, noise, and a common volume if I remember correctly. What I did was to modulate osc pitch and volume parameters with a fast and accurate (compared to Basic) assembly code. The drum sounds were assigned to the keys. This was about 1984, inspired by Yamaha's digital RX drum synths, not by analog drums. Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software

18 years, 6 months

[linux-audio-dev] Re: lad design patterns

by Juhana Sadeharju

>From: "Levi D. Burton" <ldb(a)puresimplicity.net> > >does the idea of documenting various lad design patterns make >sense to anyone? Such "LAD Gems" doc would be much needed here too. (For audio dsp gems, take a look at "musicdsp.org".) I would appreciate if somebody would take a look at Ardour and document best gems found there. E.g., the GUI and audio thread separation and start up sequences. Likewise for Linuxsampler and one of its GUI frontends. Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software

18 years, 9 months

[linux-audio-dev] jack.el -- Run and monitor JACK from within Emacs

by Mario Lang

Hi. I am sure this sounds a bit crazy to some of you, but be ensured, I am not (yet) completely out of my mind and there are actually real reasons for doing what I do :-). I am now running jackd from within Emacs, using jack.el. Find it here: http://delysid.org/emacs/jack.el Basic usage: * Install the elisp file and put (require 'jack) in your .emacs. * Customize startup options: M-x customize-group RET jack RET * I.e. jack-sample-rate and jack-period-size are two important candidates. * Start jack: M-x jack-start You will see the verbose output in a special buffer called *JACK output*. * If you want/need to get rid of your jack instance, simply do M-x jack-kill RET * If you changed sample rate or any other startup parameter, do M-x jack-restart RET to make them effective. Plans: * Do something useful with xrun output, maybe some stats (suggestions?). * Add support for dummy and oss drivers, and add remaining ALSA params. * Write a patchbay based on jack_lsp and jack_{dis,}connect. Why am I doing this? You might have noticed I am recently seriously working on Emacs extensions related to Sound and audio. osc.el is working nicely and om.el, a client to drobillas om-synth is just waiting for a polish up. midi.el is parsing binary data already and needs a bit more careful planning before it can really grow. The idea behind jack.el was that I basically got fed up by jack wasting either a virtual console, or a screen window. Both dont really offer confortable scrollback, so the idea to make jack run from within Emacs, and collect all its output into a Emacs buffer was born. Some nice sideeffects: Load statistic is collected in a variable, so if you are into elisp, you can do fancy stuff like: (with-current-buffer (jack-output-buffer) jack-load) to retrieve the current load :-) Combine all this with things like csound-x (Csound support for Emacs) and the SuperCollider Emacs frontend, and you get a truly powerful composition and experimentation environment. One day I'll learn CLM and CM, and add it to the mix as well :-) -- CYa, Mario

19 years, 4 months

[linux-audio-dev] Please test the RT rlimits patch for audio

by Jody McIntyre

The RT rlimits patch (nice-and-rt-prio-rlimits.patch) has been proposed as a solution to allow audio users to run their applications with realtime priorities. While more complicated to configure, it's a much cleaner patch than realtime-lsm and it's likely to get merged soon _if_ enough audio users test it and confirm that it works. To encourage this, I have created a wiki page containing installation instructions, links to prebuilt PAM packages, etc: http://www.steamballoon.com/wiki/Rlimits If this works for you, I am collecting success reports. Please email rlimits-success(a)steamballoon.com . If you have any problems with it, LAU is probably the best place to ask for help. Unfortunately I don't have large amounts of time to spend helping people with this, so any help requests emailed to me directly may be deleted without a reply. Sorry. Thanks for testing! Jody

19 years, 6 months

Re: [linux-audio-dev] impulse convolution LADSPA plugin

by Stefan Turner

Hi Steve, thanks for the reply. I will definitely look into using DSSI, looks like it could be good once as supported as LADSPA is (I'd never even heard of it before your post, although that's probably just me). Is it intended as an eventual LADSPA replacement? I never really saw the need to divide plugins into 'instruments' and 'effects', and it seems like DSSI can do both. Stefan Turner > It would be more practical to do it as a DSSI plugin, LADSPA has no way > to > indicate that you want to load files during runtime, and no UI. > > In DSSI you can load the impulse in the "UI" process, perform the FFT > on > it and send it ot hte DSP code with configure(). Once there the DSP > code > can the overlap-add/save on it. > > - Steve ___________________________________________________________ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com

19 years, 6 months

[linux-audio-dev] HDSP No Go With 2.6.11 Kernel

by Janina Sajka

In case this is news, I'm reporting a total failure of the snd-hdsp driver under the latest Fedora released kernel, 2.6.11-1.14_FC3spksmp, both with the x86_64 and i686 kernels. As a result, I've reverted to 2.6.10-1.770_FC3spksmp.i686. I'm using 1.0.9RC2 of alsa driver, lib, utils, and tools. Firmware is 1.0.8 -- all most current releases. It seems as if no symbol in the driver is recognized. Here's the output from attempting to start alsa, and the relevant lines in dmesg: service alsasound start Starting sound driver: snd-hdsp FATAL: Error inserting snd_pcm (/lib/modules/2.6.11-1.14_FC3spksmp/kernel/sound/core/snd-pcm.ko): Unknown symbol in module, or unknown parameter (see dmesg) WARNING: Error running install command for snd_pcm FATAL: Error inserting snd_hdsp (/lib/modules/2.6.11-1.14_FC3spksmp/kernel/sound/pci/rme9652/snd-hdsp.ko): Unknown symbol in module, or unknown parameter (see dmesg) done snd_pcm: disagrees about version of symbol snd_info_register snd_pcm: Unknown symbol snd_info_register snd_pcm: disagrees about version of symbol snd_info_create_module_entry snd_pcm: Unknown symbol snd_info_create_module_entry snd_pcm: disagrees about version of symbol snd_timer_notify snd_pcm: Unknown symbol snd_timer_notify snd_pcm: disagrees about version of symbol snd_timer_interrupt snd_pcm: Unknown symbol snd_timer_interrupt snd_pcm: disagrees about version of symbol snd_info_free_entry snd_pcm: Unknown symbol snd_info_free_entry snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl snd_pcm: Unknown symbol snd_ctl_register_ioctl snd_pcm: disagrees about version of symbol snd_card_file_add snd_pcm: Unknown symbol snd_card_file_add snd_pcm: disagrees about version of symbol snd_unregister_device snd_pcm: Unknown symbol snd_unregister_device snd_pcm: disagrees about version of symbol snd_timer_new snd_pcm: Unknown symbol snd_timer_new snd_pcm: disagrees about version of symbol snd_device_new snd_pcm: Unknown symbol snd_device_new snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl snd_pcm: Unknown symbol snd_ctl_unregister_ioctl snd_pcm: disagrees about version of symbol snd_info_create_card_entry snd_pcm: Unknown symbol snd_info_create_card_entry snd_pcm: disagrees about version of symbol snd_power_wait snd_pcm: Unknown symbol snd_power_wait snd_pcm: disagrees about version of symbol snd_device_free snd_pcm: Unknown symbol snd_device_free snd_pcm: disagrees about version of symbol snd_card_file_remove snd_pcm: Unknown symbol snd_card_file_remove snd_pcm: disagrees about version of symbol snd_info_unregister snd_pcm: Unknown symbol snd_info_unregister snd_pcm: disagrees about version of symbol snd_device_register snd_pcm: Unknown symbol snd_device_register snd_pcm: disagrees about version of symbol snd_register_device snd_pcm: Unknown symbol snd_register_device snd_hdsp: Unknown symbol snd_pcm_new snd_hdsp: Unknown symbol snd_interval_refine snd_hdsp: Unknown symbol snd_pcm_set_sync snd_hdsp: Unknown symbol snd_pcm_hw_rule_add snd_hdsp: Unknown symbol snd_interval_list snd_hdsp: Unknown symbol snd_pcm_lib_ioctl snd_hdsp: Unknown symbol snd_pcm_set_ops snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits snd_hdsp: Unknown symbol snd_pcm_period_elapsed [3 unrelated httpd lines] snd_pcm: disagrees about version of symbol snd_info_register snd_pcm: Unknown symbol snd_info_register snd_pcm: disagrees about version of symbol snd_info_create_module_entry snd_pcm: Unknown symbol snd_info_create_module_entry snd_pcm: disagrees about version of symbol snd_timer_notify snd_pcm: Unknown symbol snd_timer_notify snd_pcm: disagrees about version of symbol snd_timer_interrupt snd_pcm: Unknown symbol snd_timer_interrupt snd_pcm: disagrees about version of symbol snd_info_free_entry snd_pcm: Unknown symbol snd_info_free_entry snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl snd_pcm: Unknown symbol snd_ctl_register_ioctl snd_pcm: disagrees about version of symbol snd_card_file_add snd_pcm: Unknown symbol snd_card_file_add snd_pcm: disagrees about version of symbol snd_unregister_device snd_pcm: Unknown symbol snd_unregister_device snd_pcm: disagrees about version of symbol snd_timer_new snd_pcm: Unknown symbol snd_timer_new snd_pcm: disagrees about version of symbol snd_device_new snd_pcm: Unknown symbol snd_device_new snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl snd_pcm: Unknown symbol snd_ctl_unregister_ioctl snd_pcm: disagrees about version of symbol snd_info_create_card_entry snd_pcm: Unknown symbol snd_info_create_card_entry snd_pcm: disagrees about version of symbol snd_power_wait snd_pcm: Unknown symbol snd_power_wait snd_pcm: disagrees about version of symbol snd_device_free snd_pcm: Unknown symbol snd_device_free snd_pcm: disagrees about version of symbol snd_card_file_remove snd_pcm: Unknown symbol snd_card_file_remove snd_pcm: disagrees about version of symbol snd_info_unregister snd_pcm: Unknown symbol snd_info_unregister snd_pcm: disagrees about version of symbol snd_device_register snd_pcm: Unknown symbol snd_device_register snd_pcm: disagrees about version of symbol snd_register_device snd_pcm: Unknown symbol snd_register_device snd_hdsp: Unknown symbol snd_pcm_new snd_hdsp: Unknown symbol snd_interval_refine snd_hdsp: Unknown symbol snd_pcm_set_sync snd_hdsp: Unknown symbol snd_pcm_hw_rule_add snd_hdsp: Unknown symbol snd_interval_list snd_hdsp: Unknown symbol snd_pcm_lib_ioctl snd_hdsp: Unknown symbol snd_pcm_set_ops snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits snd_hdsp: Unknown symbol snd_pcm_period_elapsed snd_pcm: disagrees about version of symbol snd_info_register snd_pcm: Unknown symbol snd_info_register snd_pcm: disagrees about version of symbol snd_info_create_module_entry snd_pcm: Unknown symbol snd_info_create_module_entry snd_pcm: disagrees about version of symbol snd_timer_notify snd_pcm: Unknown symbol snd_timer_notify snd_pcm: disagrees about version of symbol snd_timer_interrupt snd_pcm: Unknown symbol snd_timer_interrupt snd_pcm: disagrees about version of symbol snd_info_free_entry snd_pcm: Unknown symbol snd_info_free_entry snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl snd_pcm: Unknown symbol snd_ctl_register_ioctl snd_pcm: disagrees about version of symbol snd_card_file_add snd_pcm: Unknown symbol snd_card_file_add snd_pcm: disagrees about version of symbol snd_unregister_device snd_pcm: Unknown symbol snd_unregister_device snd_pcm: disagrees about version of symbol snd_timer_new snd_pcm: Unknown symbol snd_timer_new snd_pcm: disagrees about version of symbol snd_device_new snd_pcm: Unknown symbol snd_device_new snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl snd_pcm: Unknown symbol snd_ctl_unregister_ioctl snd_pcm: disagrees about version of symbol snd_info_create_card_entry snd_pcm: Unknown symbol snd_info_create_card_entry snd_pcm: disagrees about version of symbol snd_power_wait snd_pcm: Unknown symbol snd_power_wait snd_pcm: disagrees about version of symbol snd_device_free snd_pcm: Unknown symbol snd_device_free snd_pcm: disagrees about version of symbol snd_card_file_remove snd_pcm: Unknown symbol snd_card_file_remove snd_pcm: disagrees about version of symbol snd_info_unregister snd_pcm: Unknown symbol snd_info_unregister snd_pcm: disagrees about version of symbol snd_device_register snd_pcm: Unknown symbol snd_device_register snd_pcm: disagrees about version of symbol snd_register_device snd_pcm: Unknown symbol snd_register_device snd_hdsp: Unknown symbol snd_pcm_new snd_hdsp: Unknown symbol snd_interval_refine snd_hdsp: Unknown symbol snd_pcm_set_sync snd_hdsp: Unknown symbol snd_pcm_hw_rule_add snd_hdsp: Unknown symbol snd_interval_list snd_hdsp: Unknown symbol snd_pcm_lib_ioctl snd_hdsp: Unknown symbol snd_pcm_set_ops snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits snd_hdsp: Unknown symbol snd_pcm_period_elapsed snd_pcm: disagrees about version of symbol snd_info_register snd_pcm: Unknown symbol snd_info_register snd_pcm: disagrees about version of symbol snd_info_create_module_entry snd_pcm: Unknown symbol snd_info_create_module_entry snd_pcm: disagrees about version of symbol snd_timer_notify snd_pcm: Unknown symbol snd_timer_notify snd_pcm: disagrees about version of symbol snd_timer_interrupt snd_pcm: Unknown symbol snd_timer_interrupt snd_pcm: disagrees about version of symbol snd_info_free_entry snd_pcm: Unknown symbol snd_info_free_entry snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl snd_pcm: Unknown symbol snd_ctl_register_ioctl snd_pcm: disagrees about version of symbol snd_card_file_add snd_pcm: Unknown symbol snd_card_file_add snd_pcm: disagrees about version of symbol snd_unregister_device snd_pcm: Unknown symbol snd_unregister_device snd_pcm: disagrees about version of symbol snd_timer_new snd_pcm: Unknown symbol snd_timer_new snd_pcm: disagrees about version of symbol snd_device_new snd_pcm: Unknown symbol snd_device_new snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl snd_pcm: Unknown symbol snd_ctl_unregister_ioctl snd_pcm: disagrees about version of symbol snd_info_create_card_entry snd_pcm: Unknown symbol snd_info_create_card_entry snd_pcm: disagrees about version of symbol snd_power_wait snd_pcm: Unknown symbol snd_power_wait snd_pcm: disagrees about version of symbol snd_device_free snd_pcm: Unknown symbol snd_device_free snd_pcm: disagrees about version of symbol snd_card_file_remove snd_pcm: Unknown symbol snd_card_file_remove snd_pcm: disagrees about version of symbol snd_info_unregister snd_pcm: Unknown symbol snd_info_unregister snd_pcm: disagrees about version of symbol snd_device_register snd_pcm: Unknown symbol snd_device_register snd_pcm: disagrees about version of symbol snd_register_device snd_pcm: Unknown symbol snd_register_device snd_hdsp: Unknown symbol snd_pcm_new snd_hdsp: Unknown symbol snd_interval_refine snd_hdsp: Unknown symbol snd_pcm_set_sync snd_hdsp: Unknown symbol snd_pcm_hw_rule_add snd_hdsp: Unknown symbol snd_interval_list snd_hdsp: Unknown symbol snd_pcm_lib_ioctl snd_hdsp: Unknown symbol snd_pcm_set_ops snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits snd_hdsp: Unknown symbol snd_pcm_period_elapsed -- Janina Sajka Phone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) janina(a)freestandards.org http://a11y.org If Linux can't solve your computing problem, you need a different problem.

19 years, 6 months

[linux-audio-dev] Nord Modular instrument converter

by Juhana Sadeharju

Hello. I started working on a Nord Modular to PD converter. ftp://ftp.funet.fi/pub/sci/audio/devel/nordmodular/ NM users have patched thousands of free instruments (http://nordsynth.zevv.nl). It would be nice to be able to use the user-made instruments elsewhere. I choosed PD but we should make the converter general enough so that converters to other modular systems can be written. I can work on them as well. Check for "http://nmedit.sourceforge.net" for a NM instrument file parser. The NM file format is close to PD's own. Anyone could rewrite the parser standalone in C, Python, etc? [[ I see no problem in writing the converter. Buying a Nord Modular does not mean that its users should restrict their intellectual property to Nord Modular. ]] Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software

19 years, 6 months

[linux-audio-dev] Sequencer Concept

by Thorsten Wilms

Hi! I have been thinking about how an advanced sequencer could look and work over and over again and now finaly managed to come up with one consistent concept that i would like to present here now. A mockup to illustrate the following explainations: http://wrstud.uni-wuppertal.de/~ka0394/forum/sequencer_05.png The basic idea is to have nested containers to be arranged verticaly and horizontaly. All information is tied to or contained in these containers. As the horizontal axis stands for time, i needed to express the nesting only verticaly (plus color), so that's what the round corners and the empty bottoms of the containers are for. Maybe it helps when you think on Lisp and paranthesis, only vertcaly. On the mockup the big white container defines absolute time (min/sec) and the context for playback control (only one play position inside thsi container (for each user)). Several of them could exist in parallel, all with their own playback control. The next, yellow container defines the meter (the ruler) 4/4, followed by a tempo track set to 120 BPM. The blue container is an audio container. These can take others of their kind, audio inputs and outputs and finaly audio clips. This one defines an "Out 1" and its send level and conatins 3 clips. Below it, the green container sets a 3/4 meter. Because it is inside the 4/4 container, the quarter notes match. If outside, it would have to have its own and independent tempo track. The last Container is for MIDI. It has IN and OUT as attributes. Alternatively these could be expressed on tracks like used for tempo, what would make them changeable inside the container. Every Container can be used as a pattern (instances). They could have a dropdown menu to swutch between different versions (/takes). I have some more ideas and details, but i think this should be enough for now! :) I have only basic and seldomly applied coding skills, and this doesn't look like a one man project anyway ... So I hope for interested developers ... or that at least this gives someone some inspiration. I would be happy to further develop my concepts of course (allthough my diploma in industrial design, same topic: sequencer takes priortiy for the next 3 months). --- Thorsten Wilms

19 years, 6 months

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 April 2005