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

    Layerpriority in active scenes

    Troubleshooting and Bug Reports
    5
    11
    2.5k
    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

      Hello anyone,

      I found some strange behavior, but don't really know if it is wanted like that or a bug.
      create several scenes with a projector in each getting some input. create one scene with an activate scene actor only.
      If you now active the scenes, one by one with the activate scene actor, the last activated scene has the highest layer priority, always.
      This is regardless of the layer values that are set at the projectors in each scene.
      Is this wanted like that? It's not a big issue now, but I need to build a work around for a patch I do.
      I tried this with Isadora 2.2.2, 2.1, 2.0.5
      greatings
      Dill
      1 Reply Last reply Reply Quote 0
      • DusXD
        DusX Tech Staff
        last edited by

        This is interesting. Are you testing using Opaque layering?

        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.

        1 Reply Last reply Reply Quote 0
        • R
          Reinhard
          last edited by

          Just checked and can confirm that Izzy always places the last activated scene to the foreground, regardless of the layer settings. 541603-activate_scene_layer.izz

          mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

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

            Yeah, its on opaque too...

            1 Reply Last reply Reply Quote 0
            • N
              newsound
              last edited by

              I'm seeing the same thing using 2.2.2, however it works as expected in 1.3.1

              1 Reply Last reply Reply Quote 0
              • em_txE
                em_tx
                last edited by

                I experienced that too. Is there possibility to set layer priority somewhere. I work with layers and sometimes I am ending up in a mass.

                Dell G5 5587, i7 8750 H @ 2.20, NVMe Intel 512 GB, 2TB HDD, NVidia GTX 1060 6GB, MaxQ, RAM 32GB, Win 10
                Isadora 3

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

                  What layering mode are you using?
                  Grouped by scene, or ungrouped? (option in file/layering menu)

                  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.

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

                    Grouped by scene, at mine.

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

                      @DusX, sorry if I don't get this. Is this behaviour intended and related to the setting you mentioned? If yes I find it a bit irritating to see this "(v1.x Compatible)" as it seem to say it should not be used with new patches. ´

                      I could not find any description for this.
                      1 Reply Last reply Reply Quote 0
                      • DusXD
                        DusX Tech Staff
                        last edited by

                        The 'Grouped' method allows for the cleaner 'cinematic' style cross-fades introduced with Version 2.

                        The 'Ungrouped' option is compatible with older files (opening a earlier format file will automatically set this option).
                        'Grouped' is the new default. It basically flattens all output from a specific scene, so that it can be beautifully mixed with the next scene.
                        'Ungrouped' keeps each output in its set layer.. and allows for some very interesting cross mixing of media.(crossfades like bringing your fingers together and intermixing/locking the fingers)
                        I am unsure if the issue originally posted in this thread is intended behaviour or not.
                        A more detailed description of these mixing methods would be a great topic for an official Knowledge Base article.
                        @mark , is there more you can add? 

                        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.

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

                          @DusX Thank you for the detailed description. I think I understood now that my original issue is a by Izzy intended behavior, but can be switched by the 'grouped' setting. In this case the "(v1.x Compatible)" extension in the menu is a bit disturbing, as it could mean this feature might disappear in future versions.

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