Large projects in ladish

[Excds]

In my ongoing project with setting up a good working environment I wanted to have a default ladish project I can clone to quickly get started. In the template project I added a bunch of apps, such as:
- qsampler / linuxsampler
- amsynt
- zynaddsubfx
- jack-rack
- qmidiarp
- rakarrack
- qtractor (with a bunch of tracks also containing VST:s)

My problem is that this default project gets "too heavy" to load. It seems that ladish tries to start all the apps simultaneously, which leads to everything slowing down and then for ladish to become unresponsive. I can see that the process jmcore goes wild in cpu usage... The only way to rescue the situation is to run the "force restart" option in Cadence. :-/

Is there a way in ladish project management to tell applications to be loaded sequentially? Or adding some delay?

Also, in the end I want to have a bunch of projects that I can just tell ladish to load and then to "press play on tape". But in more than 50% of the time, some apps fail to start properly or ladish just crashes.

Any suggestions?

[Excds]

Even if it is due to a buggy application, it would make sense to be able to do a workaround for that buggy application. But I don't think it is because of that. If it was, wouldn't the whole setting up of the project fail?

[studio32]

My concern with ladish is that it's to complex. It support all kind of sophisticated features and all the session api's. This strength can turn into a weakness in cases I think. That's why NSM feels more clean and straightforward to me. I can't imagine that NSM can't load a session. If one client misbehaves that client it stopped maybe (but still in the session), but it's not that an whole session doesn't load.
But anyway, it could be just a little bug in ladish or something...

Loading all apps at once shouldn't be a problem I think normally, I could be wrong. Maybe Jack(dbus) has a problem with it? You can try it with a script and load a whole bunch of software at once

Btw, I'm not advocating against Ladish. I think there is room for both session api's, each for different setups.

[Excds]

So, how should I go about working around this then? Increase the jack timeout to seconds?

[studio32]

An advantage here of NSM might be that it works independently of JACK.

So, how should I go about working around this then? Increase the jack timeout to seconds?

You might try to lower the load in JACK by putting the Frames/ Period up to 1024 or something. And yep probably timeout to 1000 or even 2000.

[studio32]

A JACK crash doesn't ruin your session in nsm. It ruins your current workflow temporarily.

[nedko]

In my ongoing project with setting up a good working environment I wanted to have a default ladish project I can clone to quickly get started. In the template project I added a bunch of apps, such as:
- qsampler / linuxsampler
- amsynt
- zynaddsubfx
- jack-rack
- qmidiarp
- rakarrack
- qtractor (with a bunch of tracks also containing VST:s)

My problem is that this default project gets "too heavy" to load. It seems that ladish tries to start all the apps simultaneously, which leads to everything slowing down and then for ladish to become unresponsive. I can see that the process jmcore goes wild in cpu usage... The only way to rescue the situation is to run the "force restart" option in Cadence. :-/

Is there a way in ladish project management to tell applications to be loaded sequentially? Or adding some delay?

Also, in the end I want to have a bunch of projects that I can just tell ladish to load and then to "press play on tape". But in more than 50% of the time, some apps fail to start properly or ladish just crashes.

Any suggestions?

Currently (ladish-1) its not possible to tell ladish daemon to start apps sequentially nor with a delay. The best suggestion regarding crashes I can give is to help with fixing crashing software. Most developers will be happier if their software doesn't crash. If you can't code, you can help with testing experimental fixes. Its not rare when software misbehaviour cannot be reproduced on developer machines.