Messages

[Questions:]

Hi,

thanks for the hint with the hello world example.

Based on these steps I created as a test a simple ML module for checking the camera screen. Showing five colours (white, black, red, green, blue) each five seconds for checking the camera screen for blind or dead pixels (see short video linked at the end).

I had a look at the different modules Alex mentioned and the game module for Arkanoid looks funny. Currently I try to understand how to address the pixels from the camera display. Thanks for your answers in Discord about these topics (different API versions and display). First I thought the display is a normal 24/32bit display with RGBA, but things seems to be a little bit more complicated. ^^

Questions:
* If I could fix a bug for example in "Arkanoid" where would I commit this bug? Pull request for current master branch or the other branches? I am not used in these concepts so I have to ask.
* Did someone knows how many fps the display can handle?

Best regards,
Thomas


Video link (40sec):
https://www.maatuu.li/ml/disptest.mp4

Hey everyone,


thanks for the hints and answers.

So I will lay my focus on the two active branches for testing, so maybe I could help you with some feedback, so its easier for you to finish them.

The last two days I try to understand the "mlv_rec" and the "pic_view" module in the lua branch. Mostly the module named "pic_view", because it is the smallest available module in the module folder. And I have to admit: Guys, you have balls of steel! Respect! :-) I am not used in firmware programming and this is really fascinating C source code. It is not complicated, but I thought before starting that these image/video topics would be far more easier to understand. ^^ Also I will join your Discord server, because I got some questions about compiling the ML modules, which currently do not work for me. "Missing" ../../src/module.h file error.


Thanks a lot and have a nice weekend!
Thomas

[My three Questions:]

Hi,


I am Thomas (C programmer) and this is my first post here.

First of all:
Thank you so much for the "Magic Lantern" software! <3

I have a meta question about the experimental branches and the current workflow:
The last days I completed the task to compile the current master trunk in a virtual box with Xubuntu 18.04 iso. I mean this master trunk: https://foss.heptapod.net/magic-lantern/magic-lantern/-/tree/branch/unified
But I am little confused because the codes from the master trunk and the latest nightly builds on your website are from the year 2018.

Then I saw that your are busy working on different branches. Some of these branches are active and others are stale branches from 2019 or 2018. I mean this: https://foss.heptapod.net/magic-lantern/magic-lantern/-/branches

What are your plans and ideas about merging these branches into master?

My three Questions:
A.) Does it make sense to change the master trunk code until you finish your work on the branches?
B.) Are you merging the active branches for Lua and Iso into master if you finish them?
C.) What about the branches which are currently staled since 2019 or 2018?

I know your free time is valuable and rare, so you do not have to answer in great detail. Just give a short summary.


Thank you so much and best regards,
Thomas