|
On startup MuLab alerts: "Can't find graphic resources -> quitting".
The MuLab zip package includes a couple of subfolders and files that MuLab needs to operate properly.
When you have extracted the zip package, and you want to move MuLab to another place on your harddisk, then make sure you move the complete MuLab folder, not the application file only.
Also note that MuLab does not support folder names that contain a slash or backslash in their name because that results in confusing file paths. E.g. a folder name "Tools/Toys" will be interpreted as the subfolder Toys in the folder Tools.
If you're sure the MuLab folder is complete and you have checked the other notes here above and you still get this alert, then note that when this situation occurs MuLab generates a Log-yyyymmdd-hhmmss.Txt file in the Mulab folder.
If you have a minute of time, please email this log file together with your mac model + processor type + OSX version to  . Thanks in advance.
In MuLab's Audio Setup, only audio input OR audio output show up. When selecting audio input, MuLab doesn't play, but when selecting audio output, you can't record anything.
It's an OSX issue.
On systems with Mac OS X 10.4 or later, sometimes the audio input and output use separate drivers, and thus show up as separate devices in audio applications, leading to the fact that you can't use both at the same time.
The solution is to make an aggregate device that uses the input/output from different audio devices on your system, and showing up as 1 device in audio applications.
This can be done via OSX' Audio MIDI Setup.
For more details, click here.
Or visit Apple at http://www.apple.com/ca/pro/techniques/aggregateaudio/
Or Google : http://www.google.be/search?q=Audio+MIDI+Setup+Aggregate
Some VST plug-ins are tagged as "Disabled".
On OSX, it's recommended to use VST 2.4 plugins. VST 2.3 (or lower) plugins will not show their custom editor because of drastic changes Apple and Steinberg made to their SDKs.
When i launch MuLab, MIDI input is not working eventhough i enabled it in the MIDI setup.
On some OSX machines, there indeed is a problem that MIDI input isn't properly enabled on startup.
When you go to MIDI Setup and simply click OK, then MIDI input is working well.
It's a strange issue and we did not yet find the very reason of this.
Luckily it's only on some OSX machines and even then it only takes a couple of clicks to enable MIDI input.
Of course we'll do our best to solve this asap.
Windows 7: Changing the files in MuLab/Settings doesn't have effect. And/or Windows 7 complains about security/administrator issues.
Due to the Windows 7 Virtual Store mechanism, not everything is allowed on a Windows 7 system.
The simplest way to avoid these problems when using MuLab is to install MuLab outside the 'Program Files' folder, but e.g. in C:\Applications\Music\Mulab (or any other non-system folder).
You can simply move the Mulab folder around to this new location, no problem, as the Mulab folder is 100% self-contained.
On startup MuLab alerts: "Can't find graphic resources -> quitting".
Make sure you unzip the MuLab zip package with the "Use Folder Names" option enabled!
The CPU meter is behaving strange.
It's a Windows issue.
This article on the Microsoft website tells you more: http://support.microsoft.com/kb/895980
| 