MuLab Prerelease broken under Leopard
-
- KVRer
- 5 posts since 3 Jan, 2007 from Pittsburgh
Hi, I just downloaded the MuLab prerelease (MU.LAB 2.0 PreRelease B), and under OSX Leopard I get the issue
where the MuLab window opens, but it's just a blank white window. No buttons, text or anything... just an empty window. CMusic used to do the same thing, too, only the CMusic blank window was grey.
I was directed here to post feedback on the prerelease, so here's my feedback!
Russ
where the MuLab window opens, but it's just a blank white window. No buttons, text or anything... just an empty window. CMusic used to do the same thing, too, only the CMusic blank window was grey.
I was directed here to post feedback on the prerelease, so here's my feedback!
Russ
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Can other users please feedback whether MU.LAB PreRelease B runs fine on OX 10.5. Thanks.
-
- KVRer
- Topic Starter
- 5 posts since 3 Jan, 2007 from Pittsburgh
Just to add some more info:
Machine is an intel iMac 20", Core 2 Duo 2.0 GHz, 3GB RAM, OSX 10.5.4, with two screens (extended desktop).
Machine is an intel iMac 20", Core 2 Duo 2.0 GHz, 3GB RAM, OSX 10.5.4, with two screens (extended desktop).
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Russ,
Can you please do the following:
-> Quit MU.LAB
-> Goto your Mulab/Settings folder
-> Open Mulab.txt
-> Set Logging=1
-> Save Mulab.txt
-> Start MU.LAB, then Quit MU.LAB
-> Email me the latest Log-yyyymmdd-hhmmss.txt file in your Mulab folder
Thanks.
Can you please do the following:
-> Quit MU.LAB
-> Goto your Mulab/Settings folder
-> Open Mulab.txt
-> Set Logging=1
-> Save Mulab.txt
-> Start MU.LAB, then Quit MU.LAB
-> Email me the latest Log-yyyymmdd-hhmmss.txt file in your Mulab folder
Thanks.
-
- KVRer
- Topic Starter
- 5 posts since 3 Jan, 2007 from Pittsburgh
Ok, I tried that, but I can't actually Quit MuLab -- The Quit is greyed out, so I have to Force Quit it.
So I did that, then edited my MULAB.txt to look like this:
GraphicsFolder={Application}/Graphics/LooxPhat
Logging=1
And started MuLab again. I still get the blank white window, and I can't quit, as Quit is greyed out. So I force quit it, but no log file was generated. Either I didn't edit the MULAB.txt file correctly, or the log file isn't saved until the program is quit correctly.
Does it matter if MULAB is launched from other than the Applications Folder? I launched it from my Downloads folder.
So I did that, then edited my MULAB.txt to look like this:
GraphicsFolder={Application}/Graphics/LooxPhat
Logging=1
And started MuLab again. I still get the blank white window, and I can't quit, as Quit is greyed out. So I force quit it, but no log file was generated. Either I didn't edit the MULAB.txt file correctly, or the log file isn't saved until the program is quit correctly.
Does it matter if MULAB is launched from other than the Applications Folder? I launched it from my Downloads folder.
-
- KVRer
- Topic Starter
- 5 posts since 3 Jan, 2007 from Pittsburgh
Aha!
I moved the MULAB folder to my applications folder and relaunched. I still get the white empty window (I suspect it's the splash screen, since it's the first launch of the app), but first it popped up a dialog asking if I wish to continue logging. Here's the resultant logfile:
Fonts[411]: OK
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
I moved the MULAB folder to my applications folder and relaunched. I still get the white empty window (I suspect it's the splash screen, since it's the first launch of the app), but first it popped up a dialog asking if I wish to continue logging. Here's the resultant logfile:
Fonts[411]: OK
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
ERROR BasicWindowClass_OSX[422]
- KVRist
- 77 posts since 9 Oct, 2002 from UK
OK here on 10.5.5.mutools wrote:Can other users please feedback whether MU.LAB PreRelease B runs fine on OX 10.5. Thanks.
-
- KVRer
- Topic Starter
- 5 posts since 3 Jan, 2007 from Pittsburgh
A-Ha!
I have found a workaround.
Mu.Lab was giving me a white window with no contents on the User License Accept/Decline screen, when I had two monitors ont my iMac. Just for the heck of it, I tried unplugging my second monitor, and then re-launched Mu.Lab.
This time the EULA screen came up, and I hit "accept", and then application launched as normal.
I quit, then re-launched again, and it came up fine.
Then, I plugged the second monitor back in, and, this time, the application launched just fine.
So I think it is just the EULA screen doesn't work right if you have two monitors on your machine. At least, unplugging the second monitor allowed me to see the EULA screen, then hit "accept", so that the EULA screen no longer comes up. And now that the EULA screen doesn't come up, MULAB has no trouble running with both screens plugged in.
I kept the logging "on" during all of this, so if you like, I can send the log files, too.
Russ
I have found a workaround.
Mu.Lab was giving me a white window with no contents on the User License Accept/Decline screen, when I had two monitors ont my iMac. Just for the heck of it, I tried unplugging my second monitor, and then re-launched Mu.Lab.
This time the EULA screen came up, and I hit "accept", and then application launched as normal.
I quit, then re-launched again, and it came up fine.
Then, I plugged the second monitor back in, and, this time, the application launched just fine.
So I think it is just the EULA screen doesn't work right if you have two monitors on your machine. At least, unplugging the second monitor allowed me to see the EULA screen, then hit "accept", so that the EULA screen no longer comes up. And now that the EULA screen doesn't come up, MULAB has no trouble running with both screens plugged in.
I kept the logging "on" during all of this, so if you like, I can send the log files, too.
Russ
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Thanks for providing feedback on this, which is a strange osx quirck imho.
I'll add this info to the Q&A section of the docs.
I'll add this info to the Q&A section of the docs.
-
- KVRist
- 146 posts since 28 May, 2005 from Brisbane, Australia
Hey, I'm back with a fresh install of OSX 10.5.5.mutools wrote:Can other users please feedback whether MU.LAB PreRelease B runs fine on OX 10.5. Thanks.
Everything is fine for me. (Phew!)
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
