TAPClean 0.34 released!

Ahead of a substantial change within the Visiload scanner, I decided to release TAPClean 0.34.

Not all binaries are available for all supported platforms, but that’s something I will work at in the next few days. Linux and Mac users can either compile the “v0_34” tag by themselves or wait for me to publish binaries for them.

The change to the Visiload scanner is quite substantial because the code now scans CBM files in order to extract initial loading parameters and supports multiple titles on the same tape image even when these use different parameters, including different threshold values.
Once I am finished with this change – I mainly need to replace a lot of legacy code – the Visiload scanner will be the blueprint for a truly comprehensive scanner, due to the support of tape compilations that contain heterogeneous loaders.

As example you can mix Visiload T1 and T2 with very different initial loading parameters on the same tape image and stash some Freeload in between: TAPClean is now able to recognize each part and decode its loading parameters seamlessly.

The initial implementation of the change is available by checking out the “HEAD” or “v0.35-pre1” tag of the code.

Happy days ahead 🙂

This entry was posted in Retrocomputing, Technical and tagged , , , , , , . Bookmark the permalink.

6 Responses to TAPClean 0.34 released!

  1. Kim L says:

    For some rather strange reason, 0.34 (also e.g. 0.32) breaks 1 of the 6 turbo blocks in Melon Mania, although the dirty .tap looks perfectly fine. If interested, see my post on http://www.lemon64.com/forum/viewtopic.php?p=788892 page 14, look for e.g. the phrase “I’d say it seems you’ve stumbled upon a really weird bug in TAPClean”. [Not related to Visiload, though].

  2. Thanks for the release
    Could you be persuaded to also upload tar.gz, zip or similar archive snapshot of the source ?

    I’m maintaining tapclean as an AUR package for ArchLinux
    The reason for my request it that the sourceforge source download/snapshot is not consistent/static.
    That means that the checksum of the downloaded source archive from sourceforge changes for every download. This makes it impossible for me to publish a PKGBUILD build file that validates the checksum of the source before building

    I would be very grateful If you could upload an archived snapshot of the source along with the binaries.

    Please see the existing AUR PKGBUILD file: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=tapclean

    • luigidifraia says:

      I’ve just uploaded a tarball of the source to the release folder on Sourceforge. You’ll have to update the download URL (including suffixing the file name with “-src”). Hope it helps.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s