Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

2 participants
7501 discussions

[linux-audio-dev] [ANN] DSSI 0.9 released

by Chris Cannam

DSSI v0.9 released ================== I'm happy to announce version 0.9 of the DSSI plugin API. http://dssi.sourceforge.net/ DSSI is an audio plugin API designed for software instruments with custom user interfaces. DSSI is based on the LADSPA effects plugin API, the ALSA sequencer event types, and OSC (Open Sound Control) communications. It's intended to be easily understood, GUI-toolkit-agnostic, and slightly biased towards familiarity with MIDI. The DSSI distribution package contains a JACK/ALSA-sequencer reference host and some plugins as well as the specification and header. DSSI 0.9 was constructed by Steve Harris, Chris Cannam, and Sean Bolton. New in 0.9 ---------- The main improvements in 0.9 are to the reference host implementation and sample plugins. The 0.9 API itself is binary compatible with the previous 0.4 release. A new convention for plugin-global (rather than instance-local) configuration data and a convention for setting a plugin's project working directory have been introduced, and 0.9 clarifies certain implementation points in the documentation. Available hosts and plugins --------------------------- Two hosts are currently known to include complete or nearly-complete DSSI support: the reference jack-dssi-host included in the DSSI 0.9 distribution, and versions 0.9.9 and later of the Rosegarden-4 sequencer. Currently available plugins include: * a FluidSynth soundfont plugin included in the DSSI distribution * Xsynth-DSSI, an analog-style (VCAs-VCF-VCO) plugin * dssi-vst, a wrapper plugin enabling the use of many Windows VST instruments and effects * hexter, a Yamaha DX7 modeling plugin * three smaller example plugins (two synths and a sampler) that are also part of the DSSI distribution.

20 years, 7 months

[linux-audio-dev] QSynth/fluidsynth having problems with looped soundfonts

by ico＠fuse.net

Hi all, Just a quick question before my tomorrow's presentation. I am hoping to be able to present fluidsynth/Qsynth but one of the issues I encountered using two different versions of fluidsynth and a number of soundfonts is that the sound of soundfonts is fine until they begin to loop (i.e. long flute sound eventually starts to loop the sample) and then at every loop cycle there is a kind of a clicking noise as if the loop points are either badly designed (unlikely, since I tried 5 different soundfonts that were downloaded from different places), there is something weird with the tested versions of fluidsynth, or this is a bug? Any help is greatly appreciated! Best wishes, Ico

20 years, 7 months

[linux-audio-dev] calling open source artists/musicians (UK London area)

by Dave Griffiths

Hi all, A couple of us are thinking of putting together an open source focussed music and visual performance night in London (UK), with the aim of making it a semi regular event with a bit of a workshop feel to it - so people can share ideas and have some fun. We're just wondering what the interest for such an event would be, whether people would be interested in participating, or indeed if there is already something going on we've missed. Also if people are already doing similar nights in other places, if you have any tips. You can contact us directly at: leechun(a)leechun.freeserve.co.uk dave(a)pawfal.org or reply to the list... cheers, dave

20 years, 7 months

[linux-audio-dev] [ANN] busted2 tonight in berlin, auguststrasse

by martin rumori

hi *, last minute announcement: busted2, sound installation with 7 us-police livestreams using LD_PRELOAD, realplay, jack, hdsp, and, last but not least, linux gallery "mount warning" auguststrasse 10 berlin-mitte 8 p.m. CET us election party till tomorrow... running right now. come along! bests, martin

20 years, 7 months

[linux-audio-dev] Full version of the ICMC2004 paper now available for download

by Ivica Ico Bukvic

Hi all, It is my pleasure to announce immediate availability of the expanded version of the ICMC 2004's paper "Linux as a Mature Digital Audio Workstation in Academic Electroacoustic Studios – Is Linux Ready for Prime Time?" It can be obtained directly from the following link: http://meowing.ccm.uc.edu/~ico/Papers/ICMC2004-full.pdf I would also like to use this opportunity to thank all who helped make this paper better as well as all of you who have made very insightful comments and/or suggestions regarding the upcoming presentation on music standards. I've written down your thoughts and will incorporate them in my speech as soon as my other presentations are over with. For those interested, the paper on Linux will be presented tomorrow at noon. Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004

20 years, 7 months

[linux-audio-dev] Ardour 0.9beta20 released

by Paul Davis

This is intended to be the last beta release before Ardour 0.9 is released. No new features will be added before we release 0.9. FYI, 0.9 is intended to differ from 1.0 only with respect to bug fixes, install and first-time user experience. We do still have a few significant crashing and other major bug fixes to be resolved before 0.9 can be released, but optimism is in the air. http://ardour.org/releases/ardour-0.9beta20.tar.bz2 NEW FEATURES ------------- * Added support for midi parameter feedback. When enabled, controls that are bound to incoming midi events will send out that event when modified. This lets you control generic midi control surface with motor faders and/or led encoders (like the incredibly affordable Behringer BCF2000, which was used for testing), to match the internal state. Note the extra/changed options in the option editor's midi tab. Reminder: to bind a fader or bar-control to midi, do a Control-Middle-Click on it, then send some midi control. * automation playback will send MIDI parameter feedback, thus making external motorized faders etc. move with automation. Note: this feature will probably be reimplemented in the future because of interlocking problems with the realtime audio thread. * Added generic midi bindability for mute, solo, and rec-enable controls. to do it, you can do Control-RIGHT-click on the mute and solo buttons (the normal binding click is taken on these buttons for other functions). For the Record-enable button, it is the normal ctrl-middle-click. You can also pick it from the context menu of the mute button. A menu will be added to other buttons later. * add -V/--novst flag to avoid using VST even if it was compiled in * multiple selected regions can be dragged across tracks (nick mainsbridge) * normalization can be undone (patch from jkyro) * export dialog redesigned - master outs appear in their own selector, preselected - button to control visibility of specific other tracks * new playlist selector (uses a tree structure in a scrolled window, instead of menus) * add "nudge by capture offset" operation for regions * remove zoom changes from the undo/redo history * sessions still load when audio files are missing or corrupt * Ardour is believed to build on OS X (CVS and/or this release) FIXES ----- * templates now get installed/uninstalled/rolled-into-tarball/etc. Let me know if some corner of "make" doesn't work with the templates. * Removed libglib dependency from libardour. Instead of guint32, we use stdint.h's uint32_t, etc. * fixed some midi prompter dialog issues * fixed some midi binding state saving issues * change entire buffer management scheme to be (more) RT-safe * a major CVS commit that includes the first pass of changes to fix some serious errors in the way ardour handles threads when exiting. it also includes a significant fix to make export work when sync'ed with JACK * new functions to do "internal seeks" within the existing playback buffer of a DiskStream, avoiding a new disk read for small adjustments of playhead position * lots of work on MTC slaving * changed prototype of pthread_exit_pbd() * don't send a message via error/info/warning/fatal if thread is not registered with GUI * remove "eox" signal from MIDI parser * cleanup a few details of MIDI parsing - importantly, all sysex messages get eox on the end when passed to specific functions * add "timecode-source-is-synced" option to ardour.rc(.in) * remove Session::request_roll() * fix bug with MMC rec-enable handling (only odd-numbered tracks could be enabled) * make region export progress bar move in the right direction * more MTC slaving fixes and improvements (not done yet) * remove wrong-thread-calling of Session::clear_event_type(), which should help a number of loop-related crashes * remove erroneous use of "abort" in function call * Automake-1.7 or higher is required for libmidi++ now * add "nudge by capture offset" operation for regions * enlarge playhead/edit cursor arrows a bit * avoid duplicate keyboard target registration * pay attention to "virtual" window enter/leave events, but continue to ignore "inferior" ones (may help with keyboard focus issues) * cancelling tempo/meter create dialog doesn't insert a default tempo/meter marker * tempo/meter create dialogs have minimal WM decor, and use standard ArdourDialog API * 2d panner fixed in many ways (still not to my taste and not really correct) * context-click on 2d panner shows context menu (Bypass is the only entry so far) * bypass added to stereo panner context menu * general panner state load/restore fixes * master outs added to connections menu * added optimizations for peak metering (use of fabsf, flag constants as floats, avoid implicit double/float casting) * Updated the Italian and Brazilian translations. * handle disk over- and under-run errors in the GUI, and be more comprehensible to regular users. * fix panning bypass for 2d panner * fix stereo panner "mute" menu item so that it doesn't toggle panner mute state every time it pops up * fix more subtle elements of panner state restoration * remove window crossing debug messages * add "OK" button and remove window decoration from "can't connect to JACK" dialog

20 years, 7 months

[linux-audio-dev] [ANN] realtime-lsm-0.8.3 beta test

by Rohan Drape

Nice work, thanks. In passing, using KERNEL_DIR := /lib/modules/$(shell uname -r)/build should behave properly for normal builds?

20 years, 7 months

[linux-audio-dev] 0.9beta21 released

by Paul Davis

Due to some untracked issues, 0.9beta20 was released in a form that prevents it from offering any MIDI I/O or MIDI configuration. In the time it took to discover that, other work had already happened that is fairly important, so we bring you an unintended extra release. http://ardour.org/releases/ardour-0.9beta21.tar.bz2 Changes ------- * MIDI support now configured and built * use Steve Harris' new libgdither code for dithering * new patch from Nick Mainsbridge for multi-region cross-track dragging * increase size of Session event pool (to aid with loading large sessions) * use "in 1" or "out 1" if a named connection cannot be found (e.g. when switching from a multichannel to a stereo audio interface) * patch for RPM building from Thac * libardour: 0.838.0 ardour/gtk: 0.536.1

20 years, 7 months

Re: [linux-audio-user] Re: [linux-audio-dev] How to automate hdsploader

by ico＠fuse.net

Thanks a lot for the help Paul! One more quick question though, has the issue with jackd + alsa + hdsp ever been fixed where jackd only allows 2 periods and no other number? Best wishes, Ico >Hence, I've been wondering what do I need to do to automate hdsploader as soon > as the cardbus has been connected? using the new modprobe.conf syntax .... install snd-hdsp /sbin/modprobe --first-time --ignore-install snd-hdsp && { /usr/bin/hdsploader; }

20 years, 7 months

[linux-audio-dev] Linux and Standards

by Ivica Ico Bukvic

Hi all, As some of you may already know, I am going to present a paper/demo at the upcoming ICMC 2004 conference in Miami on Linux titled: Linux as a Mature Digital Audio Workstation in Academic Electroacoustic Studios – Is Linux Ready for Prime Time? As promised I will be posting an expanded version of the paper online right after the presentation that is slated for the Wednesday next week. I would like to use this opportunity to thank all the members of this wonderful community for their insight and help in making my final paper as accurate and objective as possible. Furthermore, I would like to thank everyone involved in the development of audio software for the GNU/Linux platform because without you none of this would've been possible. Finally, just a couple days ago I was invited to serve as one of the panel members on Matthew Wright's discussion titled "Standards From the Computer Music Community" that will take place on Saturday November, 6. He wants me to present the Linux audio community's angle on standards and considering that this conference encompasses faculty as well as researchers and programmers from all across the World, I feel that this is a perfect opportunity to voice out our angle on the given topic and perhaps that way further expose the strengths that Linux can offer. I would like to share with you a short overview of my thoughts on this issue and would like to encourage those of you who may have additional thoughts to please send me your suggestions and/or corrections. Your help in this matter is most appreciated! However, please bear in mind due to fact that I am leaving for the conference on Sunday afternoon and am not sure how regularly (if at all) will I be able to check my e-mail while away from home, I would really appreciate it if you would please send me your responses before Sunday 2pm or so. I would of course appreciate also belated comments just in the case I do get to check my e-mail, I just cannot guarantee I'll get to read them prior to the presentation. My sincere apologies for the unusually short window of opportunity. At any rate, here's my blurb: ---------------------------------------- My initial presentation will be limited to 5-7 minutes since panel will consist of a number of members. Following everyone's initial presentation, there will be a discussion driven in part by the questions from the audience. LINUX AS A STANDARD I feel that considering linux as a standard is on one hand a kind of a paradox as it is built on the premise that individual truly can tweak it to heart's content and therefore it is relatively unlikely that any two Linux boxes would look and/or perform the same. Yet, on the flip-side of the coin Linux stands as a most successful offspring of the GNU movement and as such it is the most revolutionary and therefore the standard-setting OS in a category where it has no competition. Furthermore, this diversity it offers perhaps stands in its own light as a kind of a standard offering the end-user to shape their computer as a personalized instrument. PLANET CCRMA/DeMuDi/THAC'S RPMS/AUDIOSLACK The diversity seemingly suggests lack of standards, yet the software packages in most cases seamlessly compile on various distributions. This diversity is simply a byproduct of the diversity of the commercial Linux distributions. This is where lies perhaps the biggest problem with Linux, and that is the issue of different file tree across the different distributions which introduces hurdles for the "compile-from-the-source" crowd and in part feeds the demand for the prebuilt distros and subsequent fragmentation (a vicious circle if you like). KERNELS There is no "standard" audio kernel even though some of the kernel releases in conjunction with patches yield better performance. This diversity is however irrelevant as most of the applications work just fine on different sub-versions of the same kernel without a recompile. Therefore such disparity is more of a nuisance for the end-user than a potential standard-breaking anomaly. Furthermore the fix for such disparity is provided via aforementioned distributions. APPLICATIONS The powerful thing about Linux is that while everyone is welcome to contribute their own ideas or even design their own applications from ground-up, the strongest concepts rather than most developed applications are the ones who set the standard (i.e. JACK, ALSA, etc.) which is not always the case with the commercial proprietary World where often PR plays a critical role (i.e. VHS vs. BETAMAX -- although this is not the best example as this is not software-related but you get my point). Eventually, the strongest concepts do become also the most developed ones, but due to the fact that the source is readily available and that other developers choose to implement and therefore support those interfaces which look most promising, should there ever a new standard arise it will always have the chance to rise and overcome the leading standard, no matter how well the leading standard is established, and will likely do so in a least painful fashion for the end-user (i.e. ALSA vs. OSS as opposed to OS9 vs. OSX transition). Finally, open-source nature of the software minimizes the potential for misrepresentation of the format's features (a.k.a. false advertising in the commercial world). This is where Linux truly shines. That being said, Linux has its own share of disparate formats which impede the development of a standard (i.e. every sequencing software has a different format for saving the sessions). However, it is my feeling that this is simply a transitional phase and in due time the strongest will prevail. As far as the standard or core applications of the Linux community are concerned, I really do not wish to go there as that may spawn heated discussion which may completely detract from my goals. Besides, it is exactly this individualized preference that drives the diversity in Linux's software offering. AUDIO-RELATED STANDARDS THAT CAME FROM LINUX COMMUNITY (in no particular order -- it's 3am, give me a break ;-) Jack, LADSPA, LASH, ALSA, Ogg/Vorbis, others? (Lash is especially interesting as it is designed to unite seemingly different standards under one umbrella session controlling mechanism which is something unique for the Linux platform -- other proprietary formats are imho harder to unite under such a meta-standard, if you like, because they are often conceived to work just by themselves and do not necessarily encourage efforts from various competitive companies to conform to them; they rather come up with their own standard unless the existing standard is too strong to compete with which in either case results in a less adequate solution for the end-user) What is both interesting and in part detrimental (at least in short-term) to the Linux audio community is that many formats due to their openness are not readily supported by the proprietary world as they have no profit-making value (i.e. Apple's DRM-ed AAC is safeguarded by Apple so that they can profit from licensing it to other companies and/or locking in their iTunes/iPod market). One final remark on Linux standards as a whole is that Linux holds an upper hand when it comes to longevity of their standards as they are not encumbered by the IP limitations imposed by a particular company and therefore directly dependant on the company's longevity. ---------------------------------------- Sorry for the messy spill of thoughts, hopefully you'll get the main points of my ideas. I am just too tired at this point to try to clean-up my prose. I would really appreciate your thoughts as well as any potential additions you may have. Many thanks! Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004

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