Note Trigger Handler issues (w/ new 1.3 public release)

[shnootre]

Greetings, 
I am having issues with the Note trigger rack. I incorporated it into my work during the Clyph X alpha test, and only today installed the new files, and now...some strange behaviors. 

When I load the set from the lesson pack, on a fresh boot of Live, the track works. The built-in BPM commands work, and I am able to rename and create my own commands, such as METRO ON, 1/ARM ON etc. 

When I go to an older project that had the note trigger rack, however, it does not work. Nor does it work, in that older project, for me to enter a new version of the Note Trigger Rack  (i.e. the version I'd saved from the new lesson set). 

And... after doing this, when I go back into the original lesson set, which I did not alter (except to add a couple of commands to the rack), the rack no longer works. None of the commands do anything. 

If I shut down live and restart, and then go to the lesson set, the handler works again. But in no other instance. If I create a brand new set and load the rack into it, I cannot get it to function. 

Any advice would be much appreciated! 

[schlapbe]

Hi shnootre!
my advice: keep going, I can confirm that it works. I can't recall how I got it to work. But I got it working at some point. It is a known issue though and stray is working on it. I recommend hotswapping the m4l element and saving it as a instrument rack etc.....

[everyoneishappy]

Spent the day reintegrating CXP into my workflow for live 11 today (yay). Mostly got there, but a little stuck running into same issue as shnootre. Any tips for getting it to work?

[davlar]

Sorry have no advice to give, but seeing the same issue.
i.e. when I open a new live set, "note trigger handler" works, but then opening another live set after that and it no longer works. I have to quit live and restart to get it to function again. Not the end of the world having to restart live, but would be good to be able to issue some form of Clpyhx M4L type reset command which I could run when opening a new set to workaround this issue.

[davlar]

Looks like the first time the note trigger handler (NTH) runs everything is ok and functions as expected, but if you load another set (without restarting live) with a note trigger rack and try using that you get the M4L error:

jsliveapi: 'DeviceManagerComponent' object has no attribute 'trigger_action_list'

So something not quite right with the get_device_manager.js script in the note trigger handler ?


Should add I'm using:
NTH version 1.0.4
Live 11.2.7
Windows 11

Attachments:

[forumusername]

I am coming in to confirm the issue. It works on initial launch of a new ableton live 11, but any project reloading within that session it does not work.

Is there any official 'bug tracking' information anywhere?

[schlapbe]

May 6, 2023 20:47:09 GMT -5 forumusername said:

Is there any official 'bug tracking' information anywhere?

Hi forumusername , davlar , everyoneishappy
there is a bug handling and reporting active at the isotonik website here:

isotonikstudios.freshdesk.com/support/home

besides that, I can say that the Note Trigger Handler is working just fine. 

Try this:
Go into the help lesson with the Note Trigger Handler, open the project and save the instrument rack into your User Library. 

Then make a new project load the device from your user library and see if the error still occurs.

Best, S

[marcusfree]

Hello, guys!

Note Trigger Handler example works in Live 11.2.11 for me, every time.
In Live 11.3.10 (current) it works only first time a set is loaded.
In Live 11.3.10b5 (current Beta) it never works, gives always this error in the Max console:


jsliveapi: 'DeviceManagerComponent' object has no attribute 'trigger_action_list'

It would be nice to know if 11.3 compatibility is in the works (I know it is not stated), so for example we could use Push 3 as a controller too.

Marcus

[schlapbe]

Aug 26, 2023 8:04:01 GMT -5 marcusfree said:

Hello, guys!

Note Trigger Handler example works in Live 11.2.11 for me, every time.
In Live 11.3.10 (current) it works only first time a set is loaded.
In Live 11.3.10b5 (current Beta) it never works, gives always this error in the Max console:


jsliveapi: 'DeviceManagerComponent' object has no attribute 'trigger_action_list'

It would be nice to know if 11.3 compatibility is in the works (I know it is not stated), so for example we could use Push 3 as a controller too.

Marcus

Hi Marcus,
I did some testing with the newest update (11.3.10) and the note trigger rack works just fine.......
Which version is your note trigger handler? 
I will do a video about this at some point for sure, because you are not the only one who has problems with the NTH.....

Best,S

[marcusfree]

Hi, thanks for answering.

Version of ClyphX Pro installer is 1.3.0.

It works fine the first time I load the (for example tutorial) live set containing note trigger handler.
If I reload the set, I get the error and no action is performed. I can try to further narrow it down, for example by instantiating a second note trigger handler..

tell me if you need any information about my setup.

I also have Clyph X (free version) installed from Github, but not active as a control surface. Maybe I could check the Max 8 version I use, switch to Live bundled version.

Best,
Marcus

[marcusfree]

So, I did some tests. Every time Note Trigger Handler stops working, I have then to restart Live to get it back to working again.


Changing to bundled MAX version in Live settings makes no difference.
I can load another Live set before using Note Trigger Handler, it makes no difference (it still works only one time, stops working after reloading tutorial Set).
I can load the first ClyphX Pro tutorial, makes no difference.
I can NOT load the Max For Live integration tutorial Live set, or after loading Note Trigger Handler Tutorial, it will not work.

The simple Max For Live integration tutorial example, switching metro on/off will always work, I can load the set as many times I like.


As the Note Trigger Handler also uses the same Javascript. 'clyphx_pro_interface.js' script, I think something is messing up initialization for the second time, but only in case of the Note Trigger Handler example this bug is triggered.

I hope this can be of some help.

BTW, I didn't report the bug over the official channel yet, should I?

Best, M

[kruegersc4]

Jan 26, 2023 15:53:35 GMT -5 davlar said:

Looks like the first time the note trigger handler (NTH) runs everything is ok and functions as expected, but if you load another set (without restarting live) with a note trigger rack and try using that you get the M4L error:

jsliveapi: 'DeviceManagerComponent' object has no attribute 'trigger_action_list'

So something not quite right with the get_device_manager.js script in the note trigger handler ?


Should add I'm using:
NTH version 1.0.4
Live 11.2.7
Windows 11

As a hobby Python programmer this type of error is familiar to me.. Maybe the state of something is different when Ableton initially starts, or upon starting another session there is an error (exception caught and handled incorrectly, or a less explicit error) that then causes the wrong object to get assigned / passed to a function.

I looked at the Note Trigger Handler M4L scripts briefly and it kind of looked like the issue goes beyond the scripts - though I'm not familiar enough with how the whole ClyphX system, and M4L, works. And we don't have access to the ClyphX Pro code... I'm assuming the Note Trigger Handler doesn't work with the open source ClyphX code?

[schlapbe]

Jan 26, 2023 15:53:35 GMT -5 davlar said:

Looks like the first time the note trigger handler (NTH) runs everything is ok and functions as expected, but if you load another set (without restarting live) with a note trigger rack and try using that you get the M4L error:

jsliveapi: 'DeviceManagerComponent' object has no attribute 'trigger_action_list'

So something not quite right with the get_device_manager.js script in the note trigger handler ?


Should add I'm using:
NTH version 1.0.4
Live 11.2.7
Windows 11

I am quite sure it is the M4L bit, which is causing the problems. What it does, it looks for midi notes, and if played, it pulls the name of the pad an passes that to the ClyphX bit. and that is through the "trigger_action_list" bit.
I know a M4L specialist and ask him to have a look at this bit.....

The note trigger rack is such a valuable device, it is important to fix this once an d for all!