On Sun, 2004-12-05 at 22:59 +0100, Tim Goetze wrote:
> [Juhana Sadeharju]
>
> >>From: Tim Goetze <[EMAIL PROTECTED]>
> >>
> >> m = l + r;
> >> l = dry * l + wet * reverb_l (m);
> >> r = dry * r + wet * reverb_r (m);
> >[ ... ]
> >>'True stereo' is, of course, marketing BS. You may argue that I
On Tue, 2004-12-07 at 18:24 -0500, Lee Revell wrote:
> On Tue, 2004-12-07 at 23:39 +0100, Jens M Andreasen wrote:
> > BTW: Anybody knows how to stop Evolution from inserting my email-adress
> > as a default auto-generated signature?
>
> Ugh, I hate this feature too. The default changed from 1.x t
On Tue, 2004-12-07 at 23:39 +0100, Jens M Andreasen wrote:
> BTW: Anybody knows how to stop Evolution from inserting my email-adress
> as a default auto-generated signature?
Ugh, I hate this feature too. The default changed from 1.x to 2.0.
Tools->Settings, click the account, edit, then on the I
Hi Peter,
>Does anything like this exist? If not, does some part of it exist?
>For instance, it would be extremely helpful to have a Python wrapper
>for ALSA structs such as snd_seq_event_t. Any thoughts would be
>appreciated.
I've worked on something that has many parts of what you are looking
f
On tis, 2004-12-07 at 16:49 -0500, Lee Revell wrote:
> On Tue, 2004-12-07 at 22:33 +0100, Jens M Andreasen wrote:
> > The mouse-down, mouse-dragged signals (and friends) fits within realtime
> > constraints. It is the 'do_running_fading_ink_repaint()' (or whatever)
> > that you need to keep low pri
Hi,
I've been thinking about building a simple MIDI router with Python
and ALSA. My main motivation is to (a) save, process, and write back
bulk data from my master keyboard, and (b) map control change events
from the keyboard to GUI events, but of course note events and such
should be handled as
On tis, 2004-12-07 at 22:32 +, vanDongen/Gilcher wrote:
...
...
> Or you need to add timestamping on incoming events with respect to the
> position of the audio-playback-pointer in the current period
> Then you delay them by the same amount in the next available process cycle.
> You increase
On Tue, 2004-12-07 at 22:33 +0100, Jens M Andreasen wrote:
> The mouse-down, mouse-dragged signals (and friends) fits within realtime
> constraints. It is the 'do_running_fading_ink_repaint()' (or whatever)
> that you need to keep low priority, albeit probably above Mozilla
> repainting some nasty
On tis, 2004-12-07 at 16:42 +0100, Artem Baguinski wrote:
...
...
> > MIDI buttons/sliders do not need to have any noticeable latency if the
> > MIDI-thread is run at the (near?) same priority as jack. Although the
> > thread has high priority, it is mostly idle and will consume next to no
> > CP
On Tuesday 07 December 2004 15:42, Artem Baguinski wrote:
> Suppose I have several various devices that control various aspects of
> sound generation / processing. they all send "handful of bytes" now
> and then and I want my JACK client to react immediately.
You do realize that you can't react
Hi all,
thanks to Martin Rumori, there is now a thread called
"Linux audio, ALSA and RME support"
on the RME forum.
Please do not hesitate to contribute!
The forum can be found here:
News server: news.x-networks.de
Forum: rme-audio.forum
In case you have troubles finding the right software
On Sun, Dec 05, 2004 at 04:11:19AM +0100, Marek Peteraj wrote:
> In case you haven't found the thread, feel free to start it.
done.
> We need to agree on the topic so that people can easily find it:
> "Linux audio, ALSA and RME support"
agreed.
bests,
martin
On Tue, 2004-12-07 at 20:34 +0100, Jens M Andreasen wrote:
> Jack has been distributed with Mandrake 10.1 without the realtime
> module. So it only runs as root by default here, and then still being
> severely disturbed by the underlying journaling filesystem.
We are trying to get the realtime LSM
On tis, 2004-12-07 at 12:06 -0600, Jack O'Quin wrote:
> Jens M Andreasen writes:
>
> > > Also I've figured that to lower the nice number I'll need root
> > > priviliges. After patching my kernel [ok, downloading a patched kernel
> > > ;-P] to be able jack and friends as my normal self?.. or does
Jens M Andreasen <[EMAIL PROTECTED]> writes:
> > Also I've figured that to lower the nice number I'll need root
> > priviliges. After patching my kernel [ok, downloading a patched kernel
> > ;-P] to be able jack and friends as my normal self?.. or does this
> > patch changes the situation?
>
> I
On tis, 2004-12-07 at 17:54 +0100, Artem Baguinski wrote:
...
...
> forget the gui, suppose i meant that MIDI button.
>
> JACK does everything to make sure the audio threads run uninterrupted
> to process that audio on time and deliver it to the audio hardware,
> right? but it doesn't make sure
On tis, 2004-12-07 at 17:14 +0100, Artem Baguinski wrote:
> Jens M Andreasen <[EMAIL PROTECTED]> writes:
>
> > So if you do:
> >
> > # nice -10 audioapp [audioapp-options]
bzzt .. You are so right!
# nice --10 audioapp [audioapp-options]
>
> i couldnt decipher man nice / info coreutils nice so
>i couldnt decipher man nice / info coreutils nice so i googled to find
>out [1]
good, because nice is irrelevant for anything with even vaguely
realtime requirements.
actually, this is problem is not quite as simple as some people have
made out. i can't offer a good working solution myself beca
"Jack O'Quin" <[EMAIL PROTECTED]> writes:
>> .. your audioapp should repaint itself before any less urgent
>> process (with normal or slightly high priority) gets a chance at the
>> CPU. JACK will still run at (near?) highest priority, so if your
>> audio-processing demands 90% CPU there will be n
Jens M Andreasen <[EMAIL PROTECTED]> writes:
> So if you do:
>
> # nice -10 audioapp [audioapp-options]
>
> .. your audioapp should repaint itself before any less urgent process
> (with normal or slightly high priority) gets a chance at the CPU. JACK
> will still run at (near?) highest priority, s
> On tis, 2004-12-07 at 13:07 +0100, Artem Baguinski wrote:
> > I'm a bit puzzled with this one thing about low latency and jack: real
> > time bits can't do IO, but don't you get latency between say me
> > pressing some button and sound doing click? there's no garanty the not
> > realtime part of
Jens M Andreasen <[EMAIL PROTECTED]> writes:
> On tis, 2004-12-07 at 13:07 +0100, Artem Baguinski wrote:
>> I'm a bit puzzled with this one thing about low latency and jack: real
>> time bits can't do IO, but don't you get latency between say me
>> pressing some button and sound doing click? there
On tis, 2004-12-07 at 13:07 +0100, Artem Baguinski wrote:
> I'm a bit puzzled with this one thing about low latency and jack: real
> time bits can't do IO, but don't you get latency between say me
> pressing some button and sound doing click? there's no garanty the not
> realtime part of the applic
I'm a bit puzzled with this one thing about low latency and jack: real
time bits can't do IO, but don't you get latency between say me
pressing some button and sound doing click? there's no garanty the not
realtime part of the application will run often enough to read the
input device, no?
just
24 matches
Mail list logo