Max standalone disables m4l?

[alljvkr]

Recently I built a standalone application with max and now, whenever I have launched this application, m4l devices won't open anymore in max; they won't open at all. This behavior is fixed only after a fresh log in. The standalone functions fine, it's just that editing devices is impossible. Can anyone confirm this behavior, is this a known issue?

Live 8.2.1 / MacOSX 10.6.7 / Max 5.1.7 / Standalone built with Max 5.1.7
The standalone application is named IoR (downloads section of jvkr.nl)

[pukunui]

In the File and Folder tab of Live's prefs where is the Max application specified?

Does it work right until you restart your app? Is your app open when it breaks?

Not a known issue, so maybe take it in to support

Cheers

-A

[alljvkr]

Thanks for your reply.

The problem fro me is reproducible with these steps:
1. launch max
2. create new patch with any object
3. build standalone from it
4. launch the standalone, while max remains active
5. launch live
6. instantiate a max midi device
7. try to edit

The editing won't work. What is funny, is that in the max window of the standalone every few hundred ms the message 'cycle~: No such object' is posted.

Earlier I mentioned that logging out is required, but that is not the case. Quitting both max and the standalone, and again clicking the edit button launches max and opens the device. It appears that the order of launch is crucial. If the standalone is launched first, and after that max, then all works fine. But launching the standalone while max is active creates this issue.

You mention support, do you know at which email address they can be reached?
thank you.

[pukunui]

I can reproduce.

Sorry for the inconvenience.

It's not going to get fixed for the release of MaxMSP 5.1.8, but I'll definitely log it to get looked at.

Cheers

Andrew

[alljvkr]

> t's not going to get fixed for the release of MaxMSP 5.1.8

I'm not in a hurry. Good to know it's being looked at.
thanks