Messages

@Ottoga: Thanks for pointing it out!

@g3gg0, dmilligan: delete/copy file/dir in passthrough mode is OK! for RC2

any idea about the unhandheld (haha, sorry/not sorry) exceptions and errors reading frame headers, which I am guessing are the causes of problematic handling by premiere?...

I never experienced frame header error with premiere or anything else. You should double check that particular mlv file in other tools.

mlvfs_wrap_read(1497): caught exception 0xC0000005 - was very common (in early windows mlvfs builds) until I disabled antivirus real time protection.

bb

Thanks. Context menu is nice.

I've tried this method some time ago and mlvfs path was a problem for webgui as you described and I ended up with .bat command file as you did . Besides I always run mlvfs with admin rights b/c dokan sometimes could not properly unmount the drive. I've tested with mlvfs in compatibility mode as admin (opens 2 console windows if executed from bat) and with "runas.exe /user:Administrator ..." command and it sorta worked the way I'd like but it complicated things a bit (enter password etc) and I gave up and just use the shortcut with "run as administrator" checked on or just run it from FarManager console session.

I think the best way to solve this problem for all platforms is to hardcode the html and js resource into mlvfs binary itself (early versions were this way if I'm not mistaken). However, I guess, David had his own reasons for current implementation.

bb

http://www.amazon.com/StarTech-com-HDCDVIMM1M-Mini-DVI-D-Cable/dp/B00GJ40AD8/ref=sr_1_1?ie=UTF8&qid=1457155402&sr=8-1&keywords=minihdmi+to+dvi

This should help

yep, I know, see the commit messages

@dmilligan: Ah, my bad. Added slre source and header to the project and it compiled flawlessly
testing...

Compiling under VS fails again:

>main.obj : error LNK2001: unresolved external symbol slre_match
>mlvfs.exe : fatal error LNK1120: 1 unresolved externals

If you wanna test latest bin pm me. Can't just post it here. Would be interesting to see because you got some exception recently.

Compile latest path_rework branch -> OK! (with lots of warnings as usual)

Tested plain copy average cpu/speed: 3.5-4%/105-110mb/sec
Passtrough is working exept deletion as expected. No nasty exceptions so far.

Nice

Congrats!
bb

@g3gg0, dmilligan

compiled path_rework branch, win version of mlvfs in VS
commit e7a8e68 - with lot of warnings but ok
following commits (3 more) - failed with errors

mlvfs.h(137): error C2010: '.': unexpected in macro formal parameter list
mlvfs.h(139): error C2010: '.': unexpected in macro formal parameter list

bb

mlvfs_wrap_getattr(1746): caught exception 0xC000001D at address 0xB664A3F3

Strange. None of exceptions here. And this is not the exception (mlvfs_wrap_read: 0xC0000005) I've been getting  in earlier builds, but when it was happening, I'm sure, cause of it was antivirus real time protection. Do you run mlvfs with administrator rights? Happens with all mlvs?

@g3gg0

if you redownload, it might be a bit faster. i am caching internal structures now and skip checking for existense of the MLV file internally.

Nice you are on a good direction!

Plain copy mlvfs CPU usage: (tested on my home pc which is more powerful (1ghz diff) hence smaller numbers than in previous posts)
25feb build - average ~7-8%, peak ~18%
27feb build - average ~4-4.5% peak ~15%
Throughput about the same ~115mb/sec
Results are collected from 10 runs each, hence no placebo

In resolve 27feb build definitely snappier! almost no lug on play/pause/rewind/fast forward/scrub, however, not very-very-very sure 'bout it, could be a lil'bit placebo effect

bb

yeah take your time, thanks for doing all this stuff.

bb

@g3gg0

you are right too much noise did you read my messages above?

@g3gg0: (OT) what the snd_viz.mo does?

Right. On my system plain file copy shows that, CPU is higher 5-7% vs 10-14%, but speed is about the same 100-125mb/sec.

@g3gg0

yep, uploaded

Thanx! Great improvement over the last one !!!

1. Can create dirs and files everywhere including root dir
2. Can delete files! but not folders (guess related to the dokan issue)
3. One annoying thing: .M00, .M01 ... files are visible in root dir. Definitely we don't need this, because it's possible to delete them and mlvfs crashes its a..s off tested.

bb

@g3gg0

i found the reason. didnt create the .MLD properly

Hey, great! Can you post new binaries?

bb

@g3gg0

> updated the MLVFS_x64.zip, please retry

with new one - copy/creation of file/dir is the same (no avail) as described above.
one minor change to root dir - .IDX files disappeared (good), .Mxx files are still there (bad)

bb

@g3gg0

with the last debug version that I have

root dir looks like this. mlv folder plus IDX and Mxx files and here I can create dirs and files
------------------------------------------------------------------------
Z:\>dir
Volume in drive Z is DOKAN

Directory of Z:\

02/11/2016  12:40 PM                  5 ,572 M28-1253.IDX
05/28/2015  12:53 AM    <DIR>               M28-1253.MLV
02/11/2016  12:40 PM                   4,204 M28-1255.IDX
05/28/2015  12:56 AM    <DIR>               M28-1255.MLV
02/11/2016  12:39 PM                 10,144 M28-1313.IDX
05/28/2015  01:14 AM    <DIR>               M28-1313.MLV
02/11/2016  12:39 PM                 15,460 M28-1316.IDX
05/28/2015  01:16 AM    <DIR>               M28-1316.MLV
02/11/2016  12:39 PM                 35,512 M28-1322.IDX
05/28/2015  01:24 AM     4,294,385,716 M28-1322.M00
05/28/2015  01:24 AM          94,462,004 M28-1322.M01
05/28/2015  01:23 AM    <DIR>               M28-1322.MLV
               7 File(s)  4,388,918,612 bytes
               5 Dir(s)               0 bytes free
-------------------------------------------------------------------------

in mlv folders:

trying creating dir: no output but in reality folder did not created!
Z:\M28-1253.MLV>mkdir folder1

trying creating file: error message
Z:\M28-1253.MLV>echo 123 > file.txt
The system cannot find the file specified.

@g3gg0

> can create dirs and files without any issues.
> delete/copy not possible. trying to work around that dokan issue

Post your latest compiled binaries please and I will check them with pleasure

path to dokanktl.exe (Dokan 1.0.0-RC1): C:\Program Files\Dokan\Dokan Library-1.0.0\dokanctl.exe

edit: ah ok. nice to hear that

Saying Clicking do you mean automatic removal algo? Sometimes it misses some dots

Are dead/hot pixels always on the same place? My understanding is that the will vary from time to time. Of course a dead pixel is a dead pixel but a hot pixel could pop up anywhere? Am I wrong here?

I think you are right . Appearance of that kind of pixels depends on several things:
AFAIK canon software has factory callibration built in and maps pixels itself (however you can kinda alter this remapping with several second manual sensor cleaning procedure. That's how I cleaned up some hot pixels - not bads - on my former 7D) if you got chance read raw buffer before that then you have vanilla information with all off uncorercted pixels etc and I think this is a case when we get croped resolutions of raw data from the sensor (some buffers in memory I guess). Also line skipping/bining affects coordinates and appearence of those pixels. In short, whether they appear in output raw or not, depends on the camera mode and what canon firmware does in that moment and also what we are doing with great help of ML software .

But... the pixel correction map is still for a dedicated resolution and mode, hence valid in most cases.

This is my understanding... correct me please if i'm wrong.


bb

Here's an idea. How about if there is a pixel map file with the camera serial number in the MLVFS Contents? That way it will only fix the dead pixels on that specific camera. This would be in addition to the focus pixel map files because these cameras can also have dead pixels.

Nice idea! Let's wait what master David will say

bb

@dmilligan

I have one question about bad pixel removal. Can we do this with pixel maps (like focus pixel maps by dfort). Just having an option to remove them by the map or current algorithm and then anyone can make pixel maps for his/her needs: sensor and resolution (crop, non crop etc). It would be lot more faster.

Besides I have just one pixel and that's all

bb