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 - Licaon_Kter

#1
PR already here: https://bitbucket.org/hudson/magic-lantern/pull-requests/779/add-switch-to-reset-exposure-compensation/diff

A fix for https://bitbucket.org/hudson/magic-lantern/issues/2448/exposure-compensation-display-is-slow somewhat, as at least on (my) EOS M, I find the wheel a pain to use to get EC right (also this does not help https://bitbucket.org/hudson/magic-lantern/issues/2257/selected-wheel-setting-marked ), so having it reset to zero on restart helps me and my shooting style.

Hope it's useful for others too.

Some points that might be up to debate:
* it's ok as CONFIG_INT( hey, it does not error out on compile like this :) ) instead of static CONFIG_INT?
* is the position in the menu at Prefs/Misc key ok?
* is this working as I think on all cameras?

Thanks
#2
While recording in the upper right side of the display the UI elements are fighting for visibility

See this: https://i.imgur.com/0FZJHES.jpg

While the red recording dot is almost always half cut, using any option in Movie Tweaks -> Time indicator will make a flickering value display there too.

In standby the top bar has:
* sound bars
* filename
* framerate
* free space on card

While recording:
* sound bars
* picture style gets inserted here and
* filename is shifted to the right
* framerate AND OVER IT whatever I choose in Time indicator will be shown flickering (the screenshot was lucky)
* buffer indicator will be over histogram in all but 2 modes.

I've patched up src/bitrate.c to move things around, and they look ok on my M at least, see pics:
* 3:2/4:3 top & bottom
* 16:10 HDMI
* 16:9 HDMI
* bottom 3:2/4:3
* bottom 16:9

Images: https://imgur.com/a/WoVDN

Patch:

--- bitrate.c   2015-04-14 02:55:02.000000000 +0300
+++ bitrate.c-new       2015-05-21 01:52:39.000000000 +0300
@@ -366,16 +366,17 @@
                     time_indicator == 2 ? time_cardfill :
                     time_indicator == 3 ? MIN(time_4gb, time_cardfill)
                     : 0;
-
-    int time_indic_x = os.x_max - 160;
-    int time_indic_y = get_ml_topbar_pos();
-    if (time_indic_y > BMP_H_PLUS - 30) time_indic_y = BMP_H_PLUS - 30;
+                   
+    int screen_layout_menu_index = *get_screen_layout_ptr();
+    int time_indic_x = os.x_max;
+    int time_indic_y = get_ml_topbar_pos() + 32;
+    if (screen_layout_menu_index > 2) time_indic_y = time_indic_y - 55; // bottom modes need shifting up

     if (time_indicator)
     {
         bmp_printf(
             time_4gb < time_indic_warning ? time_indic_font : FONT(FONT_MED, COLOR_WHITE, TOPBAR_BGCOLOR),
-            time_indic_x + 160 - 6 * font_med.width,
+            time_indic_x - 11 - 6 * font_med.width, // substracted 11 pixels to get it aligned with fps
             time_indic_y,
             "%3d:%02d",
             dispvalue / 60,
@@ -407,7 +408,7 @@
         );
#endif
     }
-   
+
     //~ if (flicker_being_killed()) // this also kills recording dot
     //~ {
         //~ maru(os.x_max - 28, os.y0 + 12, COLOR_RED);
@@ -453,10 +454,13 @@
void show_mvr_buffer_status()
{
     int fnt = warning ? FONT(FONT_SMALL, COLOR_WHITE, COLOR_RED) : FONT(FONT_SMALL, COLOR_WHITE, COLOR_GREEN2);
+    int buffer_indic_y = get_ml_topbar_pos() + 32;
+    if (buffer_indic_y > 400) buffer_indic_y = get_ml_topbar_pos() - 23; // bottom modes need shifting up
+
     if (warning) warning--;
     if (RECORDING_H264 && get_global_draw() && !gui_menu_shown())
     {
-        bmp_printf(fnt, 680, 55, " %3d%%", MVR_BUFFER_USAGE);
+        bmp_printf(fnt, os.x_max - 131, buffer_indic_y, "%3d%%", MVR_BUFFER_USAGE);
     }
}


Some ideas and questions before trying out for a pull request:

* Is this an M only issue? If not/yes, is this needed?

* I've clean up this, it substracts 160 and then later adds up 160, why?

int time_indic_x = os.x_max - 160;
...
time_indic_x + 160 - 6 * font_med.width,


* In void time_indicator_show() I can use:
int screen_layout_menu_index = *get_screen_layout_ptr();
...
if (screen_layout_menu_index > 2) time_indic_y = time_indic_y - 55;

to detect current mode where screen_layout_menu_index has a value of 0/1/2/3/4 ( for top&bottom3:2 / 16:10HDMI / 16:9HDMI / bottom3:2 / bottom16:9 ) and adjust vertical offset as needed, but if I try the same in void show_mvr_buffer_status() it always says 16:9HDMI ( screen_layout_menu_index value of 2 ), hence I used a different test to determine current mode. Any reason for this difference?

* bottom 3:2 and bottom 16:9 modes are exactly the same, why?

Thanks
#3
At least on my M1, see video: https://mega.co.nz/#!1R53GIgL!_GRBQzRX_bIPcHY0t37aK0TVqGta2aJ5CMUugjfUAxs

Build info:

Magic Lantern version : Nightly.2015Apr07.EOSM202
Mercurial changeset   : de7779da4ac8 (unified) tip
Built on 2015-04-06 22:09:09 UTC by [email protected].


I got some 52 CRASH*.LOG logs and 2 LOG*.LOG, mostly duplicates or differing by 1K in the free memory info, those unique:
CRASH00.LOG:
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:504, task ?
lv:1 mode:19
Free Memory  : 134K + 3246K

CRASH06.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:504, task ?
lv:0 mode:19
Free Memory  : 134K + 3247K

CRASH11.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:504, task ?
lv:1 mode:3
Free Memory  : 130K + 3242K

CRASH33.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_READOUTDONE_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:479, task ?
lv:1 mode:3
Free Memory  : 153K + 3365K

CRASH39.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_READOUTDONE_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:479, task ?
lv:1 mode:0
Free Memory  : 157K + 3365K

CRASH40.LOG
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:504, task ?
lv:1 mode:0
Free Memory  : 158K + 3365K


LOG000.LOG: http://pastebin.com/P1s8agv2 happend around CRASH00.LOG

LOG001.LOG: http://pastebin.com/5z3BddaL happend around CRASH06.LOG

Any ideas? Should I bother with a debug build like this: http://www.magiclantern.fm/forum/index.php?topic=2388.msg113154#msg113154 ?
#4
Raw Video / [SOLVED] mlv_sound working sometimes
April 12, 2015, 02:09:51 AM
I was testing out RAW recording on my M1 today, latest nightly Apr.07 and having mlv_sound loaded and activated I got this.
- 1296302688 apr 11 19:07 M11-1906.MLV
-    7910444 apr 12 01:09 M11-1906.WAV
- 1855980128 apr 11 19:08 M11-1907.MLV
-         44 apr 12 01:18 M11-1907.WAV
- 1250427488 apr 11 19:09 M11-1909.MLV
-         44 apr 12 01:20 M11-1909.WAV
- 1283195488 apr 11 19:15 M11-1914.MLV
-    7833644 apr 12 01:21 M11-1914.WAV
- 2434007648 apr 11 19:18 M11-1916.MLV
-         44 apr 12 01:21 M11-1916.WAV
-  226767456 apr 11 19:20 M11-1920.MLV
-     652844 apr 12 01:22 M11-1920.WAV
- 1059738208 apr 11 19:21 M11-1921.MLV
-         44 apr 12 01:22 M11-1921.WAV
Where the first number is bytes size, so those 44 bytes WAV files means no sound.
The only error ( besides a huge freeze that got fixed by a battery pull ) was  "audio failed to stop, state 4" that I got several times, now that I think about it, it might coincide with those recordings that ended up soundless.

I got my MLVs processed with both latest mlvRAWviewer ( yields those 44bytes .WAV files ) and latest mlvfs ( yields big silent files ) so I guess it's not an extraction issue.


Any ideas?
#5
On my M1 I get the ML menu by 2 finger touching.


When not using ML I leave the camera on CreativeAssist mode ( means basic ) so anyone can pick it and it just works, but since one is able to enter ML menu even from here it makes things confusing.


Can this be disabled so it _only_ works when the ML mode is selected?


Thanks
#6
Feature Requests / Selected wheel setting marked
March 25, 2015, 03:41:22 AM
At least on my M1...

I can switch the role of the wheel by pressing wheel-right (BGMT_PRESS_RIGHT), say I can control Shutter speed or Aperture, on Canon the box around the current selected variable has bright green corners, on ML it looks like this:



Which one is selected?

Can the mode be detected by ML and the correct text highlighted ( eg. different color ) ?

Thanks

/PS: I had to upload my own ML picture mode screenshot since I could not find any recent one on Google, but there were some in movie mode. :-\