MuLab 7.2.24

Official support for: mutools.com
RELATED
PRODUCTS

Post

mutools wrote:The video is private, can't watch it.
Oh sorry just a sec :dog:

Post

should be visible now

Post

Ok, i see you updated the setting, watched it now. Will research it in depth soonish. Thx.

Post

Thanks.. and my best wishes for you for 2017

Post

Thanks! The same to you! Hopefully 2017 will be a wonderful and fun year :party: :party: :party:

Post

mutools wrote:Ok, i see you updated the setting, watched it now. Will research it in depth soonish. Thx.
I tried to repeat that crash but can't repeat that, even when doing the exact same steps, no crash, i can continue to play, also tested specifically on Mac 64 bit.
Please do this:
* Make sure you're using the latest M7.2.21
* Repeat the crash
* When MacOS crash alert appears click report and copy-paste all tech details into an email to me.

Thx.

Post

mutools wrote:
mutools wrote:Ok, i see you updated the setting, watched it now. Will research it in depth soonish. Thx.
I tried to repeat that crash but can't repeat that, even when doing the exact same steps, no crash, i can continue to play, also tested specifically on Mac 64 bit.
Please do this:
* Make sure you're using the latest M7.2.21
* Repeat the crash
* When MacOS crash alert appears click report and copy-paste all tech details into an email to me.

Thx.
Gotcha :wink: I'll send you the report tonight or maybe tomorrow because it's party time :party: what email adress should I send it to?

Post


Post

The frequency of updates is really impressive, haven't seen many do this. There is a bug I'm currently investigating where I hear beeps rather frequently almost as frequent as noise used to be, but I have full version I'm not supposed to hear anything unexpected. Maybe because I forgot to copy MuLab.ID before, because I can't seem to recreate it now.
Last edited by TheoXD on Sat Dec 31, 2016 2:58 pm, edited 1 time in total.

Post

If you hear short beeps it means the .exe file and the .ID file are not matching. That happens if you only update the exe and forget to also update the .ID file. Solution: Make sure to update both at the same time.

Post

Thanks, that explains it. I initially thought it was some hash signature so didn't think it was important (even though it must have been included for a reason), then I thought it was maybe a trial key or something, so by overriding it I was afraid I would have to re-enter my key again.

Post

"Render Selected Parts as new Sample" when running the screen recorder runs at below real-time (like over 10 times slower). When I'm not running the screen recorder, it runs at above real-time. The render worked correctly, though.

(Also, several times I had an app crash when trying to do the render and screen record at the same time. Couldn't reproduce it reliably, though.)

Something weird happens during the screen capture, though -- is this just a bad codec issue?

No editing was done to that.

Post

 
Best Wishes to Jo and all Mulab/Mux users. :hug:

To a bright and shining future. Cheers! :)

Post

mutools wrote:
mutools wrote:Ok, i see you updated the setting, watched it now. Will research it in depth soonish. Thx.
I tried to repeat that crash but can't repeat that, even when doing the exact same steps, no crash, i can continue to play, also tested specifically on Mac 64 bit.
Please do this:
* Make sure you're using the latest M7.2.21
* Repeat the crash
* When MacOS crash alert appears click report and copy-paste all tech details into an email to me.

Thx.
Oh. While trying to recreate it I narrowed it down to something more general actually:
*insert any preset/device/module into a rack slot
*cut the preset/device/module
*insert a new mux module into the SAME rack slot
*paste the previously cut preset/device/module into that mux modular area
*delete the mux module from the rack slot
*undo twice
*crash

sorry I know it sounds confusing but it's the best discription I can give you, should I still mail you the rapport?

Post

I can repeat the above.

Image

Post Reply

Return to “MuTools”