crash report – midi to modulator routine

Home Forums General Using Ctrlr crash report – midi to modulator routine

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #36195
    sm_jamieson
    Participant
      • Topics: 8
      • Replies: 6
      • Total: 14

      On a 64 bit window 8 machine with 64 bit windows. Ctrlr 5.3.57.
      Working panels operate fine with 32 bit or 64 bit Ctrlr executable.

      Crash report popup with 32-bit executable as follows:
      This is a crash indicator, it means that Ctrlr has crashed for some reason. Some crash information will be written to C:\Program Files(x86)\Ctrlr\Ctrlr-Win32.exe.crash
      3: LdrSetAppCompatDIIRedirectionCallback + 0x12c0f
      4: RtlInitializeExceptionChain + 0x5a

      Running 64 bit executable I get messages to write Ctrlr-x64.exe.crash, then
      3: UnhandledExceptionFilter + 0x142
      4: memset + 0xbbf7
      5: _C_specific_handler + 0x87
      6: _chktstk + 0x9d
      7: RtlRaiseException + 0xedb
      8: KiUserExceptionDispatcher + 0x2e

      The exe.crash files are not written in either case.

      The panel contains a single slider with the default routine on the “Called to calculate new modulator value from a MIDI value”. The routine is:
      test = function(–[[ CtrlrModulator –]] modulator, –[[ CtrlrMidiMessage –]] midiMessage, –[[ number –]] numericMidiValue)
      return numericMidiValue
      end

      If this routine is removed, no crash occurs.

      I also have another more complex panel with a slider connected to CC 7 (channel volume) that does not response to incoming midi but sends out from the slider just fine, in case this indicates a problem in the area.

      Simon.

    Viewing 1 post (of 1 total)
    • The forum ‘Using Ctrlr’ is closed to new topics and replies.
    There is currently 0 users and 93 guests online
    No users are currently active
    Forum Statistics
    Threads: 2,495, Posts: 17,374, Members: 77,605
    Most users ever online was 12 on January 22, 2019 3:47 pm
    Ctrlr