No internet connection
  1. Home
  2. Packages
  3. Track Data Utilities

Bulk Copy Paste?

By Brett Ryan Stewart @Brett_Ryan_Stewart
    2022-01-19 02:44:31.194Z

    Hey @Chris_Shaw Wondering if there's a way to bulk copy paste track data?

    Like, i've got a template of drum tracks setup with all their inserts, sends, etc.
    I import a new song's drum tracks in raw audio.
    Then I copy / paste the template tracks to the raw audio (as opposed to moving the raw audio onto the template tracks.

    Make sense?

    Reply
    • 9 replies
    1. Chris Shaw @Chris_Shaw2022-01-19 17:56:26.411Z2022-01-19 18:40:51.842Z

      The best way to go about this is to use track presets.

      Create a track preset for each track in your template and create a deck/surface with all of your presets:
      Then create a script that recalls each preset like this (be sure to change the menu path for each one:

      sf.ui.proTools.appActivateMainWindow()
sf.ui.proTools.selectedTrack.titleButton.popupMenuSelect({
    isRightClick: true,
    menuPath: ["Recall Track Preset", "Avid", "Channel Strips", "Bass Amp"],
});

      Then after importing your raw audio as new tracks, select each one and apply the appropriate track preset via your deck/surface.

      Once you've made track presets for all of your track types then you don't need to have those tracks in your session template anymore. You'll only need your FX returns, subgroups, etc

      I have a massive set of session prep scripts that I use in this way. I import the client's audio / tracks into the bottom of my mix template then I have scripts that apply the appropriate preset and move the tracks up into my session and into the right position. My track presets apply inserts, sends, routing, track, color, and group. After I've applied and moved everything I have another script that automatically assigns the groups to my VCAs.

      I may publish a package so that other people can use it but it is so fined tuned to my system that it will take me a while to get to work for everyone.

      Reply1 Like
      1. Brett Ryan Stewart @Brett_Ryan_Stewart
          2022-01-19 18:05:31.077Z

          Holy moly this is genius! Ok this will def be my most intensive build attempt yet. I'll report back, possibly with questions, haha. Thanks Chris!

          Reply
          1. In reply toChris_Shaw⬆:
            Brett Ryan Stewart @Brett_Ryan_Stewart
              2022-01-20 22:23:46.806Z

              @Chris_Shaw Ok diving in to build this.
              Couple questions right out of the gates:

              1. Do I need to individually select tracks in the template when creating presets, or can I select all tracks/ busses, etc, and create the preset that way. (I mean, I know that that is possible to make presets in bulk, but jw how it needs to be done for this purpose...)

              2. I'm not sure how to populate these presets on a deck.

              3. If I'm then creating a script that recalls each preset, don't I need to put that script on the deck, rather than the deck itself?

              4. Would it be one and the same to make presets for FX returns, subgroups, Etc and just create them via "New Track"? Or should I create a template that ONLY has those things, and no empty "audio tracks" since I'll have presets for those?

              This is super badass and I'd love to eventually build like you have it! Thanks for sharing this walkthrough :-)

              Reply
              1. In reply toChris_Shaw⬆:
                Brett Ryan Stewart @Brett_Ryan_Stewart
                  2022-01-21 01:07:02.195Z

                  @Chris_Shaw Ok so I think I figured out most of the above.
                  Maybe you could just clarify something for me, regarding your workflow.

                  Do you have to remake a new deck with new scripts for each project?
                  Like, if you're jumping between projects, and you get a new one that doesn't quite fit the template, track-wise, do you have to go and edit each script for each track again? Or create a new menu path?

                  Sorry this might be easier than I'm making it. I'm sure it's streamlined I just can't wrap my head around it. Thanks :-)

                  Reply
                  1. Chris Shaw @Chris_Shaw2022-01-21 14:55:25.568Z

                    Just create a script for each track preset that you need and assign each of those presets to a key/button on your deck.

                    No need to create a preset with multiple tracks, you just need one for each track type (E. GTR, Bass, Kick, Sn, Keys, etc).

                    You can select multiple tracks and recall a preset and that preset will be assigned to all selected tracks.

                    Reply1 Like
                    1. Brett Ryan Stewart @Brett_Ryan_Stewart
                        2022-01-24 23:03:21.242Z

                        Thanks @Chris_Shaw . Is it possible to save the track name with it's preset? It doesn't seem to be an option within PT, but wondering that's part of your WF using macro.

                        Reply
                        1. Chris Shaw @Chris_Shaw2022-01-24 23:29:59.728Z

                          You can name the preset with the track name:

                          Here's a screen shot of the presets that I have stored and the deck I use to recall them:

                          Reply1 Like
                          1. Brett Ryan Stewart @Brett_Ryan_Stewart
                              2022-01-24 23:34:40.649Z

                              Thanks Chris. I may've misspoke. What I mean is, when recalling these presets to a new track or existing track, is it possible to have that command rename that track with the preset name?

                              Reply
                              1. Chris Shaw @Chris_Shaw2022-03-03 15:04:09.705Z

                                Sorry I haven't responded to this earlier - been very busy with a few projects.

                                A track preset doesn't name the track so the best solution would be to build a macro/script that recalls the track preset on the selected track and then in the next step renames the track.

                                Reply1 Like
                    ReplyAdd progress note