• 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

    Isadora will not open OSX 10.9.4

    Troubleshooting and Bug Reports
    5
    7
    2169
    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.
    • S
      soobrien last edited by

      Hello all, 

      My iMac recently had a new hard drive installed after a crash, I reinstalled programs from the backup I had. I have not been able to open Isadora though. I uninstalled and reinstalled V2, but no dice. 
      Any thoughts? I also recently installed midi stage console, and midi pipe, could these programs have effected Isadora? 
      Here is the first part of the crash report:
      Process:         IsadoraCore [1840]
      Path:            /Applications/Isadora/IsadoraCore.app/Contents/MacOS/IsadoraCore
      Identifier:      com.troikatronix.isadora
      Version:         2.0.5 (2.0.5)
      Code Type:       X86 (Native)
      Parent Process:  launchd [167]
      Responsible:     IsadoraCore [1840]
      User ID:         502
      Date/Time:       2015-09-01 16:39:39.745 -0400
      OS Version:      Mac OS X 10.9.4 (13E28)
      Report Version:  11
      Anonymous UUID:  91A22B21-9C27-03F2-26FB-358252CC0C36
      Crashed Thread:  0  Dispatch queue: com.apple.main-thread
      Process:         IsadoraCore [3907]
      Path:            /Applications/Isadora/IsadoraCore.app/Contents/MacOS/IsadoraCore
      Identifier:      com.troikatronix.isadora
      Version:         2.0.5 (2.0.5)
      Code Type:       X86 (Native)
      Parent Process:  launchd [167]
      Responsible:     IsadoraCore [3907]
      User ID:         502
      Date/Time:       2015-09-01 16:54:47.931 -0400
      OS Version:      Mac OS X 10.9.4 (13E28)
      Report Version:  11
      Anonymous UUID:  91A22B21-9C27-03F2-26FB-358252CC0C36
      Crashed Thread:  0  Dispatch queue: com.apple.main-thread
      Exception Type:  EXC_BREAKPOINT (SIGTRAP)
      Exception Codes: 0x0000000000000002, 0x0000000000000000
      Application Specific Information:
      *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
      1 Reply Last reply Reply Quote 0
      • mark
        mark last edited by

        Dear @soobrien,

        It is saying that the "launch path" to the application is not accessible. That sounds like a permissions problem. Can you try repairing the permissions and see if this helps the situation?
        Best,
        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
        • S
          soobrien last edited by

          Hi Mark,

          Thanks so much for your reply. I reset the permissions, I've attached a screen shot of the permissions changes. Is there anything else you recommend checking or changing? I'm receiving the same message. 
          *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'

          21f648-screen-shot-2015-09-03-at-12.01.47-pm.png

          1 Reply Last reply Reply Quote 0
          • Michel
            Michel Izzy Guru last edited by

            Dear @soobrien

            I think Mark was talking about the Disk Utility application, there you can repair the permissions. Please try that as well.

            Best Michel

            Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

            1 Reply Last reply Reply Quote 0
            • S
              soobrien last edited by

              Hi Michel,

              Thanks for your help. I just uninstalled Epoccam software that was installed on my iMac. That seems to have done the trick. 
              =)
              1 Reply Last reply Reply Quote 0
              • gapworks
                gapworks last edited by

                I had a similar problem with epoccam. To install the program works fine, but hands off installing the drivers  (which you don´t need to use epoccam on a mac!)

                this really fucks up your system.!!
                best
                p.

                Running MBP2017 / Ventura Osx 13.6.7 / 16 GB 2133 MHz LPDDR3 / Intel HD Graphics 630 1536 MB / Latest Isadora Version / www.gapworks.at / located in Vienna Austria

                1 Reply Last reply Reply Quote 0
                • Skulpture
                  Skulpture Izzy Guru last edited by

                  Yeah Epocam is not that reliable unfortunately. it's caused many a problem in Isadora over the years.

                  Graham Thorne | www.grahamthorne.co.uk
                  RIG 1: Custom-built PC: Windows 11. Ryzen 7 7700X, RTX3080, 32G DDR5 RAM. 2 x m.2.
                  RIG 2: Laptop Dell G15: Windows 11, Intel i9 12th Gen. RTX3070ti, 16G RAM (DDR5), 2 x NVME M.2 SSD.
                  RIG 3: Apple Laptop: rMBP i7, 8gig RAM 256 SSD, HD, OS X 10.12.12

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