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

    Unable to start Isadora with NON "Pete" Free Frame plug-ins

    Troubleshooting and Bug Reports
    4
    39
    8.8k
    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.
    • CitizenJoeC
      CitizenJoe
      last edited by

      @DusX That's exactly what's happening to me using version f24.

      The newer version crashes on start up.

      Cheers,

      Hugh

      Hugh in Winnipeg - All test machines, Win10 Pro, 64 bit, OS SSD and separate data SSD.

      1. new laptop: Dell 7560, i9 11950H, 64 gigs, NVIDIA RTX A4000 w/8 GB GDDR6
      2. old desktop: Dell T5500 2009, Dual Quad Core Processor E5530, 12 gigs, 2x Radeon 5750... Still works well!
      1 Reply Last reply Reply Quote 0
      • DusXD
        DusX Tech Staff
        last edited by

        Hmm.
        I am using the latest release.
        and just now tested f24.

        F24, reacts the same.. I can open, load patch, crashes when trying to show stage.

        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
        • markM
          mark
          last edited by

          Dear DusX + Citizen Joe,

          OK. So it's not an isolated problem. I will solve this. But first, we need to get you both up to a new version because, to debug the crash reports you're sending on Windows requires that I have an exact snapshot of the source code. I have this for 1.3.1f02, but you're not using that version. (I must have provided it to you along the way somehow, and I didn't take care to make this snapshot because I wasn't ready to put it on the pre-release page.)
          So, I'm going to get 1.3.1f04 out in the next 24-48 hours and then you'll need to do these crashes again for me. I'm sorry for the trouble on that.
          But finally, to be ultra clear:
          1) If the FF plugins in question **are not** in the FreeFrame folder, there is no crash at all, yes?
          2) If the FF plugins in question **are** in the FreeFrame folder, there is a crash, but you're not actually using the FF plugins you added, right?
          Best Wishes,
          Mark

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

          1 Reply Last reply Reply Quote 0
          • CitizenJoeC
            CitizenJoe
            last edited by

            Hi Mark,

            I must say that there is a certain comfort in not being alone....

            To answer your questions, 1) correct; 2) Isadora crashes on start up, so I can't get any further.

            Thank you,

            Hugh

            Hugh in Winnipeg - All test machines, Win10 Pro, 64 bit, OS SSD and separate data SSD.

            1. new laptop: Dell 7560, i9 11950H, 64 gigs, NVIDIA RTX A4000 w/8 GB GDDR6
            2. old desktop: Dell T5500 2009, Dual Quad Core Processor E5530, 12 gigs, 2x Radeon 5750... Still works well!
            1 Reply Last reply Reply Quote 0
            • DusXD
              DusX Tech Staff
              last edited by

              Mark.
              Yes to both.
              In my case the crash is only when opening the stage.
              I just triple checked this, and have it narrowed down to a sub folder of freeframe fx (~90).
              Isadora will crash if I have the freeframes in the folder when I open Isadora (no errors reported), and even with a blank/new patch show the stage (not a single actor added to the patch)

              I will send a crash report of the crash with a blank patch in just a moment.

              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
              • DusXD
                DusX Tech Staff
                last edited by

                I have found that I have 3 freeframe files causing this crash.
                I have emailed them to Mark for further investigation.

                I would like to add that in general freeframe is working very well for me.. I even have complex freeframes like Whorld (uses external files to generate visuals) running without any problems.

                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
                • markM
                  mark
                  last edited by

                  Dear DusX + Citizen Joe,

                  Well, Ryan's FreeFrame plugins work just fine on Windows 7 64-bit. Sigh... the saga continues. I'm working on compiling the new version as we speak. Then I'll be able to take a stab at your crash reports.
                  Best Wishes,
                  Mark

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

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

                    I have submitted all the data I can gather.
                    Let me know if anything else will help.

                    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
                    • CitizenJoeC
                      CitizenJoe
                      last edited by

                      Hi Mark,

                      I submitted the bug report - sorry it took so long.

                      BUT - you've made some changes I think!  The "continue" option in the report worked a charm and I was able to load Isadora after a fatal crash!  Even those 2 suspect actors loaded and WORKED as they should!! Very exciting.

                      I haven't the opportunity to continue my research tonight, but this is great so far!

                      Thanks,

                      Hugh

                      Hugh in Winnipeg - All test machines, Win10 Pro, 64 bit, OS SSD and separate data SSD.

                      1. new laptop: Dell 7560, i9 11950H, 64 gigs, NVIDIA RTX A4000 w/8 GB GDDR6
                      2. old desktop: Dell T5500 2009, Dual Quad Core Processor E5530, 12 gigs, 2x Radeon 5750... Still works well!
                      1 Reply Last reply Reply Quote 0
                      • markM
                        mark
                        last edited by

                        Dear Hugh,

                        Well then, we're very close. FreeFrame plugins are supposed to return a code that says FF_UNSUPPORTED when you ask it if it has a feature and that feature is unsupported. Your problem plugins are returning FF_FAIL, which, by the book is the wrong response. I guess I should simply be looking for FF_SUPPORTED, which is what I'm going to do.
                        So I think you'll have everything working in the next version.
                        Best Wishes,
                        Mark

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

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