No internet connection
  1. Home
  2. How to

Turn Off Script Log

By Richard Furch @Richard_Furch
    2022-12-03 07:42:45.536Z

    Is it possible to turn off all notifications? Most of my commands trigger some kind of report, but it's both distracting and with a wide screen for some reason right in the middle. Would love to turn off until I actually need to debug something. Thanks!

    • 4 replies
    1. Hi Richard,

      It's not possible to turn off the notifications globally. But your scripts shouldn't send those in the first place, unless you want them to. I can't tell from what you're describing if it's related to built-in scripts you're using that for some reason report errors (in which case those errors should be looked at), if you're using content from the Store that sends notifications (in which case those should be deleted from the scripts) or some other reason.

      To get help with the specific scripts, see here:
      https://soundflow.org/docs/help#script-help

      1. J
        In reply toRichard_Furch:
        John Richardson @John_Richardson
          2023-01-17 21:15:43.163Z

          @chrscheuer , I'm having this issue too, when I'm running your script I found on this post, Bypass last plugin in master fader

          It runs perfectly fine, but looks like it's popping up notifications in the upper right, where I'd expect error logs, but looks like it's just duplication what I see when I open the Log on that specific macro script.

          Here is the script in question

          const trackName = 'Master 1';
          const pluginName = 'FabFilter Pro-MB';
          const insertNumber = 10;
          
          function bypassToggleInsert(trackName, pluginName, insertNumber) {
              sf.ui.proTools.appActivateMainWindow();
              sf.ui.proTools.mainWindow.invalidate();
          
              //Make sure Inserts A-J are visible
              sf.ui.proTools.menuClick({ menuPath: ['View', 'Edit Window Views', 'Inserts A-E'], targetValue: 'Enable' });
              sf.ui.proTools.menuClick({ menuPath: ['View', 'Edit Window Views', 'Inserts F-J'], targetValue: 'Enable' });
          
              //Get track by name
              const track = sf.ui.proTools.trackGetByName({ name: trackName }).track;
          
              //Show the plugin
              track.trackInsertToggleShow({ insertNumber: insertNumber });
          
              //Plugin Window
              const pluginWindow = sf.ui.proTools.windows.whoseTitle.is('Plug-in: ' + pluginName).first;
          
              //Wait For plugin window
              pluginWindow.elementWaitFor();
          
              //Bypass Button
              const effectsBypassBtn = pluginWindow.buttons.whoseTitle.is("Effect Bypass").first;
          
              //Toggle Bypass Button
              if (effectsBypassBtn.value.invalidate().value !== 'on') {
                  effectsBypassBtn.elementClick();
                  log(`The plugin "${pluginName}" on track "${track.normalizedTrackName}" has been disabled`);
              } else {
                  effectsBypassBtn.elementClick();
                  log(`The plugin "${pluginName}" on track "${track.normalizedTrackName}" has been enabled`);
              }
          
              //Close Plugin Window
              pluginWindow.windowClose();
          }
          
          bypassToggleInsert(trackName, pluginName, insertNumber);
          
          1. Kitch Membery @Kitch2023-01-17 21:42:01.481Z

            Hi @John_Richardson,

            This script has lines that log information via notifications.

            On lines 31 & 34, just comment out the code by adding two forward slashes // at the beginning of the line.

            for example, change line 31 from this.

                    log(`The plugin "${pluginName}" on track "${track.normalizedTrackName}" has been disabled`);
            

            to this.

                    //log(`The plugin "${pluginName}" on track "${track.normalizedTrackName}" has been disabled`);
            

            Let me know if that works for you. :-)

          2. J
            In reply toRichard_Furch:
            John Richardson @John_Richardson
              2023-01-17 21:50:44.653Z

              Ah that fixed it!! Thanks @chrscheuer !!