Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 direct access for the following reasons: 1. Only one setting per plug-in is available, so I can't have control over, say, attack and release in a compressor simultaneously. 2. The widget is hard to aim (which is probably a trade-off with an aim to make UI compact). Maybe some phat-like slider would do the trick? 3. The step for mouse wheel scrolling is too large by default and doesn't change to a more granular one with Alt/Shift modifier buttons. Re widgets, here is another idea: http://www.darktable.org/2012/03/bauhaus-widgets/ I'm not totally sure about it yet, I've yet to compile that branch. But just so you know... :) Alexandre Prokoudine http://libregraphicsworld.org ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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]. both c++ though ... sk [1] https://github.com/kaoskorobase/oscpp [2] http://www.rossbencina.com/code/oscpack ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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. There are many forms such a tool could take. It could be completely unaware of the 'meaning' of any messages, and just reproduce them at the right time. It could be made aware of some simple but recurring formats such as /foo/bar ,ff X Y and display them in a way that makes sense. It could even be made to store some data (e.g. continuous control values, or even 'notes' in an internal format and output them in and OSC format defined by the user. Ciao, -- FA Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 you record may make sense to Pure Data, but make absolutely no sense to, say, CSound. So what ? When a user needs a 'sequencer' or whatever you may call it, for OSC messages that means he/she already has a source and destination that understand each other. It's completely irrelevant if others understand the same messages. -- FA Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 shouldn't have to care about the particular set of OSC addresses I'm using. Agreed 100%. Agreed 40% Having a standard scheeme for _standard procedures doesn't kill your freedom to still pick custom addresses / add your own extensions to OSC, but simplifies things A LOT for those 90% of users who do standard things, as playing back notes and controlling typical values (e.g. velocity, volume, resonance...) Thus you wouldn't lose any virtue, but those 90% woud gain some. -- E.R. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 extremely happy with the current implementation of direct access for the following reasons: 1. Only one setting per plug-in is available, so I can't have control over, say, attack and release in a compressor simultaneously. the so called direct access feature does only affect one and only one plugin parameter at a time, that being an implementation/design limitation due to the fact that the provided slider widget is scalar and 1-dimensional by nature o.O 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, i'll assume you're asking for simultaneous access over the same display space, then look at the generic plugin dialog (plugin/properties) or the plugin own gui editor (plugin/edit), if any. 2. The widget is hard to aim (which is probably a trade-off with an aim to make UI compact). Maybe some phat-like slider would do the trick true. however i have no interesting plan on that regard. maybe, if someone steps up with a patch or sth... ;) 3. The step for mouse wheel scrolling is too large by default and doesn't change to a more granular one with Alt/Shift modifier buttons. true and the good news are it can be fixed sooner perhaps ;) Re widgets, here is another idea: http://www.darktable.org/2012/03/bauhaus-widgets/ I'm not totally sure about it yet, I've yet to compile that branch. But just so you know... :) too bad it looks like it's gtk2. i'm sure someone could rip it off as a qt4 widget and drop it in without much brain-sweat, someone with a lot a time to spare? ;) don't take me wrong. i love the ideas cheers -- rncbc aka Rui Nuno Capela rn...@rncbc.org ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 :) Deliberate limitation is a whole different thing, of course. Alexandre Prokoudine http://libregraphicsworld.org ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 slider per setting :) Works like a charm in A3 :) you have that in the generic plugin dialog or eventually on the its own provided gui editor. i'm sure that's exactly the same in a3. otoh, i don't think a3 has this direct access thingie, so which limitation is what? :) cheers -- rncbc aka Rui Nuno Capela rn...@rncbc.org ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 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 :) you have that in the generic plugin dialog or eventually on the its own provided gui editor. i'm sure that's exactly the same in a3. otoh, i don't think a3 has this direct access thingie http://i.minus.com/iiLod2lQiZ5nx.png awesome that's a definite plus to (flagship) a3 i guess :) cheers -- rncbc aka Rui Nuno Capela rn...@rncbc.org ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] ALAC codec being added to libsndfile
Georg Holzmann wrote: Hallo! The only real problem I've had doing it is finding time to work on it. Fortunately I am pretty sure I will find time to work on this between xmas and new year. Thanks for the answer! If you need any testing or something else let me know! Hi Georg, Support for 16 bit ALAC is in Git at: https://github.com/erikd/libsndfile Support for other bit widths will be added in the near future once I know the 16 bit stuff is working. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [ANN] Qtractor 0.5.4 - Echo Victor shouts out!
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 i've been using in a
couple of projects [1] and oscpack [2]. both c++ though ...
OSCPack uses the stream-style abuse syntax, arguably (though not
really) the most awful thing about C++.
OSCPP looks pretty good though. Basically a C++ey version of what I was
talking about. Thanks for the pointers.
The require a size before constructing a message thing sucks for
certain cases of generic construction, however this might only be really
much of an issue for bundles which don't have that problem, so maybe
it's not such a big deal.
I have been idly wondering if a round-trip OSC=Atom bridge would be
possible. Atoms are essentially primitives (int, float, string, etc)
with a few simple collections, all POD (vector, dictionary). You can
think of it as sort of a JSONish approach, but low-level rather than
text.
I wonder how one would express a dictionary in OSC?
Assuming for the moment embracing and extending types is fine, there is
one easy cop-out solution, make a type-tagged-blob type, the same as the
normal one except it starts with a type int, but that's pretty opaque.
Maybe something like [] for arrays? {kvkv...}, e.g.
/foo/adict {sssi} name David id 42
=
{ name: David
id:42 }
-dr
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
