MU.LAB crashes when I delete a module in a MUX

[johnjaypl]

I get a "pink screen" (maybe it's red) crash when I try to delete a VST (midiProbability) from a MUX. The pink screen mentions a serious error in MULAB or a vst

The mux only uses vsts from a free midi package that I learned about at KVR and a minimogue. I simplified my session quite a bit but I hate to take it down further because I might change the behavior. It happened about 4 times in a row, it seems very repeatable.

Also, one of the times that MU.LAB crashed it lost my license info, it lost it's VST pointers too. It was like starting from scrath.

Is this something you're interested in debugging? I open the session, open the mux, try to deleate midiProbability(2) and get pink screen.

John

[MuTools]

Is this something you're interested in debugging?

Sounds like a very cynical question John. Do you mean it like that?

I open the session, open the mux, try to deleate midiProbability(2) and get pink screen.

Yes, please email me the musession. Thanks!

[johnjaypl]

Is this something you're interested in debugging?

Sounds like a very cynical question John. Do you mean it like that?

Not at all. It's just that the pink screen warns that it could be a MU.LAB or VST problem and you're sometimes not too interested in debugging VST problems.

I open the session, open the mux, try to deleate midiProbability(2) and get pink screen.

Yes, please email me the musession. Thanks![/quote]

I'll send it to you. I was just checking to see if I need to send you anything in addition to the session and I noticed I had another MUX in the rack called "MY RING OSC.MUX". I tried to delete that to simplify things further and I also get a pink screen when I delete that from the rack. It happened twice in a row so that might be as good as the first problem to debug.

John

[MuTools]

Is this something you're interested in debugging?

Sounds like a very cynical question John. Do you mean it like that?

Not at all. It's just that the pink screen warns that it could be a MU.LAB or VST problem and you're sometimes not too interested in debugging VST problems.

Just to avoid any confusion towards you or anyone else, i'll repeat what i've said multiple times:

I indeed try to avoid wasting time with examining every little (buggy?) VST
because there are a lot of buggy VSTs out there, if you're an experienced VST plugin user, you should know this, else believe me.

When i try to avoid wasting time it's not because i don't care, at the contrary, it's because i also do care about the many items on the MUTOOLS/MU.LAB whishlist.

It's about assessing the problem, whether it's a problem on MU.LAB's side or on the VST plugin's side.

That's why i ask to narrow things down as much as possible so we can get a better view on the source of a problem.

If you can find overlaps in the VST plugin issues, i mean if the same problem is there with plugin X Y and Z (of different manufacturers), then chance is growing that it's a MU.LAB issue, and i've always been and will always be interested in researching that.

I open the session, open the mux, try to deleate midiProbability(2) and get pink screen.

Yes, please email me the musession. Thanks!

I'll send it to you.

Well received, thanks.

I've narrowed things further down so i only have 1 rack with the mux and the 2 "MidiProbability" plugs. Whenever i try to delete one of them i also get a crash. The debugger tells me the crash occurs inside the "MidiProbability" plug. I've contacted the developer of "MidiProbability" in order to sort this out. Waiting for his/her reply.

[johnjaypl]

Well received, thanks.

I've narrowed things further down so i only have 1 rack with the mux and the 2 "MidiProbability" plugs. Whenever i try to delete one of them i also get a crash. The debugger tells me the crash occurs inside the "MidiProbability" plug. I've contacted the developer of "MidiProbability" in order to sort this out. Waiting for his/her reply.

Just out of curiosity, does the debugger also tell you that crash occurs inside "MidiProbability" when you delete "My Ring Osc.Mux"?

John

[MuTools]

I didn't get a crash when deleting "My Ring Osc.Mux".

But as i got a crash on deleting midiProbability, i thought it's best to research that first, then once that problem is fully resolved, then we can focus on another prob. Otherwise we might suffer from problem interference.

Note that when i say that the debugger points to a crash in midiProbability, i don't say/conclude it's midiProbability which makes the very fault. I don't take conclusion until the reason is clear. Just wanted to add this to avoid confusion.

[MuTools]

Extra problem regarding the midiProbability problem is that the crash does not occur always, i've the impression it's system dependent.

I'm communicating with the developer of midiProbability about this.

Hopefully it crashes on his system and he'll be able to narrow it down more.

[insertpizhere]

i don't know exactly what the problem was, but it probably was due to my code... i got it to crash with the uploaded version, in other hosts as well, but not with the latest compiled version on my hard drive. so, hopefully i fixed it already.

please try this one:
http://thepiz.org/pizmidi/midiProbability_test.zip

[MuTools]

Thanks insertpizhere!