Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - gerk.raisen

#1
Hello,

Like sure many other users, I miss every day more the app for Android"ML camera controller" wrote by forum user Sztupy
It ceased working a long time ago, maybe when we changed all the layout menu or even before.
Now the only possibility to continue using it is with very old builds that lacks all the new big features developed after that (all modules, RAW rec at first)
So why not starting a funding raise to help resurrecting it? Like a sort of bounty :)
I'm starting offering 200$ (raised to 300$ !!!) that the developer/s can choose between: keep the money, donate it to the ML project, a charity organization or any other use.
If, (and I hope that) more rewards offers will come from other users, I'll update this post accordingly.

Prerequisites for the developer/s:
Be excited about working on it :) (of course).
An android Smartphone/Tablet (better if rooted) with an USB Host capable port, (maybe not necessary, Sztupy successful run it within a Android-x86 build inside VMWare Player)
A ML-compatible camera
Android developing knowledge

Unfortunately only source code for the ML part is available (not for the Android .apk part) but maybe Sztupy can help us with that or join this challenge itself.
I wrote a PM to him (see response below)

Sure it's not a simple work but I also hope that starting working on it can also work like a leverage and start a chain reaction :)
Just to assure of the goodness and seriousness of my intentions we can concord a step by step path with reward at every progress step reached.
All the work need to be public and open-source:
The ML part need to be regularly committed to bitbucket ML repository (if the developer have write access to it) or a pull-request created and keep updated if not.
Also the Android .apk part need to be totally open-source and hosted in a freely chosen code-repository platform (Bitbucket preferred)
My camera actually is a 60D and I own both a Samsung rooted phone and a rooted Samsung tablet so obviously is necessary that works at least on these devices combinations for reward purpose)

More info here:

Original developing thread on Google groups https://groups.google.com/forum/#!topic/ml-devel/Sw0B1kpFlIU

Bitbucket ML controller source https://bitbucket.org/sztupy/magic-lantern/src
Xda Android apps http://forum.xda-developers.com/showthread.php?t=1527773
App on Play Store https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=it

The idea is to fuse the the "Sztupy android ML controller" with the Android "DSLR Dashboard" app (a remote control camera app very similar to "Chainfire DSLR controller" but totally opensource GPLv3)
The "DSLR Dashboard" program itself is a mature opensource project that we can use as good start point.
It has the advantage of don't loss developing time duplicating functions already available on that program. (the "Liveview" part for example, if we find it more faster/reliable than Stzupy implementation).
We can focus instead on the "remote control" part, modifying it at our needs, integrating it with specific code from old Stzupy app to send and receive from/to camera other than normal PTP commands also the specific PTP-ML ones, simulate keypress of camera physical buttons and interact with ML menus, and maybe also have a sort of "command line" with possibility to launch command and scripts (when they will return :)

Anyone interested ?? :)

About the Dslr Dashboard program:

Source repository https://code.google.com/p/dslrdashboard/
App on Play Store https://play.google.com/store/apps/details?id=com.dslr.dashboard

development thread (it called nikon DSLR dashboard but don't worry :)
http://forum.xda-developers.com/galaxy-s2/themes-apps/app-nikon-dslr-dashboard-via-usb-v0-30-t1256583

It's also recommended from the author of LrTimelapse (..<<Shooting Holy Grail sequences involve changing exposure time and ISO in between the shooting interval. To avoid touching the camera when doing this, Zoltan Hubai, the developer of DslrDashboard, kindly agreed to implement a "LRTimelapse Mode" into his great Android App for controlling the camera.>>)

Maybe the GUI is not so nice as the popular "DSLR Controller" but have more or less the same features including the ability of remote control the camera with PTP commands other than USB cable also via wireless with the cheap (less than 40$) "TP LINK MR3040 - Portable Battery Powered 3G/4G Wireless N Router" as described here in a previous post
http://www.magiclantern.fm/forum/index.php?topic=10688.msg104121#msg104121
But most important is opensource GPL v3
On Nikon side also the little Nikon WU-1a/1b adapter is supported (not tested on Canon perhaps)

Simply flashing the TPLINK MR3040 with a customized firmware based on opensource project Openwrt that include a little serverside program called DslrDashboardServer (also totally opensource)
That program, auto-loaded at MR3040 startup, with the camera connected to it with USB) to it, relay PTP commands to the client program on smartphone or tablet via WiFi, from where you can control the camera.
DslrDashboardServer repository: https://github.com/hubaiz/DslrDashboardServer

I did not yet contacted the author but maybe also he can help us. (He can be willing, he already did some custom changes to the program after LRtimelapse author suggestions)
I'll keep this thread updated with every progression about the project.

++A free MR3040 will be offered at the first user that make a first tangible step to this project.

UPDATE 20/05/14
Increased reward to 250$, added a first-step reward (a MR3040) and changed to the Dslr Dashboard as opensource starting point.
See http://magiclantern.fm/forum/index.php?topic=9570.msg115991#msg115991

UPDATE 10/07/14
Changed this post to reflect info from my last post.
Raised reward to 300$
#2
Hello,

What about the possibility to have some APIs to create scripts and compile it "like a module" so that we can circumvent the big problem of the impossibility of TCC in-camera compiling?
The basic ideas is that it can be a sort of template module where you only need to call the APIs and then compile it like other modules.
After that they can be simply runs as a modules.
In order to maintain a simple one-click run maybe at the start of that script-modules it ask immediately to confirm (with "SET") or edit (with another button) the built-in script parameters (like intervals, etc).
I don't remember if still they are problems to unload modules but probably for not very complex scripts the memory used it isn't a real problem. (I hope)
Maybe it's not so flexible as real scripts (ex. you can't edit it on camera, except for the parameters) but it would be a big step forward.

#3
It's possible to have the "Movie Restart" working also for RAW videos?
I tried enabling it but it seems doesn't work for RAW.
Yesterday for example I was recording a fireworks show in RAW and after every time that RAW filled the buffers (and the record stopped) I had to wait and continue check for the moment when the buffers to SD write is complete to start it again.
I think it can be very useful.
+Another interesting feature can be the ability of start again a new recording before the completion of buffers to SD/CF reversal write (it can became like a pause button),
(You can miss a lot of action waiting for completion)
#4
I need for a special project the possibility to use decimal number values in intervalometer (maybe also bulb) (like 0.8 and 1.6 sec for example)
I'm trying to figuring out how to add it...
I've added the custom values to "timer_values" and changed it to float
I've also changed some other variables to float to host the decimal numbers
The compiling is OK but in the intervalometer menu the values appear in menu in this manner:           
0.8s appear as another "0" value, 
1.6 appear as another "1" value   
3.2 appear as another "3" value         

The calculated timelapse values are incorrect, and seems also the shooting times
What I'm doing wrong or I forgotten?

It's also seems that with silent pictures and values just below one second the camera start to shoot normally ignoring silent pic option.
Is this 1 second value hardcoded somewhere?

CHANGES MADE:


+static float timer_values[] = {0, 0.8, 1.0, 1.5, 1.6 ............................



static MENU_UPDATE_FUNC(timelapse_calc_display)
{
-    int d = timer_values[interval_timer_index];
+    float d = timer_values[interval_timer_index];
     d = MAX(d, get_exposure_time_ms()/1000);
     int total_shots = interval_stop_after ? (int)MIN((int)interval_stop_after, (int)avail_shot) : (int)avail_shot;
     int total_time_s = d * total_shots;



static MENU_UPDATE_FUNC(interval_timer_display)
{
-    int d = timer_values[CURRENT_VALUE];
+    float d = timer_values[CURRENT_VALUE];
     if (!d)
     {
         MENU_SET_NAME("Take pics...");



static MENU_UPDATE_FUNC(interval_start_after_display)
{
-    int d = timer_values[CURRENT_VALUE];
+    float d = timer_values[CURRENT_VALUE];
     MENU_SET_VALUE(
         format_time_hours_minutes_seconds(d)
     );



static MENU_UPDATE_FUNC(intervalometer_display)
{
    int p = CURRENT_VALUE;
    if (p)
    {
        float d = timer_values[interval_timer_index];
        MENU_SET_VALUE("ON, %s%s",
            format_time_hours_minutes_seconds(d),
            BULB_EXPOSURE_CONTROL_ACTIVE ? ", BRamp" : ""
        );



static MENU_UPDATE_FUNC(bulb_display)
{
-    int d = BULB_SHUTTER_VALUE_S;
+    float d = BULB_SHUTTER_VALUE_S;
     if (!bulb_duration_index) d = 0;

     if (bulb_timer)



static MENU_UPDATE_FUNC(bulb_display_submenu)
{
-    int d = BULB_SHUTTER_VALUE_S;
+    float d = BULB_SHUTTER_VALUE_S;
     if (!bulb_duration_index) d = 0;
     MENU_SET_VALUE(
         format_time_hours_minutes_seconds(d)
#5
Feature Requests / PicoC or TCC Scripting (Module?)
June 20, 2013, 05:01:41 PM
Now that also the TCC scripting part of code is removed...(if I understood correctly the commits)
It's now possible to create a PicoC module for scripting?
Or it's time to start moving the API to TCC and create a specific TCC module?
Before my switch to modules and RAW video I used very often some useful scripts for automatize my shots but now that I can't use it anymore...
I miss a lot the script feature.
#6
I receive this error trying to compile modules running make inside the MODULES folder

~/magic-lantern/modules# make clean
make: `clean' is up to date.

also

~/magic-lantern/modules# make
make: `all' is up to date.

Instead running make inside every specific plugin folder is ok.
What I'm doing wrong? :)
#7
Feature Requests / [DONE] Loading modules features
June 03, 2013, 11:58:14 AM
I think interesting features for modules could be:


- Possibility to choose which module enable or not at the startup/manual loading, instead of enable it all

- Continue loading other modules in case one fail
#8
I tried to open text files (es.script file) with the viewer inside File_man module .
It works ok but I can't scroll if the file is long.
Am I doing something wrong?
I think it could be useful to have a scrollbar or the possibility to scroll file if it doesn't fit.
#9
Feature Requests / Keyboard for Fileman module
May 30, 2013, 09:23:53 AM
I think next idea for the just born Fileman module it will could be:

Implement a simple on-screen keyboard so that you can interact, like the one that guys of CHDK project made.
http://chdk.setepontos.com/index.php?topic=7272.0

it's a step to obtain for example, the possibilty to do on-camera:

-Create/Rename/folders
-Create/change some values editing small files (scripts,config files etc)
...

#10
Now that many people (me too) are trying raw_rec module (so with PicoC disabled and TCC enabled),
I was figuring out how to convert simple scripts from PicoC to TCC.

I read that with TCC scripting is a little more complicated.

For example (taken from brack.c)
What i need to run to make it work?



// Custom bracket sequence
// ISO 3200 1/10 f1.8
// ISO 100 1/10 f8
// ISO 100 1" f8
// ISO 100 10" f8

console_hide();

set_aperture(1.8);
set_iso(3200);
set_shutter(1./10);
takepic();

set_aperture(8);
set_iso(100);
takepic();

set_shutter(1);
takepic();

set_shutter(10);
takepic();
#11
Hello,

I think is becoming even more useful to have a file browser to interact with file oncamera.
With this you can also delete *.DNG and raw recording, renaming it and directly and more.

Why not trying to port the file browser of CHKD? Even if as a module?
It can be a good start point.

#12
Hello,

Is possible to enable/disable the lens IS stabilization from API in a script?
If not, and it's not too difficult, could be added?
Thank you.
#13
General Development / Error trying FEATURE_HDR_EXTENDED
February 03, 2013, 03:00:59 AM
I was trying for the first time the FEATURE_HDR_EXTENDED but compiling I receive this error:

../../src/hdr.c: In function 'hdrv_extended_shutter_display':
../../src/hdr.c:93:32: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
../../src/hdr.c: In function 'hdrv_extended_iso_display':
../../src/hdr.c:162:32: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
../../src/hdr.c: In function 'hdr_step':
../../src/hdr.c:230:13: error: 'FRAME_SHUTTER_TIMER' undeclared (first use in this function)
../../src/hdr.c:230:13: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [hdr.o] Error 1

From what I understand it seems that the FRAME_SHUTTER_TIMER is not set, it's correct?
I checked in the file and seems that is true, is missing.

Thank you.
#14
General Development / ptp-ml compile error [ce2d748]
February 01, 2013, 07:03:29 PM
Hello,

compiling with ptp-ml activated as usual, I receive this error:

[ CC       ]   ptp-ml.o
../../src/ptp-ml.c: In function 'menu_data_fill':
../../src/ptp-ml.c:56:22: error: 'struct menu_entry' has no member named 'id'
make[1]: *** [ptp-ml.o] Error 1


CONFIG_PTP          =      y
CONFIG_PTP_CHDK     = n
CONFIG_PTP_ML       = y
#15
General Development / compile error [6c4efa1]
January 31, 2013, 07:14:33 PM
[solved] we can close.
Thank you
#16
General Development / PtpCam compile error
January 29, 2013, 06:10:28 PM
Hello,

I'm trying to compile ptpcam under linux for use with a linux pc but I receive this error:


canon@testing01:~/magic-lantern/contrib/ptpcam$ make
gcc -o ptpcam myusb.c properties.c ptp.c ptpcam.c  -lusb
myusb.c:32:17: fatal error: usb.h: No such file or directory
compilation terminated.
In file included from ptp.h:27:0,
                 from properties.c:22:
libptp-endian.h:39:0: warning: "htobe16" redefined
/usr/include/endian.h:64:0: note: this is the location of the previous definition
libptp-endian.h:40:0: warning: "htobe32" redefined
/usr/include/endian.h:69:0: note: this is the location of the previous definition
libptp-endian.h:41:0: warning: "be16toh" redefined
/usr/include/endian.h:66:0: note: this is the location of the previous definition
libptp-endian.h:42:0: warning: "be32toh" redefined
/usr/include/endian.h:71:0: note: this is the location of the previous definition
In file included from ptp.h:27:0,
                 from ptp.c:23:
libptp-endian.h:39:0: warning: "htobe16" redefined
/usr/include/endian.h:64:0: note: this is the location of the previous definition
libptp-endian.h:40:0: warning: "htobe32" redefined
/usr/include/endian.h:69:0: note: this is the location of the previous definition
libptp-endian.h:41:0: warning: "be16toh" redefined
/usr/include/endian.h:66:0: note: this is the location of the previous definition
libptp-endian.h:42:0: warning: "be32toh" redefined
/usr/include/endian.h:71:0: note: this is the location of the previous definition
In file included from ptp.h:27:0,
                 from ptpcam.c:21:
libptp-endian.h:39:0: warning: "htobe16" redefined
/usr/include/endian.h:64:0: note: this is the location of the previous definition
libptp-endian.h:40:0: warning: "htobe32" redefined
/usr/include/endian.h:69:0: note: this is the location of the previous definition
libptp-endian.h:41:0: warning: "be16toh" redefined
/usr/include/endian.h:66:0: note: this is the location of the previous definition
libptp-endian.h:42:0: warning: "be32toh" redefined
/usr/include/endian.h:71:0: note: this is the location of the previous definition
ptpcam.c:36:17: fatal error: usb.h: No such file or directory
compilation terminated.
make: *** [ptpcam] Error 1


I'm missing something?  :)

#17
General Development / [SOLVED]Compile error [92f972ed556d]
September 12, 2012, 04:49:39 PM
plugin Y
console Y
ptp-ml Y


ptp-ml.o: In function `ptp_handler_PTP_ML_CODE':
ptp-ml.c:(.text+0x32c): undefined reference to `send_ptp_data'
ptp-ml.c:(.text+0x360): undefined reference to `recv_ptp_data'
ptp-ml.c:(.text+0x420): undefined reference to `send_ptp_data'
ptp-ml.c:(.text+0x4b0): undefined reference to `send_ptp_data'
ptp-ml.c:(.text+0x51c): undefined reference to `send_ptp_data'
#18
Feature Requests / Loop recording 4Gb
June 28, 2012, 09:07:41 AM
Hello,

I think it would be nice to have a feature to enable the possibility to continuos loop recording in the 4gb limit
It can be useful in a large amount of situation from wildlife to many other case where you hunt something.
If is not technically possible to overwrite from the beginning a file maybe we can arrange this workaround:

Implement a time interval after that ML start a new file and delete the oldest (can keep more than one)

example:
overwrite time: 10 min (or the maximum in the 4GB limit)
keep files: 2


When you start recording this will happen:

[ML actions]
rec on
create file1 and record up to min 10:00
create file2 and record from 10:01 to 20:00
create file3 and record from 20:01 to 30:00
delete file1
create file4 and record from 30:01 to 40:00
delete file2
create file5 and record from 40:01 to 50:00

and so on.

I hope is clear enough to understand.

Thanks.