Cannot seem to open a .MuProject in MuLab using the OS X Terminal

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

Post

Hi there,

Firstly, let me say that I'm really enjoying MuLab; it gives me a nice nostalgia for Amiga and Atari programs from my youth. However, I'm having a problem:

I'm trying to use the command line to open a .MuProject file, but when I do so I get a dialog box telling me essentially that my .MuProject can't be opened in MuLab. (See attached pic) Given that the only 'official' OS X menu in the app is 'Quit MuLab', and there's no Applescript dictionary for MuLab, I'm not too surprised! :wink: Even when I right-click a .muProject file and choose 'Open with.." I still get that dialog box.

It's a show stopper for me though- I'm trying to build a bridge between my pedalboard and MuLab so that I can trigger the loading of the next backing track in my set list, but without being able to automate this in some way, I'm not sure how to proceed.

Any help would be appreciated; thanks.
You do not have the required permissions to view the files attached to this post.
Top

Post

p.s I'm running MuLab 8.3.3 64Bit OS X 10.14.6
Top

Post

I don't know why MacOS tells you that MuLab cannot open MuProject files, it definitely is a false statement.
Maybe there needs to be a registered MacOS association between .MuProject files and MuLab?
As far as i see that's rather a MacOS question.
Top

Post

Hey there,

I'm a bit stuck then I'm afraid. I did try associating the .MuProject file type with MuLab but got the exact same dialog box that I showed in my initial post. Indeed, double clicking on a .MuProject file launches MuLab and shows the same dialog. Is that normal? Do other OS X users have this issue?

I've associated a keyboard shortcut within MuLab to bring up the 'open recent files' list, and from there I can open a project by pressing a key that is the first letter of a project's name, although if there are 2 or more projects that share that letter, this doesn't work, although I can work around this by starting each project with a unique letter.

So at least this is a workaround- I can use Keyboard Maestro to send keystrokes to MuLab to open my projects and then play them. A reminder that my goal is to load and play the next backing track in my set list. My set list will have to be limited to the maximum number of recent files in the list! Ideally I'd just be able to tell MuLab to open an arbitrary file.

Thanks :)
Top
Post Reply

Return to “MuTools”