• 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

    [ANSWERED] Jump By Name stops responding

    Troubleshooting and Bug Reports
    plugins
    4
    7
    1415
    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.
    • andielloyd
      andielloyd last edited by Woland

      Hi all! 

      Me & the team are currently in tech for a huge theatre production following a non-linear storyline. We are running most of the cueing from Jump By Name and today during Q2Q it stopped responding. We restarted Isadora, and the computer, started a new file, tested it in a new patch (didn't work), went back to our patch (didn't work), went back to new patch (it worked!) and back to ours and it worked again. 

      It is now working without issue, but we are wondering if it has to do with having too many scenes? (we are running 176 now), or if it's a bug? Or something else?

      Would love any insight we can get! 

      <3 <3 <3 

      Andie / Sammy / Shang-Han

      Isadora User since 2017 | Version 2.6.1 onwards

      :: Macbook Pro (2021, 16-Inch) Apple M1 Max, 64GB Memory, 1TB Storage

      bonemap Woland 2 Replies Last reply Reply Quote 0
      • bonemap
        bonemap Izzy Guru @andielloyd last edited by

        @andielloyd said:

        any insight we can get

         You should submit a ticket for this - if it is still unresolved.

        link to troikatronix support.

        Best Wishes

        Russell

        http://bonemap.com | Australia
        Izzy STD 4.2 | USB 3.6 | + Beta
        MBP 16” 2019 2.4 GHz Intel i9 64GB AMD Radeon Pro 5500 8 GB 4TB SSD | 14.5 Sonoma
        Mac Studio 2023 M2 Ultra 128GB | OSX 15.3 Sequoia
        A range of deployable older Macs

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

          @andielloyd

          In a pinch the native Jump To Cue actor can be used in many of the same circumstances to replace the Jump By Name actor if it's being finicky.

          TroikaTronix Technical Support
          New Support Ticket: https://support.troikatronix.com/support/tickets/new
          Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
          Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
          Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

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

          andielloyd 1 Reply Last reply Reply Quote 0
          • mark
            mark last edited by mark

            @andielloyd said:

            Would love any insight we can get! 

             Andie, I guess the answer will be "no", but could it have possibly been any kind of misspelling of the Scene Name? This actor is dead simple in what it does... it's difficult for me to imagine what might cause it to fail.

            The only other thing I can think of is that something went haywire with loading some particular scene, and no act (clicking on scene, space bar) would actually get the next scene to activate. Does that ring any bells?

            If you want to submit your 176 scene patch so we can try to recreate the problem, please send it by submitting a ticket.

            Best Wishes,
            Mark

            Media Artist & Creator of Isadora
            Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

            andielloyd 1 Reply Last reply Reply Quote 1
            • andielloyd
              andielloyd @bonemap last edited by

              @bonemap


              Thank you so much! It was resolved after a few restarts. 

              Isadora User since 2017 | Version 2.6.1 onwards

              :: Macbook Pro (2021, 16-Inch) Apple M1 Max, 64GB Memory, 1TB Storage

              1 Reply Last reply Reply Quote 1
              • andielloyd
                andielloyd @Woland last edited by

                @woland

                Will keep that in mind if we have similar issues in the future!

                Isadora User since 2017 | Version 2.6.1 onwards

                :: Macbook Pro (2021, 16-Inch) Apple M1 Max, 64GB Memory, 1TB Storage

                1 Reply Last reply Reply Quote 0
                • andielloyd
                  andielloyd @mark last edited by

                  @mark 

                  After some intense testing, and a few restarts, it inexplicably began working again. We aren't sure why, and don't really know what we did to make it work again. It just began responding like normal. 


                  If I run into this again, I'll document it more thoroughly and submit a ticket. Thank you for taking the time to respond to this, once it started working again I was so absorbed back into our tech that I didn't check back for the responses. 

                  Thank you Mark, @bonemap and @Woland for your time & help!

                  Isadora User since 2017 | Version 2.6.1 onwards

                  :: Macbook Pro (2021, 16-Inch) Apple M1 Max, 64GB Memory, 1TB Storage

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