No internet connection
  1. Home
  2. Packages
  3. ADR CUE Creator

GRP Scene Cue Issue I'm facing

By Brian Armstrong @Brian_Armstrong
    2023-06-05 08:26:15.945Z

    Hey Owen!
    I have a question about the "GRP =SCENE=" template. Let's say I'm on DX GUIDE track when making my selection, when I run the script (via Stream Deck and via hitting "run script") it jumps the scene track, makes the correct selection but then goes back to DX GUIDE before prompting for the choices for clip name info, then it creates a clip, renames it, cuts it, moves it to the first of my listed tracks that doesn't have a conflict and pastes it there, but then I think it goes back to DX GUIDE and does a slide clip function. I did a screen record, but I don't think I can upload videos here. Hope linking to YouTube is ok.

    Thanks Owen. I have some other ideas as well such as the ability to pull Scene Info from the Sc Cut Track. Or if there are ways to use a text (or tab) file to populate the location options. That and a few other "Brian" ways of doing things. I look forward to implementing these scripts into my workflow!!

    Solved in post #4, click to view
    • 5 replies
    1. S
      SoundFlow Bot @soundflowbot
        2023-06-05 08:26:17.881Z

        Thanks for posting a question or an issue related to the 'ADR CUE Creator' package.
        This package is made by @Owen_Granich_Young. We're auto-tagging them here so that they will hopefully be able to help you.

        Please note, that the best way to get help with a script, macro or other content installed from the Store is to select the script you installed, then click the red Need help button, and then click "Get help with this script or macro".
        By using this workflow, the developer of the package will get access to more information so they'll be able to help you quicker.
        You can read more about how to best get help in this article: bit.ly/sfscripthelp

        1. O
          In reply toBrian_Armstrong:

          Yo bud,

          So yes this is working as intended. -- And as intended is not ideal. The first problem being the check and paste aspect of the script is actually just a rip of this script here - Move clip to specified track - if partial or full overwrite move to next track - because the original script was moving an already existing file, the way this version is scripted creates a group on your currently selected track before moving it around. Obviously if your currently selected track has regions and or files on it those will get grouped in and moved... not ideal. At the time I couldn't warp my head around unpacking that script to get the pieces I needed out, I think I can now... The second issue as noted in the documentation for the script - the original script also fails if the cue is the exact same length, it will overwrite, so if you're doing multiple fulls scene cues, i've 'hacked it' to do a one frame shift so you can continue to cue full length scenes. Once again.. not really an ideal workflow.

          TBH I've pretty much abandoned use of this script myself in favor of a 2 button solution while on my group tracks because I realized this wasn't really helping me personally anymore. I press a 'select scene' button and then use the https://soundflow.org/store/pkg/pro-tools-spotting App to create a cue.

          I'd love to take the time to build this template back from the ground up, I do have the code to be able to pull the scene track name to include in your cue (I'll include it below). I'd also like to change the choice arrays from fixed preset list to a json list that every time you enter a new one it then loads into the list for quick access the following time.

          Here's get current clip name so you could select the scene track then grab the clip name to include in the new cue.

          function getCurrentClipName() { //This gets the current region name in Pro Tools
          
              const clipNameWin = sf.ui.proTools.windows.whoseTitle.is('Name').first
              try {
                  clearFind();
                  sf.ui.proTools.menuClick({ menuPath: ['Clip', 'Rename...'] }, `could not find rename window`);
                  clipNameWin.elementWaitFor({ onError: "Continue" });
                  let currentClipName = clipNameWin.groups.whoseTitle.is('Name').first.textFields.first.value.invalidate().value;
                  clipNameWin.buttons.whoseTitle.is('Cancel').first.elementClick({}, `could not click Rename window: cancel button`);
                  return currentClipName
              } catch (err) {
                  throw `error in getCurrentClipNameWin(): ${err}`
              }
          }
          
          1. O
            In reply toBrian_Armstrong:

            I've published a version 2.7.0 with some upgrades.

            I've fixed the first problem with the GRP cues, it will no longer create the group first, it will navigate through and find a free track before creating the group. I've also included the option to turn off the SHIFT at the end.

            I also posted the package we worked on together for Edicue session interface instead of SF prompts.

            Bests,
            Owen

            The exact length issue is not fixed yet, nor is the ability to pull the scene data from the Scene Track name.

            Reply1 LikeSolution
            1. BBrian Armstrong @Brian_Armstrong
                2023-06-05 17:31:21.875Z

                Not that I'm impatient for this... but as a curiosity question, how long does it take for a package to update in the store once submitted?

                1. I've always found it a little bit funky. Try quitting out ENTIRELY from soundflow and re-opening.