Messages

Hi braxtonk,

Thanks for the feedback !
We used the shogun for two reasons. First, comfort and monitoring (the small 5D screen is too small) and second, to record the takes and be able to play it back for validation purpose. MLV is great but you can't play it back smoothly in full res so it's hard to tell if the actor's performance was good or not. Any other recorder would have done the job but we happened to have a shogun at hand

Hi everyone,

We'd like to have your opinion on our first short film we did for the RODE REEL competition using the MLV feature.
If you like it, feel free to vote for us so we have a chance to win the public choice prize and give it back to the community for this amazing tool you guys created.

http://www.rode.com/myrodereel/watch/entry/876

Thank you guys !

Sadly yes, same result with mlv_dump
I can provide a DNG file for whoever wants to try something. It might help others that encounter the same problem. Thanks again.

Hey Deaf,

Thanks for the reply. I shot it in 24p in normal mode (not crop mode). I had corrupted footage before but never that one in particular. It's weird because 15% of the frame (the offset part) is not pink, and is actually good to use (well, per say) but the rest is pink.

Don't know what to do with it. It is the only footage from cam B that I have (about 2 minutes long) and now I'm screwed for the edit :/

Anyone had this kind of issue before ? Pink frame coupled with a shifted cropping. Is it recoverable ?



MLV Nightly 2014 sept 27 5D3 1.1.3 - normal mode

Thank you !

Thank you for the feedback lostfeliz !
I think I will update to 1.2.3 to benefit from the clean HDMI out. As you explained, not easy to pull focus on a 480p stream.

Have you noticed any problem while using 1.2.3 ? I generally don't record for a long time (2min at most) so it shouldn't be a problem. But I'm more worried about interviews that tend to last for more than 15/20 minutes, where 1.1.3 seems more efficient.

Thanks !

Hey everyone, quick question about external monitors.

I'm using 1.1.3 since ages and I've been following the 1.2.3 development since it's been released without feeling the need to upgrade.

I'm about to shoot a personal project using a DJI Ronin using RAW and the question of external monitoring comes. I know one of the benefits of 1.2.3 is clean HDMI out, but from your experiences, is it worth the upgrade ? I mean, is the 480p out from 1.1.3 really dirty and unstable ? And if I upgrade to 1.2.3, are there known issues with external monitoring, or will it work seamlessly ? Is there a thread dedicated to that (I've read the forum for hours).

Last observation about upgrading/downgrading firmware back and forth between 1.1.3 and 1.2.3. I've read that some of you guys do it on a regular basis ("happy swingers"), but I recall a1ex saying we might avoid doing that because each time it moves/removes/add code into the camera core and it can have consequences in the long run. Is that really critical or just a general guideline to avoid up/downgrading 5 times a day ?

Thank you so much for the work you guys have done and keep doing. I really hope to see a1ex getting back on it, and I hope I'll be able to contribute again to this fabulous project.

Thanks for your feedback dyfid, that would explain why I don't get this behavior on my iMac 2011 which implements AMD graphics. This means Resolve cannot be the solution when working with newer macbooks. Dang !

Nope the clips are straight CDNG added in the media pool and played without any modifications on it.
I reinstalled the 11.0 version from the app store and I get the same problem BUT when I add a LUT on the problematic footage, it goes away and I'm able to render it correctly without any corrupted frame.

So I'm a bit confused right now, I have no idea what's going on, it is still an annoying problem to deal with but it seems that I can make it work by tweaking some settings in the RAW panel. Weird.

Does your graphics card and graphics drivers meet Blackmagics minimum spec for Resolve? What operating system and how are you feeding your monitor?

If it were "simply a problem with Resolve" then all the other Resolve users out there would have same issues. I'd look closer at your setup first.

I'm on a Macbook pro retina 2.3Ghz 16GO RAM Intel Iris Pro so no reason for Resolve to behave like this in my opinion. And again, not the whole footage is corrupted but only some frames in it, and when I tweak one of those frames (contrast, WB, exposure...) it goes back to normal permanently. And as I mentioned before, the same footage in lightroom presents no corrupted frame at all.
That's why I deduce it comes from Resolve and not the build, but I might be wrong.

Levas, I can't see your screenshot. Is it the same problem ?

So no one experiencing the same bugs with the newest beta of Resolve ?

Hi Rob,

After playing a bit with the settings in Resolve, I think it's simply a bug in the new version. If I set the playhead on the problematic frame and change a setting in the RAW pael (the white balance for example), the frame becomes normal and stays normal. But the footage still appear corrupted when I move the playhead on other frames. I need to grab the earlier beta versions of Resolve 11 I think. Anyone knows where to get it ?

Hi everyone,

I'm on a different computer than usual and I just installed the newest beta of Resolve (11.1), imported a CDNG sequence converted from MLV files by RAWMagic 1.2.2 and I get very strange colors on some frames, on every footage. Those frames look black-and-white-ish, kinda like a GIF file. I thought maybe it concerned only the preview in Resolve but it is here when I export a prores proxy.
Here are two screenshots. The first one is the normal frame without any problem, and the second one is the problematic one :



I haven't experience such a thing before. I'm using the nightly build 1.1.3 2014-08-31 on a 5DIII. I've imported the sequence in lightroom and everything seems OK, so I can deduce it comes from Resolve and not ML. Anyone having the same issue, and managed a workaround ?

Thanks !

Hi everyone,

Glad to share with you some of my early work in the wedding ecosystem using RAW only :

Feel free to ask for technical details !
Cheers to the ML team !

Hi everyone,

Been using ML and reading the forum for a year now, love it and thank all the people involved in this project a million times. I just created an account to get some feedbacks from you guys about something weird regarding CF write speed.

I've been using this Lexar 32GB 1000x for my ML tests so far : http://www.bhphotovideo.com/bnh/controller/home?O=productlist.jsp&A=details&Q=&sku=841566&is=REG&fromDisList=y
which is given, according to B&H, to be able to write at 95mb/s. Yesterday I got the new Sandisk 128GB 160MB/s and was hoping to get massive write speed improvements since it is given to be able to write at 150MB/s.

Well, after few hours of tests, I'm quite disappointed by this card and the results. Here are two 5 minutes benchmarks for both cards, and... Well, as you can see, the Lexar one, which again, is given for 95MB/s, achieve 118MB/s write speed, while the Sandisk only reach 110MB/s at most.



Can anyone explain me how is it possible for a CF card to write a lot faster than its original write speed (not that I'm not happy with it), and another one to write a lot slower than its theoretical speed ? I mean, my old Lexar is way faster than this new 160MB/s, and I can tell you that it is true in real world situations.

Thank you everyone for your time and answers, hope you can help me understand what's going on.