• Isadora
  • Get it
  • Forum
  • Help
  • ADD-ONS
  • Newsletter
  • Impressum
  • Dsgvo
  • Impressum
Forum
    • Categories
    • Recent
    • Popular
    • Tags
    • Register
    • Login

    [ANSWERED] What's more efficient/recommended?

    How To... ?
    3
    7
    235
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      Weston
      last edited by DusX

      When utilizing an active scene workflow, and manipulating active scene actor values numerous times throughout a show file, is it best practice to put the heavier actors (envelope generators for example) on the individual cue side, and then transmit the change of values back to the active scene via broadcaster/listener? This keeps the active scene much lighter... but is heavier information transmission. OR would you recommend keeping all of your envelope generators on the active cue side, and just transmitting the triggers from the individual cue (via broadcaster/listener) making the active cue a heavier cue but the transmission a simple trigger. Or does it not matter which? Hope i'm coming across and making sense!

      Thanks! 


      MacBook Pro 15" 2017 | Mojave 10.14.6
      2.8 Ghz Intel Core i7 | 16 GB 2133 MHz LPDDR3 | Radeon Pro 560 4GB

      DusXD 1 Reply Last reply Reply Quote 0
      • DusXD
        DusX Tech Staff @Weston
        last edited by

        @weston

        I don't believe it matters.

        Each scene is processed in the same processing engine, so no benefit to specific locations. 

        Also the listener/broadcaster message system works nearly identically to a link connected between actors, so again there is no savings either way.

        What is important is turning off unused elements. If you have a complex scene, I highly recommend wrapping sections/features into user actors, and using the User Actor on/off actor to disable user actors that are currently unused.(turn them back on when needed)

        This reduces the number of components the engine needs to look at and will improve performance. Basically if a user actor us set to Off, Isadora doesn't need to look at any of the contained actors. This can be substantial, especially when user actors contain other user actors.

        Troikatronix Technical Support

        • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
        • Isadora Add-ons: https://troikatronix.com/add-ons/
        • My Add-ons: https://troikatronix.com/add-ons/?u=dusx

        Running: Win 11 64bit, i7, M.2 PCIe SSD's, 32gb DDR4, nVidia GTX 4070 | located in Ontario Canada.

        W 1 Reply Last reply Reply Quote 1
        • W
          Weston @DusX
          last edited by

          @dusx 

          That is awesome. Thank you for the great advice! I had no clue I could manually turn user actors on/off... I will absolutely be looking into implementing that. 
          Much thanks!!
          Wes


          MacBook Pro 15" 2017 | Mojave 10.14.6
          2.8 Ghz Intel Core i7 | 16 GB 2133 MHz LPDDR3 | Radeon Pro 560 4GB

          DusXD 1 Reply Last reply Reply Quote 1
          • DusXD
            DusX Tech Staff @Weston
            last edited by

            @weston

            It is a really powerful feature. One thing to be aware of is that turning On the User actor, triggers the INIT function of all contained actors.
            This is actually very useful, but can be confusing if you are not aware.
            I suggest using the User Actor on/off within the user actor as a way of seeing the INIT occur (note. you can copy this actor to the main scene patch, and force the re-INIT of all actors as well... super helpful)

            Troikatronix Technical Support

            • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
            • Isadora Add-ons: https://troikatronix.com/add-ons/
            • My Add-ons: https://troikatronix.com/add-ons/?u=dusx

            Running: Win 11 64bit, i7, M.2 PCIe SSD's, 32gb DDR4, nVidia GTX 4070 | located in Ontario Canada.

            W 1 Reply Last reply Reply Quote 0
            • W
              Weston @DusX
              last edited by

              @dusx


              I can't seem to find how to turn user actors on/off.. can you please clarify how this works? 

              TIA!! 


              MacBook Pro 15" 2017 | Mojave 10.14.6
              2.8 Ghz Intel Core i7 | 16 GB 2133 MHz LPDDR3 | Radeon Pro 560 4GB

              WolandW 1 Reply Last reply Reply Quote 0
              • WolandW
                Woland Tech Staff @Weston
                last edited by Woland

                @weston

                1. Place a User Actor/Macro
                2. Go inside the User Actor/Macro
                3. Place a User Actor On/Off actor (they can only be placed inside a User Actor or Macro)
                4. Place a User Input actor (they can only be placed inside a User Actor or Macro)
                5. Connect the two actors

                6. Leave the User Actor/Macro
                7. Your User Actor/Macro now has an on/off switch on the outside

                TroikaTronix Technical Support
                New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
                TroikaTronix Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
                TroikaTronix Add-Ons Page: https://troikatronix.com/add-ons/

                | Isadora 3.2.6 | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

                W 1 Reply Last reply Reply Quote 2
                • W
                  Weston @Woland
                  last edited by

                  @woland 

                  Ah!! Amazing. Thank you. I kept trying to bring up the on/off actor outside of the user actor which is why it wasn't appearing. 

                  Much appreciated! 


                  MacBook Pro 15" 2017 | Mojave 10.14.6
                  2.8 Ghz Intel Core i7 | 16 GB 2133 MHz LPDDR3 | Radeon Pro 560 4GB

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post