Couldn't load AudioSetup.txt

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi,
I just want to try Mu.Lab so I downloaded it, unzipped it and started it. But when I click on the "play" button nothing happen. I opened the Console (I'm on Max OSX 10.6) and when the application starting, I saw this log :
com.mutools.mulab[416] 1724> BasicFileStuff[218]: -43
:?

When I want to change Audio Setting, I saw this log in the console :
com.mutools.mulab[416] 5930> Couldn't load AudioSetup.Txt
:?

Can you help me ? :)

Thanks

Remi
Top

Post

Hi Remi,

Could you please try out the new MU.LAB 3, which currently is in its test stage.

You can download the latest version of MU.LAB 3 test from http://www.mutools.com/mulab/azalea

Can you do Audio Setup in MU.LAB 3?

If not, what exactly happens?
Top

Post

Hi,
I tried with MU.LAB 3 but it's the same thing.
When I click on play button, the timeline doesn't start. I activated logging and I changed audio setup. The log traces are :

"02:54:12:973 Core audio device 1: Built-in Microphone
02:54:12:974 Core audio device 2: Built-in Input
02:54:12:974 Core audio device 3: Built-in Output
02:54:12:974 Core audio device 4: Test
02:54:17:303 ApplicationFilePath=/Volumes/Data HD/mylogin/Downloads/MULAB/MULAB.app
02:54:17:710 Load AudioSetup.txt NOK"

I tested all audio devices (in, out and Test (it's an aggregate audio device)) but "AudioSetup.txt" doesn't load.

I tried MU.LAB 3 in virtual with parallels desktop and winXP on my macbook. It's OK.

Do you have an idea ?

Thanks

Rémi
Top

Post

Is your system case-sensitive?

I mean:

Could it be that AudioSetup.txt and AudioSetup.Txt are two different files?
Top

Post

In the next version, MU.LAB always uses "AudioSetup.Txt" as the file name.
There was a case issue somewhere, and so if you are on a case sensitive file system, that could have been the reason. Please retry using MU.LAB 3.0.22 which will be made available very soon. Please watch this topic thread: http://www.kvraudio.com/forum/viewtopic.php?t=274889
Top

Post

Wooooooo!
I forgot to verify this little thing. I renamed the file AudioSetup.txt to AudioSetup.Txt and it work perfectly.
It's great!

Thank you very much for your help. I will be able to enjoy MU.LAB!
Long life to MU.LAB

Remi
Top

Post

MU.LAB also had a typo in the code where it here uses "AudioSetup.Txt" and there "AudioSetup.txt". This has been fixed in MU.LAB test 3.0.24, which is available in http://www.mutools.com/mulab/azalea/

By the way: Does anyone knows how to detect whether OSX runs on a case-sensitive system or not, or maybe more specific: whether drive X is case-sensitive or not?
Top

Post

If it's anything like most unix systems, it's down to the file system. NTFS is not case sensitive, so remote shares of NTFS drives/folder aren't either. (From a general unix background) I can't think of an easy way other than:
1) Check if ".filea" exists; remove if found
2) Check if ".fileA" exists; remove if found
3) Create ".fileA"
4) Attempt to remove ".filea"
5) Success indicates non-case sensitive.

Of course, nothing's simple:
http://en.wikipedia.org/wiki/Comparison ... s#Features
http://en.wikipedia.org/wiki/Comparison ... note-36-70

Basically, you really have to assume the filesystem is case-sensitive: even NTFS is only faking insensitivity.
Top

Post

pljones wrote:If it's anything like most unix systems, it's down to the file system. NTFS is not case sensitive, so remote shares of NTFS drives/folder aren't either. (From a general unix background) I can't think of an easy way other than:
1) Check if ".filea" exists; remove if found
2) Check if ".fileA" exists; remove if found
3) Create ".fileA"
4) Attempt to remove ".filea"
5) Success indicates non-case sensitive.
Thanks for this idea!
Interesting, thanks!
Basically, you really have to assume the filesystem is case-sensitive: even NTFS is only faking insensitivity.
I try to support case-sensitivity as much as possible.

Besides this, i always wondered what the advantage is of a case-sensitive file system. It sounds non-ergonomic to me because humans (the ones who work with computers!) normally regard "MyText.Txt" and "mytext.txt" as the same thing.
Top
Post Reply

Return to “MuTools”