Post by oconnorstp on Dec 16, 2018 11:01:53 GMT -5
Well... dang! While restarting Live, reloading the preset and restarting the Launchpad didn't clear the problem last night, restarting the *computer* did clear it. And I can't reproduce it this morning after that restart. rats! I should have run the Debug last night while the rascal was misbehaving. Lesson learned -- I'll grab that debug data right away the next time.
Today I tried it with and without the [IDENT] brackets and can confirm Stray's comment -- no problem either way. Sorry for the false alarm.
Post by cliffhanger on Dec 16, 2018 11:34:34 GMT -5
actually I have also had this happen on occasion , particularly with the M4L Trigger Handler device . being a newbie I've assumed it was me making mistakes in syntax or whatever , but on some occasions I've reloaded LiveSet next day & actions that didn't work before then worked .
hope this is relevant , I know it's not a chat forum , but I was passing....
A long time has passed, but the Keys accessory finally started acting up again. This time it's a simpler problem -- it just isn't doing anything.
The setup is the same:
- using a Launchpad Pro with a few simple key-command scripts on buttons -- the two I'm testing in this DEBUG session are:
[mute clip] KEY 0 and
 KEY MOD DN ; KEY R ; KEY MOD UP
- MT Player is at v1.8.0 and I've tried both the ClyphX Pro Keys * and the ClyphX Pro Keys [Thru] projects. Those two .bmte scripts are the Apr 25, 2018 versions, which is the same as what I got when I re-downloaded the installer a few minutes ago (thinking I might need to re-install).
- Launchpad is being driven by the "ClyphX Pro for LP Pro v1.0.2.amxd" M4Live script
- Clyphx Pro is the first control surface in Midi Settings, Input is set to "None" and Output is set to "To MT Player 1" (many other non-Keys scripts on Launchpad buttons are working fine)
I set up the DEBUG X-Clip and here are the results of a very short session where I launched DEBUG and then hit the two Launchpad Pro buttons with those two scripts.
Everything looks good in the log. Have you tried using other shortcut such as save (KEY MOD DN ; KEY S ; KEY MOD UP)? The reason I ask is because the save shortcut is global (works regardless of what is in focus or what is selected). By comparison, the shortcuts you mention both do different things (or potentially nothing at all) depending on what part of Live's window has the focus and what is selected within that focus. As an example, the rename shortcut won't do anything if the browser is in focus or if the main view is in focus but no clip is selected. If you find that a particular shortcut isn't working, always make sure to try triggering that same shortcut from your keyboard as it's probable that it won't work there either.
As a side note, keystrokes should only be used as a last resort. We have an action for toggling the muted state of a clip which, unlike the related shortcut, always toggles the muted state of the selected clip regardless of what's in focus. That's SEL/CLIP(SEL)
Ah! Thanks for the SEL/CLIP(SEL) tip. It's very close to what I'm trying to do -- but in my case I'm trying to mute a range of selected clips (or notes). Your suggested string seems to act only on the single clip selected by ClyphX (bordered in red) rather than the range of clips I've selected with the mouse (which can be non-contiguous and can span several tracks). It behaves just like CLIP MUTE, right?
I tried both of your suggested tests and neither worked. New DEBUG log is attached. The keyboard command to Rename a clip worked from the keyboard, but didn't with the script. And the Save command didn't trigger the save.
I agree about keyboard-commands -- they're definitely not my preferred route. It's true that key-commands are context sensitive, but sometimes that's actually quite useful. I've used key commands where I haven't been able to figure out how to do things in ranges (and especially discontinuous ranges) and are also able to act on a variety of objects depending on the context. Another good example is the Delete key-command which can be applied in weird ranges, across a variety of objects.
Any ideas about deeper-debugging I could do to get this rascal running again? Happy to do draconian stuff like a re-install, but it would be nice to avoid that if I can.
Post by oconnorstp on Jun 11, 2019 10:27:52 GMT -5
Thanks again for all the help today. My "homework" was to delete the Keyboard Maestro app and see if it was mucking around at a really low level in the keyboard stack. No such luck. Deleted the app and the puzzler lives on. That concludes my report. ;-)