Re: [LAD] PHASEX (jacksession)

On 07/02/2011 07:25 PM, Emanuel Rumpf wrote:
> 2011/7/2 rosea grammostola<rosea.grammostola@email-addr-hidden>:
>> It seems to work good here. You have to disable JACK autoconnect in PHASEX
>> and then the connections seems to work.
>>
> Here they don't.
> And phasex requires much time to start.
Tested with Phasex and jack-rack (jackd1). Connections seems to be
restored here (all though at one occasion I used the 'recent' option in
qjackctl - session, and the connections didn't restore, another test
with 'recent' seems to work though).

The problem with a2jmidid I reported a while ago, was because qjackctl
doesn't support infra clients atm I think.

Regards,
\r

> How does jack-session know, when an application is ready for creating
> connections ?
>
> Suggestions:
> For larger gui-intense applications (which take time to start),
> SaveAndQuit should rather be SaveAndClose(current Documents).
> The some for single-instance applications.
> Else, it may take too much time restarting a whole setup.
>
> jack_session_reply( client, ev );
> could additionally inform jack, whether it is using single instance mode.
> ev->app_in_single_instance_mode = true;
>
> and provide a method to load patches, without closing
> the application:
> int my_load_setup( void* data, void* event );
> ev->load_setup = my_load_setup;
>
> This way, jack-session would be able to distinguish, whether
> to call ev->load_setup() or start the app with ev->command_line
> This load command would tell single_inst. apps to load a document
> and start multi_inst. apps with the path.
>
> An additional close_session command would be good (in qjackctl).
> This would close the documents of single_instance applications
> and quit multi_instance applications (but not jackd and pulse and patchage).
>
>

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Thu Jul 7 12:15:03 2011