Messages

Thanks a1ex,

I'm afraid I have not enough time to dive into this in near future.

If someone has made such a script already, please share. If I write it, I'll share for sure.

It is well known that different batteries have different discharge curves (see https://blog.lexa.ru/2017/04/03/o_sortah_lp_e6.html for some examples—text is in Russian but plots are quite self-explanatory). This fact leads to errors in predicting remaining battery life.

My idea is to calibrate batteries by measuring their actual characteristics and storing them, say, in ML config file. It would be possible if a battery has any unique ID readable by ML. The workflow for calibration may be as following:

1. Fully charge a battery.
2. Put camera in some special calibration mode—discharge the battery in a controlled manner and write its properties to file.
3. When a battery is exhausted, the calibration is complete.
4. Repeat for all batteries in use with the camera.
5. Copy config to all memory cards in use with the camera.

This approach allows not only to show correct percentage values but also to estimate an approximate remaining time of the battery operation.

I've noticed that file size is greatly reduced when converting from MLV to DNG (say, 4.77G MLV becomes only 2.56G DNG, and so on). I'm using MlRawViewer to convert files.

The question is if there's any redundant data contained in MLV, or do I lose image quality when converting? Does it make sense to store large MLVs for archiving purposes, or DNGs are good enough?

My issue has been fixed spontaneously after updating video drivers (nVidia K2000D).

1.4.3 looks pretty much the same. It does show a right thumbnail image after launching, but then falls into black screen again with similar log records:

Code Select Expand

MlRawViewer v1.4.3
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
Loading u'D:/temp\\M28-2358.MLV'
D:/temp\M28-2358.WAV D:/temp\M28-2358.WAV
None
Traceback (most recent call last):
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 315, in __draw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Viewer", line 374, in onDraw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 265, in renderScenes
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Display", line 454, in prepareToRender
ZeroDivisionError: float division by zero

Filed a new bug, https://bitbucket.org/baldand/mlrawviewer/issues/151/black-screen-division-by-zero

I've got a black screen on w7-64. Please help.

Code Select Expand

MlRawViewer v1.3.3
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
Traceback (most recent call last):
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 295, in __draw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Viewer", line 303, in onDraw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 246, in renderScenes
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Display", line 438, in prepareToRender
ZeroDivisionError: float division by zero
Traceback (most recent call last):
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 295, in __draw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Viewer", line 303, in onDraw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 246, in renderScenes
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Display", line 438, in prepareToRender
ZeroDivisionError: float division by zero
Traceback (most recent call last):
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 295, in __draw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Viewer", line 303, in onDraw
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 246, in renderScenes
  File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\Display", line 438, in prepareToRender
ZeroDivisionError: float division by zero
Traceback (most recent call last):

(The log grows very quickly; it seems that division by zero error occurs when trying to decode every frame.)

I think ML should check orientation sensor continuously while in a movie mode live view, and display a pokemon every time when the camera is rotated to portrait. The user for sure should be able to switch this off, but I highly recommend to set the feature on by default.