schwarzmathias

I came across the following problem while using

Every time I hit the Master STOP button in Ableton, the Max console shows up and gives me the following message:

live.remote~: Setting the Id cannot be triggered by notifications. You will need to defer your response.

It doesn't make a difference if the M4L Patches are in different channels. The problem only occurs, when both patches are in the same ableton set. Both patches are working well, regarding their main functions.

The live.remote~ object can be found only in the ARP patch.

I use the following soft- & hardware: LIVE 10.1.9 & MAX 8.1.1 on a Windows 10, 64-bit machine.

For my live performance it's very annoying to see the max console showing up every time I stop ableton.

Is there a way to get rid of this problem?

Max1.png

Max2.png

I came across the following problem while using two M4L devices (ARP & GranulatorII) together:

Every time I hit the Master STOP button in Ableton, the Max console shows up and gives me the following message:
live.remote~: Setting the Id cannot be triggered by notifications. You will need to defer your response. 

I use the following soft- & hardware: LIVE 10.1.9 & MAX  8.1.1 on a Windows 10, 64-bit machine.
For my live performance it's very annoying to see the max console showing up every time I stop ableton.
Is there a way to get rid of this problem?

Hey there,
I came across the following problem while using two M4L devices (ARP & GranulatorII) together:
Every time I hit the Master STOP b

conflict-between-2-m4l-patches-id-setting-for-live-remote~-with-arp-granulator-ii

Granulator II automatically opens the Max Window, when ever any Device creates an error message. The error message you see here are annoying but harmless and are not created by Granulator II but by other devices. However you can turn OFF the Granulator II opens the Max Window on errors, by clicking "about..." and unchecking "show errors".

Screenshot 2021-07-02 at 23.02.00.png

Granulator II automatically opens the Max Window, when ever any Device creates an error message. The error message you see here are annoying but harmless and are not created by Granulator II but by other devices. However you can turn OFF the Granulator II opens the Max Window on errors, by clicking "about..." and unchecking "show errors". 

Thank you so much for your answer and your work Robert !

Conflict between 2 M4L Patches: ID Setting for live.remote~ with ARP & GRANULATOR II