H9 Control v2.0.1 Windows app

Home Forums Products Stompboxes H9 Control v2.0.1 Windows app

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #112109
      Styrioci
      Member

      Hello, I just found some strange behavior of latest version of H9 Control SW for Win.

      Win7 x64 pro

      H9 Control v2.0.1

      Audio Interface Native Instruments Komplete Audio 6 with latest drivers

      H9 with latest FW

      symptoms:

      I have H9 connected via MIDI to my audio interface and that goes via USB to my Laptop. Worked fine until I upgraded H9 Control app to latest version and H9 FW as well. When I have it connected via midi and audio interface and I start H9 control app it crashes immediately. Same when I have connected audio interface (with MIDI cables disconnected) and H9 connected via USB to my laptop. H9 Control app works fine when H9 is connected via USB with no other devices plugged in via USB.

      What I have tried – H9 FW downgrade to previous version, reinstall H9 Controll app, reinstall audio interface driver  – with reboots after each SW (un)install, no help. So it seems it's H9 Control app for Windows which is causing problems.

      There are following events logged in app event logs. 

      Log Name:      Application

      Show More...

      Source:        Application Error

      Date:          26. 11. 2014 14:29:58

      Event ID:      1000

      Task Category: (100)

      Level:         Error

      Keywords:      Classic

      User:          N/A

      Computer:      StyriOci-PC

      Description:

      Faulting application name: H9 Control.exe, version: 2.0.1.0, time stamp: 0x546f90db

      Faulting module name: H9 Control.exe, version: 2.0.1.0, time stamp: 0x546f90db

      Exception code: 0xc0000005

      Fault offset: 0x0002eefa

      Faulting process id: 0x948

      Faulting application start time: 0x01d0097d129957e3

      Faulting application path: C:Program Files (x86)EventideH9 ControlH9 Control.exe

      Faulting module path: C:Program Files (x86)EventideH9 ControlH9 Control.exe

      Report Id: 508d25d3-7570-11e4-be0b-20cf30d0caf1

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt;

        <System>

          <Provider Name="Application Error" />

          <EventID Qualifiers="0">1000</EventID>

          <Level>2</Level>

          <Task>100</Task>

          <Keywords>0x80000000000000</Keywords>

          <TimeCreated SystemTime="2014-11-26T13:29:58.000000000Z" />

          <EventRecordID>43088</EventRecordID>

          <Channel>Application</Channel>

          <Computer>StyriOci-PC</Computer>

          <Security />

        </System>

        <EventData>

          <Data>H9 Control.exe</Data>

          <Data>2.0.1.0</Data>

          <Data>546f90db</Data>

          <Data>H9 Control.exe</Data>

          <Data>2.0.1.0</Data>

          <Data>546f90db</Data>

          <Data>c0000005</Data>

          <Data>0002eefa</Data>

          <Data>948</Data>

          <Data>01d0097d129957e3</Data>

          <Data>C:Program Files (x86)EventideH9 ControlH9 Control.exe</Data>

          <Data>C:Program Files (x86)EventideH9 ControlH9 Control.exe</Data>

          <Data>508d25d3-7570-11e4-be0b-20cf30d0caf1</Data>

        </EventData>

      </Event>

      Log Name:      Application

      Source:        Windows Error Reporting

      Date:          26. 11. 2014 14:30:08

      Event ID:      1001

      Task Category: None

      Level:         Information

      Keywords:      Classic

      User:          N/A

      Computer:      StyriOci-PC

      Description:

      Fault bucket 671410942, type 17

      Event Name: APPCRASH

      Response: Not available

      Cab Id: 0

      Problem signature:

      P1: H9 Control.exe

      P2: 2.0.1.0

      P3: 546f90db

      P4: H9 Control.exe

      P5: 2.0.1.0

      P6: 546f90db

      P7: c0000005

      P8: 0002eefa

      P9: 

      P10: 

      Attached files:

      C:UsersStyriOciAppDataLocalTempWERC0A0.tmp.WERInternalMetadata.xml

      These files may be available here:

      C:UsersStyriOciAppDataLocalMicrosoftWindowsWERReportArchiveAppCrash_H9 Control.exe_56e2abd9d19f934b39bb41b4fefea3d623086d2_0284e7a1

      Analysis symbol: 

      Rechecking for solution: 0

      Report Id: 508d25d3-7570-11e4-be0b-20cf30d0caf1

      Report Status: 0

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt;

        <System>

          <Provider Name="Windows Error Reporting" />

          <EventID Qualifiers="0">1001</EventID>

          <Level>4</Level>

          <Task>0</Task>

          <Keywords>0x80000000000000</Keywords>

          <TimeCreated SystemTime="2014-11-26T13:30:08.000000000Z" />

          <EventRecordID>43089</EventRecordID>

          <Channel>Application</Channel>

          <Computer>StyriOci-PC</Computer>

          <Security />

        </System>

        <EventData>

          <Data>671410942</Data>

          <Data>17</Data>

          <Data>APPCRASH</Data>

          <Data>Not available</Data>

          <Data>0</Data>

          <Data>H9 Control.exe</Data>

          <Data>2.0.1.0</Data>

          <Data>546f90db</Data>

          <Data>H9 Control.exe</Data>

          <Data>2.0.1.0</Data>

          <Data>546f90db</Data>

          <Data>c0000005</Data>

          <Data>0002eefa</Data>

          <Data>

          </Data>

          <Data>

          </Data>

          <Data>

      C:UsersStyriOciAppDataLocalTempWERC0A0.tmp.WERInternalMetadata.xml</Data>

          <Data>C:UsersStyriOciAppDataLocalMicrosoftWindowsWERReportArchiveAppCrash_H9 Control.exe_56e2abd9d19f934b39bb41b4fefea3d623086d2_0284e7a1</Data>

          <Data>

          </Data>

          <Data>0</Data>

          <Data>508d25d3-7570-11e4-be0b-20cf30d0caf1</Data>

          <Data>0</Data>

        </EventData>

      </Event>

      Show Less...
    • #127045
      gkellum
      Participant

      Hm… We'll have to see if we can reproduce that.  Hopefully, we won't need a Audio Interface Native Instruments Komplete Audio 6 to do so.

      You mentioned that H9 Control is crashing even when it isn't connected through your MIDI interface if that MIDI interface is connected. I think you could get rid of that problem by erasing the setting that causes it to try to connect to your H9 through the MIDI interface.  You can reset all the app settings by clicking on the Settings button in the bottom right hand corner of H9 Control and going to Reset Settings and using the reset all settings function.  After you do this, when you restart H9 Control with your device connected (via USB), you're going to need to enter your user name and password again to verify your registration info, but hopefully after you do this, you'll be able to connect your devices via USB without it causing anything to crash.

    • #127051
      Styrioci
      Member

      reset settings procedure worked wonderfully, nothing crashes now 🙂 many thanks for hint

Viewing 2 reply threads
  • You must be logged in to reply to this topic.