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:
Documents\Kemper Amps\RigManager\DebugLog.txt
Documents\Kemper Amps\RigManager\InstallationLog.txt
C:\Windows\INF\setupapi.dev.log
Sorry again for the trouble.
hi, i tried but the same problem remains ?
Thanks
Gigi
It seems an old Protools installation is preventing the Rig Manager installer from completing. It might be worth trying the solution mentioned in here:
Still rolls back unfortunately....
I see you had opened a ticket. Could you provide us with the following files?
Documents\Kemper Amps\RigManager\InstallationLog.txt
C:\Windows\INF\setupapi.dev.log
Without those, we can't find out why exactly your installer is rolling back.
Hi everyone,
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:
https://www.dropbox.com/s/3bi8…Windows%2064-bit.msi?dl=0
If you need a 32 Bit Windows installer, please let me know.
Looking forward to hear from you!
Best regards,
Arne
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
Documents/Kemper Amps/RigManager/Autobackup
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.
Display MoreCrashes on open for me. anyone else get it working after something simliar?
macOS 10.12 sierra
crash log:
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.
Then please open a support ticket.
You can always rate rigs in your local library and in your Profiler. If you want to rate rigs in the Rig Exchange, you need to preview them on your Profiler first.
The rigs from Rig Exchange are downloaded to your computer. Right now, they take up ca. 76MByte of disk space.
Das Einfachste wäre erst mal ein Reboot, falls noch nicht versucht. Falls Rig Manager sich nämlich nicht richtig beendet hat, kann man ihn nicht mehr starten, weil das Programm nicht zweimal gleichzeitig aktiv sein darf.
Hilft das nicht, bitte Support kontaktieren.
