Messages

Thanks g3gg0 and a1ex!

Your camera will either skip frames or stop recording. You can specify. It does not hurt your camera or card.

Here is a test frame which includes the vertical banding. Some info on the shot, it was shot yesterday on the latest nightly build then, taken through the latest mlv2dng on the first post of this thread. I have no idea what is relevant so I will just post everything. No Dual ISO or Auto ETTR, shot manual, WB was set to Tungsten in camera, mlv2dng changed WB. I did not touch ACR at all.

5D3, 50mm, f1.4, ISO1250
MLV Video & Sound (.wav not included)
Resolution: 1920x818
Global Draw: Allow
Preview: Auto
Extra Hacks: On
Buffer fill method: 4
CF-only buffers 3
(if option not stated, it was off or none)

Link (Active for 1 month or so): https://www.dropbox.com/sh/r6vqv5g8m6frt85/Ih5aVJ0Q1G/MLV%20Test%20%28Vertical%20Banding%29

I know the vertical banding has been fixed with raw2dng, but I seem to still have it with the mlv2dng. I haven't seen any news on it in a while. The workflow and use of sound in mlv has made that format very practical, especially for larger projects. But, the vertical banding can be discouraging. Any news? Am I looking at the wrong threads? Need me to run some tests? Here to help.

I just wanna say thank you! Everything you guys have been doing are what Canon and other companies higher huge teams and pay them quite well. You guys are doing this with a small, passionate team that work off of donations and in your free time. Everyday I see new milestones being reached! With this batch editor, this makes larger projects more practical. The technical side has been very fine tuned, just the work flow has become difficult for those not the most familiar with all of the different directions they can go. Glad you included the compression, that also makes it more practical for those who don't have top of the line machines and space. It is extremely hard to tell the difference and you cut the space by a fifth or so. Works great and I don't have any more ideas than the ones already said. Great job!

Just downloaded the latest, works perfectly! Thanks!

I downloaded the latest nightly, I went though the MLV and IME forums and downloaded the latest which were on your first post and had them over write any of the previous files from the nightly and got the same error. I feel like I am doing something wrong?

Will do. I'll post any news.

As much as I would love to learn, full time school and work take me away...

What I did was downloaded the lastest 5D3 build and then the latest IME modules from your sticky post. There was a link to download them from the bottom of your first post. I enabled all three, restarted, then this message came up.

I just updated everything on the 5D3 and it says:

Linking..
tcc: error:undefined symbol 'malloc'
tcc: error:undefined symbol 'bfnt_printf'
tcc: error:undefined symbol 'free'
    [E] failed to link modules

Hey ML team,

I have been trying to get the text input for MLV on the 5D3 to work (text, take) but, I cannot put anything in. I have tried the IME module but, it did not work, I assume it is older. Am I suppose to make a .txt file on the card before hand or something? Thanks!

Very cool!

Did you go out with a tape measure and chalk to measure it all out before shooting? And, I think I saw a push/pull near the end!?

What if it is just put in how it is or was previously? At least just for now, because shorter clips can work for dialogue or give a starting point for scratch audio for a music video. Even if they are slightly off. It may also inspire people with more knowledge to implement it properly. I sure have no idea.

I got this message when I tried to open the .dng files in Pr and Sg CC with the latest update. Downloaded all the latest versions of 5D3 ML, latest modules of raw_rec and mvl_rec, and raw2dng and mvl2dng.

Premiere Pro
Error Message:
The file appears to have no media data.

SpeedGrade
Failed to decode frame.

I am on PC, is this a PC related issue?

Been searching for a fix most of the afternoon and haven't found one yet. Ideas?

Thanks for the info. And, the peace of mind!

I was testing out the latest for 5D3 (Oct 2) with the bars facelift. Like the new design btw! Along with it it also displays your temp which I like. I wanted to test it out the temps out of curiosity and just played some exposure settings and then let it record for about one minute at 1080p and it jumped up to 60C which was red. So, I shut it off. Then, I went back in after a few minutes and it was sitting at 49C. I was just going through the menus and seeing if there were any updates. When I went back to the LiveView it was in the orange. I was wondering if this was typical and others have been experiencing this. Have I been running it too hot far too long? I looked at the Canon site and it said the operating temps were 0-40C. I would assume that would be the environment temps and not the camera itself. Thoughts? Am I just worrying too much? Is the color coding too low?

I have used the 5D3 ML RAW in the field before. Midphase makes great points. If you are worried about capturing moments that cannot be redone, I would not recommend shooting RAW. If I had to guess, I get a stopped recording about 1 in 50 shots. If you have a ton of footage, expect at least a day just to convert footage to a usable format. So, if time is of an essence, I wouldn't shoot RAW either. If you aren't familiar with using proxies and have a not so powerful computer, you will be ripping your hair out with load times. I would recommend getting cards at least 64 GB, that is about 10 min of footage. I would also look into your workflow in the field with transferring data to an external hard drive or the alike. You need to transfer things fast. USB 2.0 will be very slow and you will be waiting on your cards to dump to your storage device. USB 3.0 will transfer 64 GB in about 10 min, which is time efficient. All of this can be worth the quality you get but, you don't need to shoot RAW all the time, if it is a controlled scene, you can get by without shooting RAW and with proper editing, pixel peepers would have trouble telling with YouTube compression. Nonetheless, practice, test, research and come up with an efficient workflow before you get in too deep. MLV is looking promising, I would look into it and maybe wait for it to be finalized.

After the black bars were taken care of, we are looking at 8 pixels. eg. 1928. Less than previously thought. Not really worth it.

It very well may have been a bug. I will check it out and see what I find. I'll look up the older builds too if they are around. You guys know your stuff so I doubt I will find anything you guys don't know or worth talking about. If it is only 10 pixels, I doubt even pixel peepers would find a difference.

Yes, which is slightly over. But, you could also go bigger than 1920. It is just a few pixels, more one way than another. The point is just a bit bigger to help some quality while removing some shake at the same time. Example could be: handheld shot with 1% Warp Stabalizer in Premiere/AE gives a nice "dramtic" look, especially for conversations. Not those fast little shakes you get with light dslr's but, smoothed out camera motion. You don't need much at all for gear to get that look so run and gun is very easy. And, time is always of the essence as we all know. There have been a few times where I wish the frame was just a bit tighter or straightened out a bit. This would help.

I will have to do more digging when I have my camera in front of me to give you more details. I remember it was there because I was excited about it an ran a few tests and was happy with the results. I do not have much knowledge on code writing and no idea how long or how difficult it would be to bring it back. I also know there are more important things on your plate such as MLV. It would just be a nice addition again to get everything the 5D3 can offer.

Unfortunately, I no longer have that version. But, I do remember it was when you could select your resolution by horizontal and vertical resolution instead of the aspect ratio and one of the resolutions. If you tried to go larger than 1920x1080 in the older version, it said it maxed out at a certain number which was just a bit larger. In this video at 8:15, Dave Dugdale says he recorded just a bit bigger than 1920x1080 and scales it to 101% to match the H.264 version. http://www.youtube.com/watch?v=CBDacTLTGxo Since the video came out Jun 5, 2013, I would guess it would be a build a bit before then. This is for the 5D3 model if that matters.

I am confused on what you want to have proven? I may not have written my idea properly. If it is regarding longer focal length leading to exagerated camera shake with handheld/steadicam, I can give some reasources supporting that. If it is having a 16:9 ratio using all of the sensor avaible so it is just a bit more that 1920x1080, even just a little, it would help maintain some quality with scaling 101-104% using stabalizing software in post.

I remember in the beginning stages of this latest addition of shooting RAW, there was an option to shoot just slightly over 1080p and take in everything the sensor has to offer. When ever I do handheld or steadicam, I use warp stabilizer at 1% just to make the shot movement a bit more fluid and I notice it is always scaled up slightly to about 101-104%. I know you can zoom in 3x and shoot over 1080p but, I would rather not use that method when possible because camera shake is more noticeable. With those few extra pixels to play with, the scaling up wouldn't hurt quality at all. I know there are a ton of other things on your guy's plate and have no idea how hard it would be to include this or not but, it would be a nice addition again. Thanks for everything ML!

I use a WD 2TB HDD USB 3.0, Lexar Card Reader USB 3.0, Windows Surface Pro (USB 3.0), and Orico 4-Port USB 3.0 4-port hub. All running at USB 3.0 so, a 64 GB card can download to my external hard drive in 8-10 min and it can hold about 4+ hours of footage. I have two 64 GB cards so I can swap while one is being transfered. A 64 GB card holds about 8-10 min so, it works out just fine for time effeciency. I have tried to use BATCHelor while off loading my footage and compress it to 'lossy' (cuts the size in almost half and converts to .dng) which I have yet to see any difference in quality, but it is too slow. I save that for when I get back to my desk. I haven't had a project where I require 4+ hrs of footage in the feild in one day but, just have extra hard drives and use the open slots on the hub. Also, this method runs on batteries! No external power source required, just watch your bettery life though! 

Equipment links:
http://www.newegg.com/Product/Product.aspx?Item=9SIA1DS0HF2994
http://www.newegg.com/Product/Product.aspx?Item=N82E16822236187
http://www.bhphotovideo.com/bnh/controller/home?O=&sku=845797&is=REG&Q=&A=details

Good info!