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

Messages - gerk.raisen

#76
RAW Rec resolution unfortunately is too low :)

I've seen your proposal and it's very interesting but it seems not yet integrated in main code.
I see that the raw_rec code change very often, also from the date of your post, could you prepare a .diff file against the lastest commit? Even better a pull request....

Back to business, isn't possible to modify the normal intervalometer to be more precise (especially with low values) maybe applying to it  some of your code?
If the problem is with longer values, maybe we can use a more precise algorithm (like yours) for low timer values and standard algorithm (with loop) for higher values.

I think a similar change can be useful not only for me :)
#77
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)
#78
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)
#79
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.
#80
Feature Requests / Re: ML Auto ISO (as a module)
June 11, 2013, 01:20:22 PM
Totally agree with Marsu42.

It was quick and effective, useful for many situation where ETTR is not (yet?) fast enough.
I miss it much. :)
Can anyone help to reborn it?

Where we can start to encapsulate the removed code into a module?
#81
Hello A1ex,

at the end what of the three possible solutions (weight, noweight, noweight_hilight ) had you choosen?
It's already implemented in the last commit?
#82
I have added

ML_MODULES_STATIC = file_man raw_rec
ML_MODULES_DYNAMIC =

and it works, thank you.

But I didn't understood exactly the difference between static and dynamic.
#83
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? :)
#84
Feature Requests / Re: RAW + Settings at Start
June 03, 2013, 03:04:19 PM
+1 Have its values stored became a lot more comfortable :) (especially when the "Load modules at startup" option is turned ON)

Maybe we need a section of magic_ini where store the modules settings, ex. raw_rec, bolt_rec, file_man etc?
Or an optional separate ini for every module is preferred?

#85
Feature Requests / Re: Alarm/Timer/clock
June 03, 2013, 02:50:37 PM
An option to have a little digital clock in the liveview will be very pleased...
#86
Feature Requests / Re: Loading modules features
June 03, 2013, 02:42:44 PM
Quote from: Marsu42 on June 03, 2013, 02:14:16 PM
As I see it, the ui is already there but not enabled, so you'll just have to wait for the devs to implement it...

I was suppose the same :)
#87
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
#88
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.
#89
Raw Video / Re: 60D RAW video - it's working !!!
May 31, 2013, 01:26:47 PM
It's strange, but why every time I restart the camera (autoload module = ON) the RAW_REC module return to default settings: 16/9 and separated beep, instead of my previous 3/2 + separate wave?
Is possible to store these settings?
#90
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)
...

#91
Modules Development / Re: Port CHDK file browser
May 28, 2013, 03:54:36 PM
All you are the best...
#92
Raw Video / Re: 60D RAW video - it's working !!!
May 28, 2013, 11:58:22 AM
Marekk,

Quote from: marekk on May 27, 2013, 11:55:31 PM
I had to remove some features because 60D has problems with booting of full ML package with modules enabled.

What exact error did you get?
What features you removed?
Maybe is similar/related to my error
http://www.magiclantern.fm/forum/index.php?topic=5650.0

#93
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();
#94
Modules Development / Re: Port CHDK file browser
May 27, 2013, 09:28:17 AM
Any help is welcome..
You can try and then submit a pull request for review/approve :)
#95
Feature Requests / Re: Delete recorded RAW videos
May 21, 2013, 09:38:18 AM
I think the best solution as I suggested here http://www.magiclantern.fm/forum/index.php?topic=5522.0 is to try to port CHKD file browser
Any volunteer?
#96
If is only question of moving zoom box up down left right we can't simply try to script it?
#97
Hello,

I'm still trying to understand...what is the maximum resolution we can get in DNG or also in RAW mode?

I tried the LV 5x tricks and the resolution increase but I can't get other step-up with 10x.

Is possible to obtain high resolution like with now deprecated 422 hi-res pic?
#98
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.

#99
Seems that Marekk precede me  :(
Thanks of course :)
#100
Thank you A1ex.

I created all the missing entries in raw.c
I have enabled FEATURE_SILENT_PIC_RAW
and added the .o modules
Now compiling is ok.

I enabled the
RAW_DEBUG   
RAW_DEBUG_DUMP

to find the Raw buffer size for photos

but I can't understand what do in-camera to generate the raw.buf required for guesspitch.

Is there a menu?