• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    Copy Changes in one Scene to others

    Feature Requests
    5
    8
    2307
    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.
    • D
      DillTheKraut last edited by

      If you have alot of scenes, and you have to change things, that need to be changed in others as well, to just copy them in.

      Something like a funktion "Do changes to all Scenes","...folowing scenes", "scenes before".
      1 Reply Last reply Reply Quote 0
      • vanakaru
        vanakaru last edited by

        I thought of something, but it did not work.

        MBP 4.1 & MBP (Retina, Mid 2012) MBP Retina 2017

        1 Reply Last reply Reply Quote 0
        • Maximortal
          Maximortal last edited by

          use broadcaster and listeners actors

          Iro Suraci | Win 10 - Ryzen 3600 - 32GB - nVidia gtx 960 4gb / Win 10 - i5 4210U - 8 GB - R5 M230 | Isadora 3.0.7| Located in Brescia, Italy

          1 Reply Last reply Reply Quote 0
          • vanakaru
            vanakaru last edited by

            Uhh! I forgot to make scenes active. Broadcaster will talk to Listener on active scene only.

            MBP 4.1 & MBP (Retina, Mid 2012) MBP Retina 2017

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

              This is one of the great benefits to using User actors extensively, and probably the only way to make cross scene updates.

              Listener and Broadcasters are great for passing data between active scenes.

              Troikatronix Technical Support

              • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
              • My Add-ons: https://troikatronix.com/add-ons/?u=dusx
              • Profession Services: https://support.troikatronix.com/support/solutions/articles/13000109444-professional-services

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

              1 Reply Last reply Reply Quote 0
              • D
                DillTheKraut last edited by

                Sorry, for answering so late, haven't seen the answers. Should change my notices Mailadress ;-).

                I think you guys misunderstood me. I asked for what your answers describes here at a different post. The only real solution to update Values cross Scene, is the Data array actor, that writes values at a certain point and read 'em at scene load.
                but what i'm asking here is something different! I meant changes in the patches, as putting one or more new actors in several scenes witch are build in the same way.
                Maybe you have ten Scenes, all with a (maybe nearly) same structure of actors. Maybe only to have a nice Fade between the Scenes. And now you want a new effect in ALL scenes. At the moment you have to go to each scene separately and disconnect patches, put the new actor and the new connections to other actors, and this all ten times.
                Great would be some kind of batch recorder. Like in photoshop. You start do a recording of your changes in one scene and repeat (replay) them in others needed.
                1 Reply Last reply Reply Quote 0
                • T
                  tadakan last edited by

                  The answer is definitely DusX's reply. Use user actors. Build your whole signal chain inside of one. If you need to differentiate media values between scenes or something, pipe the values in from outside the user actor. Any changes made to one user actor can be saved and updated across all user actors. Until you make it a seperate actor, in which case you would lose that functionality.

                  OSX 10.11.6 on 15" rMBP from Oct. 2014. 2.5ghz i7 16gb ram.

                  1 Reply Last reply Reply Quote 0
                  • D
                    DillTheKraut last edited by

                    Ah, thank you tadakan! And DusX as well for sure...

                    It is kind of pretty obvious, but now i understood it!
                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post