<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#333333" text="#FFFFFF">
<div class="moz-cite-prefix">On 01/17/2017 04:35 AM, john gibby
wrote:<br>
</div>
<blockquote
cite="mid:CAPHHX=MU6ED493gz8UX=qZqZCs3hGfxAE0Lxqmba-10pVU7e2w@mail.gmail.com"
type="cite">
<div dir="auto">Sound is via ALC 1150 chipset; I don't think
that's the problem. When I go directly from pianoteq to alsa
there's no problem; can use even a 64 sample buffer. Maybe I
need a little help in killing the default jack server and
starting it back (with dummy back end ) using direct jackd
command line instead of using qjackctl? Then I think it may
keep my specified buffer size. Am Linux newby, takes a little
work! :)</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Jan 17, 2017 4:23 AM, "Jeanette C."
<<a moz-do-not-send="true" href="mailto:julien@mail.upb.de">julien@mail.upb.de</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Jan 17
2017, john gibby has written:<br>
...<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
When qjackctl brings up<br>
the jack server, the buffer size gets overridden to
1024; I see the message<br>
in the log. What am I doing wrong? Is Jack the wrong
approach, when it is<br>
ecasound, not jack, that writes to alsa?<br>
</blockquote>
</blockquote>
Hi John,<br>
it appears that your soundcard is the problem. I've only
started JACK on<br>
the commandline or through a dedicated start script, not
using qjackctl<br>
or other JACK-supplied tools. But if you give a buffersize
to JACK it<br>
will honour that buffersize, if the soundcard can stand it.
I haven't<br>
seen an application before that couldn't honour JACK's
buffersize,<br>
whatever it is. Especially Ecasound can certainly go down to
64 samples.<br>
<br>
What soundcard do you have? Have you tried starting JACK for
your<br>
soundcard on the commandline and see what happens?<br>
jackd --timeout 4500 -R -d alsa -d hw:0 -p 128<br>
Assuming that your soundcard is the first one (hw:0).<br>
<br>
I have no experience with Pianoteq, but since it is meant as
a realtime<br>
app, it should make sure that its sounds are played back
without delay<br>
or with minimal delay. 128 and even 64 samples aren't that
uncommon.<br>
...<br>
<br>
Best wishes,<br>
<br>
Jeanette<br>
<br>
--------<br>
When you need someone, you just turn around and I will be
there <3<br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Linux-audio-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxaudio.org/listinfo/linux-audio-user">http://lists.linuxaudio.org/listinfo/linux-audio-user</a>
</pre>
</blockquote>
<br>
<p>maybe a jackdbus thing? if you're using jack2, what does
"jack_control status" show?</p>
<p>if it says "started", do "jack_control stop" then try your jack
command/qjackctl.</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">
--
<a class="moz-txt-link-abbreviated" href="http://www.the-temp-agency.com/lollipop-factory">www.the-temp-agency.com/lollipop-factory</a></pre>
</body>
</html>