MuLab 10.0.85

[sl23]

OK, it's just that the check is for beta versions but, as you said, it was in beta but it never informed me of updates. Not sure exactly how this is meant to work?

[MuTools]

Ah, yes, you're right.
I forgot that the betas can be included too in that check, i was focused on this M10 beta topic.

[sl23]

That's OK. Thank you.

[pekbro]

Maybe I missed it, but what's up with the user folder, MuLab 10 will not adhere to the parameter without running as admin. I want to lose my ver 9 installation. I only want a single version installed.

[MuTools]

Nothing has changed wrt how M10 uses the user folder, it's the same way as M9.
So make sure you install MuLab in a writable folder!

[pekbro]

Nothing has changed wrt how M10 uses the user folder, it's the same way as M9.
So make sure you install MuLab in a writable folder!

Hmm, they are writable. I get the cant write to user folder regardless of where it's installed.
It's been like this since the start of the beta. I thought that was intended. It wants to default
to the appdata folder... even then it cant write to the folder.

Anyway, I'll investigate, now that I know it's not working right...

[MuTools]

Try a fresh install in c:\MuTools\MuLab10\App\

[pekbro]

Try a fresh install in c:\MuTools\MuLab10\App\

In the end it was a permissions issue, Ive corrected it now thanks

*That was my fault, I don't like how windows locks you out of stuff. I often
circumvent that, some inherited permissions were gumming things up with M10.

[MuTools]

Ok, glad you could sort it out

[pljones]

I don't like how windows locks you out of stuff.

At one point, I thought Windows was starting to lock me out of my entire C:\ drive. At least it seems content to stick to folders it manages and ignore everything else now.

[mgiambro]

I'm having a minor issue in MuLab 10.1.41 when connecting cables in MuDrum. If you connect a cable to a rack, the cable doesn't appear until you click on one of the pads. I wonder if anyone else is seeing this or if it is unique to my system.

[MuTools]

Thanks for reporting this.
Will be fixed in M10.0.42 which will be available soon.

[MuTools]

MuLab App M10.0.42 is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.42 is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• MuDrum editor: Drawing a new cable did not immediately show it. Fixed.
• The user preset "New Rack.Mux" is now to be placed in User/Mux/Racks/New Rack Templates (instead of User/Mux/Racks), together with your other 'new rack' presets.
• When clicking the + rack button and User/Mux/Racks/New Rack Templates/New Rack.Mux exists then this immediately creates this new rack without popup, even if there are other new rack templates. When you want the popup with all new rack templates then Shift+click the + rack button.
• Right-click on project window buttons did not work as expected anymore. Fixed.
• Plugin scan log file now is saved in User/LogFiles. (instead of the legacy User/Settings sub-folder)

So if you already have a custom "New Rack.Mux" in your "User/Library/Mux/Racks" folder then move it into the "New Rack Templates" sub-folder there (create that sub-folder if it does not yet exist) so to match the updated location.

[MuTools]

No, you're not the only one. Drop mulab.exe to virustotal.com ...

I've spent time doing A-B compilations to find the culprit for this false positive issue and it really is a false positve and it's caused by the Microsoft Platform Toolset 2022
I've posted a question about this on the Microsoft dev forum and now waiting for their answer.

[paulbreeze]

Thanks.