MuLab 7.1.30

[jd88]

Yes try emailing it.

ok, sent it before 1 minute.


(and if you use fader or other knobs of this plugs, you see something like black overlay's withing the range of the GUI-Elements. Seems, that blanc-gifs / png or whatever will be intransparent in that moment ?? )

[MuTools]

jd88, thx for the video.

Pls try this:

* Quit MuLab
* Open User/Settings/MainSetup.txt
* Add / update this parameter line:
MacOs-FlushBlittedPictures=0
* Save that text file and relaunch MuLab 7.1.15

Does that make a difference wrt the flickering?

[jd88]

jd88, thx for the video.

Pls try this:

* Quit MuLab
* Open User/Settings/MainSetup.txt
* Add / update this parameter line:
MacOs-FlushBlittedPictures=0
* Save that text file and relaunch MuLab 7.1.15

Does that make a difference wrt the flickering?

no, changes nothing!

(you read, that the flickering is too and much harder by 'korg-vst's if changing parametes via GUI-Elements? - - allways redrawing GUI-Elements. Sorry, forgott to show in video )

- - - - - - -

another point:
if I opened one of the vst I'm talking about, going now in preferences to change maybe: value of "Mouse Hover Delay time", klicking done and then leave MuTools (shut down), I'll get allways a crash and if I restart all is reset.

If I'll not change something in prefs and close MuTools with that vst opened, crash not happens

If another vst or MuTools synth is openend while doing this (changing pref-params) this crash not happens, and after restart preferences are changed like needed.

- - - -

and sorry: Dune 1.4 No problems with flickering, but the new plug of Synapse: 'The Legend' (same like Dune 2.5, if you select parameter you see 'focus-range parameter-range' as overlayed darker grafic)
'The Legend' has no keyboard or LED's for redraw.

[MuTools]

jd88, thx for the video.
Pls try this:
...
MacOs-FlushBlittedPictures=0
...

no, changes nothing!

Are you sure you have edited the MainSetup.txt for that MuLab 7.1.15 folder?
I expected that it would make a difference.

(you read, that the flickering is too and much harder by 'korg-vst's if changing parametes via GUI-Elements? - - allways redrawing GUI-Elements. Sorry, forgott to show in video )

I don't have the Korg Vsts here and no demo of them available. I only have the Dune 2.5 demo for testing this. It works fine (no flickering) with MuLab 7.1.15 on osx 10.11.6. Can't test it on my other mac with 10.6.8 as that's a 32 bit mac and unfortunately Dune does not support the "hasCockosViewAsConfig" effCanDo extension, which tells the host that it supports an NSView editor in 32 bit mode.

if I opened one of the vst I'm talking about, going now in preferences to change maybe: value of "Mouse Hover Delay time", klicking done and then leave MuTools (shut down), I'll get allways a crash and if I restart all is reset. If I'll not change something in prefs and close MuTools with that vst opened, crash not happens

Is this repeatable with Dune? I can't find such setting/can't repeat such crash.

Also please email me the osx crash report details.

[jd88]

<quote>"Are you sure you have edited the MainSetup.txt for that MuLab 7.1.15 folder?
I expected that it would make a difference."</quote>

Yes for shure. Checked it again and again. No changes.

<quote>Is this repeatable with Dune? I can't find such setting/can't repeat such crash.</quote>

again and again. Not allways. But just now I'd a crashlog and its on the way via mail. (maybe it's another reason?)

And because the problemvst's (grafic). Checked now with Renoise 3.1, Energy XT 3, Logic 10.2.2, mixbus 3.6, live 9.5 and tracktion 6 - and now Alpha 'FL-Studio'. In no of this applications this grafic-problem occurs.

[jd88]

Oh, maybe it's helpfull? if you using ppg (v2), closing / hide the keyboard and open it again, the size of the plug-wrapper (MuTools) is going wrong (to small, then to large). You've to close the wrapper and open again, and then it's ok again as so long you don't hide the keyboard of the plug again.


interesting, this does not happen with arturia plugs (like prophet 2, which need in hybrid mode much more space in wrapper, and visa). And the new resizefunction by arturia plugs working very weel too.

[Calum]

I can also confirm that M7.1 does not launch at all in OSX 10.6 Snow leopard.

Is it on a 64 bit system? If yes, what exactly happens? Eventually post a screen video?

Yes, I can boot Snow Leopard in 32 bit or 64 bit mode and the results are the same (I will email screen shots and videos to you). I can boot some other applications in 32 bit or 64 bit mode within 32 bit Snow Leopard by checking/unchecking 64 bit mode in the apps' get info screens (so it doesn't appear to be necessary to boot Snow Leopard in 64 bit mode).

I will also re-check my performance experiments again and post the results. (Probably not before Monday.)

[Zexila]

Ah ok i see, thx for explaining.
Pls try this on your osx 10.6.8:
* Quit MuLab
* Open User/Settings/MainSetup.txt
* Add this line:
MacOs-FlushBlittedPictures=0
* Save that text file and relaunch MuLab 7.1.15
Does that make a difference?

Nope.

Ok, you say it's slower than M7.0.47, but is it acceptable + usable? Or not at all?

It's usable and acceptable for sure, not thrilled about it, but hey.

[MuTools]

Thx for all feedback, it helps! Ok i discovered some things and am working on an update that may fix several of the remaining issues. Hopeful.

[MuTools]

There is a new MuLab 7.1.18 for Mac 64 bit: http://www.mutools.com/galaxa/mulab-7-1 ... 64-app.zip

How to install: Replace the current M7.1.x MuLab.app file with this newest version.

This new version should fix all open issues:

* Flickering VSTs issue solved
* Slower UI issue solved
* Sometimes doesn't launch issue solved
* ...

Please let me know how this one flows on your Mac. (pls mention your Mac OS version)

Any remaining issues? Or is this one ready to rock the Mac?

[MuTools]

Ps @jd88: About that ppg vst issue: for now i assume this is a plugin specific issue.

[pgregory]

Can confirm it launches successfully now on my macOS Sierra MacBook Pro. Thanks for the rapid response. Will spend this evening testing and report anything I find. Looks positive so far, sounds good too.

Paul

[Calum]

Great job! M7.1.18 is now launching in Snow Leopard for me and CPU performance appears to have improved when compared to M7.0.47.
Also working in Sierra. I will compare the CPU performance of the recent M7.1 versions again in Sierra and post the results later.

Thanks Jo!

[Zexila]

Sluggishness is gone and you knocked CPU usage down a notch too (from 13% to 11%), awesome. 10.6.8

[Calum]

I agree, on Snow Leopard, M7.1.18 walks all over M7.0.47 with CPU performance. Using the Airtime demo as a test project, both versions of MuLab idled at 11% but there was a noticeable difference in Max CPU values – 70% for M7.1.18 and 89% for M7.0.47. I also tried cutting the CPU limit to 50% in the Audio setup resulting in the transport stopping at bars 10, 14, 18 and 22 in M7.0.47 and M7.1.18 holding out until bar 42. Great result!

I wish I could say the same about Sierra but the results were not as hoped for. In the CPU average/max test M7.0.47 was the clear winner followed by M7.1.14. When I cut the CPU limit to 50% the results changed dramatically: M7.0.47 stopped at bar 10, M7.1.18 stopped at bar 14, M7.1.9/M7.1.15 stopped at bar 18 and M7.1.14 held out until bar 41.

I repeated all the tests three times and averaged the results for accuracy. Not sure how this would affect performance in real world usage but I was surprised at how different the results were on two versions of OSX.

Jo, if you think my tests are valid and useful to you, I would be happy to install other versions of OSX and repeat the tests. Just let me know. Or perhaps others would be willing to repeat the tests on OSX Lion - El Capitan.