Posts by Arne

You will lose all changes you did in RM 1.5. Your rig databases will have the state from the moment you upgraded to RM 1.5.

The database file for the Profiler is just a cache - each time you start Rig Manager it is updated to reflect the Profiler content. You won't lose any data.

Would you mind sending Documents/Kemper Amps/RigManager/DebugLog.txt to support? Maybe we can find out what went wrong before you solved the problem.

Probably, your Profiler database is corrupted on your local hard disk. Please send your DebugLog.txt to support, then try deleting the file:
C:\Users\YourUserName\AppData\Local\Kemper Amps\RigManager\KPA#serial#.db
Then Rig Manager should sync all Rigs and Performances once again, but not every time you launch the app.

All tags you edit in Rig Manager are immediately saved. If you copied the rig to Local Libary, of course you need to copy it back to the KPA after editing.

Hi Micha,
are you on OS X or Windows?
There are some known problems regarding sync. In some cases, the currently selected performance is not immediately updated, but only the stored performance is synced in the background. In those cases, you can switch performances forth and back in the KPA to see the change.

Is this in Rig Manager 1.3.5 or 1.5.11 Public Beta?

We are currently working on 10.11 compatibility, but I can't tell you a date yet.

~/Documents/Kemper Amps

You should not delete it, it contains backups and the debug log. It cant prevent the Rig Exchange from working in Rig Manager.

~/Library/Application Support/Kemper Amps

This is the folder containing all your Local Library data, and the cached Rig Exchange database. If you delete it, Rig Manager will pre-install a copy of the Rig Exchange database that is contained in the App and reflects the RX state from the time of Rig Manager release.
If deleting this folder did not help, then this was not the problem. From time to time, the Rig Exchange server is responding very slow or not at all.

~/Library/Preferences/com.kempermusic.rigmanager.plist

That might work after a reboot, but is not the correct way of deleting preferences. OS X usually keeps a copy of it in memory, so deleting does not change anything immediately. The correct way would be to use the defaults command in Terminal. Anyway, as long as the Connect test in the Rig Manager preference window passes, your preferences are not the problem.
According to the log file, everything is fine. I suspect a (temporary) Rig Exchange server problem.

Because in the local library, you do not have program numbers. They get lost during the drag operation, and the Performances can't be distinguished from each other. It is exactly like a folder in your file system, where you can not have to files with the same name. Right now, the Local Library is simply not able to reflect the Profiler content including program numbers.

Hi,
thanks for all the feedback! First a reminder: please always tell your platform and OS version when reporting a bug.
Then let me explain the issues with ordering performances. Only the Profiler location is organized into 125 numbered programs, as it it in the device. All others (Local Library, sub folders, USB Stick, All Performances) work like the Rig locations: they are pools with no program numbers and no limit in Performance count. This is more convenient regarding file handling (import, export), and it is necessary for the "All Performances" view. In a pool, of course you can't have duplicate performances.
The program bank view of the Profiler location is also the reason for the limited capability of moving performances around. If you drag multiple performances from the Local Library to the Profiler, where should they go? Automatically overwrite the Profiler content? Fill up the empty programs only? Start overwriting performances beginning from the line the mouse pointer is at? There is no obvious solution, different users will expect different behavior. So we decided that for now only single performances can be copied to the Profiler. For drag&drop, open a second window with the Local Library you are dragging from, then move the performance onto the program number that you want to overwrite. For Copy/Paste, copy only one performance to the clipboard, then select a program in the Profiler view and do a paste.
Now it seems that some of you want to organize your performances in banks of 125 each, and easily copy the whole banks to and from the Profiler. We will start a discussion here if and how we can find a solution for that.
Arne

Rig Manager uses some operating system functions that did not exist in XP. It will never work, sorry.

The computer's clock does not matter. Rig Manager compares the complete list it gets from Rig Exchange with its internal database, then downloads all missing rigs. If the message "Requesting rig list" vanishes without any new rigs being downloaded, then Rig Manager probably gave up due to a connection timeout. If you still experience this problem, please contact support.

The previous version is 1.2.2 on OS X and 1.2.3 on Windows. Please do not downgrade to any older version, you might lose your Local Library data.

It should, but as I explained, it doesn't. Re-installing 1.2.3 did not work for you, because the program file was already there, and it was still V1.3.1. The installer does not overwrite newer files. Delete it manually in Explorer, then reinstall V1.2.3.

We will look into the way our installer works, maybe we can improve things here. The basic problem is that the 1.3.1 installer overwrites the files from the 1.2.3 release. Windows counts how many times a file with the same name (in this case, Rig Manager.exe) was installed. If you uninstall 1.3.1, the count remains 1 (from the 1.2.3 installation), so Windows does not delete the file. Unfortunately, it is still the file from the 1.3.1 installation. The solution would either be to uninstall all Rig Manager versions before re-installing the 1.2.3, or delete all files in c:\program files\kemper amps\rigmanager before re-installing V1.2.3.
Finally, always check the about box in Rig Manager after up-/downgrading to verify which version you are actually running.
BTW: deleting registry entries won't help at all, you only lose your preferences.

The folders in Rig Manager are designed like the folders in the Finder or Explorer. In file systems, you don't see the files of subfolders mixed with the files in the parent folder. This might be a good feature for you, but I'm pretty sure there are other users who would be really confused if we changed the behavior of Rig Manager's folders. viabcroce: moving is just the default when you drag between Local Library folders. Press Ctrl while dragging, and it will become a copy instead of a move.

If you want to delete some rigs, do that before upgrading Rig Manager. RM 1.3.1 will not work with the 2.2 firmware.

Cab Maker does not create Rigs, but Cabinet Presets. Rig Manager only handles Rigs. It is of course a bit misleading that both file formats have the same extension.

Do you still have the damaged .RigExchange.db file in your trashcan? Would be great if you could send it to support, so we can find out why it prevents Rig Manager from starting.