>> Hello all,
>>
>> Today I just released the version 1.0.2 of the ams-lv2 plugins.
>
> Please don't kill me, but I would personally much prefer a linux-native
> VSTi version...
*sight* why?
There are only 3 hosts that I know of that can (or will be able to)
combine plugins in a modular way: ams, Ingen and Carla.
Ingen and Carla both support LV2, and can be loaded as instrument (at
least for Ingen, not sure about Carla), what would linux-native VSTi
bring?
Aurélien
On 8 Feb 2014 18:16, "mark hadman" <markhadman(a)googlemail.com> wrote:
>
> Interesting. I can't try it with Ingen though, because its dependency
> ganv has been unbuildable for years (Arch Linux). Does it work with
> another lv2 host?
>
I'd say no. Only Ingen provides support for CV port and the possibility to
connect plugins the modular way.
Has this issue with Ganv and Arch Linux be reported to David?
> On 8 February 2014 17:13, Aurélien Leblond <blablack(a)gmail.com> wrote:
> > Hello all,
> >
> > Today I just released the version 1.0.2 of the ams-lv2 plugins.
> > ams-lv2 is a port of alsa-modular-synth in the lv2 format to create
> > modular synth primarily with Ingen.
> > Source code and more information available on the website:
> > http://objectivewave.wordpress.com/ams-lv2/
> >
> > To celebrate this release, I created two videos:
> >
> > The first is a demo of 3 synths created with ams-lv2 and Ingen (a
> > bass, a lead and a pad) soloed and inside a mix:
> > http://www.youtube.com/watch?v=LWfF71NerkQ
> >
> > I created as well this first tutorial on the basics of ams-lv2:
> > http://www.youtube.com/watch?v=IuQZajaSw6M
> >
> >
> > I would as well like to take advantage to thank a lot of people who
> > helped with this project:
> > - David for his patience to answer my 1000+ questions and for all his
> > work on lv2 and Ingen
> > - Robin for creating the sisco.lv2 plugins, they are featured in the
> > demo and they are a great help when creating modular synths
> > - Harry for the dials used in the GUI of ams-lv2
> > - and finally Fons for creating the great alsa-modular-synth in the
first place
> > - the whole Linux Audio community in general
> >
> > I really hope you enjoy these plugins and find them useful somehow!
> >
> > Aurélien
> > _______________________________________________
> > Linux-audio-user mailing list
> > Linux-audio-user(a)lists.linuxaudio.org
> > http://lists.linuxaudio.org/listinfo/linux-audio-user
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, I have a percussion piece written in hydrogen and recorded from
there into ardour 3, one track per instrument. At a certain point I'd
like to have an accelerando, i.e. a progressive tempo increase. What are
my options?
Best would be able to do it from within ardour, having many tempo
changes, ardour set as jack master, so that when I play that part it
gradually increases the jack playback tempo. The second solution would
be to export the mix from ardour and use another program to increase the
tempo in the .wav file.
The problem is I'm not sure how exactly go about for neither
solution... for the first one, could I use a knob on my midi
controller to generate a smooth succession of tempo changes? How? For
the second, which program could I use? I seem to recall there was some
utility to generate rubberband map files, but I can't find it ATM.
cheers,
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJS/llYAAoJEBz6xFdttjrf2XsH/2hP0asPC0gbje4AT6aNTf5f
vByKypVexk4VD9OdHzCO3ypIaEU7zZPa2jKNcBkvKIsGF6BTUNkwwhpl0LNEAOJe
tch/9j1boZV/+aM1lZ2/wEkKfAmC9WXG+8bW1hIcaENdTd40sbdPdQvrP3stSL4s
sr5OuLSY+c9Gr/mZeXBkphqINFjBlrtEPFROh/709MBnctC5Y7iJto7XkogYz7C8
A5fHETF5xpvJ69L3HkOXNqGzzgDTAN8cC7rlXptqZ3LjyUd+6gNFAmruGICmeWss
Khiy4htOXlNsVXWW7u/7VPhPxgDrfvDh8dJadFfU/XhtIxU+089uzEzVUeCJjsI=
=tL4C
-----END PGP SIGNATURE-----
CAPS 0.9.19
===========
http://quitte.de/dsp/caps.html
The latest release of this collection of LADSPA plugins extends the
dynamics modulation capabilities of the 'virtual guitar amplifier'
AmpVTS and fixes a nasty bug in the Noisegate circuit that had been
causing spurious gain fluctuations in closed gate state.
http://quitte.de/dsp/caps.html#Download
Upgrading is recommended.
Enjoy,
Tim
So my previous email about the Focusrite can be discarded...I linked
all the clicking and pops to the wifi. With it turned off, I have no
issue. This is fine and great for my music production, but what do I
do if I want to browse the net and listen to my music collection?
Currently, it'll crackle like crazy.
Thanks!
Cliff
Clifford Dunn
Flutist/Composer
http://www.myspace.com/clifforddunnhttp://www.youtube.com/user/beatleboy07https://www.soundcloud.com/clifford-dunn
'Script' might be a big word, but a command-line way to remove all the
files that are not used in Ardour(3). Is it safe to assume that all
files found in ../dead/ can be removed without deleting files that are
in use ?
Date: Sat, 25 Jan 2014 15:11:23 +0100
> From: Mario Lang <mlang(a)delysid.org>
> To: linux-audio-user(a)lists.linuxaudio.org
> Subject: [LAU] A text-only environment for composing electronic music?
> Message-ID: <87zjmki22c.fsf(a)fx.delysid.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi.
>
> I am looking for a programmable (text mode) sequencer solution.
> I know that Linux has a few small languages for creating
> MIDI files, like MMA. Even LilyPond can be tricked into being a MIDI
> file generating language. However, none of the solutions I have seen so
> far could be easily integrated as the center/hub of a full composition.
>
> <snip>
> --
> CYa,
> ?????
>
> I didn't see these text based music programs in this thread.
For a MIDI based composition environment athenacl is a very dense python
based command line composition program. It does have a steep learning
curve but the thick documentation is good. I don't think it is exactly
what you are looking for but if you are interested in creating your own
composition environment, this might be worthwhile. It seems to be intended
for music students who can extend it with python.
http://www.flexatone.org/athena.html
If you are more interested in live coding ixi is a fun and easy to
comprehend command line program, built on top of SuperCollider. It
probably wouldn't be the center of a full composition, but its command line
syntax is sweet.
http://ixi-audio.net/ixilang/index.html
Renick Bell blew me away at LAC2013 using his Conductive library for
Haskell. It appears that you could compose a whole piece as a program or
revise the program on the fly.
http://www.renickbell.net/doku.php?id=conductive
-- Jeff Sandys
I've just been using this to do some tests on an Amp and it's produced some
interesting and useful results. However, I would really like a log frequency
scale.
Is this a practical future option?
I'm using V 0.8.4 which comes with debian testing.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hi.
I am looking for a programmable (text mode) seuqnecer solution.
I know that Linux has a few small languages for creating
MIDI files, like MMA. Even LilyPond can be tricked into being a MIDI
file generating language. However, none of the solutions I have seen so
far could be easily integrated as the center/hub of a full composition.
I am imagining a workflow where I do not need to click my way through a
sequencer, setting up all the content and connections, but rather define
a composition in terms of source code. For this to be useful, it should
include conventional sample playback, as well as real time MIDI event
generation. I am not sure if we have a sufficiently remote-controllable
sampler without GUI requirements, but if we do, I might be able to get
away by using that via OSC or MIDI, instead of re-inventing the sampler wheel.
However, it feels like it would be good to have the sample definitions
part of the composition source code file. After all, I finally want all
the meta-data required to play my composition together in more or less
one play (modulo include files).
This composition compiler should ideally support JACK, with stuff like
transport control. It should be able to support optional hardware
synths, which will be controlled via MIDI messages and mixed back into
the full result via an input JACK port.
I am aware of the KISS principle and actually love it very much. So if
anyone has suggestions on how to implement such a workflow/tool with
existing tools and plumbing code, I am very open to ideas and
suggestions. However, I get a feeling that what I want is only
convenient if relatively tightly integrated, so that I do not have to
tinker with too many individual tools while trying to be productive.
Any hint on how to get such an environement going is very appreciated.
This is actually a long-long-term project of mine: Since I have started
to play with computers, I have always been frustrated by the lack of
accessibility of tools to create electronic music. I have occasionally
managed to get limited solutions working for me, and have always had
very much fun creating content when it sort of worked for me. In the
good old DOS days, there were (due to the limits in what a PC could do)
still some people trying to implement pure text-mode solutions, which
sometimes worked really good with a braille display.
I remember creating several tracks with ModEdit on MS-DOS in one
particular summer in the late 90s. Using that felt quite productive,
but also limited (due to a 4-track limit).
When I switched to Linux in 97, I
had many new things to learn and was quite busy, not really caring about
the sequencer thing. But later on, I had to discover that the situation
for me has gotten a lot worse now: All the big Linux sequencers were
purely graphical and not accessible through other means either. The
same situation is mostly true for Windows and Mac OS X unfortunately.
The obvious solutions like Reactor, Fruityloops or Abelton Live are all
far from being even remotely usable for blind musicians.
As far as I currently understand, the chances of finding usable support
for some professional screen reading solution and music composition on
Windows is relatively low, plus it might cost me a lot of money. So I
might as well try once again, and stay on Linux, where I actually
belong.
--
CYa,
⡍⠁⠗⠊⠕