Messages

what is the native iso for the M?

greetings!

I've been having some errors while playing with MLV which generated a handful of crashlogs. I'm just recording and trying to focus with the * key. It only focuses once until I stop and start a new clip. Error occurs when I stop recording. Error logs are here: http://tl.bot-fly.com/misc/crashes
THAAAANKS =D

I have always crashed using any build since last July if I try to autofucus when shooting raw.

Of course if encryption is on it will take more memory and try to encrypt anything you write to the card. Dot tune you don't load because there are no adjustments for focus in EOSM.

then that says something for RAW over MLV since RAW always recorded when MLV choked. [ was in the habit of installing all the modules instead of loading just a few modules. I thought for testing purposes the camera should work with all modules loaded.

Yes, it is because Ginger HDR plugin... Very nice, thank you!

yet, there is no interaction with the plugin. i just installed it to the correct folder for ppro. i assume it is doing something in the background.

Proxies are veru useful.
It's impossible to work with DNG in real-time.
So I edit ProRes and replace it with DNGs (making color correction) before final render.
Don't see any other way to work with RAW faster

I drag n drop ML RAW files straight into PPro CC ver 7.0. I can play them in real time with the Quality set to full. Now, what can be faster than that? Do not use PProCC Import and MLV files will not work. The adobe 7.1 update does not work i also have the Ginger HDR plugin installed and maybe that is why it works. I don't know. It just works and I can also apply effects. All raw files are noisy so I use Neat Video "after" the edit is final because that filter chokes real time playback. I also use Ginger white balance if needed and adjust levels with adobe fast color corrector if needed. If you keep Neat Video disabled, then it all runs real time with the full quality setting.

I love BATCHelor. But as MLV can record audio now and fixed all initial bugs most people probably switched from raw to mlv.

Will BATCHelor be updated to also do MLV?

1%,

MLV Rec does not work again using the latest TL Feb 25.
message says  Threads failed to start and the camera hangs requiring a reboot. Sometimes a battery pull is needed.

I unloaded the crypt mo and then MLV Rec worked. We also still need to not load the dot tune module for the camera to work.

Sorry if you have already seen this, but i posted a bit ago with no response. If it is a dumb question feel free to ignore it.
I always get the error "MLV2DNG has stopped working." any ideas? I have a brand new very quick computer (Windows 8.1), and Ifran, MLV viewer, and Adobe DNG converter are all installed. Any ideas?

I was getting the same errors today. windows 7 64 bit

Gary,
I think we should suggest the correction of ProRes with "raw2dng_cs2x2_ahdlike_noise.exe" on the apps "mlrawviewer" from baldand. That is the apps for ProRes inside MLV Converter, except for the output DNG.
Please, correct me if I am wrong.

Pilgrim,
Whatever it takes to go from MLV to ProRes that gets rid of the pink dots on the EOS-M camera.

Edit- I just looked at mlrawviewer and tried it. it seems to only be a raw/mlv viewer and i cannot get any of the options to work for MLV files, such as brightness, white balance, etc. These options do work on the original ML Raw files. how do you get it to do prores and dng's? i have a feeling it takes some programming since there are no menus or anything except space bar for start and stop playback. I admit I didn't read the whole thread. Just the OP and downloaded the app. Tony's app does most of what I need except the pink dot removal and no raw files (just mlv).

I just realized that we need a PDR inside this app to use the proxy/ProRes feature. It is useless since after it becomes a ProRes file, we cannot get the pink dots removed. The only app I know of for MLV files that reduce pink dots is the set from Alex, such as raw2dng_cs2x2_ahdlike_noise.exe  Maybe that could be incorporated inside this app?? But, from what I understand, not all cameras get pink dots and the original PDR app had to use a specific map for each camera, like my EOS-M, because the pink dots always have the same position when shooting raw/mlv.

I use Neat Video filter for noise reduction inside PPro CC on the ProRes file created from Tony's app, but it does not get rid of the pink dots. I tried, in addition, the dust and scratch filter which does help reducing the pink dots, but at the expense of softening the whole image and that defeats the purpose of shooting raw for crisp, high resolution.

If am wrong and missing something, someone please fill me in on how to do it. This is on the EOS-M camera shooting 720p24 crop mode.

ok, i'll give it a go.. a bunch went in today from ML

ok, seems to be working after the push today.

MLV Rec is now working again in TL Feb 24.

If you flush every 30 frames then you're keeping them all in the buffer. If you do gop 30 then that is the longest one you can have at 30fps... all of the frames will be referenced to eachother at least in theory.

1%,

if I flush 30 and GOP 1, will that then make it Intra-frame? not inter-frame. and if so, would VBR be better or CBR for the best quality?

Thank you,
Gary

ok, i'll give it a go.. a bunch went in today from ML

ok, seems to be working after the push today.

same thing with TL Feb 23 build. No MLV recording, but RAW will record as usual. Same message at start of MLV recording then it hangs the camera. "Threads failed to start"

Is there anything wrong with using flush rate 30? I am using TL Feb 21. I do need audio and 1080p30 all the time. Audio off seems to allow better settings.

How many people out there with the M and TL? Can we get everyone to post their best settings for H264? Would it be better with a new thread subject POLL EOS-M best H264 settings?

Here's TL1.

Here's TL2.

TL1 has more h264 controls (for the 600D) than TL2.

which one is posted daily on http://tl.bot-fly.com/  ??

Please expand this feature even more! \o/

I use ProRes for editing and final delivery. Usually, after converting to DNG I will use AE to convert to ProRes 4444 10 bit or 422 for editing and grading. This means the ProRes version would look really flat/use a log gamma so it will grade nicely, and since it's an edit friendly format, it will playback smoothly without a hitch.

It'd be nice if I can skip this step and just get a setting for the various prores output. This is without a doubt, a crucial feature to have.

Currently, I can't seem to set the LUT (the No LUT on the proxies section is always greyed out)

Also, the output files always suffixes with Proxy1 and Proxy2. Would be nice if it suffixes the type of prores it is (e.g. ProRes422 and ProRes4444 suffixes)

Btw, is it possible to have the output folders automagically filled in as child folders of the input folder? (and ability to ctrl-v paste a folder into the box?)

Another feature that would be crucial to have would be the Pink Dot Removal for us EOS-M users and (I think) 600D, 650D, and 700D, to remove the in-sensor phase detect pixels recorded with the MLVs.

Anyway, enjoy your vacation and thanks for all the fish!

+100

i never heard of TL version 1 or 2. I just always download  http://tl.bot-fly.com/

good catch. thanx

I have never tried the flush rate that high until today. and i also saw before that the bitrate setting will depend on ISO. meaning, the higher the iso setting i use, the lower the bitrate had to be set so it would not crash. usually use between 100 to 1600 iso. but when i tried 320-0, i had to lower the bitrate. a CBR of 2.5 seemed to work the best for all iso settings. these tests results i just posted here were all iso 800. i do not know if these high numbers are good or worth using for some reason. it is just what i was able to set and working without crashing.

1%, today's build of TL for the M does not allow MLV recording. Raw recording does work as usual. same settings I always use.720p24 crop mode all audio off 16x9 global draw on, MLV starts in red and says 1 line skipped and thread failed to satrt. hangs camera requiring battery pull.

Edit-Update. after i unloaded the crypt module, I was able to record MLV. Start and then Stop recording. BUT, then I could not access TL anymore with the usual two finger swipe. or, power off the camera. pushing power off pops up "Busy". i had to pull the battery.

[Can anyone compare the quality of RAW and H264 produced from these two cameras, running ML/Tragic Lantern?]

Can anyone compare the quality of RAW and H264 produced from these two cameras, running ML/Tragic Lantern?

In general, first, with ML settings optimized  (bitrates maxed, etc),
how would users compare the resulting RAW and H264 results on these two cameras?

And, more specifically:
I saw some lovely examples of H264 video shot on a 600D, that looked almost as good as RAW; the comments indicated that using tragic lantern they'd jacked up bitrate (played with Slice and GOP settings too i think?), and were getting something like 90-95Mbps, so the video didn't have nearly the compressed look I'm getting on my EOSM.
I'd really like to have one of my cameras running H264 with audio, while the other does RAW (two camera documentary shoots), so getting the H264 to look that good would be absolutely great.
But my EOSM is limited to 40Mbps, so I'm thinking that's why I'm stuck with so much more in the way of compression artifacts?  So,
WOULD BUYING A T3i GIVE ME A MUCH LESS COMPRESSED-LOOKING H264 video result?   
HOW MUCH DIFFERENCE IS THERE?
Thanks!

raw in crop mode gives excellent resolution and greater range for color grading. but, what a hassle and huge amount of time just to get the raw on a NLE timeline to edit. might be fine for a small thing like a commercial but imagine how long it will take processing all the raw files on a documentary. and forget shooting a long interview with raw. same reasons. get a BMPCC if you want prores or raw to work with in a decent amount of turnaround time.

Save half or more of your money from a T3i and get the M. I had a T3i. the only thing i liked more about it was the articulating screen and the normal lense mount. Same quality images/video from both cameras using the APSC sensor.

I have the T3i, and I just got the EOS-M.

The T3i can use Tragic Lantern 1, but the EOS-M cannot, so there are more h264 settings available with the T3i (D-block settings, most importantly).

Not true at all. I have used every nightly build of TL since last July without any problems. Read all the threads for the M. And read my latest post I just made about H.264, CBR up to 20. 0, flush rate 30, GOP 1 shooting 1080p30 with audio on the M.

The best GOP setting would be "1," as that setting eliminates inter-frame compression and its artifacts.  Some folks report good results with a GOP of 3 (inter-frame compression across two out of every three frames), and that setting allows a little more boosting of the bit rate.

In either case, the bit rate can probably be set to CBR 2.5 with a fast card and a fairly complex scene.

Perhaps someone else can chime-in on ideal slice settings, etc.

I have the M camera. I just did some testing of various settings shooting H264. I am shooting 1080p30 with audio on. F2.0, 1/64 shutter and iso 800. I managed to get CBR 10.0x, flush rate 30 and gop 1. I was surprised, but i never tried the flush rate that high. it might even go lower, but a flush rate 10 was crashing no matter what CBR setting I used. I also have a Sandisk 32gb, 45mb/s  write.   A faster card will be of no use on this camera since the internal hardware cannot write above an average 36mb/s. I was also getting bitrate readings around 30 for A and B. In the past I was able to get up to 115 bitrate readings with certain CBR settings.   
This was all done using the latest TL build from today. 

Edit, I just shot with the CBR at 20.0 and it still worked. Is this good? I don't know.

There are legacy versions for Win too

Duh, I now found it right at the top inside a drop down menu. Seems to work ok. I wish it had batch processing.

Lol. I always use it man. It installs lots of stuff because originally it's a software from Linux. But it's the best I found that can convert a tree of folders... anyway, just have a little faith It DOES convert H264 to Prores, the only thing I use it for...

where and what exactly are the settings you use for the prores? I saw DNxHD options, but no ProRes were in that list.