Messages

@cannelloni

Hmmm,  you appear to be doing everything correctly now. The only thing that I can think of that may be causing it not to work for you is the virtual drive letter that you are using ('X') when launching mlvfs. This virtual drive letter must be unique.

In you clip I noticed that you had three network drives assigned. The first was active but I didn't see what drive letter was assigned to it. The other two were inactive with drive letters "Y' and 'Z' assigned respectively. I am thinking that maybe your first network drive has already been assigned to drive 'X'.

If this is the case, just pick a free (unused) drive letter for use with mlvfs.  e.g.: mlvfs64.exe M: --mlv-dir=c:\mlvs

Failing this, you could try reddeercitys' suggestion to use the 32 bit version of mlvfs.

@canneloni

Thanks for the video clip. A couple of points:

• The instructions below should be done in a cmd window with admin rights. My bad, I didn't clarify this in my earlier response to you. This should see the results of each command just being displayed within the cmd window.
• There is no need to include the actual driver path to achieve what we are trying to do here.
• The little window that flashed up when you entered 'dokanctl /I d' actually confirmed that the service was installed and started. If you are quick with the pause button you can see it.

From what I've seen, I think that the dokan service is installed and running. to convince yourself just try the commands (exactly as per below again in a cmd window with Admin rights). :



C:\Program Files\Dokan\Dokan Library-1.0.0>cd /d C:\Program Files\Dokan\Dokan Library-1.0.0

C:\Program Files\Dokan\Dokan Library-1.0.0>dokanctl

Driver path: 'C:\WINDOWS\system32\drivers\dokan1.sys'
dokanctl /u MountPoint (/f)
dokanctl /m
dokanctl /i [d||n]
dokanctl /r [d||n]
dokanctl /v

Example:
  /u M                : Unmount M: drive
  /u C:\mount\dokan : Unmount mount point C:\mount\dokan
  /u 1                : Unmount mount point 1
  /u M /f             : Force unmount M: drive
  /i d                : Install driver
  /i n                : Install network provider
  /r d                : Remove driver
  /r n                : Remove network provider
  /d [0-9]            : Enable Kernel Debug output
  /v                  : Print Dokan version

C:\Program Files\Dokan\Dokan Library-1.0.0>dokanctl /v
Driver path: 'C:\WINDOWS\system32\drivers\dokan1.sys'
dokanctl : Mar  8 2016 13:07:15
Dokan version : 100
Dokan driver version : 0x190

C:\Program Files\Dokan\Dokan Library-1.0.0>



As I said, I think that the dokan service is up and running on your PC. Can you do a similar clip of what happens when you launch MLVFS. remember it also needs to be in a cmd window with admin rights. Please include the launch process, what you see in file manager and the localhost browser details.

@canneloni

Some screen shots or a video clip taken with your smartphone would help.

Also, double check whether you have a 32 or 64 bit version of windows installed and that you are using the correct version for your operating system.

@A1ex,

Thanks for clarifying.

@A1ex

I didn't know whether they would be created automatically in camera or not or, if the camera would get upset if they weren't there at boot time. As such, I took the cautious approach to manually create the directories avoid any risk.

Nightly build magiclantern-Nightly.2016May07.7D203.zip is missing the following ML subdirectories:

• logs
• settings

No problem for me, I added them manually. Just letting the devs know.

Other camera model users should check that these directories exist before updating to this build.

@cannelloni

Re: the m22-1744 in your --mlv-dir path. Is this the actual mlv file or the directory where that mlv resides. The path should be to the directory where the mlv files reside.

Also, have you actually checked that dokan is loaded? See below for how to check (in a cmd window):


C:\Program Files\Dokan\Dokan Library-1.0.0>cd /d C:\Program Files\Dokan\Dokan Library-1.0.0

C:\Program Files\Dokan\Dokan Library-1.0.0>dokanctl
Driver path: 'C:\WINDOWS\system32\drivers\dokan1.sys'
dokanctl /u MountPoint (/f)
dokanctl /m
dokanctl /i [d||n]
dokanctl /r [d||n]
dokanctl /v

Example:
  /u M                : Unmount M: drive
  /u C:\mount\dokan : Unmount mount point C:\mount\dokan
  /u 1                : Unmount mount point 1
  /u M /f             : Force unmount M: drive
  /i d                : Install driver
  /i n                : Install network provider
  /r d                : Remove driver
  /r n                : Remove network provider
  /d [0-9]            : Enable Kernel Debug output
  /v                  : Print Dokan version

C:\Program Files\Dokan\Dokan Library-1.0.0>dokanctl /v
Driver path: 'C:\WINDOWS\system32\drivers\dokan1.sys'
dokanctl : Mar  8 2016 13:07:15
Dokan version : 100
Dokan driver version : 0x190

C:\Program Files\Dokan\Dokan Library-1.0.0>



The above is for the 64bit version. If you don't get any or, the correct version displayed then you probably need to install the dokan driver and network provider.

Do this via the following commands:
dokanctl /i d
dokanctl /i n

You only need to do this once, it will automatically load at boot time from then on.

You might also like to create a batch file to launch MLVFS. below is an example of mine.


cd /d C:\OtherPrograms\MagicLantern\MLVFS_x64
mlvfs_x64.exe X: --mlv-dir=D:\MLVs



You won't see the drive mounted in the command window, check under "This PC" in file manager to see the dokan virtual drive.  Also, you need to keep the command window active the entire time that you are using MLVFS. Just minimise it. If you close the command window, the dokan virtual drive will be unmounted.

Assuming that you can now see your virtual dokan drive. Fire up you browser and enter http://localhost:8000/ You should now see all of the MLVs listed.

A little tip:  Choose your MLVFS configuration options in the browser before accessing the mlv file in the dokan virtual drive. It saves you having to force or wait for a refresh cycle in file manger.

Hope this helps....

@_OLLE_

ML does not work with v2.0.5.

@garry23

ETTR settings should be no dual, S/Ns to zero, highlights very low or zero

Just for clarity, does this mean:

• Highlight ignore should be set to a low value or Zero
• Midtone and Shadow SNR limits set to zero?
  if so, neither of these have a zero setting. They can either be set to OFF or a nominated EV value
  As such, are you really suggesting that they should be set to off

Follow the link. It's explained there.

@A1lex - logging is working correctly now. Thanks

@A1ex

Thanks, I just need to remember to unload the mlv_play module as well before running the script again.

The script is still running so no feedback on the logging yet.

@a1lex

I'll try it again tonight and let you know if it is now logging correctly.

btw: When the script says finish, have a little sleep.... My camera appears to go into preview mode of a clip (don't know which one).  After the sleep period the script resumes and continues as per normal. As a result though, the camera never really gets the intended break and chance to cool a little.

Here is a link to a video captured with my phone:  https://www.dropbox.com/s/880kd2t74rddk21/20160427_193655.mp4?dl=0

@Frank7D

Interesting article. Also, thanks for your analysis. I've updated my spreadsheet as well for future use.

@Frank7D

Happy to provide the feedback in what ever the preferred format is.

I don't know what the following are/represent or how they are calculated. Do you have a sample spreadsheet that I could follow?

T -Stat: 0.97
Critical T: 1.70

The raw_rec version info has been manually captured while the script was running and added after the event as the logging is not capturing this information. I can add the path if it's important even though the script looks for them in a specific location.

@A1ex

Here are the test results after running rawbench.lua. I ran two series of tests, one with global draw on and the other with it off. I transposed the log file details into a spreadsheet in a format that is bit more readable for me. I'm not sure if all the required log entries have been written into the log or not. As such, the original log files are supplied as well.

I also ran the api_test.lua through a couple of cycles as you suggested and have included the log file.

Test results can be found here:  https://www.dropbox.com/s/ohr3qlav4ozh810/Rawbench_Testing_7D.7z?dl=0

Let me know if you want me to try anything else.

@nifreak

Anyone testing this with files produced by "MLV Lite"?

They open fine for me (normal mlv_lite, no dual_iso)

@A1ex

Stopping at 1 minute should be OK now.

The other... I'm not sure where to look. Do you see the raw_rec version messages on the screen (including "For next experiment"), right after formatting the card, but before restart?

The 1 minute restart is working fine now thanks. I've also tried it with settings that won't record continuously and it is looping through that nicely as well.

Also, I am seeing the raw_rec version messages on screen. They don't stay for long, but they are there.

Thanks for your time and effort to get this script working for. I'll put a recharged battery in tomorrow and let it run until it dies. It should give a few cycles of good info for you.

Can't look at this again for a couple of hours.  Will test it again tonight though before hitting the sack.

@A1ex

The script assumes you have picked recording settings that do not result in very long clips. But, indeed, I can see why a timeout can be useful, so I've hardcoded a 1-minute timeout.

At the minute mark the error in the linked screenshot was displayed and the camera continued recording.

Screenshot:  https://www.dropbox.com/s/3d119euqnr2dz0i/20160421_184655.jpg?dl=0

Sorry, its a bit blurry

Which raw_rec module is running?
Quote

Looking at the log files generated, I can't tell which raw module was executing



This happens right after formatting the card, before restarting. I don't see it in the log file though, but I pushed a possible fix.

Nothing in the log file.

[Edit] The log Contents


===============================================================================
ML/SCRIPTS/RAWBENCH.LUA - 2016-4-21 19:37:58
===============================================================================

[19:38:03] Recording test clip 1 of 8...

===============================================================================
ML/SCRIPTS/RAWBENCH.LUA - 2016-4-21 19:42:31
===============================================================================

A:/DCIM/100EOS7D/M21-1938.M02: 4654 frames, 12.745171 GB
ML/SCRIPTS/LIB/stats.lua:29: attempt to perform arithmetic on a nil value (field '?')
stack traceback:
   ML/SCRIPTS/LIB/stats.lua:29: in function 'globals.getMedian'
   ML/SCRIPTS/LIB/stats.lua:69: in function 'stats.quartiles'
   ML/SCRIPTS/RAWBENCH.LUA:216: in function 'globals.check_files'
   [C]: in function 'globals.xpcall'
   ML/SCRIPTS/RAWBENCH.LUA:322: in function 'globals.run_test'

===============================================================================
ML/SCRIPTS/RAWBENCH.LUA - 2016-4-21 19:43:59
===============================================================================

[19:44:04] Recording test clip 1 of 8...

@dmilligan

April 19, 20 and 21 nightlies display the flowing error message on my 7D when trying to load the adv_int module:



Linking..
tcc: error: undefined symbol 'get_out_of_play_mode'
    [E] failed to link modules


Note that error only appears if the adv_int module has been selected to load. I proved this by trying to load it on its own with no other modules selected and got the error. If I exclude this module then all other modules load successfully.

Nightlies prior to April 19 don't have this error.

@A1ex

Having mixed success with the rawbech.lua script. Feedback can be found here: https://www.dropbox.com/s/q5s1whs1vsqwph7/Rawbench_Testing.7z?dl=0

@A1ex

April 19 nightly displays the flowing error message:

Linking..
tcc: error: undefined symbol 'get_out_of_play_mode'
    [E] failed to link modules


Note that error only appears if the adv_int module has been selected to load. If this module is excluded then all other modules load successfully.

@A1ex

I'm making some progress, the script is trying to run. however, I see the following error message on the screen when I turn the camera on and enter the ML menu system.


Stack Traceback:
[c]: in function "require"
ML/SRIPTS/RAWBENCH.LUA:21: in main chunk


Looking at the script, I assume that I'm missing addition scripts called "logger" and "stats"


Camera conditions are:
April 19, 2106 nightly
Camera AV mode
rawbench.lua installed within the ML\scripts directory
Modules loaded:  raw-rec.mo, lua.mo
ML - Global draw off, defaults for all other settings

@a1lex
Is there a compiled version of the rawbench.lua script available. I don't have the facilities to compile.
Also, in your post you say that this script is not compatible with the latest nightly, is this still the case? if so is there a test build of a compatible nightly available?