MuLab 10.0.85

[PelletProject]

Found a semantic error when attaching a Parameter Event Generator to the ME_Q

[PelletProject]

I also happened to find a crash when moving the pre/post fader in a rack with sub-racks after changing a sub-rack output to the parent rack's Mixer Strip

[MuTools]

Found a semantic error when attaching a Parameter Event Generator to the ME_Q

Thx for reporting this!
Will be fixed in the next update.

[nenneb]

Cannot move the small triangles within the rack ...

[MuTools]

Cannot move the small triangles within the rack ...

It's just a click on the new position, not a drag towards the new position.
Does that clarify it?

[pekbro]

Cannot move the small triangles within the rack ...

It's just a click on the new position, not a drag towards the new position.
Does that clarify it?

This is a bit confusing, clicking to move the fader to after, say a limiter, doesn't seem like it does anything, where as before the limiter would stop any clipping before it got to the fader.

*Heh, I also made it crash by trying to manually rewire the fader to where I wanted it.

Code: Select all

 Exception in non-user thread
0x00002E00 12:18:06:346 Exception code=C0000005
0x00002E00 12:18:06:346 Exception address=00007FF76AF078E0
0x00002E00 12:18:06:346 Exception code bytes[-8]=AA B4 03 00 00 45 8B F9
0x00002E00 12:18:06:346 Exception code bytes=4C 63 A1 D0 00 00 00 41
0x00002E00 12:18:06:346 Exception code bytes[+8]=8B D8 48 8B F2 4C 8B F1
0x00002E00 12:18:06:346 Rax 1
0x00002E00 12:18:06:346 Rcx 0
0x00002E00 12:18:06:346 Rdx 12505158
0x00002E00 12:18:06:346 Rbx 12505158
0x00002E00 12:18:06:346 Rsp B5DFCF0
0x00002E00 12:18:06:346 Rbp 2
0x00002E00 12:18:06:346 Rsi 100
0x00002E00 12:18:06:346 Rdi 1295A060
0x00002E00 12:18:06:346 App base address=00007FF76AC70000
0x00002E00 12:18:06:346 Exception map offset=00000000002968E0
----------
0x00002E00 12:18:06:346 Caller EIP 0 @ 00007FF76ACD9E47 = @ map 0000000000068E47
0x00002E00 12:18:06:346 Caller EIP 1 @ 00007FF76B3BC7D8 = @ map 000000000074B7D8
0x00002E00 12:18:06:346 Caller EIP 2 @ 00007FF76B3277AF = @ map 00000000006B67AF
0x00002E00 12:18:06:346 Caller EIP 3 @ 00007FFB3D35527F = @ map 00000003D26E427F
0x00002E00 12:18:06:346 Caller EIP 4 @ 00007FFB3D2CE886 = @ map 00000003D265D886
0x00002E00 12:18:06:346 Caller EIP 5 @ 00007FFB3D35426E = @ map 00000003D26E326E
0x00002E00 12:18:06:346 Caller EIP 6 @ 00007FF76AF078E0 = @ map 00000000002968E0
0x00002E00 12:18:06:346 Caller EIP 7 @ 00007FF76B02A899 = @ map 00000000003B9899
0x00002E00 12:18:06:346 Caller EIP 8 @ 00007FF76B0257C2 = @ map 00000000003B47C2
0x00002E00 12:18:06:346 Caller EIP 9 @ 00007FF76B00A942 = @ map 0000000000399942
0x00002E00 12:18:06:346 Caller EIP 10 @ 00007FF76B00AE31 = @ map 0000000000399E31
0x00002E00 12:18:06:346 Caller EIP 11 @ 00007FF76B03BA8D = @ map 00000000003CAA8D
0x00002E00 12:18:06:346 Caller EIP 12 @ 00007FF76B05335D = @ map 00000000003E235D
0x00002E00 12:18:06:346 Caller EIP 13 @ 00007FF76B052C3A = @ map 00000000003E1C3A
0x00002E00 12:18:06:346 Caller EIP 14 @ 00007FF76AE2E776 = @ map 00000000001BD776
0x00002E00 12:18:06:346 Caller EIP 15 @ 00007FF76B344922 = @ map 00000000006D3922
0x00002E00 12:18:06:346 Caller EIP 16 @ 00007FFB3BC3259D = @ map 00000003D0FC159D
0x00002E00 12:18:06:346 Caller EIP 17 @ 00007FFB3D30AF38 = @ map 00000003D2699F38
----------
0x00002E00 12:18:06:348 Caller EIP 1 = 0000000000000002 = map @ FFFF80089538F002
----------
0x00001818 12:18:06:351 URM[794] Append: Delete Audio Cable
0x00001818 12:18:06:355 IWindow[530]
0x00001818 12:18:06:363 gonna shutdown MIDI engine
0x00001818 12:18:06:382 Gonna shutdown ASIO engine
0x00001818 12:18:06:408 AAE[185]
0x00001818 12:18:06:408 MessageAlert: A serious error has occured.
0x00001818 12:18:06:425 BWindow[715]
0x00001818 12:18:09:868 LeftClick  in window "" : 217,159 -> 0000000000BEFDA8 = PSBT = btn1 = [198,145,33,29] = "OK"
0x00001818 12:18:09:979 BWindow[715]
0x00001818 12:18:09:979 BWindow[715]
0x00001818 12:18:09:979 BWindow[715]
0x00001818 12:18:09:979 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:980 BWindow[715]
0x00001818 12:18:09:981 BWindow[715]
0x00001818 12:18:09:983 [OK]

[MuTools]

Please email me the complete log file for that crash.

And is this crash repeatable?
Which steps?

[pekbro]

Is this crash repeatable?
Which steps?

Ill try, basically I just disconnected the audio lead to the fader to cause the crash seemingly.
The transport was not running. Anyway, it just happened, I will try...

One other thing that happened last night fyi. I set an effect processor to modulate a parameter
in a plugin I was using, which was fine, then I replaced the plugin and forgot to undo the audio to modulation converter>>event processor (plugin parameter) >>'plugin', chain. It didn't crash, but did not complain that the parameter was missing. The replacement plugin worked but pegged the cpu to the red in the cpu meter.

Anyway, I dunno if it's supposed to be like that. I would think it might stop or request another
parameter? Just seemed odd to me in addition to the cpu spike thing of course...

*I guess if you're counting parameters, it would not know that a parameter is missing.
If there was an option to auto-reset any parameter modulation upon replacing a plugin
I would probably choose that most times myself.

[MuTools]

Is this crash repeatable?
Which steps?

Ill try, basically I just disconnected the audio lead to the fader to cause the crash seemingly.
The transport was not running. Anyway, it just happened, I will try...

Please also email me the complete log file for that crash so i have the full context, precise version numbers etc etc.

One other thing that happened last night fyi. I set an effect processor to modulate a parameter
in a plugin I was using, which was fine, then I replaced the plugin and forgot to undo the audio to modulation converter>>event processor (plugin parameter) >>'plugin', chain. It didn't crash, but did not complain that the parameter was missing. The replacement plugin worked but pegged the cpu to the red in the cpu meter.

Anyway, I dunno if it's supposed to be like that. I would think it might stop or request another
parameter? Just seemed odd to me in addition to the cpu spike thing of course...

MuLab will not ask for another parameter in such case.
The cpu spike could be caused by the fact that, by coincidence, the generated parameter also is an existing parameter in the new plugin and is a cpu heavy parameter.
If you think it's not that reason feel free to elaborate on this case, preferably with a little screen video demonstrating it, together with the complete log file.

[pekbro]

Please also email me the complete log file for that crash so i have the full context, precise version numbers etc etc.

Ok

MuLab will not ask for another parameter in such case.
The cpu spike could be caused by the fact that, by coincidence, the generated parameter also is an existing parameter in the new plugin and is a cpu heavy parameter.
If you think it's not that reason feel free to elaborate on this case, preferably with a little screen video demonstrating it, together with the complete log file.

Yeah I figured that out, eventually heh:

*I guess if you're counting parameters, it would not know that a parameter is missing.
If there was an option to auto-reset any parameter modulation upon replacing a plugin
I would probably choose that most times myself.

[MuTools]

I also happened to find a crash when moving the pre/post fader in a rack with sub-racks after changing a sub-rack output to the parent rack's Mixer Strip

Thx for the video!
I'll investigate this asap.
(currently in the middle of another code operation)

[nenneb]

Cannot move the small triangles within the rack ...

It's just a click on the new position, not a drag towards the new position.
Does that clarify it?

Aaahhh Thank you!

[Scrubbing Monkeys]

where can one download the 10.0.08beta version?

[MuTools]

Good question!
The full MuLab 10.0.8 zip package is here:
https://www.mutools.com/mulab/app/lates ... -win64.zip

From there upgrade to the latest M10 beta version, currently M10.0.11, which is here:
https://www.mutools.com/mulab/app/lates ... /beta.html

[Scrubbing Monkeys]

Thank you!