Category: software

  • littlegptracker: 1.1c_38 out

    lvptNew 1.1c_38 version (aka ‘the wolfie fuzz’) is out.

    New feature:

    * There’s a new command ‘IRTG’ to use in tables

    IRTG stands for instrument retrigger and will retrigger the current instrument. It gives table the ability to work as progammable phrases that then can be triggered simply by changing tables.

    IRTG –yy: will retrigger the current instrument transposed by yy semi-tones. Note that each IRTG transposition is cumulatively added. So a table with

    IRTG 0001

    in it will keep going a semi tone up. Great for dubby echoes :)

    The retriggered instrument is NOT reset (as if you enter a note with no instrument number). The table (obviously) will continue to run and all running variable (filter,etc) won’t be reset

    This system is also pretty useful to implement temporary non 4/4 signature without having to switch grooves, since you have the ability to re-trigger the instrument at tick resolution

    and don’t forget trying to combine it with complex hop structure !

    Works both with audio & midi instruments

    Bug fixes

    * MIDI on PC: Because MIDI on PC is a bitch to synchronise and that the ONLY system that kind of worked was, surprisingly, the old MMSYSTEM audio system, I’ve re-enabled it as an option. So, if you need good midi sync or good timing, you will NEED to use this. The latency isn’t great but in our case it’s not a problem. To enable the old ass audio system, add an entry in the config.xml with

    Then you should enjoy pretty stable midi out

    * PSP doesn’t lock anymore when using the exit.

    * Fixed the cloning an empty note bug

    * Now mute states are reset when reloading a project

    Updated PSP,GP2X,WIN,MAC,DEB

    via littlegptracker: 1.1c_38 out.

  • Oliver Wittchow Interview pt1

    nanoloopFor our third interview, I was lucky enough to talk to a gentleman who needs no introduction, Oliver Wittchow, developer of the highly respected Nanoloop music software. In the first part, we talk a little about Oliver’s background, the very first performance using Nanoloop and the port that never was. A quick thanks to Peter and Matt who suggested a couple of very interesting topics for questions. This interview was conducted by email over a period of about a month and I would like to thank Oliver for his time and detailed answers.

    Click here to read the full interview!

  • 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 0.9.0.3, 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 0.8.8.8, patch offset 0x29182 to 0xEB

    Version 0.9.1.4, 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. :)

  • DigiBooster Professional 3 status report 05/2009

    album_picphpSome of you (few :P) may remember my post about this new up and coming tracker for the Amiga back in January. If not, check it out.

    After being rejected for a beta tester position (damned jerks!), I rely on public announcements to keep you updated, so I’m sorry if you have read this somewhere already. To be honest, the company developing it, APC&TCP, have proved to be major asshats to the Amiga community throughout these years so I wouldn’t be surprised they do something not nice with this software. It’ll be my utmost pleasaure to pirate them :P

    Anyway, I am also NOT fond of the generic Intuition/OS3 look of the software, something which was a pet peeve of mine in MusicLine, but that aside, the tracker seems to be packed with features as I mentioned in my previous article.

    Clicking on ‘More’ you will find the full report…

    (more…)

  • Squidman’s ym2151 tracker Herzeleid

    herzeleid3A little while back we mentioned that Squidman had documented the YM2151 soundchip. The tracker “Herzeleid” is in the extremely early development but it is available for the brave to try. It is cross platform, but please note you will need to compile it yourself. B00daW and the Squidman are talking about the tracker in this 8BC thread where you can follow the development and find some useful info if you have problems getting it to run. Keep your eyes on this one, I have a feeling its going to develop into a very interesting piece of software.