Kapture doesn't work with very large sets

[lalo]

Hi all,
i've just started incorporating Kapture in my very big liveset.
It has a lot of grouped tracks and almost 50 devices / vst / M4L.
A lot of midi and key mapped parameters.
Kapture shows only the first track in its list?
Tried with smaller livesets and Kapture works as it should.
There are limitation for Kapture?
thanks

[unguitar]

did you ever got a reply to your question or discovered the answer?

[[email protected]]

I have been having the same issues. It takes over 10 minutes to analyses the api in Live, to grab all the information for your session when you first load it. If it does not give you a complete list of all your tracks, (like I was getting), then it's a track name issue. Every track needs a unique name. No two tracks or groups can have the same name. This fucks up Kapture. If you rename every track that has a duplicate name, then reload Kapture, it will work. As I mentioned above. It will take a long time to first grab the api info for a very large session. Once it is done, it will work fine.

One thing to look out for though. This should be done only when you live setup and session is finalized. If you continue to add tracks, or other songs, Kapture needs to update its app list, each time you add a track. This is so fucking slow and annoying.. If you add Kapture, once you are done it will be much quicker. It is a pain having to create all the snapshots again, but it's the quickest way to sort it all out. I as it then grab a coffee and take a break. I would also not bother renaming snapshots. It's one extra hassle you don't need.

Good luck.

Bazz