Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7501 discussions

by Harry Van Haaren

Hey all, A while ago I asked about LADSPA plugins, they're implemented & working smoothly now, thanks all that replied & Robin for the code! The next plugin I want to tackle is LV2, I've read lv2plug.in, and I understand how it works. I just don't have a clue where to start with implementing. Does anybody out there have some code lying about that just "bare-bones" loads the plugin? I've read the ZynJackU sources... but to no avail, they're too big for easy learning. Thanks for reading, -Harry

14 years, 6 months

Re: [LAD] LV2: Howto

by Sakari Bergen

On 13.12.2010 11:25, Harry Van Haaren wrote: > Hey all, > > A while ago I asked about LADSPA plugins, they're implemented & > working smoothly now, > thanks all that replied & Robin for the code! > > The next plugin I want to tackle is LV2, I've read lv2plug.in > <http://lv2plug.in>, and I understand how it works. > > I just don't have a clue where to start with implementing. Does > anybody out there have > some code lying about that just "bare-bones" loads the plugin? > > I've read the ZynJackU sources... but to no avail, they're too big for > easy learning. > > Thanks for reading, -Harry If you grok C++, here is some wrapper code and a tutorial: http://www.nongnu.org/ll-plugins/lv2pftci/ -Sakari-

14 years, 6 months

Update of zita-at1 (bugfix)

by fons＠kokkinizita.net

Zita-at1 has been updated to 0.2.1 fixing a nasty bug. Thanks to Oleg Ivanenko for reporting the problem and helping to solve it. As usual: <http://www.kokkinizita.net/linuxaudio/downloads> Ciao, -- FA There are three of them, and Alleline.

14 years, 6 months

Interesting new functionality in Neil tracker

by Vytautas Jancauskas

Recently an option to allow easy resampling (in the tracker sense, not DSP sense) and a new pattern effect that allows you to generate and modify patterns using Python code has been added to Neil modular tracker. Enjoy, if you are in to that kind of thing. -- http://sites.google.com/site/neilsequencer/

14 years, 6 months

Re: [LAD] [LAU] New release of zita-at1

by fons＠kokkinizita.net

On Sat, Dec 11, 2010 at 08:06:26PM +0300, Oleg Ivanenko wrote: > So, zita-at1 WAS installed from "source-dir" > /mnt/music/src/audio/fons/zita-at1-0.2.0/source Indeed... Since the build doesn't produce any information, the only way seems to run zita-at1 from gdb and get a stack trace. Is there anything unusual about your system/X11/Jack ? Ciao, -- FA There are three of them, and Alleline.

14 years, 6 months

Re: [LAD] [LAU] New release of zita-at1

by fons＠kokkinizita.net

On Sat, Dec 11, 2010 at 07:07:36PM +0300, Oleg Ivanenko wrote: > What am I doing wrong? > -- > Truly yours, Oleg Ivanenko aka Ash > [if it wasn't so sad, it would be funny] You must do a 'make install'. It will not run from the build directory. Ciao, -- FA There are three of them, and Alleline.

14 years, 6 months

Re: [LAD] Project proposition: llvm based dsp engine

by Stéphane Letz

> > > Message: 8 > Date: Fri, 10 Dec 2010 22:01:50 +0000 > From: Victor Lazzarini <Victor.Lazzarini(a)nuim.ie> > Subject: Re: [LAD] Project proposition: llvm based dsp engine > To: "linux-audio-dev(a)lists.linuxaudio.org >> The Linux Audio > Developers' Mailing List" <linux-audio-dev(a)lists.linuxaudio.org> > Message-ID: <EEFBDE7E-30EB-4C1D-87FF-39621F1EC4A8(a)nuim.ie> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; > DelSp="yes" > > This is all very interesting. One question I had regarding the future > development of FAUST is whether it will include some sort of scheduler > so that various faust-coded objects can be instantiated at different > times, connected together in series, etc.. Then an interpreter could > be developed with JIT compilation etc. > > Or is this more like the idea of combining FAUST with another language > like pure? > > Victor > On 10 Dec 2010, at 12:28, St?phane Letz wrote: I would say yes. Faust should stay as the DSP computation stage only. Stéphane

14 years, 6 months

Re: [LAD] Project proposition: llvm based dsp engine

by Stéphane Letz

Le 9 déc. 2010 à 22:17, Maurizio De Cecco a écrit : > On Thursday12/9/10 2:24 PM, Stéphane Letz wrote: > >> By since you have a lot of jMax object coded in C, I guess testing the idea with the current jMax environment should be easy: just compile your jMax objects in LLVM bitcode ad try to "combine" (Link Time Optimization) them with LLVM API. > > > Exactly (well, more or less). > One interesting point is the control part; it is theoretically possible to get a control patch made of simple objects (things like ints, operators, trigger, if) up to native C speed. > > This would require writing objects in a slightly different way. > > Anyway, for the moment all this is out of reach, not enough time. > But you never know :-> > > Maurizio Well what could be interesting to share would be something similar to the "FIR" (Faust Intermediate Language) that we are currently designing and implementing. Basically Faust currently does : Faust dsp program ==> [BDA (Block Diagram Algebra) evaluation ] ==> Signals ==> FIR loops DAG (Direct Acyclic Graph) ==> C/C++, JAVA, LLVM, (possibly CUDA, OpenCL at some point) backends. FIR is a imperative like language where a Faust program is represented as a data structure + list of functions (init, buildInterface, compute...). The "compute" function does the actual DSP computation and is currently executing the DSP loops DAG in different modes: 1) vector mode : the loops DAG is simply topologically sorted and compiled in the target language (C/C++, LLVM...). The we hope GCC or ICC auto-vectorization features can do the job to produce SIMD code. 2) OpenMP mode: OpenMP pragmas are inserted at the right place in the DAG to express parallelism (and each loop can possibly be auto-vectorized). 3) Work Stealing Scheduler : the loops DAG is compiled with an "embedded" WSS algorithm (and each loop can possibly be auto-vectorized). 2) and 3) steps are typically expressed as "FIR to FIR" transformations. It could be possible to let other tools enter the chain before the "FIR loops DAG" step so that to take benefit of all the later steps : FIR to FIR parallelisation, and all available backends. We can even imagine to implement some kind of "inter plug-in" optimizations at the FIR level. But of course the simplest way to produce this "FIR loops DAG" is... using Faust itself, and "inter plug-in" optimizations are way simpler to handle at the Faust level (basically at the "signal step") . So I don't know if the idea makes sense, but you never know :-> Stéphane

14 years, 6 months

lv2_jack_host

by alex stone

I'm experimenting with lv2_jack_host with Gabriel's excellent composite loaded, and have a general question. Is lv2_jack_host, from a terminal, jack-sessionable? Or, if this isn't viable, if any loaded plugins are jack-session capable, can lv2_jack_host save a "state", enabling any jack-session capable plugins to have their state re-instated, when a jack session is started/restarted? Alex. -- www.openoctave.org midi-subscribe(a)openoctave.org development-subscribe(a)openoctave.org

14 years, 6 months

New release of zita-at1

by fons＠kokkinizita.net

An update of zita-at1 is available at the usual place: <http://www.kokkinizita.net/linuxaudio/downloads>. Changes: * The resampler now uses cubic interpolation (at twice the sample rate for 44.1 and 48 kHz), giving even cleaner output. * The offset control now has 400 steps of exactly 1 cent (1/100 semitone) each, and displays the set value when touched. Default mousewheel step is 10 cents, 1 cent with Shift pressed. Enjoy ! -- FA There are three of them, and Alleline.

14 years, 6 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