Re: [LAU] Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
5 Mar
2011
5 Mar
'11
8:47 p.m.
Yes they are, basically everything is MIDI
controllable in Qtractor
(mute, solo, panning, volume, plug-in parameters). Together with my
BCF2000 and BCR2000 it really is a powerful mixing tool. BCF2000 for the
mixing and BCR2000 for the plug-in parameters. I've programmed the
automation for the fade-out in seq24.
also, curious why you used Qtractor instead
of Ardour?
are there params that aren't not able to be controlled in Ardour?
5 Mar
5 Mar
9:01 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On 03/05/2011 08:47 PM, Kim Cascone wrote:
also, curious why you used Qtractor instead of Ardour?
Qtractor is my DAW of choice.
are there params that aren't not able to be
controlled in Ardour?
Don't know, I've never used Ardour.
Best,
Jeremy
8 Mar
8 Mar
6:42 a.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Sun, Mar 6, 2011 at 4:47 AM, Kim Cascone <kim(a)anechoicmedia.com> wrote:
Yes they are, basically everything is MIDI
controllable in Qtractor
Sure - parameters of GUI based LV2 plugins for one thing, at least in
Ardour2.x...
-michael
(mute, solo, panning, volume, plug-in
parameters). Together with my
BCF2000 and BCR2000 it really is a powerful mixing tool. BCF2000 for the
mixing and BCR2000 for the plug-in parameters. I've programmed the
automation for the fade-out in seq24.
also, curious why you used Qtractor instead of Ardour?
are there params that aren't not able to be controlled in Ardour?
1:14 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Tue, Mar 8, 2011 at 12:42 AM, michael noble <looplog(a)gmail.com> wrote:
On Sun, Mar 6, 2011 at 4:47 AM, Kim Cascone
<kim(a)anechoicmedia.com> wrote:
Sure - parameters of GUI based LV2 plugins for one thing, at least in
Ardour2.x...
not that i'm aware of ... could you go into a bit more detail about this?
i don't care that someone is using QTractor - its a fine program - but
i'm really not sure if the claim you made is correct, and i'd like to
understand it.
Yes they are, basically everything is MIDI controllable in Qtractor
(mute, solo, panning, volume, plug-in parameters). Together with my
BCF2000 and BCR2000 it really is a powerful mixing tool. BCF2000 for the
mixing and BCR2000 for the plug-in parameters. I've programmed the
automation for the fade-out in seq24.
also, curious why you used Qtractor instead of Ardour?
are there params that aren't not able to be controlled in Ardour? 
2:18 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
Paul Davis wrote:
On Tue, Mar 8, 2011 at 12:42 AM, michael noble
<looplog(a)gmail.com> wrote:
Perhaps I can add something to this.. Paul - I think what this is about
is that there is no way (as far as I'm aware) to assign a MIDI
controller to a control on an LV2 (if it has its own UI). I think the
nicest way to do this would be to adopt a scheme similar to assigning
other controls, where the control is moved and the corresponding MIDI
controller is 'learned' and associated with the control.
- For example in energyXT, you just choose the MIDI controller, and then
tell the program to learn a corresponding control (even on a VST plugin)
by just moving the required control.
From a plugin developers point of view, this would best be handled by
ardour just listening to or generating the LV2 port events in response
to the midi control (in the same way that automation can generate port
events) rather than any fundamental changes to the way the LV2 GUI
controls are handled. This would mean no changes would be necessary to
the LV2 plugins (good from my point of view) and it would probably also
just work with plugins that don't generate their own UI (if that isn't
handled already)
On Sun, Mar 6, 2011 at 4:47 AM, Kim Cascone
<kim(a)anechoicmedia.com> wrote:
Sure -
parameters of GUI based LV2 plugins for one thing, at least in
Ardour2.x...
not that i'm aware of ... could you go into a bit more detail about this?
i don't care that someone is using QTractor - its a fine program - but
i'm really not sure if the claim you made is correct, and i'd like to
understand it.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
Yes they
are, basically everything is MIDI controllable in Qtractor
(mute, solo, panning, volume, plug-in parameters). Together with my
BCF2000 and BCR2000 it really is a powerful mixing tool. BCF2000 for the
mixing and BCR2000 for the plug-in parameters. I've programmed the
automation for the fade-out in seq24.
also, curious why you used Qtractor instead
of Ardour?
are there params that aren't not able to be controlled in Ardour?
4:15 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Tue, Mar 8, 2011 at 10:46 PM, linuxdsp <mike(a)linuxdsp.co.uk> wrote:
Paul Davis wrote:
Yes, the conversation was in regards to midi control of parameters, hence my
statement. I raised the question on the ardour-users list on Dec 8, 2009, if
you wish to reference the conversation.
Paul, your response was:
they do not work. Ardour does not own or control the windows that they
not that i'm aware of ... could you go into a
bit more detail about this?
i don't care that someone is using QTractor - its a fine program - but
i'm really not sure if the claim you made is correct, and i'd like to
understand it.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
Perhaps I can add something to this.. Paul - I think what this is about
is that
there is no way (as far as I'm aware) to assign a MIDI controller to
a control on an LV2 (if it has its own UI). I think the nicest way to do
this would be to adopt a scheme similar to assigning other controls, where
the control is moved and the corresponding MIDI controller is 'learned' and
associated with the control.
- For example in energyXT, you just choose the MIDI controller, and then
tell the program to learn a corresponding control (even on a VST plugin) by
just moving the required control.
From a plugin developers point of view, this would best be handled by
ardour just listening to or generating the LV2 port events in response to
the midi control (in the same way that automation can generate port events)
rather than any fundamental changes to the way the LV2 GUI controls are
handled. This would mean no changes would be necessary to the LV2 plugins
(good from my point of view) and it would probably also just work with
plugins that don't generate their own UI (if that isn't handled already)
create (this includes LV2 ext GUI) and so there is no
reasonably sane
way to interpose between the user's input devices and the GUIs in
order to initiate MIDI binding, etc.
There was some discussion of possible ways to get around this issue. At the
time, however, you regarded the issue as "just not very high on my list of
priorities." I believe you stated that the overhauled binding system in A3
would potentially fix the issue.
-michael
4:18 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Tue, Mar 8, 2011 at 10:15 AM, michael noble <looplog(a)gmail.com> wrote:
Yes, the conversation was in regards to midi control
of parameters, hence my
statement. I raised the question on the ardour-users list on Dec 8, 2009, if
you wish to reference the conversation.
Paul, your response was:
ah, thanks for that. yes, indeed the binding system in a3 will fix
that issue, at least in the sense that MIDI binding maps can reference
any parameter in any plugin.
it doesn't address a "MIDI learn" style of binding, which i still
can't see how to implement since the action that would start it occurs
(presumably) with some user action in the plugin GUI, and the host
doesn't know about it.
they do not work. Ardour does not own or control
the windows that they
create (this includes LV2 ext GUI) and so there is no reasonably sane
way to interpose between the user's input devices and the GUIs in
order to initiate MIDI binding, etc.
There was some discussion of possible ways to get around this issue. At the
time, however, you regarded the issue as "just not very high on my list of
priorities." I believe you stated that the overhauled binding system in A3
would potentially fix the issue.
4:33 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Wed, Mar 9, 2011 at 12:18 AM, Paul Davis <paul(a)linuxaudiosystems.com>wrote;wrote:
it doesn't address a "MIDI learn" style of binding, which i still
can't see how to implement since the action that would start it occurs
(presumably) with some user action in the plugin GUI, and the host
doesn't know about it.
The last SVN of A3 I tried actually does solve the issue in a sense. By
exposing the parameter as an automation lane you can use Ardour's standard
midi learn on the exposed control UI element that appears. Given this was
essentially the suggestion I made in the earlier conversation, the
implementation seems just fine to me...
-michael
4:38 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
On Tue, Mar 8, 2011 at 10:33 AM, michael noble <looplog(a)gmail.com> wrote:
On Wed, Mar 9, 2011 at 12:18 AM, Paul Davis
<paul(a)linuxaudiosystems.com>
wrote:
that's true! i forget the details of "my own" software :) (mostly
because its not really "my own"!)
thanks for pointing that out.
it doesn't address a "MIDI learn" style of binding, which i still
can't see how to implement since the action that would start it occurs
(presumably) with some user action in the plugin GUI, and the host
doesn't know about it.
The last SVN of A3 I tried actually does solve the issue in a sense. By
exposing the parameter as an automation lane you can use Ardour's standard
midi learn on the exposed control UI element that appears. Given this was
essentially the suggestion I made in the earlier conversation, the
implementation seems just fine to me...
5:01 p.m.
New subject: Music Made with Linux: The Infinite Repeat - Money, or Love (DJ AutoStatic Remix)
Paul Davis wrote:
On Tue, Mar 8, 2011 at 10:15 AM, michael noble
<looplog(a)gmail.com> wrote:
Normally, (in some other DAWs), the MIDI learn style of binding is
initiated with some action by the user on the host e.g. the user clicks
on an option in one of the hosts standard menus (not a plugin specific
menu) e.g. just a generic 'Options->MIDI Learn' kind of thing, or
activates a general purpose host key binding, then the user is prompted
through a sequence of operations along the lines of 'Operate control on
MIDI device' followed by 'Operate Control on GUI' and the two events are
then bound together. This doesn't require any special menus or options
on the plugin since its not specific to plugins, it just allows anything
the user can generate events from (MIDI controllers, LV2 ports via
plugin UIs, normal host controls etc.. to be bound together). That said
it sounds like A3s method of setting bindings to LV2 ports is a
perfectly good way of achieving the same result, so perhaps its not
really an issue.
Yes, the conversation was in regards to midi
control of parameters, hence my
statement. I raised the question on the ardour-users list on Dec 8, 2009, if
you wish to reference the conversation.
Paul, your response was:
ah, thanks for that. yes, indeed the binding system in a3 will fix
that issue, at least in the sense that MIDI binding maps can reference
any parameter in any plugin.
it doesn't address a "MIDI learn" style of binding, which i still
can't see how to implement since the action that would start it occurs
(presumably) with some user action in the plugin GUI, and the host
doesn't know about it.
they do not work. Ardour does not own or control
the windows that they
create (this includes LV2 ext GUI) and so there is no reasonably sane
way to interpose between the user's input devices and the GUIs in
order to initiate MIDI binding, etc.
There was some discussion of possible ways to
get around this issue. At the
time, however, you regarded the issue as "just not very high on my list of
priorities." I believe you stated that the overhauled binding system in A3
would potentially fix the issue.
5003
days inactive
5006
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Jeremy Jongepier -
Kim Cascone -
linuxdsp -
michael noble -
Paul Davis