Saturday, July 20, 2013

Troubleshooting: Drumkit 2.2

Here are some fixes for problems that could appear in the version 2.2.

Application gives error at the loading page

There is a number of problems which can cause an error message to appear at the loading page, like the corruption of configuration files, or missing assets.

If the problem you are experiencing started after installing a drum package, deleting it may solve the problem
  1. Close the application. You can do this by dragging it from the top edge (when you see the hand cursor) to the bottom of the page, and waiting for a few seconds, or using the task manager.
  2. Open Explorer, and type in the address bar: %appdata%\..\Local\Packages
  3. Locate the DrumKit package, in my case it is 35555TiberiuChibici.DrumKit_rpr4x2y6afkpe
  4. Go inside the RoamingState folder
  5. Go inside the DrumKits folder
  6. Delete the folder which contains the drum package causing the problems.  

A last resort solution is to force the application to reset to its original state when it was installed (if it worked then). This will delete all preferences, and drum packages installed. To do this, follow these instructions:
  1. Follow steps 1-4 above.
  2. Delete the installed.xml file.

Drums are off the screen

The easiest method to fix this issue is to create a new layout. In a new layout, all the drums are by default in the top left corner, and they can easily be placed.

A more advanced method of fixing this issue is to edit the configuration xml file, which can be found in the application's AppData folder (look for instructions above).

Lag when hitting the drums

This is a common problem, which cannot be fixed from a developer point of view. The lag exists because the operating system itself, and the underlying libraries have slower response times, which cause the lag. There is not much I, as a developer, can do about it, although I am still investigating and doing any optimisation I can.

One thing you could try is disabling animations which would slightly improve the response time, although in most cases it will not make any difference. Also, reducing the polyphony may help, because it would use fewer system resources.

Sound of previously hit drum is cut, when a new drum is hit

The most likely problem is that the polyphony is set too low. I recommend setting it to at least 32.

The problem is not listed

You can request support by commenting on this page, or sending an email to chibicitiberiu@outlook.com.

Update: Drumkit 2.2 almost here

A new version of DrumKit is about to be released.

New features in Drumkit 2.2:
  • Volume can be changed for every drum
  • Polyphony is now configurable

Improvements in Drumkit 2.2:
  • (Slightly) improved lag.