Messages

All great ideas. When I was testing, the PTP liveview cut off when I started recording RAW or MOV. There's a slim chance there's a way around this, but I'm not sure.
A packet transmission status was exactly what I was thinking of, maybe an icon in the bottom that lights up green when packets are being received or sent.

EDIT Oct 2023:
Am working on rewriting the frontend of the app. Old frontend was HTML/CSS/JS. I think it's pretty obvious to see why that was a mistake.
New version will have all the same features, but have USB and WiFi connectivity, as well as UPnP discovery.

I've been working on a PTP (Picture Transfer Protocol) library in C lately, with the main intent of making a DSLR controller Android app out of it.

Features that will come in the first release:
- Get Live EOS viewfinder image (can't use while recording)
- Interface with ML - Live screen data (320x240, see all Canon menus and ML menus while recording RAW or MOV)
  Not a solid replacement for HDMI, but useful (in case you don't have a HDMI adapter, or it blocks the USB port)
  Currently 15fps - should be possible to optimize (see https://github.com/petabyt/ptpview)
- Scripting in Javascript (scripts can run on demand or in background)
- Get live aperture+ISO+shutter speed+image format+battery
- Raise flash
- Take pictures and do BULB shots
- Image/File explorer
- Extensive settings and customization
- Plugins/mods/scripts written in Javascript (run on demand or in background, can modify UI)
- Script generator (timelapse)

Here are features I'll probably add in the future, other than the typical features you'd expect in a camera app:
- Sync camera video start time with phone, use internal phone mic as camera mic
- ML Like overlays over live view
Looking for suggestions - I only do astrophotography with my camera, so the feature set will be biased.

- The app will not only run on Android, but Linux too (as a web server). It would be possible to connect a Raspberry Pi to your DSLR and control your camera from inside (or technically, anywhere in the world)
- iOS support is not out of the question, but it would be a learning curve. I've never used an modern Apple device apart from when I fixed them, and I don't know how iOS apps are made.
- It's worth noting that the PTP library I made is very portable (and open source, https://github.com/petabyt/camlib) and can easily be compiled and ported to different platforms.
- The user interface for the app is written in HTML/CSS/JS and is layered over a graphics canvas, where the liveview is drawn. The app is mostly C and Javascript. Under 500 lines of Java code is required the the entire app to work.

After I realized my intervalometer port was broken, I realized ML was basically my only option for an intervalometer. Since then I've been obsessed.

I was being careless today and called "SetTuningFlag" with no parameters. Managed to turn on factory menu and factory USB mode. PTP didn't work.

Factory Menu: https://eggnog.danielc.dev/f/55-y740bxdh9ki5sa4zs91w6ack9nst3v.jpg
Tried a few things, didn't understand most of it.

Had to experiment in Qemu, and compared some ROM dumps. On my 1300D/T6 the flag is located at 0xfee60000+0x2c.
Default value is 0xFFFFFFFF, factory value is 0x0. Running `SetTuningFlag 0xFFFFFFFF`disabled the factory mode.
Or in Lua:
dryos.call("SetTuningFlag", 0xFFFFFFFF)

Thinking of one day getting an SL3 to replace my T6. Does anybody have a ROM dump?

Install tutorial I made: https://youtu.be/oY4RbCaadrc

For Mac users, or people who want a simpler version of mlinstall:
Here's a standalone python script to enable bootdisk flag:
https://github.com/petabyt/mlinstall/blob/master/boot.py
Untested.
In order to run:
pip3 install ptpy
python3 boot.py EnableBootDisk

I wanted to wait a while to see if anybody reports any bugs before I call it "officially stable".
In software 1.0.0 is generally considered to be a stable release.

- Make English an option
- Applied some community patches to language files

`mlt-mcu.mo`: All translations with MCUfont as a text rendering backend. Can write some Unicode characters. You will need to rename it to "mlt.mo".

https://github.com/petabyt/mlt/releases/tag/0.3

Version 0.9.1 has been released.
https://github.com/petabyt/mlinstall/releases/tag/0.9.1
- Improved error messages and handling
- Added bound checks wherever possible
- Added ExFAT support
- Made drive code a lot better

The next release will be the final (and hopefully stable) 0.1.0.

Hi Gabochess, I just fixed the manual link.
https://petabyt.github.io/mlinstall/MANUAL#no-ptpusb-device-found
You might need to do a hard refresh to update the cache (Ctrl+Shift+R)

Pre-release for 0.9:
Implemented ExFAT card flag writing (for Linux only)
Any testing and feedback is appreciated.

https://github.com/petabyt/mlinstall/releases/tag/0.9

Version 0.8.1 Released.

https://github.com/petabyt/mlinstall/releases/tag/0.8.1

I've implemented srsa_4c's findings in the mlinstall EvProc parser.
See https://chdk.setepontos.com/index.php?topic=4338.msg147738#msg147738

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

Use at your own risk.

critix, some things I noticed:
- In liveview, trash button opens ML, and menus "glitch" every 3 seconds
- Was "fps override" lowercase before? Camera crashes when I enter liveview with it

temperature, lv focal length, and custom white balance are working good.
mltetris.mo and silent.mo seem to be working fine.
Nice work.

Could you send a screenshot?
Try EOSCard. If that doesn't work, then you probably want to talk with critix.

critix The link doesn't seem to work. The bitbucket one your posted on the Discord room works, so I'll put my findings here:

One strange thing:
- Enter menu
- Press Q on "Close register log"
- Can't use arrows to navigate menus (a popup should be shown?)
- Press Q again, can navigate menus

Other than than it seems to be working well. Nice job.

I was going to do a fresh install on my camera and decided to make an installation guide.

https://docs.google.com/document/d/1PdUBSY9Ao1l8G-8axQo4XcFOP-bxDbqWvRK-hcXm0LY/edit?usp=sharing

I've enabled editing for anybody, so feel free to make any edits. Eventually I may add it into the ML wiki.

Thanks for letting me know names_are_hard, fixed.

Also, note that the mcufont backend is entirely experimental and disabled by default.
I'm 100% open to removing it in favor of something else.

Chinese:

Here are a few German characters working:

I had just used the python3 unidecode package to fix the characters.
It looks like they have a reason for this, see https://pypi.org/project/Unidecode/ section "German umlauts are transliterated incorrectly"

For now, I'm think I'm just going to leave them as regular ASCII.
Here's the translated Google Doc: https://docs.google.com/document/d/12txrdFAE401KNcIKUeSYorWbLPK-fVQg9ILj_HRBrME/edit

It might be possible to get my alternative font rendering backend test to work with German characters (see https://github.com/petabyt/mlt/tree/mcufont).
It doesn't seem to show them out of the box, but the Spanish accent characters work:



It could also possibly be used to show Chinese characters too.

Not right now, but If I remember correctly, I was able to get some custom Unicode characters working
with https://chdk.setepontos.com/index.php?topic=12813.0

With a few Python scripts and Google Docs Translate, I was easily able to get several different languages working with MLT.
https://github.com/petabyt/mlt/releases/tag/0.1-more

These were done entirely by Google translate and received hardly any manual review, so feel free to suggest any changes.

Eventually, it may not be a bad idea to pack all languages into a single module. (each language is only 30-40kb)

Version 0.7 released.

https://github.com/petabyt/mlinstall/releases/tag/0.7

- Added an untested activator for 0x9052 as per Ant123's findings (https://www.magiclantern.fm/forum/index.php?topic=26162.msg236146#msg236146)
Still not sure what models require it, so it's just a button for now.

- Added a "module store"
I thought this would be a cool idea. You can plug the SD card into your computer and install modules, just like an app store on a smartphone. Here's a demonstration: https://diode.zone/w/4u1GYt88LP5h9t53C1fWNE

Sure. Although I would think that the MANUAL.txt in the zip file and the note in the release description would be enough...

Thanks for testing!