For a wierd reason, I’m always drawn trying to get gear to do more that they were originally intented for. So, after realizing last month that the Kaoss Pad 3 OS 2.x image looked like a simple non crypted file, I had an interesting opportunity to fiddle with the data and maybe get the KP3 to do some strange stuff.
The first test I had to do was simply to alter slightly the image, upload it to the KP3 (thanks BTW Korg to have allowed the ‘force update’ option in the updaters) and see if it would take the modifications.
Since the patch is really easy to find in the image, I just substituted Drm.1 ‘HouseBeat’ name by ‘M-.-n HxC’ (since it’s got the same amount of letter) and uploaded it to my KP. For some reason it didn’t work the first time but the second one got it alright !
Now, this useless stunt aside, it is a matter of finding out what image modification could bring. On top of my head I can list:
- Alter patch data. Since the name of the patch can be changed, obviously others parameters can too, leading possibly to a couple of custom patches in case the choices of the build in patches doesn’t satisfy you or are too ‘tamed’..
- Maybe a long strech but if we find the bootstrat code as well as the CPU type and a dev kit for it, there’s a possibility to write our own algorhytms inside the KP. This could lead to DIY open platform but it’s way to early to figure out if possible at this stage.