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

    using 'run-only' remotely on another computer in 'demo' mode?

    How To... ?
    3
    6
    226
    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.
    • NotdocN
      Notdoc
      last edited by

      I have read the 'How-to' support page on 'How to move an Isadora Show to another Computer' and I'm looking for a bit more detailed advice, and tips from people who have used this method to put art-work in place remotely ( = I won't be there!).

      I would like to be able to send a simple single-screen Izzy show via email or download to someone else with no Izzy expertise to install as run-only in demo mode. 

      The show potentially contains customised GLSL shaders which normally reside in the plugins folder on my computer.

      Will these be found if I add a 'GLSL Plugins' folder to the project folder? Or will the code be embedded in the saved project? It seems like it's different from loading image/movie/audio media..?

      any other related tips welcome, but the shader code is my main concern. I'm not able to test at home as my other machine is too old for Izzy 3.

      Ventura 13.0 on Macbook Pro 14-in M1 Max 2022

      DusXD WolandW 2 Replies Last reply Reply Quote 0
      • DusXD
        DusX Tech Staff @Notdoc
        last edited by

        @notdoc

        The GLSL code is not copied into the actors when you use GLSL Shaders from your toolbin which reside in the shaders folder, and and they are not found if added to the folder with the IZZ file.
        The GLSL text files will need to be placed in the ...TroikaTronix\GLSL Plugins folder on the installation machine.
        I would instruct the user to open this folder via the Help/Open Plugin Folder/Troikatronix GLSL shaders menu option, then add the TXT files and then restart Isadora.

        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
        • WolandW
          Woland Tech Staff @Notdoc
          last edited by Woland

          @notdoc said:

          The show potentially contains customised GLSL shaders which normally reside in the plugins folder on my computer.

          If you copy and paste the code from the customized shaders into normal GLSL Shader actors and then use the normal GLSL Shader actors instead you won't need to load them in as plugins.

          If you need to update them globally, do the same as I said above, but wrap the normal GLSL Shader in a User Actor.

          If you do the above, the GLSL Shaders won't need any external text files in order to work.

          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 |

          NotdocN WolandW 2 Replies Last reply Reply Quote 1
          • NotdocN
            Notdoc @Woland
            last edited by

            @woland @DusX 


            thanks. i appreciate both your responses, but I'm still a bit confused, as the two seem to be opposed. 

            @DusX - this seems clear. the installation computer running demo mode needs the relevant GLSL code to be added to the folder for the patch to work.

            @Woland - you seem to be saying that it WILL be saved within the patch, but that I need to transfer the code into a new GLSL Actor..? Otherwise I'm not really sure what you mean by 'normal' GLSL Shader actors. 

            I think I need to test this...

            Ventura 13.0 on Macbook Pro 14-in M1 Max 2022

            NotdocN 1 Reply Last reply Reply Quote 0
            • NotdocN
              Notdoc @Notdoc
              last edited by

              @notdoc said:

              @woland @DusX 

               ok. i get it. Thanks

              To save shader code inside the project, the code has to be cut & paste into a new GLSL actor in every instance. Otherwise the customised actor needs to be saved in a GLSL folder on the destination computer in order to be found by Isadora. 

              This makes sense, but it's a bit fiddly. Forgive my ignorance, but would it be very difficult for Izzy 'run-only' files to save/embed code that is active within the saved project scenes? It doesn't seem to be more complex than saving any other project-specific settings...

              I'm going to make a feature request and find out...

              Ventura 13.0 on Macbook Pro 14-in M1 Max 2022

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

                @Notdoc said:

                To save shader code inside the project, the code has to be cut & paste into a new GLSL actor in every instance.

                See my comment below, you don't need to paste the code into a new GLSL actor in every instance.

                @woland said:

                If you need to update them globally, do the same as I said above, but wrap the normal GLSL Shader in a User Actor.

                More specifically:

                1. Put the GLSL code into one GLSL Shader actor.
                2. Create a User Actor.
                3. (Optional) Rename the User Actor to whatever you want.
                4. Copy the GLSL Shader actor (with the code inside it) and paste it inside a User Actor.
                5. Create User Inputs for the video in, height, width, and any other parameters you want to expose and connect them to the inputs on the left side of the GLSL Shader actor.
                6. Create a User Output for the video out and connect it to the video out of the GLSL Shader.
                7. Leave the User Actor and Save & Update All.
                8. (Optional) tRight-Click the User Actor and select "User Actor to Document Toolbox"
                9. Now you can go to the User Actor bin (the one with the little person icon) and from there you can add the User Actor anywhere in the file that you need that particular GLSL code. Also, if you go inside the User Actor and make changes to the code of the GLSL Shader, you can save and update all to push those changes to every instance of the GLSL Shader User Actor that are in the file.

                Best wishes,

                Woland

                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 |

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