Re: [LAU] Linux Audio podcast, episode001

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Louigi Verona <louigi.verona@...>
Cc: linux-audio-user <linux-audio-user@...>
Date: Tuesday, July 2, 2013 - 7:14 pm

--089e0160bd0e66414e04e08c2863
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jul 2, 2013 at 6:41 PM, Louigi Verona
wrote:

Nice perspective, informative. I think it would be a great resource to get
feedback like what you said from a wide range of linux-audio musicians, as
a kind of "probe" to find the most significant lacking elements. Perhaps
I'll be told "we know that already", but what harm in confirming our
suspicions?
Anybody know how to best gather up such info? (I'm not experienced in that
kinda thing)

Re workflow, if some type of OSC protocol could be established between a
synth ("client"/"automate-able") and an automation program
("host"/"automater"), twisting the knob on the synth client could inform
the host which parameter to show in the editor...?
Perhaps its a bit of a hack, and it would require wide-spread
implementation to become useful, but it is a *workable* solution. Perhaps
not the neatest, but I think worth mentioning.

--089e0160bd0e66414e04e08c2863
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 2, 2013 at 6:41 PM, Louigi Verona <louigi.verona@gmail.com> wro=
te:> Just some thoughts to share <snip>Nice per=
spective, informative. I think it would be a great resource to get feedback=
like what you said from a wide range of linux-audio musicians, as a kind o=
f "probe" to find the most significant lacking elements. Perhaps =
I'll be told "we know that already", but what harm in confirm=
ing our suspicions?
Anybody know how to best gather up such info? (I'm not exper=
ienced in that kinda thing)Re workflow, if some type of =
OSC protocol could be established between a synth ("client"/&quot=
;automate-able") and an automation program ("host"/"aut=
omater"), twisting the knob on the synth client could inform the host =
which parameter to show in the editor...?
Perhaps its a bit of a hack, and it would require wide-spread im=
plementation to become useful, but it is a *workable* solution. Perhaps not=
the neatest, but I think worth mentioning.

--089e0160bd0e66414e04e08c2863--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Linux Audio podcast, episode001, Louigi Verona, (Tue Jul 2, 5:41 pm)
Re: [LAU] Linux Audio podcast, episode001, Julien Claassen, (Tue Jul 2, 10:56 pm)
Re: [LAU] Linux Audio podcast, episode001, Harry van Haaren, (Tue Jul 2, 7:14 pm)
Re: [LAU] Linux Audio podcast, episode001, Harry van Haaren, (Tue Jul 2, 7:41 pm)
Re: [LAU] Linux Audio podcast, episode001, Louigi Verona, (Tue Jul 2, 7:17 pm)
Re: [LAU] Linux Audio podcast, episode001, Diego Simak, (Tue Jul 2, 6:27 pm)
Re: [LAU] Linux Audio podcast, episode001, Louigi Verona, (Tue Jul 2, 6:55 pm)
Re: [LAU] Linux Audio podcast, episode001, Dave Phillips, (Tue Jul 2, 8:38 pm)
Re: [LAU] Linux Audio podcast, episode001, Paul Davis, (Wed Jul 3, 7:03 am)
Re: [LAU] Linux Audio podcast, episode001, Louigi Verona, (Wed Jul 3, 7:12 am)
Re: [LAU] Linux Audio podcast, episode001, Paul Davis, (Wed Jul 3, 5:51 pm)
Re: [LAU] Linux Audio podcast, episode001, david, (Wed Jul 3, 7:38 am)
Re: [LAU] Linux Audio podcast, episode001, Rui Nuno Capela, (Tue Jul 2, 9:43 pm)
Re: [LAU] Linux Audio podcast, episode001, Diego Simak, (Tue Jul 2, 7:26 pm)