Chipmusic • Games • software

PXTONE crack deprotects “*.pttune” modules

PXTONE by pixel

PXTONE by pixel

PXTONE by pixel is an extended piano-roll sequencer for Windows based on the Cave Story sound engine.  The sequencer in PXTONE is called ptcollage; which is normally able to open up *.ptcop project files.  These files can be exported as *.pttune files which are essentially write-protected files sharing the same exact data — but with a different header containing the protection info.  CaitSith2, hacker extraordinaire, has recently cracked all current versions of PXTONE to allow the novice hacker to hex edit ptcollage.exe at the offsets mentioned by CaitSith2:

Version, Patch offset 0x28842 to 0xEB to disable the edit prohibit. (Not compatible with older format files though, but still, the protection is completely stupid, if it only checks one thing.)

Version, patch offset 0x29182 to 0xEB

Version, patch offset 0x293D2 to 0xEB.

Any other version, search for 0x3E E0 01 00 00 74. There should only be one instance, if so, replace the with 0x3E E0 01 00 00 EB.

(This took me less than 5 minutes to crack.)

You will then be able to open the previously edit-protected *.pttune files after selecting *.* from the file type on load; just as you would be able to edit the original *.ptcop project files.

I believe this opens an ethical debate.  How would you feel if you had previously felt your PXTONE created music was safe from n00bz editing and remixing your material?  How do you think pixel feels having his file format protection circumvented?  Do you think this does more good than it does harm to musicians?  Is anything really protected or safe?

What do you think?  Please comment. :)