On Sun, Jun 12, 2011 at 3:23 PM, Paul Davis <span dir="ltr"><<a href="mailto:paul@linuxaudiosystems.com">paul@linuxaudiosystems.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Jun 12, 2011 at 12:48 PM, Aaron Krister Johnson<br>
<<a href="mailto:aaron@akjmusic.com">aaron@akjmusic.com</a>> wrote:<br>
> Hi Paul-<br>
> I'm not sure if what you're saying matters, since the buffer settings, etc.<br>
> were the same between jack and alsa settings in the PianoTeq setup<br>
> dialogs....unless I'm missing something, the /proc directory info you are<br>
> asking me to compare with jackd settings verify that they were the same.<br>
<br>
</div>oops, i somehow missed this in the thread. the settings cannot be the<br>
same because PianoTeq doesn't control the JACK settings. just run the<br>
command i mentioned and that will let you see how ALSA gets configured<br>
by PT and then we can compare it with the way JACK does it.<br>
<div class="im"><br></div></blockquote><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> P.S. Did you get my email ever about jackctl.py? Not the one in the jack<br>
> source tree, but my CL utility of the same name that I wrote?<br>
<br>
</div>yeah, its in the backlog at present. its functionality overlaps quite<br>
a lot of other stuff.<br></blockquote><div><br></div><div><br></div><div>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?</div>
<div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>AKJ </div></div><br>-- <br>Aaron Krister Johnson<br><a href="http://www.akjmusic.com" target="_blank">http://www.akjmusic.com</a><br><a href="http://www.untwelve.org" target="_blank">http://www.untwelve.org</a><br>
<br>