Messages

Please run CrystalDiskMark benchmark for this drive and post a screenshot.

GPU: NVIDIA GTX 970**
GPU has 4GB of VRAM
See Full Descript here: http://www.geforce.com/hardware/desktop-gpus/geforce-gtx-970/specifications

-

Samsung 960PRO 1TB M2 in PCI Express Slot

1GB Test


32GB Test

I'm not a developer but I can suggest you to ask your question also to Blackmagic: https://www.blackmagicdesign.com/support/contact/email

if possible write here their reply maybe this could help someone here to help you better. bye!

Davinci Resolve says it is playing back 23fps but it is clearly 8 or 12 or something. I don't think they will help. I think this is to do with MLVFS.

Can anyone confirm smooth playback of say a 20GB file in MLVFS in Resolve?

Maybe I have the opportunity to reproduce this. May I ask about GPU, CPU, RAM. RAMDisk or any other modifications?

GPU: NVIDIA GTX 970
CPU: INTEL i7-3770K @ 3.50GHz
RAM: 32GB (8gbx4) Corsair Vengeance @ 1600Mhz
Storage Drive: Samsung Pro 1TB M2 in PCI Express Port

I cloned windows to a 256GB Samsung 850 EVO to see if more space would help - it doesn't help.

I agree about the sound. In my opinion the lack of sound integration is the most significant short-coming of magic lantern. I record the h264 proxies but they require syncing to the mlvs in post and it is exhausting.

Maybe a funding situation can be organized or something to basically achieve synced sound asap. Then plural eyes can do the rest for external recorders.

MLVFS in Resolve on a Samsung M2 960Pro 1Tb and playback is great as long as the MLV file is SMALL (less than 20GB). As soon as I try to playback a 40GB+ file the playback is about 12FPS but the CPU is not working that hard, only 60-70% and plenty of memory available and not much drive traffic.

Any ideas on how to get MLVFS working great with large MLV files 40GB+??

I'm on Win7 64bit in Resolve 12 and 14 beta.

One workaround is to just record short files but this increases the post work flow because I have to sync up the H264s to get the audio (frame match with opacity and two layers)..

Is this possibly because of limited space on the OS drive?

I'm having the same problem stuttering problem with 12bitlossless mlvfs in both Windows 7 64 and linux centos7 in Resolve 14 beta2. In windows its awful, in linux it usually sorts itself out in a couple seconds but it makes editing tiring.

I've been running trial and error with nvidia gpus.

GTX 970 = bad
GTX 1060 = not good
GTX 1070 = not bad still not good

I've overclocked my 3770k to 4.4Ghz, turned off intel speedstep and other power saving stuff in bios and it's working at around 40%-60% capacity in Linux.

The stuttering seems like a hard drive issue but I have a samsung m2 drive in the pci port that does well on the crystal mark test.

The GTX 970 was not doing any work at all according to the gpu monitor at around 12-20% and 1GB of memory max used. This is basically the same case with the 1060 and 1070 yet playback performance is quite obviously a noticeable improvement from the 970 as the stuttering is less.

Why are the GPU monitors stating only 20% load and why is Resolve stating 23.98fps playback when it is clearly stuttering and playing back maybe 12fps?

I also turned off v-sync.

I have a feeling there is something else going on and upgrading the gpu is just easing off the tension indirectly helping the problem.

Any ideas? Trying to finish a project.

I've installed the latest version of ML with 10 and 12 bits colors featured, but can't find how to change the color settings to 12 or 10 Bits,
where is that option?

Magic lantern Menu > Movie > RAW video > (press Q and scroll down to..) Data Format >  (press set)12-bit or 12-bit lossless

It seems that 10bit causes vertical lines so avoid that and you're good. Basically 12-bit lossless is your best option it would seem. I haven't personally ran the tests but others indicate this is the case because 10bit won't pull shadows up without introducing noise and 14bit is no noticeable improvement from 12.

Using 5D3 4k crop Latest Build (2017-04-29 14:30) doing audio test and have noticed that the ML audio levels are reading very low compared to the internal canon levels that can be found in the canon menu.

Don't see why it would matter but for context I have a sennheiser ME66 plugged into a JuicedLink plugged into a H4N plugged into the 5D3.

I look at the H4N levels (gain set low) and they are hot, I look at the Canon Menu levels (gain set to lowest) and they are hot, I look at the ML levels and they are not hot or even close.

Quick fix possibly?

Did a quick un-scientific test of the same scene in 10-, 12- and 14-bit 1080p.
Only 10-bit shows the horizontal stripes, so the best workaround when using MLVFS seems to be shooting in 12-bit!

10-bit:
https://www.dropbox.com/s/hkb87e6shaads76/M18-2044MLV_1_2017-05-18_0001_C0000_000000.dng?dl=0

12-bit:
https://www.dropbox.com/s/ty2kvj9oynp73l2/M18-2045MLV_1_2017-05-18_0001_C0000_000000.dng?dl=0

Problem solved! Easy workaround, thank you!

Im bad at shortening MLV files, so here is a DNG:
https://www.dropbox.com/s/0h6clqcxnsb2njt/M26-1259MLV_1_2017-04-26_0001_C0000_000031.dng?dl=0

As Erik said, its not bad, but its there.

Yours is very mild! But yes it is there still ever so slightly. Mine is more moderate, I'm thinking maybe it's worse with 10bit than 12bit. Shot 12bit lossless and will review those shortly.

I meant the original MLV samples that shows this.

Voila!

https://drive.google.com/open?id=0B4vmGGvYWCzJYlQ1QXEwR3VYWUE

Care to share some original samples guys?

https://vimeo.com/216951179

Here you go, if you watch the out of focus mids throughout the video you will see them. It's not BAD, it's just there.

Using MLVFS on Win7 in Resolve 12.5 free with 5D3 10bit footage and there are vertical Stripes in the MIDS with the fix checked.

Do I just have to live with this or am I missing something?

Would it help to mark the first MLV frame somehow?

An example would be changing the exposure only for that first frame, so it can be recognized easily in H.264. Turning it into a bias frame (by setting its exposure to 0) could also be interesting, and it's easy to implement.

Alternative (requires reverse engineering): save a sidecar file with a ffmpeg command that will cut the H.264 stream to match the raw one.

Hey Alex, is there anyway to include an option in magiclantern that syncs the mlv and h264 recording start and stop times perfectly at the cost of a delayed start (ex. recording in 3..2...1...) and delayed stop so that a user could drag and drop all the h264s into a timeline on layer 1 and all the mlvs into the same timeline on layer 2 and it would be synced naturally. Then the user could link the files within resolve for ease of editing?

That's the best I can think of so far. If not, your idea of a white frame would be better than the current situation. I would basically drop all the footage into the timeline and then begin sifting through lining up the white frame of the mlv with the h264 before linking the files. I'm going to try and find some frame matching plugin meanwhile.

What can be done?

Davinci Resolve timeline has a sequence of 5D3 H264 proxies that include audio and I'm wondering if there is an easy method for matching up the MLV files with some sort of plugin or resolve function?

Right now I am creating a second layer, bringing down opacity and sliding the mlv over the h264 until the frames match - time consuming.

Thank you,
Erik

Do you still use the DNG's in Resolve?

I am. I notice that MLVFS is always negotiating. Sometimes the big files are playing back perfectly other times a restart makes it snap to it. I haven't found perfection here but mlvfs in resolve is allowing me to avoid converting the mlvs and color correct as a final step before export which is the flexibility I was looking for.

Now noticing that sometimes I'm getting almost no playback with some of the big MLV files, as in 20min long recordings. It'll play 2fps back. And then immediately following that suddenly other files resolve say are playing back 24fps green light stop playing back properly and are lagging intensely. I restart computer and suddenly it plays back properly?

That's pretty quick. I find MLVFS substantially slower than dealing with normal DNG files.

It's coming off the samsung 960pro 1TB and the playback is good but the file directory is still laggy. I was also wondering which dokany & mlvfs.exe files are the fastest. There seems to be a few different packages. ex. latest mvlfs.exe mod supporting 12bit lossless

Selecting "Davinci Resolve file names" did not display anything in the folders.

Highlighting the folders and dragging them into the media bin works, about a 20 second delay/lockup for 128GB of mlvs - sound about right?

Is there a method to importing mlvs into Davinci resolve that is faster than manually clicking each folder and individually adding each video file?

1TB 8 cards of footage... :*(

Cheers,
Erik

Switched to resolve recently and haven't found a reason to miss premiere yet.

Right, I had two commits in the raw-h264-branch that I thought were included, but looks like they were not (I've never actually tried this feature on this branch). One is a workaround to prevent hard lock-ups when the H.264 stream stops, and the other attempts to sync the file names.

Last time I've checked (a long time ago), I had good results with H.264 IPB on SD, but recording stopped very quickly with both on CF (don't remember much about ALL-I).

Build updated.

Hey Alex, unfortunately those changes you made to the latest build (2017-04-27 21:51) didn't do it. It still only records 6 seconds ALL-I or IPB before I get an "emergency stop" notification on the live view. Tried 12bit lossless, 12bit raw, and 10bit raw, makes no difference. I made sure to set record to card 2 (SD) in the canon menu each time.

Thank you for the recommendation and explanation why!

In theory and as you understand it, is there a possibility that the last 2 bits provide some type of head-room for difficult shots? Or would you say 99% not likely..

Thank you Alex!

Quick question, are there any real strong incentives to record 10bit raw instead of 14bit lossless besides possibly better stability with crop mode build?

Hey, installed latest build on 5D3 today as I was really hoping to record 24fps 1080p 14bit lossless on the CF and proxy files on the SD.

Unfortunately, the proxy files will only record for about 6 seconds or so before live-view locks and the battery needs to be pulled. Recording both the 14bitlossless and proxy on the CF card results in the same/similar result.

With the latest crop mode build recording 10bit 1080p on CF and proxy on SD works great!

Anychance I'm missing something or there is a quick fix for this? Cheers