Used-and-removed VSTs left in session file?

[nicenoise]

If you put a VST in a rack, play around with it, then remove it some time later, are some traces of it left in the .MuSession file? I ask because when I upgraded my M2.64 session files and loaded them in M3, M3 complained about not finding most of the VSTs I'd used (due to M3 Free only supporting 8 VSTs and me having a few dozen installed in M2.64), but the number it complained about was far greater than the number I ended up using. It looked like the names of all the VSTs I'd experimented with while composing the tracks even though I'd removed most of them.

If so, wouldn't session files get unecessarily large or unstable if you load/unload lots of VSTs? Is there a way of cleaning/purging a session file?

[liquidsound]

You probably used "Pull out of Rack" instead of replace/Delete them.
Pulling, in version prior to v3, removes them from the rack but they still in the Modular Plug-in Area and part of the session file.

[nicenoise]

You probably used "Pull out of Rack" instead of replace/Delete them.
Pulling, in version prior to v3, removes them from the rack but they still in the Modular Plug-in Area and part of the session file.

Yes, that's what I did - thanks for that.

In general, how do you get to know this stuff? Specifically, how did you get to know that?

"pull" only exists once in the docs and once on mutools.com, both times referring to something else. Is there a secret manual beyond the docs on the Web site or are people here just experienced enough to work this sort of thing out?

[MuTools]

No, there is no 'secret' docs.

All the available docs/tutorials are here: http://www.mutools.com/support.html

This forum is also very helpful in sorting things out

I agree the docs are basic, and they'll always be updated where necessary. But it's not the intention to doc every single possibility with MU.LAB as that would be a too big job. At the contrary: I would rather invest time in making the app more simple than making the docs more complex

Anyway be welcome with your questions.

[nicenoise]

No, there is no 'secret' docs.

All the available docs/tutorials are here: http://www.mutools.com/support.html

This forum is also very helpful in sorting things out

I agree the docs are basic, and they'll always be updated where necessary. But it's not the intention to doc every single possibility with MU.LAB as that would be a too big job. At the contrary: I would rather invest time in making the app more simple than making the docs more complex

Anyway be welcome with your questions.

I'll try not to embarass myself out of asking questions on here then I'd be happy to write a bit of a tutorial or help out with the docs at some point if time allows and I get up the learning curve.

What about setting up a wiki? That works really well for some programs I use.

[liquidsound]

Hi nicenoise,
No secret manual but like you did. I ask questions when I can't find them in the manual.
I don't read manuals because I like hands-on approach but Mu.LAB manual is short enough for me to dig in and the rest is by this amazing forum.

The Wiki is a great idea but some one must begin the proces because Jo is busy creating/updating/answering/dealing/accommodating/kicking a*s... etc.

[MuTools]

Yes, the wiki is a great idea!

I have no experience with setting it up.

Someone experience with it?

We can use mutools.com to host it, no problem, it's just about the practical steps to set it up.