Author Topic: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter  (Read 367169 times)

Welles

  • New to the forum
  • *
  • Posts: 28
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1550 on: June 18, 2017, 07:32:49 PM »
4. Renamed dokanfuse1.dll (in MLVFS_x64 folder) to dokanfuse.dll and dokan1.dll to dokan.dll

Thanks a ton! That did the trick for me! I had the same symtoms as others: mlvsfs was dying without any message.
100D.100B / EF-S 10-18mm IS STM / EF-S 18-55mm IS STM / EF-S 55-250 mm IS II / EF 40mm STM

bouncyball

  • Member
  • ***
  • Posts: 199
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1551 on: June 20, 2017, 07:35:40 AM »
Also just noticed that mlvfs does not offer time code?
Actually it does. Every DNG frame has it's time code in the header.

voblaunsane

  • New to the forum
  • *
  • Posts: 28
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1552 on: June 20, 2017, 12:26:08 PM »
yeah, sorry it's raw2cng, not mlv.. Tried 3 methods to access dngs on that same 23.976 file and can confirm that both mlvfs virtual cdngs and cdngs extracted to a drive are stuttering and are impossible to work with, overal cpu load is *only* 18%.. Now using extracted dngs wit raw2cdng (16bit maximised) procesor load goes up to ~40% and it's playing back normally..

@bouncyball, any idea why is this happening??

bouncyball

  • Member
  • ***
  • Posts: 199
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1553 on: June 20, 2017, 02:44:11 PM »
@bouncyball, any idea why is this happening??
Nope. I have to take a look at DNGs produced by raw2dng.

I don't even know how raw2dng does (as you say) 16 bit maximization - really converts values to 16 bit (black/white will be also affected) or just unpacks them to 16 bit word.

voblaunsane

  • New to the forum
  • *
  • Posts: 28
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1554 on: June 21, 2017, 03:54:17 PM »
Also just noticed that mlvfs does not offer time code?

ok, so the reason I thought mlvfs does not offer timecode was because the first frame is reporting 00:00:00.00 when I'm using free runing timecode, hence it's incorrect!..

and first frame extracted with raw2cdng has a timecode of 15:47:12.0 which is a correct timecode!

Nope. I have to take a look at DNGs produced by raw2dng.

I don't even know how raw2dng does (as you say) 16 bit maximization - really converts values to 16 bit (black/white will be also affected) or just unpacks them to 16 bit word.

I wish I could understand that code or the theory behind it, but I'm sure you could see how it's done here: https://bitbucket.org/chmee/raw2cdng

mlvfs 1st frame:
https://drive.google.com/open?id=0BzU9K72Ryy5YMEZnN3Z2V3BrNTQ

raw2cdng 1st frame:
https://drive.google.com/open?id=0BzU9K72Ryy5Ya1FIaFNfNGxaQ0k

Danne

  • Hero Member
  • *****
  • Posts: 2946
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1555 on: June 21, 2017, 04:17:37 PM »
Timecode starts from zero then counts frames synched with fps. Are you referring to timestamp? Can't check the files atm.

voblaunsane

  • New to the forum
  • *
  • Posts: 28
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1556 on: June 21, 2017, 04:35:08 PM »
Timecode starts from zero then counts frames synched with fps. Are you referring to timestamp? Can't check the files atm.

Well on 5d mkIII 1.2.3 I have two timecode options:
rec run, which starts from zero and
free run, which is equal to cam time..

I'm talking about free running, because it's the setting of my choice..
My point is, raw2cdng dng files gets it right and also cam native MOV files gets it right and mlvfs seem to lack this functionality..

bouncyball

  • Member
  • ***
  • Posts: 199
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1557 on: June 21, 2017, 07:00:49 PM »
@voblaunsane:

Thanks for DNG files. Used exiftool and rawdigger to view the raw data.

raw2cdng (in maximized mode) converts and interpolates 10/12/14 bit values to real 16bit range (0-65535) and sets Black level to 0 and White level to 65535 in DNG header. But I can't say why NLE likes those DNGs more than MLVFS produced ones and why it chokes on your system when fps is 23.976.

And you are right about the time code. MLVFS always starts from 00:00:00.00. It seems raw2cdng gets time from RTCI block and sets timecode start to that time and then increments according to FPS.

bb

arboldeconfianza

  • New to the forum
  • *
  • Posts: 17
Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter
« Reply #1558 on: June 22, 2017, 08:13:02 PM »
Hi guys I wanna begin with MLVFS WORKFLOW in macbook pro, I used after effects and my macbook pro have ati radeon and cudda is not compatible, anybody haved experience with final cut in MLV workflow?, probably in the future i can make a test and share!, thank you!!