On Thu, Mar 1, 2012 at 10:40 PM, Rui Nuno Capela wrote:
- Direct access plugin/insert parameter changing tool-tip added.
I'm not sure it makes a terrible sense to post this to LAD rather than
to LAU, but I'd just like to notice that I'm not extremely happy with
the current implementation of
On 3/5/12 2:16 AM, David Robillard wrote:
I think a very simple stand-alone API to deal with OSC message would go
a long way towards making OSC more feasible for plugins or Jack apps.
there are at least two options: a header library i've been using in a
couple of projects [1] and oscpack [2].
On Sat, Mar 03, 2012 at 11:20:00PM +0100, Albert Graef wrote:
I don't know if it's of practical use for anyone else, but time and
again I would have had good use for this apparently simple feature.
Same here. It would have immensely simplified some past projects,
and some more the come.
On Sat, Mar 03, 2012 at 05:29:14PM -0500, Paul Davis wrote:
this general language is the whole problem.
you can't send OSC to an OSC capable plugin or an external OSC
application in any generalized sense, because there is no shared
format for the messages.
the sequence of messages that
Am 5. März 2012 12:24 schrieb Fons Adriaensen f...@linuxaudio.org:
On Sun, Mar 04, 2012 at 12:55:39AM +0100, Albert Graef wrote:
Well, what you see as a problem, I see as a virtue. It gives me the
flexibility to just pick my own set of messages for the application at
hand. The sequencer
On 03/05/2012 10:33 AM, Alexandre Prokoudine wrote:
On Thu, Mar 1, 2012 at 10:40 PM, Rui Nuno Capela wrote:
- Direct access plugin/insert parameter changing tool-tip added.
I'm not sure it makes a terrible sense to post this to LAD rather than
to LAU, but I'd just like to notice that I'm not
On Mon, Mar 5, 2012 at 8:43 PM, Rui Nuno Capela wrote:
to tweak more than one parameter simultaneously, for what i'm curious on how
you actually could do just that with one 1-dimensional slider
What would I want that for? Just provide one slider per setting :)
Works like a charm in A3 :)
On 03/05/2012 04:48 PM, Alexandre Prokoudine wrote:
On Mon, Mar 5, 2012 at 8:43 PM, Rui Nuno Capela wrote:
to tweak more than one parameter simultaneously, for what i'm curious on how
you actually could do just that with one 1-dimensional slider
What would I want that for? Just provide one
On 03/05/2012 05:15 PM, Alexandre Prokoudine wrote:
On Mon, Mar 5, 2012 at 8:59 PM, Rui Nuno Capelarn...@rncbc.org wrote:
On 03/05/2012 04:48 PM, Alexandre Prokoudine wrote:
On Mon, Mar 5, 2012 at 8:43 PM, Rui Nuno Capela wrote:
to tweak more than one parameter simultaneously, for what i'm
On Mon, 2012-03-05 at 12:13 +0100, Stefan Kersten wrote:
On 3/5/12 2:16 AM, David Robillard wrote:
I think a very simple stand-alone API to deal with OSC message would go
a long way towards making OSC more feasible for plugins or Jack apps.
there are at least two options: a header library
On Sat, Mar 3, 2012 at 11:14 PM, Emanuel Rumpf xb...@web.de wrote:
Am 3. März 2012 23:29 schrieb Paul Davis p...@linuxaudiosystems.com:
OSC
this general language is the whole problem.
you can't send OSC to an OSC capable plugin or an external OSC
application in any generalized sense,
On Sun, Mar 4, 2012 at 2:50 AM, Emanuel Rumpf xb...@web.de wrote:
Am 4. März 2012 11:14 schrieb J. Liles malnour...@gmail.com:
On Sat, Mar 3, 2012 at 11:14 PM, Emanuel Rumpf xb...@web.de wrote:
There should at least be an accepted, standardized
way for transmission of MIDI data over OSC !
On 03/04/2012 03:31 AM, David Robillard wrote:
However, I doubt Ardour ever will, nor do I think it even should,
support sequencing of events that are transmitted by some mechanism
other than Jack. That would be a gigantic inconsistent mess for more
reasons than I feel like listing, and trying
On 03/04/2012 03:47 AM, David Robillard wrote:
I probably said this. Internally it's like Jack in most of the
important places, i.e. the actual type of the event payload is pretty
much irrelevant. The biggest problem to solve is the on-disk format.
That shouldn't be a real problem. OSC is
On 3/4/12, J. Liles malnour...@gmail.com wrote:
I personally don't think that the way notes are encoded is the primary
limitation imposed by MIDI. A note is a frequency, an attack/decay
modulation, and a duration.
apparently you're forgetting or have not been a part of the many
debates with
Am 4. März 2012 14:38 schrieb Paul Davis p...@linuxaudiosystems.com:
... the
problem for users is that it leaves the mappings unspecified, and
although there are some clever solutions for this (several of them),
from a user's perspective it always adds an extra layer of complexity.
contrast
On Sun, 2012-03-04 at 14:14 +0100, Albert Graef wrote:
On 03/04/2012 03:47 AM, David Robillard wrote:
I probably said this. Internally it's like Jack in most of the
important places, i.e. the actual type of the event payload is pretty
much irrelevant. The biggest problem to solve is the
On Sun, 2012-03-04 at 08:38 -0500, Paul Davis wrote:
On 3/4/12, J. Liles malnour...@gmail.com wrote:
I personally don't think that the way notes are encoded is the primary
limitation imposed by MIDI. A note is a frequency, an attack/decay
modulation, and a duration.
apparently you're
Guys, can you explain to me, who is not very well aware of OSC
and MIDI debates, why not come up with at least a Linux Audio OSC
standard for notes and just use that?
--
Louigi Verona
http://www.louigiverona.ru/
___
Linux-audio-dev mailing list
The chance for MIDI to improve seems very low, due to its technical
limits.
HD-Protocol MIDI is coming, albeit with painfully slow progress.
Best Regards,
Jeff
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
On 03/04/2012 06:32 PM, David Robillard wrote:
What do you mean by pick the OSC addresses that I want?
I mean those symbols with the slashes that are the first part of any
atomic OSC message like /foo/bar 4711.0. Usually such a symbol would
denote the particular control that the value
On Sun, 2012-03-04 at 22:38 +0300, Louigi Verona wrote:
Guys, can you explain to me, who is not very well aware of OSC
and MIDI debates, why not come up with at least a Linux Audio OSC
standard for notes and just use that?
Chicken Egg problem.
(Never trust a spec not actually used by anyone)
On Sun, 2012-03-04 at 22:27 +0100, Albert Graef wrote:
On 03/04/2012 06:32 PM, David Robillard wrote:
What do you mean by pick the OSC addresses that I want?
I mean those symbols with the slashes that are the first part of any
atomic OSC message like /foo/bar 4711.0. Usually such a symbol
On 03/04/2012 09:27 PM, Albert Graef wrote:
P.S.: Rui, apologies for hitchhiking your thread. I hope that you will
forgive me over a glass of good Californian wine. ;-)
no worries. given the length of the thread i think i'll take two please ;)
cheers
--
rncbc aka Rui Nuno Capela
On 03/04/2012 11:26 PM, Rui Nuno Capela wrote:
no worries. given the length of the thread i think i'll take two please ;)
Ok, granted. I'd even make that two bottles if you implement OSC tracks
in Qtractor. ;-)
Albert
--
Dr. Albert Graf
Dept. of Music-Informatics, University of Mainz,
On Mon, Mar 5, 2012 at 7:47 AM, Albert Graef dr.gr...@t-online.de wrote:
On 03/04/2012 11:26 PM, Rui Nuno Capela wrote:
no worries. given the length of the thread i think i'll take two please ;)
Ok, granted. I'd even make that two bottles if you implement OSC tracks in
Qtractor. ;-)
On Mon, 2012-03-05 at 09:40 +0900, michael noble wrote:
[...]
I'm chiming in late here, but it is a topic I've thought about a
little having experimented in the domain. Given the open-endedness of
OSC, I've always thought it makes more sense to implement some kind of
plugin based translators,
On Mon, Mar 5, 2012 at 10:16 AM, David Robillard d...@drobilla.net wrote:
I don't really grasp what you're getting at here, or what MIDI has to do
with it, etc. However, using plugins to process/filter/whatever OSC
messages is natural (same thing for Jack apps). You can use any event
types
On 03/03/2012 07:36 AM, Albert Graef wrote:
I don't see why an OSC track should make any assumptions about the
semantics of OSC messages.
For optimized representation and editing.
Avoiding artificial restrictions can give you both freedom and clumsiness ;)
--
Thorsten Wilms
thorwil's
On Sat, 2012-03-03 at 07:36 +0100, Albert Graef wrote:
On 03/03/2012 06:50 AM, David Robillard wrote:
There is also the chicken egg problem, last I checked there wasn't an
OSC note standard in use anywhere to have Ardour send...
I don't see why an OSC track should make any assumptions
On 03/03/2012 08:25 PM, David Robillard wrote:
Sure, you could just implement dumb raw OSC recording and playback, but
there's little point in using a DAW for that (not to mention little
practical musical use)
But that's exactly what I want. For starters, even just simple messages
consisting
On Sat, Mar 3, 2012 at 5:20 PM, Albert Graef dr.gr...@t-online.de wrote:
On 03/03/2012 08:25 PM, David Robillard wrote:
Sure, you could just implement dumb raw OSC recording and playback, but
there's little point in using a DAW for that (not to mention little
practical musical use)
But
On 03/03/2012 11:20 PM, Albert Graef wrote:
On 03/03/2012 08:25 PM, David Robillard wrote:
Sure, you could just implement dumb raw OSC recording and playback, but
there's little point in using a DAW for that (not to mention little
practical musical use)
But that's exactly what I want. For
On 03/03/2012 11:29 PM, Paul Davis wrote:
you can't send OSC to an OSC capable plugin or an external OSC
application in any generalized sense, because there is no shared
format for the messages.
Yes, there is. It's the OSC format itself. If you want to keep it
simple, you could boil it down
On 03/03/2012 11:36 PM, Robin Gareus wrote:
I use Algoscore for sequencing OSC.
http://kymatica.com/Software/AlgoScore
Hi Robin,
thanks for the pointers. Yes I know about AlgoScore and Iannix, but
that's not quite what I had in mind.
There was a presentation at Piksel a few years back
On Sat, 2012-03-03 at 23:20 +0100, Albert Graef wrote:
On 03/03/2012 08:25 PM, David Robillard wrote:
Sure, you could just implement dumb raw OSC recording and playback, but
there's little point in using a DAW for that (not to mention little
practical musical use)
But that's exactly what
Am 3. März 2012 23:29 schrieb Paul Davis p...@linuxaudiosystems.com:
OSC
this general language is the whole problem.
you can't send OSC to an OSC capable plugin or an external OSC
application in any generalized sense, because there is no shared
format for the messages.
the sequence of
On 03/01/2012 07:40 PM, Rui Nuno Capela wrote:
So here it goes: Ardour is a full fledged, pro-level DAW and, for crying
out loud on its own, the flagship of the free/open-source pro-audio
fleet and movement, not only Linux anymore nowadays.
It goes without saying that Ardour offers an
Hey guys!
I would have to respectfully disagree with Rui as to amateurishness of
his sequencer. Having less features or being geared towards specific
workflow or being more specialized rather than all in one hardly makes a
tool a home studio tool.
As for people comparing it to Ardour, I would
On 03/02/2012 05:41 PM, Albert Graef wrote:
One thing I've been wondering about... Could you please elaborate on
what exactly the --enable-lv2-state-files configure option is for? That
was marked as experimental in previous svn revisions, and is one of the
very few options which are disabled by
On Fri, 2012-03-02 at 18:41 +0100, Albert Graef wrote:
On 03/01/2012 07:40 PM, Rui Nuno Capela wrote:
So here it goes: Ardour is a full fledged, pro-level DAW and, for crying
out loud on its own, the flagship of the free/open-source pro-audio
fleet and movement, not only Linux anymore
On 03/03/2012 06:50 AM, David Robillard wrote:
There is also the chicken egg problem, last I checked there wasn't an
OSC note standard in use anywhere to have Ardour send...
I don't see why an OSC track should make any assumptions about the
semantics of OSC messages. It should just treat it
Howdy,
There's no victory over anything whatsoever. Read it again, it's just a
codename. If that serves anything at all, to my own defense that is,
Qtractor is still a pet project hobby of mine, as all things in Linux
audio world for that matter.
There's been too many saying and comparing
43 matches
Mail list logo
