MuLab 10.0.85

[humanboeing]

What could be the reason for Mulab to display "Couldn't save project" upon saving attempt?

[humanboeing]

Nevermind, my racks were not updated to M10 and they were classified as restricted area.

[humanboeing]

MuLab crashes without any error message when the user tries to update .mucomposer files through "Upgrade projects"

[humanboeing]

Copy looks -> paste looks doesn't paste corner rounding correctly, from corner rounding=auto it gives corner rounding=0

[humanboeing]

FR: when selecting a rack that's tied to a track, move the composer timeline view to the connected track (just like it works with racks when you select a track)

[humanboeing]

Factory instrument template "Rhipidon" is not updated to M10 - FX section is protected area.

"Taifunk VCO3" template cannot be opened at all.

[MuTools]

MuLab crashes without any error message when the user tries to update .mucomposer files through "Upgrade projects"

Please email me such .MuComposer file that causes such crash. Thanks.

[MuTools]

Copy looks -> paste looks doesn't paste corner rounding correctly, from corner rounding=auto it gives corner rounding=0

Will be fixed in the next update. Thx.

[MuTools]

Factory instrument template "Rhipidon" is not updated to M10 - FX section is protected area.

The preset itself is ok, but due to a bug in MuLab there indeed is an issue with that "FX" front panel button. Will be fixed in the next update.

"Taifunk VCO3" template cannot be opened at all.

Taifunk VCO3 had several incompatibility issues in its front panel and has been removed from the library. But now it seems that the library cache files (which speed up listing the presets) were not yet updated. Will do.
@Taifunk: If you read this, pls email me about this.

[humanboeing]

MuLab crashes without any error message when the user tries to update .mucomposer files through "Upgrade projects"

Please email me such .MuComposer file that causes such crash. Thanks.

I don't have the file anymore, I recreated it in M10 and deleted the M9 file. I wrongly assumed that happens to every .MuComposer file. However I still have a folder of .MuComposer files that crashes M10 every time, but I'm not comfortable sharing it (too many bangers in there ;p). The log files from the crash always end in such a message:

0x00000850 09:45:50:114 LeftClick in window "Choose Project File/Folder To Upgrade" : 212,710 -> 0000000000BD6A58 = PSBT = O.K. = [177,691,54,29] = "OK"

I could send you the log file but I doubt it will be of any help as there are no statements after confirming to upgrade. I can say that when I go through those files one-by-one, as opposed to upgrading the entire folder at once, MuLab doesn't crash and I correctly get error message indicating failure to upgrade.

[MuTools]

I don't have the file anymore, I recreated it in M10 and deleted the M9 file. I wrongly assumed that happens to every .MuComposer file. However I still have a folder of .MuComposer files that crashes M10 every time, but I'm not comfortable sharing it (too many bangers in there ;p).

Not being native english, for my curiosity: What are "bangers"?

Anyway, i found the cause of the crash.
It happens when doing upgrade projects using a folder that does not contain any project.
In fact, technically, because the progress bar does a null progress.
Will be fixed in the next update.
Thx for reporting this bug

[humanboeing]

Banger = very good song

[MuTools]

Ohw great!
Well, i hope you'll share a link to the finished track once it's online

[humanboeing]

Module input/output selector: it is impossible to set an input (of any kind) through this front pannel component

[humanboeing]

Not sure if this is inteded or not, but you can have multiple cables going from the same inlet to the same outlet.
I'll play it safe and report it as visually it is impossible to tell there are 2 cables. It is also impossible to select a different cable to edit its parameters, only one can be edited.