2 Jul
2011
2 Jul
'11
8:09 p.m.
On Sat, Jul 02, 2011 at 12:07:33PM +0200, rosea grammostola wrote:
On 07/02/2011 11:50 AM, rosea grammostola wrote:
a jack session client is not supposed to do any connections itself.
if a flag to disable it already exist, just include this flag in the
jack-session reply.
--
torben Hohn
On 07/02/2011 11:28 AM, rosea grammostola wrote:
Just a note. AFAIK applications which make connections automatically
with JACK are problematic for JackSession (also for Ladish iirc).
It isn't bad to have JACK autoconnect in a application (could be
handy), but there should be an option to disable it. Like it's
possible in PHASEX and also in StretchPlayer (svn) for example. On 07/02/2011 11:06 AM, rosea grammostola wrote:
>On 07/02/2011 12:52 AM, Emanuel Rumpf wrote:
>>2011/7/1 rosea grammostola<rosea.grammostola(a)gmail.com>om>:
>>>Hmm PHASEX deserves the same kind of love Zynaddsubfx gets
>>>these days via
>>>Yoshimi imho. It's one of the few quality synths on Linux.
>>>Maybe a generous
>>>hacker will provide a patch for JS support in PHASEX :)
>>>
>>Hi
>>Following your call, rosea, I added JackSession support to phasex !
>>The concept is still very new to me, but the result is
>>promising at least.
>Thanks a lot man!
>>It currently doesn't restore the connections made,
>>not sure why, maybe I'm doing anything wrong with the uuid ??
>I am sure Torben can help you with that.
It seems to work good here. You have to disable JACK autoconnect
in PHASEX and then the connections seems to work.