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

Messages - erikbaldwinson

#1
Generally I have been starting CMD and typing in the following..

C:\MLVFS_x64>mlvfs.exe Z:\ --mlv_dir=H:RAW

and then running microsoft edge and clicking a bookmark that launches http://localhost:8000/

When I created a .BAT that included the command to start explorer or microsoft edge (microsofts new browser) and load http://localhost:8000/ I had all sorts of weird things happen depending on the code I put in the .BAT file. Ex. 1. .BAT file required two clicks to load the launch the browser and thus unmounting the drive. 2. http://localhost:8000/ was a white blank screen and 3. finally windows blocked mlvfs.exe and made the program 0 bytes - turned off windows smartscreen and security features to no avail.

Wondering if anyone knows how to launch MLVFS, and a browser with the http://localhost:8000/ page loaded in one .BAT file? Maybe even launch resolve as well all in one click?

Cheers,
Erik
#2
Quote from: bouncyball on December 15, 2017, 12:12:39 PM
I've taken a look at your mlv (investigated with mlv_dump, it is healthy), with latest mlv app there are none of black or corrupted frames. The issue was what @masc said. Please wait for next release, use other tools for now.

Thx! I used resolve with MLVFS and the results look better than the pro-res 444 output with bilinear. Maybe the Amaze option is better? I saw the bokeh problem and thought to use Bilinear.
#3
Quote from: masc on December 14, 2017, 09:18:01 PM
A reason may be that the frames in your MLV are not in the right order. In v0.12 we did not care about this yet, what could result in black frames. Some days ago bouncyball fixed that by replacing the false frames in the right order. This will come with the next release.
With this few information you gave, I don't know if it is really this reason. Best is, if you upload some seconds of your MLV (the seconds where you get the problems), so we can debug.

https://drive.google.com/open?id=1eU2t2cCUMTy6fXudJ3F-QCUMTIsXrpzz
#4
When exporting 14bit lossless in MLV.App.v0.12.alpha.Win64.static every few seconds a frame is black. This is not the case in Resolve?
#5
Quote from: a1ex on November 23, 2017, 08:13:49 PM
I'm not going to - it's your claim and your job to prove it.

The two DNGs you've posted do not even have the same brightness, so they simply cannot be compared for this case. All I've asked for was a test where this difference is visible.

I think I have. The difference is mostly in the quality and definition of the shadows. I watch the footage on my monitor and the 12-bit doesn't have a definition in the shadows that the 14-bit does. The additional noise of 12-bit is obvious when you lift the shadows of both dngs.

I think both are awesome.
#6
Quote from: a1ex on November 23, 2017, 09:49:32 AM
Unable to compare, please use a tripod...

Hey Alex you're welcome to run your own test on your own terms. If you want to save the time, open the dngs in photoshop and raise the shadows. The result is apparent. Also, 14-bit footage looks better in general.
#7
Quote from: a1ex on November 22, 2017, 01:56:33 PM
Do you mind sharing a short clip that shows the difference?

If possible, also a few DNGs.

https://www.dropbox.com/sh/67vforsr9ovuc86/AAB_ON_F-UNEugiSXh7AnCuta?dl=0

14bit shadows pull better and overall image looks better - more depth.
#8
Quote from: a1ex on November 22, 2017, 10:55:41 AM
After decompression, 14-bit lossless is identical to uncompressed.

(6D is an exception - each channel differs by a constant offset, but other than that, the image data is identical here as well)

Yes this is my mistake. The differences I am witnessing are between 14 and 12 bit.
#9
In order to avoid having to sync the H264 proxies with the RAW 14-bit lossless files in Davinci Resolve to have sound (when using Windows).

Integrated audio recording at 48kHz 16bit or 24bit with MLV Lossless would be a perfect solution for sound!

You're the man!!
#10
Quote from: Levas on November 27, 2016, 10:00:20 PM
Hello pixelpeepers,

I was wondering if people already seen/tested the difference in video quality of 10bit magic lantern raw vs 14 bit magic lantern raw.
I've used 10 bit raw today in the real world. And I'm used to color aliasing, and in most cases I have no problem in removing the color aliasing.
But the footage I shot today got very hard to remove, or almost impossible to remove, color aliasing.
Could it be explained in the difference between 10bit vs 14 bit, could that give more color aliasing ?
Or was it just a coincidence, since I shot a lot of bricks today, while visiting an old castle :P

Just recorded 14bit, 14bitlossless and 12bitlossless. 14bit looks better in every way. The differences are most noticeable with motion and colour as opposed to pixel peeping for sharpness and noise or something - although the noise is definitely lower with 14bit as well. There is depth and strength there that just does not exist with lossless. Lossless is great though, the small file size to quality ratio is awesome and practical.
#11
Quote from: masc on September 29, 2017, 10:39:53 PM
Thx. H264 audio? You record H264 and mlv at the same time and now you like to add the audio track from the H264 to the output of MLV App? Is that right? Hmmm...  I never thought about that, but for now we do not decode H264 files, just MLV.

Yes that's correct. I'm on windows and there does not seem to be an easy way to do this. The way I have been doing it is manually clip by clip in Resolve.
#12
When using MLVFS with Resolve editing with 10-bit lossless during final Export Dokany (Dokan Library-1.0.3) is un-mounting on a specific file. Even just moving the file on the timeline will unmount the dokany drive. This happens in every project it seems with different MLVs.

Thank you for any suggestions,

Cheers,
Erik

PS: I have organized all the MLVs in folders of less than 50GB in size.

*******
I think the file must be different in some way. My guess is from the card reaching full capacity during recording and the camera needing restarting.
#13
Cool program! Thank you for sharing.

Is there a solution for adding the H264 audio to the final proress export in windows using this program?

Cheers
#14
Quote from: Danne on September 20, 2017, 10:28:15 PM
A1ex implemented blackframe detection help in MOV files.

It´s fully working in Switch post workflow.
http://www.magiclantern.fm/forum/index.php?topic=15108.msg189604#msg189604

Also check from here:
http://www.magiclantern.fm/forum/index.php?topic=19300.msg189257#msg189257

I'm on windows 7 64bit using Blackmagic Resolve and MLVFS. Is there an option for me? The threads looked confusing..
#15
This method for syncing audio between RAW and H264 was discussed previously and I'm sure many others are wondering when it will be implemented?

Cheers,
Erik
#16
Quote from: eNnvi on June 27, 2017, 11:45:16 AM
Avoid putting too many MLVs in the same folder or many folders under mlvfs Scan base directory. When refreshing scans every file so probably means a overflow somewhere o too much cpu work

Thx for the tip eNnvi! I split up the folder that contained the .mlv that initiated the hang-up/loop and things seem to be working again.
#17
Quote from: dmilligan on June 27, 2017, 04:05:04 AM
It's totally virtual and the size doesn't matter.

Working on the same project in Resolve Beta 2 Win7 64bit with lossless .mlvs and virtual drive suddenly and randomly ejects (stops working - drive no longer reads "DOKAN").

1. Reinstall Dokany 64 bit and MLVFS 64 bit
2. Uninstall anti-virus products

And immediately upon opening the project in Resolve the drive ejects. It's a loop. Thankfully I have a backup but regardless I've been experiencing similar issues on other projects.

Any ideas/suggestions?
#18
Using Dokany wondering if the virtual files on the virtual drive that are exceeding the size of the original drive is a problem that is being resolved by ram shuffling files around or if it's actually totally virtual and the size doesn't matter or mean anything?
#19
Raw Video / Re: Artefacts on shooting RAW video
June 01, 2017, 07:46:15 AM
Looks like a bit of a moire/fringe/hot-pixel mash-up. What lens are you using? Have you tried using the "bad pixel fix"?

You can expect lots of bad stuff like that to happen when you shoot fine detail in front of an over exposed sky.

Work around..

- Don't clip highlights
- Use lens with no fringing problems
- Bad Pixel Fix or "Remove hot pixels"
- Shoot shallow DOF and close subject so background trees etc are soft & out of focus.

I see you also cranked the exposure which will make all the artifacts worse.
#20
Quote from: voblaunsane on May 30, 2017, 01:10:02 AM
Hi all,

It's been a while since I used mlvfs and now that I have fresh windows and reinstalled everything, took me a while to get this beast running..

Anyway, I am experiencing a massive stutter and general performance issue with 23.9 footage to the point where it is hardly possible to edit. I reported this long ago and someone found a timecode problem. I was under impression this was fixed and I think I was using it with no problems at some point..err..or maybe I'm dreaming? hahaha..

Or maybe using a wrong build or something..here how I got it working:

1. Installed Dokan 1.0.3.1000 (x64) from https://github.com/dokan-dev/dokany/releases/tag/v1.0.3

2. Unzipped MLVFS_x64.zip from http://www.magiclantern.fm/modules/modules/MLVFS_x64.zip/

3. Unzipped optimized.zip to MLVFS_x64 folder and renamed files adding "_opt" from http://www.magiclantern.fm/modules/modules/mlvfs_optimized.zip/

4. Renamed dokanfuse1.dll (in MLVFS_x64 folder) to dokanfuse.dll and dokan1.dll to dokan.dll

I tried all (mlvfs_x64.exe, mlvfs_x64_avx.exe, mlvfs_x64_opt.exe and mlvfs_x64_avx_opt.exe) and finaly capitalised on using mlvfs_x64_avx_opt.exe which seemed to be the fastest (super subjective/based on feeling)


all the settings on localhost panel are set to off, disabled, default or none (default values)

Same issues occur with footage copied from mlvfs drive onto HDD;
Yet unpacked using raw2cdng 1.7.5 works really well, not using mlvfs that is;

Also 25fps with mlvfs works like a charm too..


Thanks a ton! Good night..

Hey man, thank you for sharing your installation workflow in great detail but unfortunately the optimized versions are outdated and do not support the Canon HW compressed MLVs.

The problem I am experiencing is playback with the 12bit lossless files. Some files playback perfectly and some files, for whatever reason, do not. Large files (ex.40gb+) both lossless and raw do not playback well - maybe your installation suggestions will solve that, I'll check next project.
Also, perhaps some of these optimized mlvfs.exe files could include the lossless playback support to resolve this playback problem.

I think having a latest greatest CPU would just strengthen through this lossless playback problem possibly. Although that being said in Linux my 3770K was not working hard at all (40-60%) and the playback was still stuttering as if the drive was failing or the CPU was maxed. Then suddenly playback was perfect with all files all sizes.. until I hit stop and then play.. and stuttering ensues..

Sometimes with big files on Windows the CPU is maxed.
#21
Quote from: Walter Schulz on May 24, 2017, 11:13:47 PM
GTX 970 can be a beast. Nvidia messed up and performance drops for some games are reported.
https://forums.geforce.com/default/topic/855174/geforce-900-series/all-gtx-970-msi-gigabyte-asus-have-some-problem-/post/4601330/#4601330
Absolutely no clue if this drop occurs with Resolve, too. Please ask in Davinci forum how well Resolve and 970 play together.

No GTX 970 at hand. Will try looking if scaling problems occur with my (aged) equipment.

This is not to do with the GTX 970 or likely gpu related. This is to do with MLVFS not negotiating lossless 12bit smoothly despite latest support.
#22
@bouncyball @a1ex

When I mount 5d3 lossless 12bit .mlvs in linux they grow to 2x their original size in the mount location which surpasses the drive capacity that the original mlvs reside on. (1.4TB virtual files - 1TB Drive Capacity)

Does this explain the inconsistent stuttering performance problems I'm having in Davinci Resolve timeline playback?


Stuttery inconsistent playback in Resolve with 12bit lossless and Bouncyball's mlvfs mod. Not an issue with non-lossless.

When can a fix and update be expected?
#23
Quote from: Licaon_Kter on May 25, 2017, 11:39:29 AM
Oh come on, using a "letter in Linux? :)

"mount point" = /home/yourname/mymlvfsfolder/

;) first time linux user

hero user Danne who is the man got back to me with something to try and I removed some parts until I was left with the following which is currently working.

./mlvfs /home/ebaldwinson/Desktop/MOUNT_TEST --mlv-dir=/run/media/ebaldwinson -f -o allow_other

MLVFS is now playing back all file sizes equally in Linux CentOS 7. The only glitch I'm noticing is that regardless of the file size there is a seeking time of about 2 seconds to 4/5 seconds before it snaps to it perfectly.

Other than that this Linux Resolve situation seems really nice. Any tips more than welcome!

PS: Anyone know how to migrate a Resolve Project from windows to Linux? It look liks the .DRP from windows I tried to open in Linux is empty..
#24
Trying to run MLVFS in Linux CentOS 7 distro. Figured out how to use the Make function to generate the MLVFS file. Now when I enter in the terminal: ./mlvfs H: --mlv_dir=/home/ebaldwinson/Desktop/MLVS

I am getting back a "Fuse: bad mount point"? Changing the mount point to different letters doesn't seem to return anything good. What does it want? What code are other linux users using as a mount point?
#25
Quote from: Walter Schulz on May 24, 2017, 11:13:47 PM
GTX 970 can be a beast. Nvidia messed up and performance drops for some games are reported.
https://forums.geforce.com/default/topic/855174/geforce-900-series/all-gtx-970-msi-gigabyte-asus-have-some-problem-/post/4601330/#4601330
Absolutely no clue if this drop occurs with Resolve, too. Please ask in Davinci forum how well Resolve and 970 play together.

No GTX 970 at hand. Will try looking if scaling problems occur with my (aged) equipment.

GPU load is very low playing back large or small files, less than 30%. And the memory being used is only 1GB.

So what you are saying is that file size is not the issue. You are confirming you can playback 10, 20, 40GB + files with MLVFS smoothly? Yes or no?


Installed Linux CentOS 7 with Resolve 14 and this seems to have resolved the playback of large files. There is now a short seek time of about 2secs with all files tho, any tips on improving that are welcome.