-
-
Notifications
You must be signed in to change notification settings - Fork 55
FAQ
The patch will always be free (as in beer) and I can't distribute pre-patched firmware due to copyright.
If you want to support the project financially you are very welcome to become a sponsor,
see How to support hacktribe for more details.
Hacktribe will continue to be updated. Anything labeled enhancement is something I have some idea how to approach.
Some of these may turn into features some day.
This will always be a hack. Each new feature is a bug.
Apply the latest patch to factory sampler firmware 2.02 every time.
You can upgrade hacktribe without flashing back to factory firmware.
Firmware update file must be at path KORG/hacktribe/System/SYSTEM.VSB
.
There is no need to edit the file header if hacktribe or the sampler firmware is currently installed.
See #281.
Follow the Hacktribe Tutorial to get the patched firmware files.
See Revert to Factory Firmware and #70, particularly this comment.
This usually means the file has the wrong device ID in the header.
If you are installing Hacktribe from synth firmware you will need to edit the header to look like the synth firmware.
python e2-header.py SYSTEM.VSB synth
Probably not, but I might try.
Small changes to existing features are much easier than big changes and new features.
I haven't looked at longer patterns yet.
It might be as simple as increasing the iterator and giving it more data to read, but I doubt it.
See Patch with a GUI.
To patch manually try bsdiff for Windows, which appears to provide bsdiff and bspatch executables. I haven't tried these.
Follow the Hacktribe Tutorial to get the patched firmware files.
See #41.
Before patching the firmware, sha256 hash of SYSTEM.VSB should match the hash in hash/SYSTEM.VSB.sha
.
This proves you have the correct version of the factory firmware.
After patching the firmware, sha256 hash of hacked-SYSTEM.VSB should match the hash in hash/hacked-SYSTEM.VSB.sha
.
This proves you have the same modified firmware I have tested.
See Factory Samples
and #77.
There were some bugs with card formatting when I changed the path from KORG/electribe sampler
to KORG/hacktribe
.
See #298.
Edit the e2sSample.all
file so the first sample is in slot 501.
Put the file at path KORG/hacktribe/Sample/e2sSample.all
.
Hacktribe will try to create files under the KORG/hacktribe
directory.
If this directory does not exist, many file operations will fail.
If you have the patterns from the sampler and the samples from the sampler,
you can use this script to edit the patterns.
See this comment.
Post a bug report in the Issues section.
Ask questions in the Discussions section.