I can't open my session!!!

[dakkra]

While working on a track of mine I had an error. While trying to save my session Mulab gave me an error saying "Could not save data for Kv-ReverbCM" (or close to this) and then crashed. I tried to re-open my session but it loads and then breaks. Help!!!

[dakkra]

To give more detail:

Most of my racks and their related plugins have disappeared. The tracks stayed but are un-assigned. No audio playback happens when I play.

[MuTools]

First thing to do: Rescue your backup session!

More in detail: Every time MuLab saves a session it renames the previously saved .MuSession as .MuSession.Backup. Make sure you make an extra copy of that file and then rename that copy back to .MuSession. Then try to load that session. Hopefully you save regularly so that you only miss your very last edits.

Also check for any "...#Autosaved.MuSession" in your MuLab folder. Also backup all of them so you can carefully check whether any of them is rescueing you.

About that crashed MuSession: Was the alert saying "Exception while saving VST data for Kv-ReverbCM"?

[dakkra]

The Backup Session was corrupted too and there are no auto saves. I guess I'm out of luck

Yes that was the alert message I received.



Due to weird activity in Mulab recently I'm going to be formatting my drive and re-installing everything. I'm thinking some of these issues may not be Mulab. I've had MIDI messaged not send form my controllers. I've had crashes every other hour. This isn't normal Mulab behavior.

[MuTools]

The Backup Session was corrupted too

So you did another save after the crash save?

Due to weird activity in Mulab recently

Which weird activities?

I'm thinking some of these issues may not be Mulab. I've had MIDI messaged not send form my controllers. I've had crashes every other hour. This isn't normal Mulab behavior.

I'm quite intensively using MuLab myself too and all seems quite stable here. I also did't receive recent crash reports that point to MuLab. I regard MuLab 5.2.16 as stable unless the contrary is clearly indicated. Please take into account that VST plugins can crash the host too. In the above case it looks like the VST crashed. Does the plugin developer know about such case?

[dakkra]

I don't know if I did or didn't save after the crash. I kinda ran through the panels that popped up (rather foolish of me to do so).

The weird activity being the crashes and lack of MIDI signal reception etc...

The developer has been in-active for a while. The plugin has never given me any trouble before though. It wasn't an update that caused the issue because I've never had an update for it.

The only plugin I have that I know causes issues is Tone2 Firbird. It stops working and then Mulab crashes. I solve this with constant saving but it's never good when my save file is corrupted.

I'm pretty sure it's my system. I've installed/uninstalled plenty of software on this machine so it's very likely that bad data may be the cause of these problems.