Arne Last tests:
he 3.1.60 installation has finished and the Rig Manager is reactive as it has finished syncing the rigs presets and performances. On my Kemper I still have the message "Syncing Performance 55 of 125" and it was stucked there. No Sysncing message in Windows anyhow.
After a while I switched the kemper off and restarted it. It was not recognized by the Rig Manager.
I closed and restarted Rig Manager and got the same error mesage as before, "Rig Manager will quit now due to software conditikon that can not be recovered."
I then restarted my PC and Rig Manager started again with no problem and has recognized the Kemper and finished the Performances sync.
1.Close-restart Rig Manager with a running Kemper - Kemper not recognized.
2.Leave Rig Manager running and stop - Restart the Kemper - Rig manager does not see it.
3. On the third try, Close-restart Rig Manager - a messages pops up saying that "Rig Manager needs to be updated".
4. Next Try ( close - restart Rig Manager comes with the error above:"Rig Manager will quit due to ...'
5. Next time Rig Manager starts but still does not see my Kemper. The wheel that usually pops up when it is syncing with the Kemper comes but for a very short period of time.
So on my PC I still have problems.
Sorry to hear this, I was quite sure that the update would fix it for you. Could you please send the latest DebugLog.txt again?
I tried installing this latest (60) build over whatever was installed - probably beta 59. I am on Win 8.1 and device manager still reports no driver is installed for the Kemper Profiler.
Is there a specific procedure that you have in mind for getting this to install the driver on a machine where there is no driver installed?
Of course it is supposed to work out of the box after installing Rig Manager, no matter if there was a different driver installed before or not. Anyway, we have identified 4 different problems when updating to 3.1, and the update to 3.1.60 was supposed to fix three of them. To find out what your problem is I need some log files. Did you already open a support ticket?
I have installed the 3.1.59 with the profiler running. The installation worked, it recognized the profiler than performed updates of the rigs, presets and performances for 40 minutes!
Restarting the Rig Manager brings out a fatal error and the Rig Manager does not start anymore. Tried it twice same error, see attachment.
Uninstalled the 3.1.59 using the Kemper driver removal tool and control panel to uninstall Rig Manager, then reinstalled 3.0.45.
Even this one hasn't recognized the profiler, the trick here was to go to the driver manager under other devices, and with a right click on the Profiler device choose update driver. Afterwards everything worked as usual with the 3.0.45.
The Debuglog has 2 MB, I have compressed it witz 7zip and renamed the file txt to allow uploading it.
Hope this helps the developers to identify the problem.
I think I will try again and apply the trick with the device manager even with the 3.1.59 version and hope that it solves the problem. I'll have to spend another hour for this.
there is a problem with the new Rig Manager that shows up only on a few Windows installations, and yours is one of them. The trick with the device manager won't help. If you like, try out this update:
Thanks for your patience and best regards,
Dave, Lokasenna and everyone else who hasn't done so yet, would you please open a support ticket? If the problem is that the Profiler is not recognized after the 3.1 update, we need the following files to find out what went wrong:
Sorry again for the trouble.
Still rolls back unfortunately....
I see you had opened a ticket. Could you provide us with the following files?
Without those, we can't find out why exactly your installer is rolling back.
sorry for all the trouble. Unfortunately, we haven't encountered these update problems on our own Windows machines, but we have identified a potential issue with the driver update. It might fix both the installer rolling back and the Profiler not being recognized after reboot problems. If you want to try it out, please download it from here:
If you need a 32 Bit Windows installer, please let me know.
Looking forward to hear from you!
The type should be "Sound, Video and game controllers", not "Other device" (Andere Geräte). And Hersteller should be "Kemper GmbH" instead of Unbekannt. For some reason, the Profiler is not even correctly recognized as the type of hardware it is.
Could you please send the file C:\Windows\INF\setupapi.dev.log to support? Hopefully this will give us a hint what went wrong.
What am I doing wrong ?!!
Nothing, most probably. There were three different issues that could cause a crash on startup. Only two of them have been fixed in the latest beta. If you haven't done so yet, please send a crash report either via the Rig Manager feedback function or by opening a support ticket.
mac OS 10.12 (16A323)
Actually, this is the very first release of 10.12. The latest update is 10.12.6 (16G29 and later). That is probably the reason why the crash does not happen on our machines.
You won't see the message box at all. You can try the following: Rename the folder
and create a new, empty folder with that name. This might solve the crash in case it was a problem writing the auto backup file.
Crashes on open for me. anyone else get it working after something simliar?
macOS 10.12 sierra
Exception Name: NSInvalidArgumentException
Description: -[KemperApplication setAppearance:]: unrecognized selector sent to instance 0x61000013edc0
User Info: (null)
0 CoreFoundation 0x00007fff94db87bb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffa9524a2a objc_exception_throw + 48
2 CoreFoundation 0x00007fff94e38d84 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
3 CoreFoundation 0x00007fff94d2bfc3 ___forwarding___ + 1059
4 CoreFoundation 0x00007fff94d2bb18 _CF_forwarding_prep_0 + 120
5 Rig Manager 0x0000000101c4a518 -[PTTAppDelegate applicationWillFinishLaunching:] + 274
6 CoreFoundation 0x00007fff94d456ac __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
7 CoreFoundation 0x00007fff94d455ab _CFXRegistrationPost + 427
8 CoreFoundation 0x00007fff94d45312 ___CFXNotificationPost_block_invoke + 50
9 CoreFoundation 0x00007fff94d03a32 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 2018
10 CoreFoundation 0x00007fff94d02a1b _CFXNotificationPost + 667
11 Foundation 0x00007fff967300e3 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
12 AppKit 0x00007fff929bb278 -[NSApplication finishLaunching] + 327
13 AppKit 0x00007fff929bad2a -[NSApplication run] + 267
14 AppKit 0x00007fff92985a8a NSApplicationMain + 1237
15 libdyld.dylib 0x00007fffa9e00255 start + 1
Which is the exact version of your OS? We tested on two machines with 10.12.6, and it worked on both.
I need to correct Timo's statement: right now, Rig Manager 3.0 is not HiDPI capable on Windows. It was planned for the release, but because we were late already, we postponed it. But it will come sooner or later.
There is a problem in Catalina when Rig Manager tries to open a message box during startup (e.g. if the auto backup did not work). This crash will be fixed in the next beta.
Sorry for that. Should be sorted out in the next beta that we plan to release this week.
You can press any key from A to Z, and the list will jump to the first entry starting with that letter. This applies to the column that is currently sorted.
I think every other key command can be found in the manual.
Wenn auch vorherige Updates per Rig Manager gemacht wurden, befinden sich die älteren Installer wahrscheinlich noch im Downloads Verzeichnis. Dateiendung ist .msi
Einfach per Doppelklick starten.
Cursor left/right does the trick
Rig Manager comes with a pre-installed database that reflects the contents of Rig Exchange at the time of release. From then, it will download only the new, missing rigs. You can switch off using Rig Exchange in the Preferences, but that does not remove the database from your computer.