Thx for confirmation!Zexila wrote:Runs fine on 10.6.8 here too.mutools wrote:MuLab 7.1.15 runs fine on OSX 10.6.8 here.jd88 wrote:Problem since first 64bit version. It don't start on MAC 10.6.8 at all (and maybe OS-versions below?)![]()
MuLab 7.1.30
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3186 posts since 18 Mar, 2008
My pleasure.
Also CPU usage went down, remember in one thread I reported 16-15%, now is 13% (Activity Monitor).
Also CPU usage went down, remember in one thread I reported 16-15%, now is 13% (Activity Monitor).
This entire forum is wading through predictions, opinions, barely formed thoughts, drama, and whining. If you don't enjoy that, why are you here?
ShawnG
-
- KVRAF
- 3186 posts since 18 Mar, 2008
Same here, MuLab 7.1.15 on 10.6.8.LYTZ wrote:Went on to check the last versions out, all looking good so far as well,
but what I noticed is a severe performance dropdown between 7.1.9 GUI performance
and prior Versions (i.e. 7.0.47) in a quite linear fashion.
(i.e. draggin selections, moving stuff around and things of that nature have quite a delay to it.
It looks like a severe frame rate dropdown or what you get when the app is at it's CPU limits for example.)
This entire forum is wading through predictions, opinions, barely formed thoughts, drama, and whining. If you don't enjoy that, why are you here?
ShawnG
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Zexila, i'm confused: A couple of posts ago you wrote M7.1.15 runs fine on 10.6.8, and now you seem to say that M7.1.15 does not run fine on 10.6.8. Pls elaborate.
-
- KVRAF
- 3186 posts since 18 Mar, 2008
It runs, opposed to other user that can't even run/launch it, so I just reported that it actually runs, basically I installed MuLab, check does it run, reported here, than checked CPU usage with just playing empty project, reported here, than tried to make a sequence/clip and move it around, noticed a lag, dig around to see if anyone reported, quoted&reported back.mutools wrote:Zexila, i'm confused: A couple of posts ago you wrote M7.1.15 runs fine on 10.6.8, and now you seem to say that M7.1.15 does not run fine on 10.6.8. Pls elaborate.
This entire forum is wading through predictions, opinions, barely formed thoughts, drama, and whining. If you don't enjoy that, why are you here?
ShawnG
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
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?
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?
- KVRist
- 121 posts since 7 Apr, 2008 from germany
Definitly NOT running here.
BUT:
OK, it's a Hardwareproblem. So in my case it's fixed btw. I cannot test
NEW:
Some redraw problems with VST-Plugs (Korg Legacy complete and Synapse Dune 1.4 & 2). All realtimeparts of GUI like keys and Led's hard flickering while playing. ( nervy, but maybe
Arturia (Coll. V4 & 5 - exc. NOT Synclavier), AAS (actual new versions), Dexed, Tracktions (BioT / Synth, Mastering), Waldorf a.s.o. working fine. Thanks for that (Y)
Last edited by jd88 on Sun Oct 02, 2016 12:24 am, edited 1 time in total.
-
- KVRAF
- 3186 posts since 18 Mar, 2008
Nope.mutools wrote: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?
This entire forum is wading through predictions, opinions, barely formed thoughts, drama, and whining. If you don't enjoy that, why are you here?
ShawnG
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Do you get a crash alert from OSX?jd88 wrote:For shure, on my old IMAC with OSX 10.6.8 MuLab starts (icon jumping, for only one second I see MuLab-texti n menu), but then it stop loading and maybe crashing??
Ok.Definitly NOT running here. OK, I will reinstall tomorrow. Test again.
Just tried dune 2.5 demo in M7.1.15 on osx 10.11.6 and it all looks fine, don't see any redraw issues nor flickering. Anyone else having issues with Dune 2.5 in MuLab 7.1.15 ?Some redraw problems with VST-Plugs (Korg Legacy complete and Synapse Dune 1.4 & 2).
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Ok, you say it's slower than M7.0.47, but is it acceptable + usable? Or not at all?Zexila wrote:Nope.mutools wrote: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?
- KVRist
- 121 posts since 7 Apr, 2008 from germany
10.6.8 - OSX-problem (MuT not workin) fixed. It's a Hardwareproblem
Sorry for that!!!
grafik - Flickering-problem (s.o) found on 3 I-MAC's with NVidia-grafic-card (GeForce 9400), all running actuall version of OSX Maverick, all same installation. Problem only in 64-bit-version.
VST-s working fine in MuLab 32-bit version.
Sorry for that!!!
grafik - Flickering-problem (s.o) found on 3 I-MAC's with NVidia-grafic-card (GeForce 9400), all running actuall version of OSX Maverick, all same installation. Problem only in 64-bit-version.
VST-s working fine in MuLab 32-bit version.
Last edited by jd88 on Sun Oct 02, 2016 12:44 am, edited 1 time in total.
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Just for my curiosity: Which hardware prob was it?jd88 wrote:10.6.8 - OSX-problem (MuT not workin) fixed. It's a Hardwareproblem![]()
![]()
Sorry for that!!!
Pls make a screen video of it and post a link to it here.grafik - Flickering-problem (s.o) found on 3 I-MAC's with NVidia-grafic-card (GeForce 9400), all running actuall version of OSX Maverick, all same installation. Problem only in 64-bit-version.
- KVRist
- 121 posts since 7 Apr, 2008 from germany
"Just for my curiosity: Which hardware prob was it?"
wrong intel. This computer is to old. It's missing 32 bit's
I'm so stupid
can I mail video (7MB)? recorded 2 examples DUNE 2.5 & Legacy cell.
(you sent me email via FB yesterday)
wrong intel. This computer is to old. It's missing 32 bit's
can I mail video (7MB)? recorded 2 examples DUNE 2.5 & Legacy cell.
(you sent me email via FB yesterday)
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
- KVRAF
- 2473 posts since 25 Sep, 2014 from Specific Northwest
This is from a fresh boot where nothing else is open. I can't imagine the memory management subsystem is all that different from 32- to 64-bit. Oh, wait... This is Apple.mutools wrote:I don't know why, don't see any reason on MuLab's side. May be because it's 64 bit now. Or maybe you have other open apps in the background. Pls be sure to compare in exact same conditions. Simply opening a web browser may already make a big difference in performance.syntonica wrote:One small issue though that I have been noticing. The first time I play a track, when the VSTs on that track first start to run, the audio glitches slightly as they grab their resources. Anytime after that, there's no issue on playback. I have not heard this issue with the 32-bit version at all.
I'll take a look at it more closely to see what's going on. I wonder if tuning shared memory would help?
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
