Hi,
While porting the new AMS modules into LV2, I noticed the High and Low
Offsets controls are not used in the code.
I wanted to open a ticket on Sourceforge about it but I don't seem to have
the rights to do so.
Could this be checked?
If you want me to create a patch to remove references to these 2 controls,
please let me know.
Aurélien
Hello all,
The first release of pyjacktools is now available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>
Python C++ extensions and classes for audio. I wanted to demo
these during the Audio Measurements workshop at LAC 2014, but
we ran out of time...
AudioFile
Read/write audio files to/from numpy arrays. Reads anything
libsndfile can read, and writes wav, wavex, amb, aiff, caf
and flac, any number of channels.
JackControl
Simple Jack client allowing to connect arbitrary ports and
control Jack transport.
JackPlayer
Multichannel (up to 64) audio file player. The interface is
deliberately kept low level, but it's easy to create derived
classes providing a higher level interface. This is the player
used in the automated systems at La Casa del Suono in Parma.
JackSignals
Generate and capture arbitrary test signals from/to numpy
arrays. Combined with numpy, matplotlib, pyqt, etc. this
can be used to create anything from a simple measurement
to sophisticated automated test systems.
All four classes are documented using Python docstrings (use
Python's help function to read these). Some simple examples
are provided as well.
The C++ extenstions should work with either Python 3.x or
2.7. The Python code is tested using Python 3.4, but will
probably work even with 2.7. If not the required changes
should be minimal.
To install you need the Python setuptools, then just make
and sudo make install. The examples require numpy and for
some also matplotlib.
Enjoy !
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
Hi,
I recently moved with my Band (www.jimson-drift.de) into a new
rehearsalroom. I'm thinking of building a drum booth especially for
recording. Can someone point me to the right literature? I'm interested the
Physics of room acoustics and would like to first understand the problem
theoretically (that means the math). I want to understand the
distribution of the acoustic modes of a given room in order to
optimize/minimize their amplitude, as well as the
reverberation/reflection aspects of different materials. Just want
deeper insights to plan the booth.
Thanks,
Gerald
While porting AlsaModularSynth modules to LV2 plugins, I was wondering
something... AMS has some similar modules where the only thing changing is
the number of inputs (Mixer with 2, 4 or 8 inputs), the number of outputs
(CV source with 2, 4 or 8 outputs) or the number of VCOs/Envs/etc.
(DynamicWaves with 4, 8 or 16 VCOs).
In AMS there is only one class for such plugins and AMS would pass the
number of inputs/outputs/sections/etc. when creating the different modules.
I couldn't find an easy way to reproduce this in LV2 plugins, therefor so
far I have been creating different LV2 plugins for each and everyone of
them and doing a lot of copy/past/editing.
That let me to wonder if there wouldn't be a better way.
The pros:
- it's easier to maintain if I have only one class
- it's a lot less boring than doing a lot of copy/past/editing - I have
been doing it only for simple ones so far like Mixers or CV source, but now
I'm starting to port DynamicWaves which is way more complex
The Cons:
- I have the feeling that gaining on code simplicity actually decrease the
performance when the plugin is running - i can imagine it to be less
strainuous on the CPU to have simple code instead of dealing with loops and
arrays
Being a rare case I can't imagine the need to have this supported directly
in LV2, but I was wondering if people with more talent than me in creating
audio software might have some advice?
Aurélien
Bug-fix release 0.32.1 is out, update is recommended!!
This release fix a long outstanding issue with LADSPA/LV2 plugin
load/unload and UI modification.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
Download Site:
http://sourceforge.net/projects/guitarix/
regards
hermann
While porting AlsaModularSynth modules to LV2 plugins, I was wondering
something... AMS has some similar modules where the only thing changing is
the number of inputs (Mixer with 2, 4 or 8 inputs), the number of outputs
(CV source with 2, 4 or 8 outputs) or the number of VCOs/Envs/etc.
(DynamicWaves with 4, 8 or 16 VCOs).
In AMS there is only one class for such plugins and AMS would pass the
number of inputs/outputs/sections/etc. when creating the different modules.
I couldn't find an easy way to reproduce this in LV2 plugins, therefor so
far I have been creating different LV2 plugins for each and everyone of
them and doing a lot of copy/past/editing.
That let me to wonder if there wouldn't be a better way.
The pros:
- it's easier to maintain if I have only one class
- it's a lot less boring than doing a lot of copy/past/editing - I have
been doing it only for simple ones so far like Mixers or CV source, but now
I'm starting to port DynamicWaves which is way more complex
The Cons:
- I have the feeling that gaining on code simplicity actually decrease the
performance when the plugin is running - i can imagine it to be less
strainuous on the CPU to have simple code instead of dealing with loops and
arrays
Being a rare case I can't imagine the need to have this supported directly
in LV2, but I was wondering if people with more talent than me in creating
audio software might have some advice?
Aurélien
