30 May
2010
30 May
'10
7:13 a.m.
Hi all,
I just finished up my port of Autotalent (A real-time pitch manipulation
program by Tom Baran) to an LV2 plugin (Okay, It's not finished, but all the
important features are there.)
It should work basically the same as Autotalent except:
- It is an LV2 plugin instead of an LADSPA plugin
- It provides MIDI output of the pitch
- It accepts MIDI input
- It separates the pull to semitone and snap to scale functionality
- It uses FFTW for the DFT routines, greatly improving performance.
- Minor performance tweaks (substituting memcpy for loops, etc)
- It is greatly refactored (broken into methods and structures, variables
renamed)
- Does not include smooth pitch jumping or LFO functionality in the first
release (will add later)
- The formant corrector causes artifacts not present in the original (I'm
not sure how to fix, as it's the only part of the original I don't
understand)
I think especially significant is the midi input and output. This would
allow you to do the following:
- Record an audio track in your favorite DAW while running it through the
plugin, and outputting the MIDI to another track
- Correct the midi however you want (keep it monophonic)
- Feed the corrected MIDI track back into the plugin with the recorded
audio, and listen as it corrects the pitch to match the MIDI you gave!
There are also other options, such as controlling an MIDI synth with your
voice, or getting a vocoder-like effect by controlling your voice with a
MIDI keyboard.
You can check out the project page for more information
here<http://code.google.com/p/autotalentlv2/> or
if you want a direct source download, see
here<http://autotalentlv2.googlecode.com/files/autotalent_source.tar.gz&…
.
Any feedback on the source code or plugin would be welcome.
Jeremy Salwen
30 May
30 May
11:20 a.m.
Hi Jeremy,
söndag 30 maj 2010 07.13.14 skrev Jeremy:
Hi all,
I just finished up my port of Autotalent (A real-time pitch manipulation
program by Tom Baran) to an LV2 plugin (Okay, It's not finished, but all
the important features are there.)
It should work basically the same as Autotalent except:
Nice work, or perhaps great work! I know that many people want your additions
of Autotalent. :-)
That leads me into thinking: Perhaps you should rename your project as soon as
possible to something different? I mean, you have many new features (and will
possibly come up with more), refactoring has being done and your program is an
LV2 plugin witch act more as a fork that take a new direction compared to
Autotalent.
Why do I care? Well, the reason is that it's will not be a big surprise if Tom
Baran comes up with an LV2 version of the plugin while the program still
continues as it did as a LADSPA plugin. After a look at Autotalent's website,
it seem to me that Tom Baran continues to develop Autotalent.
This will in that case lead us into a situation where we have two plugins with
wich goes in to (very) different directions while have a common ground idea
and and names: Autotalent and autotalentlv2. I can imagine that it's not very
cool if the original Autotalent also acts as an LV2 plugin and perhaps come up
with MIDI support in the future. And why the "LV2" in the name anyway?
All the Q*'s, G*'s, *K*'s and *LV2's in the project names are probably one
of
the biggest reasons that keeps the world from adapting it to use Linux apps
when making music and use Linux at all. Q's, G's, K's and in some respect LV2
are for people that already know about toolkits, desktop environments and what
they like - It's very confusing for newbies, and the Linux world have confused
the rest of the word in at least 15 years now.
That said, kudos to you for bringing up Tom Baran and Autotalent in the light
and giving him credit. You and Tom Baran have delivered two great apps, but
your project is already a grown up one and have it's own character - it
deserves it's own name.
Jostein
7:48 p.m.
On Sun, May 30, 2010 at 5:20 AM, Jostein Chr. Andersen <jostein(a)vait.se>wrote;wrote:
Hi Jeremy,
söndag 30 maj 2010 07.13.14 skrev Jeremy:
I agree, but quite frankly, I don't have any good ideas for names. As long
as it's googleable, I'm up to suggestions (I hate applications that have
names like "USA" or something, so it is impossible to google for any
information.)
Hi all,
I just finished up my port of Autotalent (A real-time pitch manipulation
program by Tom Baran) to an LV2 plugin (Okay, It's not finished, but all
the important features are there.)
It should work basically the same as Autotalent except:
Nice work, or perhaps great work! I know that many people want your
additions
of Autotalent. :-)
That leads me into thinking: Perhaps you should rename your project as soon
as
possible to something different? I mean, you have many new features (and
will
possibly come up with more), refactoring has being done and your program is
an
LV2 plugin witch act more as a fork that take a new direction compared to
Autotalent.
Why do I care? Well, the reason is that it's will not be a big surprise if
Tom
Baran comes up with an LV2 version of the plugin while the program still
continues as it did as a LADSPA plugin. After a look at Autotalent's
website,
it seem to me that Tom Baran continues to develop Autotalent.
This will in that case lead us into a situation where we have two plugins
with
wich goes in to (very) different directions while have a common ground idea
and and names: Autotalent and autotalentlv2. I can imagine that it's not
very
cool if the original Autotalent also acts as an LV2 plugin and perhaps come
up
with MIDI support in the future. And why the "LV2" in the name anyway?
All the Q*'s, G*'s, *K*'s and *LV2's in the project names are probably
one
of
the biggest reasons that keeps the world from adapting it to use Linux apps
when making music and use Linux at all. Q's, G's, K's and in some respect
LV2
are for people that already know about toolkits, desktop environments and
what
they like - It's very confusing for newbies, and the Linux world have
confused
the rest of the word in at least 15 years now.
That said, kudos to you for bringing up Tom Baran and Autotalent in the
light
and giving him credit. You and Tom Baran have delivered two great apps, but
your project is already a grown up one and have it's own character - it
deserves it's own name.
Jostein
7:52 p.m.
Excerpts from Jeremy's message of 2010-05-30 19:48:30 +0200:
On Sun, May 30, 2010 at 5:20 AM, Jostein Chr. Andersen
<jostein(a)vait.se>wrote;wrote:
I don't know whether you've contacted the original author or not, but
maybe cooperate and keep the same name?
--
Regards,
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen
offen." Bertolt Brecht, Der gute Mensch von Sezuan
Hi Jeremy,
söndag 30 maj 2010 07.13.14 skrev Jeremy:
I agree, but quite frankly, I don't have any good ideas for names. As long
as it's googleable, I'm up to suggestions (I hate applications that have
names like "USA" or something, so it is impossible to google for any
information.) Hi all,
I just finished up my port of Autotalent (A real-time pitch manipulation
program by Tom Baran) to an LV2 plugin (Okay, It's not finished, but all
the important features are there.)
It should work basically the same as Autotalent except:
Nice work, or perhaps great work! I know that many people want your
additions
of Autotalent. :-)
That leads me into thinking: Perhaps you should rename your project as soon
as
possible to something different? I mean, you have many new features (and
will
possibly come up with more), refactoring has being done and your program is
an
LV2 plugin witch act more as a fork that take a new direction compared to
Autotalent.
Why do I care? Well, the reason is that it's will not be a big surprise if
Tom
Baran comes up with an LV2 version of the plugin while the program still
continues as it did as a LADSPA plugin. After a look at Autotalent's
website,
it seem to me that Tom Baran continues to develop Autotalent.
This will in that case lead us into a situation where we have two plugins
with
wich goes in to (very) different directions while have a common ground idea
and and names: Autotalent and autotalentlv2. I can imagine that it's not
very
cool if the original Autotalent also acts as an LV2 plugin and perhaps come
up
with MIDI support in the future. And why the "LV2" in the name anyway?
All the Q*'s, G*'s, *K*'s and *LV2's in the project names are probably
one
of
the biggest reasons that keeps the world from adapting it to use Linux apps
when making music and use Linux at all. Q's, G's, K's and in some respect
LV2
are for people that already know about toolkits, desktop environments and
what
they like - It's very confusing for newbies, and the Linux world have
confused
the rest of the word in at least 15 years now.
That said, kudos to you for bringing up Tom Baran and Autotalent in the
light
and giving him credit. You and Tom Baran have delivered two great apps, but
your project is already a grown up one and have it's own character - it
deserves it's own name.
Jostein
8:01 p.m.
On Sun, May 30, 2010 at 12:50 PM, Philipp Überbacher
<hollunder(a)lavabit.com>wrote;wrote:
Excerpts from Jeremy's message of 2010-05-30
19:48:30 +0200:
long
I have talked to him, and he seemed enthusiastic about someone else using
his code, but I'm not sure if he's done work on it since version 2. If he
has, it might not make sense to keep the same name, unless we agree to merge
the changes.
Jeremy
On Sun, May 30, 2010 at 5:20 AM, Jostein Chr.
Andersen <jostein(a)vait.se
wrote:
> Hi Jeremy,
>
> söndag 30 maj 2010 07.13.14 skrev Jeremy:
> > Hi all,
> >
> > I just finished up my port of Autotalent (A real-time pitch
manipulation
> > program by Tom Baran) to an LV2 plugin
(Okay, It's not finished, but
all
> > the important features are there.)
> >
> > It should work basically the same as Autotalent except:
>
> Nice work, or perhaps great work! I know that many people want your
> additions
> of Autotalent. :-)
>
> That leads me into thinking: Perhaps you should rename your project as
soon
> as
> possible to something different? I mean, you have many new features
(and
> will
> possibly come up with more), refactoring has being done and your
program is
> an
> LV2 plugin witch act more as a fork that take a new direction compared
to
> Autotalent.
>
> Why do I care? Well, the reason is that it's will not be a big surprise
if
> Tom
> Baran comes up with an LV2 version of the plugin while the program
still
> continues as it did as a LADSPA plugin.
After a look at Autotalent's
> website,
> it seem to me that Tom Baran continues to develop Autotalent.
>
> This will in that case lead us into a situation where we have two
plugins
> with
> wich goes in to (very) different directions while have a common ground
idea
> and and names: Autotalent and autotalentlv2.
I can imagine that it's
not
> very
> cool if the original Autotalent also acts as an LV2 plugin and perhaps
come
> up
> with MIDI support in the future. And why the "LV2" in the name anyway?
>
> All the Q*'s, G*'s, *K*'s and *LV2's in the project names are
probably
one
> of
> the biggest reasons that keeps the world from adapting it to use Linux
apps
> when making music and use Linux at all.
Q's, G's, K's and in some
respect
> LV2
> are for people that already know about toolkits, desktop environments
and
> what
> they like - It's very confusing for newbies, and the Linux world have
> confused
> the rest of the word in at least 15 years now.
>
> That said, kudos to you for bringing up Tom Baran and Autotalent in the
> light
> and giving him credit. You and Tom Baran have delivered two great apps,
but
your
project is already a grown up one and have it's own character - it
deserves it's own name.
Jostein
I agree, but quite frankly, I don't have any good ideas for names. As as it's googleable, I'm up to suggestions
(I hate applications that have
names like "USA" or something, so it is impossible to google for any
information.)
I don't know whether you've contacted the original author or not, but
maybe cooperate and keep the same name?
--
Regards,
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle
Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
6:41 p.m.
On Sat, May 29, 2010 at 10:13 PM, Jeremy <jeremybubs(a)gmail.com> wrote:
Record an audio track in your favorite DAW while
running it through the
plugin, and outputting the MIDI to another track
Correct the midi however you want (keep it monophonic)
Feed the corrected MIDI track back into the plugin with the recorded audio,
and listen as it corrects the pitch to match the MIDI you gave!
Seems like you could do some interesting effects this way... like
feeding by the incoming midi pitch tracking to an arpeggiator, then
autotuning off the arpeggiator. Actually something that does a half
decent job at pitch tracking would be pretty cool in it's own right...
so this autotune business is just nice frosting :-)
Thanks, this is very cool.
However, my excitement was soon dashed by not knowing enough about
LV2, or the lack of an "install:" rule in your Makefile :-)
After doing "yum install plotutils-devel" (nb: dependency on
'fftw-devel' too) I was able to generate autotalent_lv2.so via make on
Fedora 12, x86_64. How do I use this library?
I could certainly create a directory /usr/lib64/lv2/autotalent.lv2 for
the .so file, but what do I use for plugin.ttl and manifest.ttl?
Thanks!
Niels
http://nielsmayer.com
6:52 p.m.
On Sunday 30 May 2010 12:41:05 Niels Mayer wrote:
I could certainly create a directory
/usr/lib64/lv2/autotalent.lv2 for
the .so file, but what do I use for plugin.ttl and manifest.ttl?
This is where I am hung up at the moment too. Help appreciated.
Thanks!
Niels
http://nielsmayer.com
all the best,
drew
7:05 p.m.
On Sunday 30 May 2010 12:52:49 drew Roberts wrote:
drew
On Sunday 30 May 2010 12:41:05 Niels Mayer wrote:
OK,
I can see two .ttl files here:
http://code.google.com/p/autotalentlv2/source/browse/#svn/trunk
which were not in the archive I downloaded.
autotalent.ttl and manifest.ttl
perhaps autotalent .ttl is plugin.ttl?
time to experiment.
I could certainly create a directory
/usr/lib64/lv2/autotalent.lv2 for
the .so file, but what do I use for plugin.ttl and manifest.ttl?
This is where I am hung up at the moment too. Help appreciated. Thanks!
Niels
http://nielsmayer.com
all the best,
drew
7:55 p.m.
On Sun, May 30, 2010 at 1:05 PM, drew Roberts <zotz(a)100jamz.com> wrote:
On Sunday 30 May 2010 12:52:49 drew Roberts wrote:
drew
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Sorry for the mistakes everyone. I left out the ttl files, which should be
included, and removed the libplot dependency, which I was only using for
debugging purposes.
I also added an "install" option in the Makefile which puts it in the .lv2
folder in your home directory.
That should make any lv2 host recognize it, although probable only ones that
can handle nonstandard inputs and outputs will work (lv2_jack_host and Ingen
both work for me)
Jeremy
On Sunday 30 May 2010 12:41:05 Niels Mayer
wrote:
OK,
I can see two .ttl files here:
http://code.google.com/p/autotalentlv2/source/browse/#svn/trunk
which were not in the archive I downloaded.
autotalent.ttl and manifest.ttl
perhaps autotalent .ttl is plugin.ttl?
time to experiment.
I could certainly create a directory
/usr/lib64/lv2/autotalent.lv2 for
the .so file, but what do I use for plugin.ttl and manifest.ttl?
This is where I am hung up at the moment too. Help appreciated. Thanks!
Niels
http://nielsmayer.com
all the best,
drew
8:29 p.m.
I setup a directory /usr/lib64/lv2/autotalent.lv2 containing
-rwxr-xr-x 1 root root 26622 2010-05-30 11:06 autotalent_lv2.so*
-rw-r--r-- 1 root root 310 2010-05-30 11:04 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
(I renamed autotune.ttl to plugin.ttl to make it like all the other plugins).
Unfortunately, with this directory in place, every time I browse the
LV2 plugins in Qtractor it core dumps. I'm browsing LV2 via the
View->Buses... Under "Input Plugins" or "Output Plugins" tab,
click
"Add..." then crash. Removing the directory makes it work again.
When using the "make install" version in ~/.lv2, even after telling
Qtractor about the new LV2 directory, it simply ignores the plugin
(but also doesn't crash).
Anybody here know what it would take to get this to work in Qtractor,
which is my preferred plugin host. (will need to investigate ingen).
Niels
http://nielsmayer.com
8:37 p.m.
On Sun, May 30, 2010 at 2:29 PM, Niels Mayer <nielsmayer(a)gmail.com> wrote:
I setup a directory /usr/lib64/lv2/autotalent.lv2
containing
-rwxr-xr-x 1 root root 26622 2010-05-30 11:06 autotalent_lv2.so*
-rw-r--r-- 1 root root 310 2010-05-30 11:04 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
(I renamed autotune.ttl to plugin.ttl to make it like all the other
plugins).
Unfortunately, with this directory in place, every time I browse the
LV2 plugins in Qtractor it core dumps. I'm browsing LV2 via the
View->Buses... Under "Input Plugins" or "Output Plugins" tab,
click
"Add..." then crash. Removing the directory makes it work again.
When using the "make install" version in ~/.lv2, even after telling
Qtractor about the new LV2 directory, it simply ignores the plugin
(but also doesn't crash).
Anybody here know what it would take to get this to work in Qtractor,
which is my preferred plugin host. (will need to investigate ingen).
Niels
http://nielsmayer.com
Do not rename the autotalent.ttl to plugin.tll unless you reflect this
change in manifest.ttl.
I also would not expect it to work in qtractor, because qtractor expects
standard input and output ports. Ingen requires compiling from source, but
lv2_jack_host will also work, and it recognizes the plugin in it's current
form on my system. Your distro repositories should have it.
Jeremy
9:45 p.m.
On Sun, May 30, 2010 at 11:36 AM, Jeremy <jeremybubs(a)gmail.com> wrote:
Do not rename the autotalent.ttl to plugin.tll unless
you reflect this
change in manifest.ttl.
After correcting the naming in manifest.ttl, and placing the plugin
directory as /usr/lib64/lv2/autotalent.lv2/
-rwxr-xr-x 1 root root 26622 2010-05-30 11:14 autotalent_lv2.so*
-rw-r--r-- 1 root root 306 2010-05-30 12:19 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
I am now able to load this plugin into Qtractor (as a midi input or
output plugin) and see the LV2 control panel with many sliders and
controls. It even activates successfully. Attempting to use it as an
audio plugin, either for input or output, causes qtractor to crash.
I guess that's a good first step, and verifies what Rui just posted
:-) I guess this means the right way to use this is a via a plugin
host, and then hook that up via jack or alsa??
Rui -- any chance qtractor's "use cases" can be expanded to fit this
scenario (which seems pretty common).
What about the scenario of a plugin that provides audio in --> MIDI
notes (midi pitchtracker, which is part of what's provided in
autotalent). Is there a way of separately using it for audio->MIDI
input?
Thanks for all the help, hints, cool software!
Niels
http://nielsmayer.com
10:20 p.m.
On 05/30/2010 08:45 PM, Niels Mayer wrote:
On Sun, May 30, 2010 at 11:36 AM, Jeremy
<jeremybubs(a)gmail.com> wrote:
correct. that's the way it goes, asfaqg (as far as qtractor goes:)
Do not rename the autotalent.ttl to plugin.tll
unless you reflect this
change in manifest.ttl.
After correcting the naming in manifest.ttl, and placing the plugin
directory as /usr/lib64/lv2/autotalent.lv2/
-rwxr-xr-x 1 root root 26622 2010-05-30 11:14 autotalent_lv2.so*
-rw-r--r-- 1 root root 306 2010-05-30 12:19 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
I am now able to load this plugin into Qtractor (as a midi input or
output plugin) and see the LV2 control panel with many sliders and
controls. It even activates successfully. Attempting to use it as an
audio plugin, either for input or output, causes qtractor to crash.
I guess that's a good first step, and verifies what Rui just posted
:-) I guess this means the right way to use this is a via a plugin
host, and then hook that up via jack or alsa??
Rui -- any chance qtractor's "use cases"
can be expanded to fit this
scenario (which seems pretty common).
What about the scenario of a plugin that provides audio in --> MIDI
notes (midi pitchtracker, which is part of what's provided in
autotalent). Is there a way of separately using it for audio->MIDI
input?
besides the crash issue, which should not happen in any circumstance,
life's cruel however, there's no plan going on in that direction.
things can change though, but i will let Paul (i mean ardour3) take the
head on this one ;)
Thanks for all the help, hints, cool software!
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
10:25 p.m.
On Sun, May 30, 2010 at 4:26 PM, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
On 05/30/2010 08:45 PM, Niels Mayer wrote:
I wouldn't rule out my plugin crashing, so I'd first check that first.
By the way, I just added and tested some new pitch detection code, which
uses the MPM algorithm (as used in Tartini) I've released it as version
1.5.
Of course, that isn't very useful if you can't even get it running. I would
suggest running lv2_jack_host and connecting it though jack to Qtractor or
whatever.
On Sun, May 30, 2010 at 11:36 AM, Jeremy
<jeremybubs(a)gmail.com> wrote:
correct. that's the way it goes, asfaqg (as far as qtractor goes:)
Do not rename the autotalent.ttl to plugin.tll
unless you reflect this
change in manifest.ttl.
After correcting the naming in manifest.ttl, and placing the plugin
directory as /usr/lib64/lv2/autotalent.lv2/
-rwxr-xr-x 1 root root 26622 2010-05-30 11:14 autotalent_lv2.so*
-rw-r--r-- 1 root root 306 2010-05-30 12:19 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
I am now able to load this plugin into Qtractor (as a midi input or
output plugin) and see the LV2 control panel with many sliders and
controls. It even activates successfully. Attempting to use it as an
audio plugin, either for input or output, causes qtractor to crash.
I guess that's a good first step, and verifies what Rui just posted
:-) I guess this means the right way to use this is a via a plugin
host, and then hook that up via jack or alsa??
Rui -- any chance qtractor's "use
cases" can be expanded to fit this
scenario (which seems pretty common).
What about the scenario of a plugin that provides audio in --> MIDI
notes (midi pitchtracker, which is part of what's provided in
autotalent). Is there a way of separately using it for audio->MIDI
input?
besides the crash issue, which should not happen in any circumstance,
life's cruel however, there's no plan going on in that direction.
things can change though, but i will let Paul (i mean ardour3) take the
head on this one ;)
Thanks for all the help, hints, cool software!
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
31 May
31 May
3:29 a.m.
On Sun, May 30, 2010 at 4:25 PM, Jeremy <jeremybubs(a)gmail.com> wrote:
On Sun, May 30, 2010 at 4:26 PM, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
Another update, version 1.6. This time the LFO has been dutifully copied
over (the actual implementation is slightly different for quantized LFO, so
it will rest longer on notes before and after a jump in the scale, but it
shouldn't be too noticeable. If you'd like it the other way, I could always
implement it.)
Once I finish implementing pitch smoothing, I will move on to the next big
feature: voice duplication, to allow harmonizing, etc, and polyphonic midi
playback.
Jeremy
On 05/30/2010 08:45 PM, Niels Mayer wrote:
I wouldn't rule out my plugin crashing, so I'd first check that first.
By the way, I just added and tested some new pitch detection code, which
uses the MPM algorithm (as used in Tartini) I've released it as version
1.5.
Of course, that isn't very useful if you can't even get it running. I
would suggest running lv2_jack_host and connecting it though jack to
Qtractor or whatever.
On Sun, May 30, 2010 at 11:36 AM, Jeremy
<jeremybubs(a)gmail.com> wrote:
correct. that's the way it goes, asfaqg (as far as qtractor goes:)
Do not rename the autotalent.ttl to plugin.tll
unless you reflect this
change in manifest.ttl.
After correcting the naming in manifest.ttl, and placing the plugin
directory as /usr/lib64/lv2/autotalent.lv2/
-rwxr-xr-x 1 root root 26622 2010-05-30 11:14 autotalent_lv2.so*
-rw-r--r-- 1 root root 306 2010-05-30 12:19 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
I am now able to load this plugin into Qtractor (as a midi input or
output plugin) and see the LV2 control panel with many sliders and
controls. It even activates successfully. Attempting to use it as an
audio plugin, either for input or output, causes qtractor to crash.
I guess that's a good first step, and verifies what Rui just posted
:-) I guess this means the right way to use this is a via a plugin
host, and then hook that up via jack or alsa??
Rui -- any chance qtractor's "use
cases" can be expanded to fit this
scenario (which seems pretty common).
What about the scenario of a plugin that provides audio in --> MIDI
notes (midi pitchtracker, which is part of what's provided in
autotalent). Is there a way of separately using it for audio->MIDI
input?
besides the crash issue, which should not happen in any circumstance,
life's cruel however, there's no plan going on in that direction.
things can change though, but i will let Paul (i mean ardour3) take the
head on this one ;)
Thanks for all the help, hints, cool software!
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
30 May
30 May
9:31 p.m.
On 05/30/2010 07:29 PM, Niels Mayer wrote:
I setup a directory /usr/lib64/lv2/autotalent.lv2
containing
-rwxr-xr-x 1 root root 26622 2010-05-30 11:06 autotalent_lv2.so*
-rw-r--r-- 1 root root 310 2010-05-30 11:04 manifest.ttl
-rw-r--r-- 1 root root 12803 2010-05-30 11:04 plugin.ttl
(I renamed autotune.ttl to plugin.ttl to make it like all the other plugins).
Unfortunately, with this directory in place, every time I browse the
LV2 plugins in Qtractor it core dumps. I'm browsing LV2 via the
View->Buses... Under "Input Plugins" or "Output Plugins" tab,
click
"Add..." then crash. Removing the directory makes it work again.
When using the "make install" version in ~/.lv2, even after telling
Qtractor about the new LV2 directory, it simply ignores the plugin
(but also doesn't crash).
Anybody here know what it would take to get this to work in Qtractor,
which is my preferred plugin host. (will need to investigate ingen).
qtractor, as a plugin host, is currently accepting only the following
signal flows:
a) audio_fx plugins: audio_in -> plugin -> audio_out
b) instrument plugins: midi_in -> plugin -> audio_out
any other topology is, well, not designated to comply
a vocoder plugin is usually an audio_fx with direct midi control, which
i'm afraid, is not supported ootb-- it doesn't fit in any of the above
categories :(
gosh, there was this indirect solution as inserts but, don't go that
way. it doesn't work, you'll get just silence :S
bbl
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
5077
days inactive
5078
days old
linux-audio-dev@lists.linuxaudio.org
16 comments
7 participants
participants (7)
-
drew Roberts -
Jeremy -
Jostein Chr. Andersen -
Niels Mayer -
Paul Davis -
Philipp Überbacher -
Rui Nuno Capela