bug causing project lock down

[yul]

Hello! I love Mulab and am starting to widen my use of the modular aspect.

I just stumbled on the following bug in M6.5 when I used the note key splitter on multiple rack destinations.

This had caused an error User Thread Wait Timeout @ (REP12) and could not use the project anymore.

I tried restarting and to delete the key splitter but could never retrieve the ability to edit the project (the error popped out).

I then used the latest M7.012 and still having issues but in 7.0.18 was able to delete the key splitter and recover the project (but won't open anymore in M6).

Anyhow just wanted to bring in forward. I tried to replicate the bug and wasn't able.

If I find anything more I will post. Thanks!

[MuTools]

If you still have the .backup version of that MuProject file (see same folder) and that's still the M6 version (you can check that by opening it in a text editor (read only!!)) the please email me that M6 .backup version so i can check why the TimeOut error pops up. Thx.

[yul]

Sent it via email. Don't worry about returning the working project I was just testing.. nothing serious. Thanks

[MuTools]

Thanks for the project.

It turned out that output 1 of the Note Key Splitter in this project is connected to its own input,
which creates an infinite loop, which causes the time-out error or even a complete system hang.

To fix this project:

* Quit MuLab
* Make a backup of User/Settings/AudioSetup.txt
* Then open User/Settings/AudioSetup.txt in a text editor
* Set DriverType=None
* Launch MuLab and open that project
* Delete that invalid connection
* Save the project
* Quit MuLab
* Restore the original User/Settings/AudioSetup.txt

In the next M7.0.19 i added protection against connecting a module with itself.

[yul]

Thanks a lot! I will upgrade my M5 key tomorrow! Cheers

[bibz1st]

Haha, I had a same problem with the parameter randomizer module the other day, finally found the output to input of the same module was the culprit so that new feature is a blessing.