• Isadora
  • Get it
  • Forum
  • Help
  • ADD-ONS
  • Newsletter
  • Impressum
  • Dsgvo
  • Impressum
Forum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    Neither 1.3 or 2.05 is starting up-Crashing during Midi:initializing

    How To... ?
    5
    6
    1427
    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.
    • C
      casselli last edited by

      Installed 10.5.5 recently and since then have not been able to get any version of Isadora to work-Stalls and then crashes at the same part of the start up. Have repaired permissions, removed old digidesign software and done a lot of general maintenance.

      Here is the hardware overview:

      Hardware Overview:

      Model Name: Mac Pro
      Model Identifier: MacPro3,1
      Processor Name: Quad-Core Intel Xeon
      Processor Speed: 2.8 GHz
      Number of Processors: 2
      Total Number of Cores: 8
      L2 Cache (per Processor): 12 MB
      Memory: 6 GB
      Bus Speed: 1.6 GHz
      Boot ROM Version: MP31.006C.B05
      SMC Version (system): 1.25f4
      Serial Number (system): G8809423XYL
      Hardware UUID: 236CE0C8-6C36-5965-9032-41BC85E16167

      Not sure how much of the crash report is helpful so here is just the top section:

      Process: IsadoraCore [383]
      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: ??? [1]
      Responsible: IsadoraCore [383]
      User ID: 501

      Date/Time: 2015-09-06 12:40:04.125 -0400
      OS Version: Mac OS X 10.10.5 (14F27)
      Report Version: 11
      Anonymous UUID: 712B5023-5E70-384B-F75D-C9F656F10E1D

      Time Awake Since Boot: 440 seconds

      Crashed Thread: 0 Dispatch queue: com.apple.main-thread

      Exception Type: EXC_BAD_ACCESS (SIGSEGV)
      Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000126

      VM Regions Near 0x126:
      -->
      __TEXT 0000000000001000-000000000059b000 [ 5736K] r-x/rwx SM=COW /Applications/Isadora/IsadoraCore.app/Contents/MacOS/IsadoraCore

      Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
      0 com.troikatronix.isadora 0x001aa534 CMidi::BroadcastPendingMidiInputMessages() + 14
      1 com.troikatronix.isadora 0x0020c025 CHighPriorityTasks::ServiceIzzyTask(unsigned long long, EventRecord const&, bool) + 209
      2 com.troikatronix.isadora 0x0020c69e CIzzyPeriodical::DevoteTimeToRepeaters(bool, EventRecord const&) + 132
      3 com.troikatronix.isadora 0x0020c72a CIzzyPeriodical::ServiceTasks(bool, bool, bool) + 74
      4 com.troikatronix.isadora 0x002b4a08 CPPTestApp::IzzyTickTimerFired(bool) + 80
      5 com.troikatronix.isadora 0x002b4be7 CPPTestApp::HiResTimerFired(void*, unsigned long) + 333
      6 com.troikatronix.isadora 0x002b4a94 non-virtual thunk to CPPTestApp::HiResTimerFired(void*, unsigned long) + 36
      7 com.troikatronix.isadora 0x002509f8 CCarbonHiResTimer_Old::TimerFired() + 52
      8 com.troikatronix.isadora 0x00250aac CCarbonHiResTimer_Old::StaticHighPriorityTimerProc(__EventLoopTimer*, void*) + 142
      9 com.apple.HIToolbox 0x903d19e6 TimerVector + 22
      10 com.apple.CoreFoundation 0x98839006 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 22
      11 com.apple.CoreFoundation 0x98838ab4 __CFRunLoopDoTimer + 1316
      12 com.apple.CoreFoundation 0x988b454f __CFRunLoopDoTimers + 351
      13 com.apple.CoreFoundation 0x987f0531 __CFRunLoopRun + 2081
      14 com.apple.CoreFoundation 0x987efaa6 CFRunLoopRunSpecific + 390
      15 com.apple.CoreFoundation 0x987ef90b CFRunLoopRunInMode + 123
      16 com.apple.HIToolbox 0x903bd8f8 RunCurrentEventLoopInMode + 262
      17 com.apple.HIToolbox 0x903bd631 ReceiveNextEventCommon + 494
      18 com.apple.HIToolbox 0x9056b1d4 _AcquireNextEvent + 79
      19 com.apple.HIToolbox 0x90558bda RunApplicationEventLoop + 225
      20 com.troikatronix.isadora 0x0023fff4 LCarbonApp::Run() + 742
      21 com.troikatronix.isadora 0x002c7a28 main + 171
      22 com.troikatronix.isadora 0x000106b5 _start + 208
      23 com.troikatronix.isadora 0x000105e4 start + 40

      Any thoughts? I am supposed to install tomorrow and have never had a problem with this machine old as it is.

      Thanks

        

      1 Reply Last reply Reply Quote 0
      • C
        casselli last edited by

        Got it figured out, was a conflict with the midi drivers stored in the library/audio/mididrivers.

        Seems to have been related to old digidesign mbox configurations. All is working again.
        CAsselli
        1 Reply Last reply Reply Quote 0
        • Skulpture
          Skulpture Izzy Guru last edited by

          Glad you have this sorted.

          At my last place of work we had many troubles with digidesign stuff; they seem to really hijack the Core Audio (and Core MIDI too it seams). 
          Thanks for letting us know. It may help other users in the future. 

          Graham Thorne | www.grahamthorne.co.uk
          RIG 1: Windows 11, AMD 7 Ryzen, RTX3070, 16gig RAM. 2 x M.2 SSD. HD. Lenovo Legion 5 gaming laptop.
          RIG 2: Windows 11, Intel i19 12th Gen. RTX3070ti, 16gig RAM (ddr5), 1x M.2 SSD. UHD DELL G15 Gaming laptop.
          RIG 3: Apple rMBP i7, 8gig RAM 256 SSD, HD, OS X 10.12.12

          1 Reply Last reply Reply Quote 0
          • jhoepffner
            jhoepffner last edited by

            Hello,

            I had the same problem one time with a huge midi initialization.
            It crashed when I opened the patch
            My solution was to
            1 start Isadora
            2 Pause engine
            3 open the faulty patch
            4 resume engine
            Perhaps that helps
            Jacques

            Jacques Hoepffner http://hoepffner.info
            GigaByte 550b / Ryzen 7 3800X / Ram 64 Go / RTX 3090 24 Go / SSD 2 To / raid0 32 To
            MBP 13' i5 2.6 Ghz 16 Go / Intel Iris / macOs 10.11.6 / izzy 2.6.1 + 3.0.3b2
            MBP 15' i7 2.6 Ghz 16 Go / GTX 650M 1Go/ MacOs10.13.3 / Izzy 2.6.1
            MSI GS65 i7 3.6 Ghz 32 Go / GTX 1070 8 Go / Windows 10 / Izzy 3.0.3b2

            1 Reply Last reply Reply Quote 0
            • primaldivine
              primaldivine last edited by

              @dodioflo
              Can you tell me name of the Driver?
              I would like to add this to a known issues list we are putting together.

              Also, if you wouldn't mind to please try this following test also? Turn off 'External Video Output' in the Isadora Preferences. Then restore the driver that you removed to your library, and see if that fixes this same issue.

              Pro-User Latest Beta - MacBook Pro i7 2.66GHz SSD
              www.jamiegriffiths.com Arctic Canada
              www.chickweedarts.com

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

                @primvaldivine,

                I am almost 100% sure that this MIDI thing is not related to the External Output feature. DigiDesign MIDI drivers have caused problems with Isadora and other MIDI software in the past. Just FYI.
                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
                • First post
                  Last post