linuxaudio.org

--20cf307f33cc25068804a58d0826

Content-Type: text/plain; charset=UTF-8
On Sun, Jun 12, 2011 at 3:23 PM, Paul Davis wrote:
> On Sun, Jun 12, 2011 at 12:48 PM, Aaron Krister Johnson

quoted text
>  wrote:

> > Hi Paul-

> > I'm not sure if what you're saying matters, since the buffer settings,

> etc.

> > were the same between jack and alsa settings in the PianoTeq setup

> > dialogs....unless I'm missing something, the /proc directory info you are

> > asking me to compare with jackd settings verify that they were the same.

>

> oops, i somehow missed this in the thread. the settings cannot be the

> same because PianoTeq doesn't control the JACK settings. just run the

> command i mentioned and that will let you see how ALSA gets configured

> by PT and then we can compare it with the way JACK does it.

>

>

PianoTeq doesn't configure things when jack is running. It just detects and

runs with what jack's setting are. However, the *user* configures things

when Alsa is running. Things like sr, buffer sizes, and periods. I was

comparing apples to apples when I announced my results: for instance, if I

set PT to run Alsa @ 256 samples and 2 buffers per period, I also ran jackd

with those setting before starting PT.

I'd love your insight into what could have been going on; things seem quite

a bit better with jack2 (jackdmp-1.9.7) on my system---and, like I said, all

of a sudden weird MIDI stuff that was happening in fluidsynth is now solved,

too....I think the fluidsynth thing was actually related to a new codebase

in FS since 1.1.2 where they merged the scheduling of MIDI and audio being

handled by the same thread, IIRC...could be that the way jack1 in the

version I was running was structured caused some unforeseen voodoo.
> P.S. Did you get my email ever about jackctl.py? Not the one in the jack

quoted text
> > source tree, but my CL utility of the same name that I wrote?

>

> yeah, its in the backlog at present. its functionality overlaps quite

> a lot of other stuff.

>

Hmmm....like what, Qjackctl? That's a GUI, this is CL. And the CL tools that

currently come with jack do the trick, but with needless typing and lack of

ease---that's what my-front end solves. What other CL tools for making jack

connections in an *easy* way are there?
AKJ
--

Aaron Krister Johnson

http://www.akjmusic.com

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

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

Content-Transfer-Encoding: quoted-printable
On Sun, Jun 12, 2011 at 3:23 PM, Paul Davis <paul@linuxaudiosystems.com> wrote:

On Sun, Jun 12, 2011 at 12:48 PM, Aaron Krister Johnson

<aaron@akjmusic.com> wrote:=
> Hi Paul-

quoted text
> I'm not sure if what you're saying matters, since the buffer s=

ettings, etc.

quoted text
> were the same between jack and alsa settings in the PianoTeq setup

> dialogs....unless I'm missing something, the /proc directory info =

you are

quoted text
> asking me to compare with jackd settings verify that they were the sam=

e.

oops, i somehow missed this in the thread. the settings cannot be the=
same because PianoTeq doesn't control the JACK settings. just run the

command i mentioned and that will let you see how ALSA gets configured

by PT and then we can compare it with the way JACK does it.

PianoTeq doesn=

't configure things when jack is running. It just detects and runs with=

 what jack's setting are. However, the *user* configures things when Al=

sa is running. Things like sr, buffer sizes, and periods. I was comparing a=

pples to apples when I announced my results: for instance, if I set PT to r=

un Alsa @ 256 samples and 2 buffers per period, I also ran jackd with those=

 setting before starting PT.

I'd love your insight into what could have been goi=

ng on; things seem quite a bit better with jack2 (jackdmp-1.9.7) on my syst=

em---and, like I said, all of a sudden weird MIDI stuff that was happening =

in fluidsynth is now solved, too....I think the fluidsynth thing was actual=

ly related to a new codebase in FS since 1.1.2 where they merged the schedu=

ling of MIDI and audio being handled by the same thread, IIRC...could be th=

at the way jack1 in the version I was running was structured caused some un=

foreseen voodoo.
> P.S. Did you get my email ever about jackctl.py? Not the one in the ja=

ck

quoted text
> source tree, but my CL utility of the same name that I wrote?

yeah, its in the backlog at present. its functionality overlaps quite=
a lot of other stuff.Hm=

mm....like what, Qjackctl? That's a GUI, this is CL. And the CL tools t=

hat currently come with jack do the trick, but with needless typing and lac=

k of ease---that's what my-front end solves. What other CL tools for ma=

king jack connections in an *easy* way are there?

AKJ=C2=A0-- Aaron Krister Johnson=

http://www.akjmusic.c=

omhttp://www.=

untwelve.org
--20cf307f33cc25068804a58d0826--