Rui Nuno Capela wrote:
> Peter Lutek wrote:
>
>> Michael T D Nelson wrote:
>>
>>> Paul Davis wrote:
>>>
>>>> On Thu, 2005-11-10 at 14:50 +0000, Michael T D Nelson wrote:
>>>>
>>>>> Paul Davis wrote:
>>>>
>>>>
>>>>
>>>
>>>>>> go to the qjackctl setup dialog and make sure that the command to
>>>>>> start
>>>>>> jack is "jackd" and not "jackstart". "jackstart" is purely for 2.4-
>>>>>> kernel based systems and should not be used on a 2.6-kernel based
>>>>>> system.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks for the prompt reply, but it's set to "jackd" already.
>>>>
>>>>
>>>>
>>>>
>>>> well then something is very confused. your error messages included a
>>>> line about not being able to write to the jackstart sync pipe.
>>>>
>>>> did you install jackd as a normal CCRMA package?
>>>
>>>
>>>
>>>
>>> Yep. And it was working fine until a couple of weeks ago. I don't
>>> think I have done anything untoward.
>>>
>>> The only software which I compile from source is completely
>>> unrelated to audio (things like OpenVPN, mainly for work).
>>>
>>> I have just noticed a recent thread on this list (started by Carlos
>>> Pino) with a very similar sounding problem.
>>>
>> yes... i was in on that thread. i get the jackstart sync pipe error
>> message when starting jackd with qjackctl, however it does start fine
>> despite the error. when starting jackd with the same parameters, but
>> from the commandline, i do not get the jackstart sync pipe error
>> message. perhaps it's a qjackctl bug?
>>
>> -p
>
>
> Have you tried whether switching off standard output capture on
> qjackctl/setup/options makes any difference on that "jackstart sync
> pipe" issue?
hmm... seems to make it go away, but is that just because the error
message is no longer being echoed to the message window? when i start
qjackctl from a terminal window, i don't any messages in the terminal
about jack status anyway, so it's hard to tell.
-p
Received on Fri Nov 11 00:15:08 2005
This archive was generated by hypermail 2.1.8 : Fri Nov 11 2005 - 00:15:08 EET