linuxaudio.org

--20cf307f33cca2b15604a58687c2

Content-Type: text/plain; charset=UTF-8
Hi, I realized that this would be pertinent info this morning, thanks for

reminding me...
I'm on Arch Linux, and I used both kernels 2.6.33-rt and the standard

2.6.32-LTS (long-term support) with the same results....
It's Jack 0.118.0-2 and also 0.120.2-1 that were problematic for me. They

also caused weird behavior with fluidsynth-1.1.3--with my M-Audio KeyRig 49

USB keyboard, there were HUGE (.5 seconds!!!) midi delays.
I installed jack2-svn today and the fluidsynth issue is now gone. And,

although the PianoTeq xruns are much better, they are still slightly more

apparent than with Alsa alone.
I don't know what happened, but, being pragmatic, one has to just find

versions that work....yikes!
AKJ
On Sun, Jun 12, 2011 at 4:36 AM, rosea.grammostola <

rosea.grammostola@gmail.com> wrote:
Which Jack version? Which kernel? Which OS?

quoted text
> Using Pianoteq myself, runs like a charm, with JACK, but it asks for pretty

> some CPU...

> \r

> On 06/12/2011 09:40 AM, Aaron Krister Johnson wrote:

quoted text
>

>> Hi all--

>>

>> I'm wondering if anyone else has experienced this:

>>

>> I'm considering purchasing PianoTeq, but I wanted to try the demo. It

>> seems to work better with just the alsa driver than it does with jack, a

>> reversal of the usual situation.

>>

>> I tested this several times by playing fast glissandi on the default

>> piano preset. Each time, my little EEE-PC netbook under jack choked with

>> xruns and a brief silence while PianoTeq 'reset' itself, but Alsa alone

>> chugged away with no xruns unless there was an extreme amount of load....

>>

>> I'm wondering if anyone can comment on this. It seems odd, especially

>> since the jack developers claim jack adds no latency by itself to the

>> picture in any situation---so, do we have a situation where the code is

>> better written for the alsa driver than for jackd? It seems we do, in

>> this case....

>>

>

>

> _______________________________________________

> Linux-audio-user mailing list

> Linux-audio-user@lists.linuxaudio.org

> http://lists.linuxaudio.org/listinfo/linux-audio-user

>

--

Aaron Krister Johnson

http://www.akjmusic.com

http://www.untwelve.org
--20cf307f33cca2b15604a58687c2

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
Hi, I realized that this would be pertinent info this morning, thanks for r=

eminding me...I'm on Arch Linux, and I used both ke=

rnels 2.6.33-rt and the standard 2.6.32-LTS (long-term support) with the sa=

me results....

It's Jack=C2=A00.118.0-2 and also=C2=A00.120.2-1 th=

at were problematic for me. They also caused weird behavior with fluidsynth=

-1.1.3--with my M-Audio KeyRig 49 USB keyboard, there were HUGE (.5 seconds=

!!!) midi delays.

I installed jack2-svn today and the fluidsynth issue is=

 now gone. And, although the PianoTeq xruns are much better, they are still=

 slightly more apparent than with Alsa alone.I don&=

#39;t know what happened, but, being pragmatic, one has to just find versio=

ns that work....yikes!

AKJOn Sun, Ju=

n 12, 2011 at 4:36 AM, rosea.grammostola <rosea.grammostola@gmail.com> wrote:
Which Jack version? Which kernel? Which OS?Using Pianoteq myself, runs =

like a charm, with JACK, but it asks for pretty some CPU...\r=C2=

=A0

On 06/12/2011 09:40 AM, Aaron Krister Johnson wrote:
Hi all--
I'm wondering if anyone else has experienced this:
I'm considering purchasing PianoTeq, but I wanted to try the demo. It

seems to work better with just the alsa driver than it does with jack, a

reversal of the usual situation.
I tested this several times by playing fast glissandi on the default

piano preset. Each time, my little EEE-PC netbook under jack choked with

xruns and a brief silence while PianoTeq 'reset' itself, but Alsa a=

lone

chugged away with no xruns unless there was an extreme amount of load....
I'm wondering if anyone can comment on this. It seems odd, especially

since the jack developers claim jack adds no latency by itself to the

picture in any situation---so, do we have a situation where the code is

better written for the alsa driver than for jackd? It seems we do, in

this case....
_______________________________________________

Linux-audio-user mailing list

=

Linux-audio-user@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-user

-- Aaron Krist=

er Johnsonhttp://=

www.akjmusic.comhttp://www.untwelve.org
--20cf307f33cca2b15604a58687c2--