1.1.1 - Hot fix

recognizes Canon.Inc as canon cameras

1.1.0 - MacOS port, shutter counter, many bug fixes

Lots of improvements made in the last year.

New Functionality (all platforms):

• Shutter count is now displayed once connected
• Internal build version is displayed once connected
• mlinstall can be invoked with CLI to upload files if ML is compiled with CHDK PTP extensions

Binary changes:

• Linux app is now an AppImage, launches faster (previously was a static binary)
• Windows app is now a single .exe (around 30x smaller)
• MacOS '.app' release is now available

MacOS binary doesn't support any SD card functionality. This will be fixed in a later release
once the code is better tested.

UI Changes:

• UI is now based on libui-ng
• Added 'Connect to camera' button which enables the rest of the USB tab
• A lot of wording improvements (thanks Walter)
• Changed the layout of the logs/tabs

MacOS users: You will have to allow unverified apps to be run (see https://macpaw.com/how-to/fix-macos-cannot-verify-that-app-is-free-from-malware)

Jan 25 2024: hot fix - remove extra uiTextFree

1.0.0 - Final Major Release

• Deleted the forked libptp backend (70% of the codebase) and replaced it with camlib
• Removed the 'module store' (cool gimmick, wasn't useful)

Unlike libptp, camlib has native support for Windows through libwpd. This means that all the libusb-win32/zadig/driver corruption nonsense is over now. Don't install Zadig to use MLinstall.

camlib has been tested and works on MacOS, so porting it should be easy if and when needed.

Full Changelog: 0.9.4...1.0.0

Windows native USB test release

very early test

0.9.3 - Include filter installer

I'm now discouraging all use of Zadig, the tool I previously recommended to install LibUSB win32 on Windows systems. This release includes a copy of the libusb filter installer (install-filter-win.exe) which is straightforward to use, and is much less intrusive than Zadig.
Source of binaries: https://github.com/mcuee/libusb-win32

Full Changelog: 0.9.2...0.9.3

0.9.2 - Pre Final Release

Next release will hopefully be the same as this. If any bugs are detected after this release, they will be fixed before 1.0.0.

• A copy of Zadig is now included in the windows ZIP.
• Tweaked some text

Windows Users:
You will need to run Zadig and install libusb0.
https://petabyt.github.io/mlinstall/MANUAL#no-ptpusb-device-found

GTK - Heavily Tested

Since 0.9 pre-release:

• Improved error messages and handling
• Added bound checks wherever possible
• Added ExFAT support
• Made drive code a lot better

I heavily fuzz tested it on my end (both Linux and Windows) but having testers would help out a lot.
You can post any feedback, suggestions, or problems on the forum post: https://www.magiclantern.fm/forum/index.php?topic=26162.msg236087#msg236087

Windows Users:
You will need to run Zadig and install libusb0.
https://petabyt.github.io/mlinstall/MANUAL#no-ptpusb-device-found

Full Changelog: 0.9...0.9.1

0.9 Test Release

This is a test binary, has not been stress tested yet.
Implemented ExFAT drive support for Linux - no Windows binary yet. See #4

GTK - Not Completely Broken Parameters

After some findings in CHDK,
I've been able to properly implement EvProc parameters.

It includes a basic command parser. It accepts plain text (commands),
strings (between quotes), and numbers (base 10 and hex).

Example:

FooBar "Hello, World"
foo_bar 123 0x123

Keep in mind that this is advanced, and could destroy cameras. Use with caution.

Windows Users:
You will need to run Zadig and install libusb0.
https://petabyt.github.io/mlinstall/MANUAL#no-ptpusb-device-found

GTK/CLI - "Less Crap"

• Windows code for drive detection uses native Win32 API rather than cmd
• Added .lua scripts in app store
• Removed evproc parameters, doesn't seem to work
• Move warning to console output
• Fixed app store button downloading/removing bug

Windows Users:
You will need to run Zadig and install libusb0.
https://petabyt.github.io/mlinstall/MANUAL#no-ptpusb-device-found