No internet connection
  1. Home
  2. How to

Talkback Toggle on Pro Tools transport

By Koenraad Foesters @Koenraad_Foesters
    2022-12-28 13:45:53.470Z

    I want to toggle a midi command whenever Pro Tools starts running or stops running (or on MTC).
    Is that possible?

    I found this script that works, it's not capable of toggling on start and stop.
    How to trigger a command whenever Pro Tools transport is stopped

    So basicly I actually need a script that sends a midi message whenever PT runs and also one that sends one when PT stops running.

    Thanks!

    • 16 replies
    1. O

      Hey Koenraad, how are you triggering record and stop? Easiest approach would be to make two stream deck buttons for Rec & Stop that also have the midi triggers slaved to that same key press. Of course if you're using CMD+spacebar and spacebar that might not be ideal. Just thinking about the easiest solution first.

      In theory though you could piggy back your Midi triggers onto whatever keyboard commands you use to record and stop/play as well...

      1. Good thinking, but indeed, I always use command+spacebar so that would be difficult…

        I now always use a midi clip that sends a sustain message to toggle on and off whenever PT starts or stops.
        The problem is that whenever clients come in, they always forget to add that to their session so
        I try to search for something that is permanent and triggered external instead of inside PT like the talkback on a C24.

        1. Just have a button to auto import that track? Easier for them to remember?
          Creating an "Import Mix Template" macro. #post-6

          I've actually just updated my Automated Protools Imports package to include the above scripts. You could simply make a button that pulls this into their session and when it's not working remind them to press the button. Feels like you already have a solid working solution you just need to make it easier for others to remember to use.

          I'm using this script all the time now to import my AudioBridge routing tracks so I can have Pandora blasting through the mains whenever I'm working :P

          1. Ow damn, totally missed this thread and possibility.
            This might be a pretty good solution actually!
            Thanks!

      2. Brenden @nednednerb
          2022-12-28 19:00:39.930Z

          I know it is technically not the most recommendable and could interrupt other workflows and operations, but in some instances I've found the best way to deal with some shortcuts is to now undo the default association in PT Keyboard Shortcuts, then takeover that shortcut in SF to do what it should normally do PLUS my extra desired functions. It could potentially be made into an SF "Profile" so it wouldn't always be active. I guess choosing that profile would become the thing that is forgotten!

          While there are certainly some concerns and provisos to consider with the above approach, the weight of the cause to do so might be significant enough to do it!

          Is there another way to NOT interrupt the official command and simply listen for the keypress to add on functions? As you put it Owen, "in theory" I figure SF might potentially be made in the future to do something like that to "piggyback" a macro/script onto another key command that still fires...

          1. Yeah indeed, but the risk of interrupting the standard PT workflow is something I'm not thrilled on.
            But it could be possible more easy I think... I know Christian posted somewhere that soundflow has a internal MTC reader, so basicly soundflow could just trigger a command on MTC start and one on MTC stop, right? @chrscheuer ?

            1. Hi Koenraad,

              Triggering things in SF based on events happening in PT is a bit tricky today. You could search for runForever on the forum to see examples of scripts running in the background checking for state changes and reacting to that.

              We'll get native support for things like this in a future SF version.

              1. Ok, nice!
                I tried out using the run forever scripts but they sometimes did weird things and I know too little coding stuff to change them in they way I want them :-) ...
                The import template macro tip from Owen might help me out in the meanwhile!

          2. Ian Bodzasi @Ian_Bodzasi
              2023-01-15 16:51:38.182Z

              Would Mute-O-Matic work for what you're trying to do? If your talkback is on an aux, this will open & close it when playback starts/stops (and it's free).https://www.soundradix.com/products/muteomatic/

              1. SSean McDonald @Sean_McDonald5
                  2023-08-23 09:23:20.505Z

                  following this thread, as im looking for an "automatic" talkback feature like Mutematic, but with a physical "over ride" button. [ something mutematic doesnt have.] I find it a pain to open the plugin, and try and hit the correct GUI button to engage the TB during playback.

                  Also, Mutematic is a native [ non DSP ] plug, so depending on how/ where youre monitoring, and running your session, youre gonna get some strong latency, making conversing really tough.

                  So Im thinking we could build a solution, with a basic auto start/ stop based off of a separate track of printed tone, sidechained to the gated TB channel.

                  thats pretty simple.

                  then could we create a SF script to?

                  1. somehow mute the printed tone track feeding the TB gate DURING playback, to talk while rolling.
                    or
                  2. bypass the TB gate DURING playback, [ over riding the side chained signal] to talk while rolling

                  thanks for your consideration guys..

                  Best,
                  Sean

                  1. Ian Bodzasi @Ian_Bodzasi
                      2023-08-23 13:18:55.571Z

                      Can’t say I’ve had latency issues with Mute O Matic before, it should be fine. You could put together a simple script to bypass the plugin from a stream deck button or something on your keyboard.

                      1. In reply toSean_McDonald5:

                        Hi Sean,

                        Did you see my comment on FB suggesting you could achieve what you want by having two parallel listening tracks, one through Mute o Matic, one going straight (and set up with Pro Tools Track Control)

                    • S
                      Sean McDonald @Sean_McDonald5
                        2023-08-23 17:20:21.166Z

                        Thanks Christian,
                        I watched the video, are you saying that we could use a separate “override” channel along side the mutematic “auto” channel during playback.

                        I see how toggling that channel’s input from streamdeck would do that.

                        Though not seeing how we would solve the physical “mute override” when parked, where mutematic is normally open.

                        And if….. this channel needs to be in Hybrid mode, mutematic does not support AAX/ DSP.

                        Thanks again for the suggestion.

                        1. Yea exactly, it would fix one of the issues (overriding to unmute) but not the other.

                          But I'm thinking the easiest solution is probably just that the SF team builds an app that fixes this altogether / or add it to the existing Pro Tools Track Control app :)

                          1. SSean McDonald @Sean_McDonald5
                              2023-10-29 23:59:35.268Z

                              cool.

                              Id happily pay for a full featured talkback SF solution that could be mapped to tactile control.

                              How do I formally ask/ petition the big brained folks here for such a product?

                              thanks

                              1. Hi Sean,

                                Please create a new thread in the Ideas section, then we can log the request and keep everybody up to date :)