Goto Next Marker Seems to tie up SF Longer than it used to.

Title

Goto Next Marker Seems to tie up SF Longer than it used to.

What do you expect to happen when you run the script/macro?

Goto Next Marker

Are you seeing an error?

What happens when you run this script?

Since going to the latest PT beta I'm finding that after the cursor moves to the next marker, if I hit Separate Clip at Selection too quickly the command does not register. This didn't used to be the case.

I may remap those commands to use the now built in commands. But for some reason your marker navigation seems more responsive/quicker than the built in ones.

How were you running this script?

I used a keyboard shortcut within the target app

How important is this issue to you?

5

Details

{
    "inputExpected": "Goto Next Marker",
    "inputIsError": false,
    "inputWhatHappens": "Since going to the latest PT beta I'm finding that after the cursor moves to the next marker, if I hit Separate Clip at Selection too quickly the command does not register. This didn't used to be the case.\n\nI may remap those commands to use the now built in commands. But for some reason your marker navigation seems more responsive/quicker than the built in ones.",
    "inputHowRun": {
        "key": "-Mpfwh4RkPLb2LPwjePT",
        "title": "I used a keyboard shortcut within the target app"
    },
    "inputImportance": 5,
    "inputTitle": "Goto Next Marker Seems to tie up SF Longer than it used to."
}

Source

sf.ui.proTools.memoryLocationsGotoDelta({
  delta: 1,
});

---

Links

User UID: KI5JeIGNSQbxx0hwB8QOimtFV812

Feedback Key: sffeedback:KI5JeIGNSQbxx0hwB8QOimtFV812:-NznpJ58HJ6SCpx1mVwT

Feedback ZIP: iZGysuAKLz60fEwIkJcCDxHKZbnCIhTzuOmaQV+Te1Ink31bY0DKcAZuVh7vqbbjDNRXnwBJyX2eLYjNoItJHFc+AFZc+XKeIyMCP5vKkzgqceHaIrEN2Gp3v2QfeNM2wriggLzL/u8iWXi0jVAmYKuCIXIIgTGCKrcG8kItt5jnYyCUHOs/Vyr7b4vEY9qTnbCaoyJzeXSM6BcaclwNzCC2GDSWxdkzeH5F+mmFrvHCSVBRXC8DFySoRBkAg5psSVUW+m2sQVGasPE6TgeULkVP9CvOZDcUpX99OGPe9sjo6SUOYL53a/NS2IMFMcFxnQNPkbXuMF/9LzhLKisTHA==