On Thu, Sep 07, 2006 at 05:56:53PM -0400, Lee Revell wrote:
> On Wed, 2006-09-06 at 18:55 +0200, Florian Schmidt wrote:
> > On Wednesday 06 September 2006 16:30, nescivi wrote:
> > > On Wednesday 06 September 2006 16:25, Alfons Adriaensen wrote:
> > > > Any chance of this ever being supported in Li
On Sat, May 06, 2006 at 10:13:42AM -0400, Lee Revell wrote:
> Same as the existing CLI tools - it would start an RT thread that polls
> on the RTC, then tell the user to generate some load (switch windows, do
> a find /, pingflood the default gateway, whatever), then report back the
> maximum laten
On Thu, Apr 27, 2006 at 08:00:36AM -0500, grae wrote:
> Agreed here, I vote to keep Ladspa. Change the acronym meaning or
> forget it entirely if desired. Lad'spa is easy to say and we all know
> what it is. :)
Yep, ladspa is just embedded in my brain. Change the 's' to super (as in
meta) if you
Hi Julien,
Protocol wise, it would be interesting to just use the X protocol.
i.e. create an X server that writes to the console. This would work
for any gui application, and you could ignore "uninteresting" graphics
stuff.
Not sure how to deal with the mouse in such an environment.
ncurses would
liboscqs is a library to provide a Query System and Service Discovery for
applications using the Open Sound Control (OSC) protocol [1]. The initial
proposal for the OSC Query System was provided by Andrew W. Schmeder and
Matthew Wright in July 2004 [2]. The next paragraph has their abstract:
A Qu
Plus not all machines have a physical RTC chip.
If you want periodic interrupt emulation on those you need a patch [1],
but that just generates a software interrupt. That would suffer from a
change in HZ value AFAIK.
--
Martin
[1] http://www.mph.eclipse.co.uk/pub/linux/patches/2.6.8/genrtc.c.pat
far off I think.
--
Martin
---
30 years from now GNU/Linux will be as redundant a term as UNIX/MERT is
today. - Martin Habets
---
On Mon, Jul 11, 200
On Sat, Jun 18, 2005 at 02:34:46AM +0200, Christoph Eckert wrote:
>
> > I think we should (and can) keep the desktop and 'pro'
> > worlds separate.
>
> I do not agree :) . We're in the free software world, so
> there's no need to tell the non-pro-audio-users "use anything
> else".
I think we c
o run at higher priority.
If that does not work, try to measure where the problem is. Could be the
program is not coded optimally, the network is too busy, or the kernel
network driver introduces a delay.
Greetins,
Martin
-------
30 years from now GNU/Linux will be as redundant a term as UNIX/MERT is
today. - Martin Habets
---
I'm looking for someone going to LAC from Zurich (or travelling through it),
who can pick up a computer for me there and meet me at the LAC.
I'll be coming from Schotland myself, and want to use it for ALSA testing
among other things.
A bit a of a strange passenger I know. I promise it won't need
I'm looking for someone going to LAC from Zurich (or travelling through it),
who can pick up a computer for me there and meet me at the LAC.
I'll be coming from Schotland myself, and want to use it for ALSA testing
among other things.
A bit a of a strange passenger I know. I promise it won't need
On Wed, Apr 06, 2005 at 11:14:03AM -0400, Dave Robillard wrote:
> > > Basically we just need a lo_discover(client_id_string) method that
> > > allows figuring out what clients are out there (optionally, with the
> > > given name). I started to implement this but it got pushed down the
> > > priori
On Tue, Apr 05, 2005 at 11:18:12AM -0400, Dave Robillard wrote:
> > On Tue, Mar 01, 2005 at 01:27:38PM -0500, Dave Robillard wrote:
> > > Implementation wise, the scheme goes something like this:
> > >
> > > - client broadcasts it's existance via rendezvous
> > > - patching server replies to clien
On Thu, Mar 31, 2005 at 03:07:28PM +0100, Steve Harris wrote:
> > Am working on a library for this stuff + service discovery on top of
> > liblo. Sub-path listing is the only thing I haven't coded up yet. Still
> > a good deal of testing to do.
>
> You might want to get in touch with Dave robillar
On Mon, Mar 28, 2005 at 12:30:30AM +0100, Steve Harris wrote:
> That sounds good, its just an oversight on my part, the patch makes
> perfect sense to me. I'l apply it when I get the chance
thanks.
> FWIW, I'm planning to add API support for the documentation etc. features
> at some point, I do t
Hi Steve,
Was testing this scenario today, which may look familiar to you:
- I created a server with some methods: '/ping/documentation' and
'/osc-schema/documentation', both of which use the same handler 'doc'.
- I send query '/*/documentation' to the server.
- 'doc' got called twice with path '
On Wed, Mar 02, 2005 at 10:47:31AM -0500, Dave Robillard wrote:
> > > The "patching server" (called that from hereon for lack of a better
> > > name) has simple commands like /set_destination
> > > , /remove_destination , etc. You can imagine a GUI
> > > jack-patch-bay like client for it.
> >
> >
On Tue, Mar 01, 2005 at 08:48:13PM +, Steve Harris wrote:
> On Tue, Mar 01, 2005 at 02:15:46 +0000, Martin Habets wrote:
> > On Mon, Feb 28, 2005 at 09:35:34PM +, Steve Harris wrote:
> > > There is a proposed specification for discovery of OSC services that was
> >
On Tue, Mar 01, 2005 at 01:27:38PM -0500, Dave Robillard wrote:
> So basically my goals are to make OSC using liblo as nice as audio using
> jack, as far as "ports" and "connections" (in jack-ese) go, with as
> little burden on clients as possible, and allowing user patching, etc.
It seems our goa
On Mon, Feb 28, 2005 at 09:35:34PM +, Steve Harris wrote:
> There is a proposed specification for discovery of OSC services that was
> presented at hte OSC conference, I intend to support it in liblo at some
> point in the future.
Do you have a link to this spec? Was it the one based on zeroco
88.html
[4] http://www.cnmat.berkeley.edu/OpenSoundControl/
---
30 years from now GNU/Linux will be as redundant a term as UNIX/MERT is
today. - Martin Habets
---
#2 removes this info.
It seems totally useless info to me anyway.
Hopefully you find these usefull. Below is some before and after data.
Thanks,
Martin Habets
---
Before:
Rule file not modified: '/etc/jack.plumbing'
On Thu, Sep 30, 2004 at 12:16:15AM +0200, Jens M Andreasen wrote:
> > No details about the protocols used. Gigabit ethernet is recommended for
> > "the best performance".
> >
> Mmm ... It says:
>
> The protocol is independent of the network hardware, thanks
> to the use of the stand
On Wed, Jun 09, 2004 at 07:18:57PM -0400, Dave Robillard wrote:
> On Wed, 2004-06-09 at 17:56, Arnold Krille wrote:
> > Still the question is: What toolkit to use for a
> > standard-LAD-Gui-elements-set? Or just define the graphics and the handling
> > and then let everyone implement it in his/he
24 matches
Mail list logo
