Topics

I try to explain the Magic Lantern RAW video look that can't be replicated with in-camera H.264.  Recently, I've been playing with the SL1. Amazing!  The ML devs got it to do something I thought impossible.  I bought a BMPCC4K (and will have to upgrade my PC to deal with it!).  Did you know you can't write CinemaDNG?   I also don't believe any of the current HDMI to RAW is real raw down to the pixel. For certain types of grainy looks, ML is becoming the only way to achieve it.

I feel there's a tremendous amount of misinformation about LOG gammas, how they supposedly give RAW like dynamic range.  So I've been working on stuff to clarify it.  Anyway, this is another proof of just how great ML!  How else could I create RAW DNGs at 640x360 resolution!  Like all my videos, I wish it was better, that I had more time, but I hope it will help someone out there get beyond the hype of S-LOG, V-LOG, etc.

BTW, took a long time to figure out how to pull out integer values from a DNG file, so, in case there are other slow people here like me:

Code Select Expand

import rawpy
import numpy

raw = rawpy.imread('D:\\M08-2120_000520.DNG')
rawdata = raw.raw_image
numpy.savetxt("D:\\dng520.csv", rawdata, delimiter=",")

VIDEO:
https://youtu.be/ONfdarINvmw

Was curious how easy it would be to "vlog" on a 7D running raw.  My findings
1. Reliable, never had a corrupt file, running at 1728x972 24fps
2. With an external powered mic and camera set to +32db, and some audio post, sound is reasonable
3. Half-press shutter button before recording would get a good focus
4. Using a tape measure to set manual focus if far away worked fine
5. Shooting a high f-stop at 3200 expected ISO gave a much better image (noise organic) than 8bit in my experience.
6. The number one benefit compared to A6300 4K was that the 4K still blew out highlights whereas the RAW always had nice dynamic range roll-off. 
7. MLVProducer for the PC makes working with MLV files a pure joy (and I don't say that lightly about software).
8. Premiere's new audio presets make it much easier to improve any audio

I built a gadget that allows one to see the back screen, but I now see it's overly complicated.  Will create a newer/cheaper one soon.  You can see my gadgets here: http://maxotics.com/

And the video I shot is here

https://youtu.be/28gq9zVgSb4

Just something I did quickly at a shoot, with Magic Lantern and my 7D.  Processed in MLVProducer. Formatted for Instagram.

https://www.youtube.com/watch?v=r7pY4BlCXzk

At article about the super high resolution photos I did at this shoot, more here at http://maxotics.com/2017/03/04/fiona-in-a-half-gig/.

More footage taken with 7D shooting ML RAW at 1172x972 with Sigma 17-25/2.8, which is a really nice lens.  Internal audio.  I bought body used, and lens used (though new) for $700.  Without MLV Producer I wouldn't even bother.; that is, it makes shooting RAW video a livable post-processing chore   It even displayed EOS-M 10bit clips the other night with focus pixels removed and moire reduced.  What an amazing Magic Lantern tool.  Great work Magic Lantern engineers!  Don't have enough money for a Canon C-100, or 5KmkIII?  Get a 7D!  It is super sweet, IMHO.  I haven't had one error yet.

AND...of course...YouTube doesn't do the original footage justice.  It is beautiful and completely film-like.

I upgraded from a 50D to the 7D.  Very stable, much easier to use.  AND audio!  To think a filmmaker could buy a $400 body and get this kind of quality is fantastic.  Too bad so many are misguided in the trade-offs between 8-bit 4K and 14-bit RAW.  Anyway, MLV Producer is amazing.  I can't get over how good it is.  It deals with my EOS-M's focus dots and does all the correction I'd want in the 7D RAW files. 

http://youtu.be/2gYiOiltsyw

I can't believe the Magic Lantern engineers got sound to record with RAW on the EOS-M!  I am so looking forward to getting a 7D to replace my 50D.

https://www.youtube.com/watch?v=eHmCNBFH414

Unlike my previous video, I will not offend your senses with in-camera 8bit video footage  

Also, again, if anyone has an current-build configuration for getting dependable 24fps non-crop video from the 50D please let me know.  I still get crashes.  Thanks!

Still, I come back to it!    I recorded audio on my Android phone using "best audio recorder", then uploaded to my Google Drive.  For video, I exported using MLRawViewer, usually as C-log, or HDR Tone-map.  Even doing this bare-bones post processing I felt I had nicer video clips to drop into my Premiere timeline.  Syncing audio was easy using hand-claps.

I experienced intermittent card-write errors and camera lock-ups.  If there is a current best practices fo 50D raw please post a link.  Seems to be working fine at the moment.  I still feel that even Sony's latest 4K video, as nice as it is, can't match the film-feel of ML RAW. 

https://www.youtube.com/watch?v=SaNZYWMRkx4

Here is the meetup information for February 5th, 2014 in Cambridge, Massachusetts (near Boston).

http://www.meetup.com/Magic-Lantern-RAW-Video-and-Blackmagic-Cinema-Cameras/events/159199382/

For the first meetup I hope to have various people go through the complete process, from installing ML, to  shooting and post.   We will also cover Blackmagic cameras.

I hope this will be a monthly or quarterly meeting.  So please don't try to travel far for this event.  Hopefully there will be others.

Microsoft has agreed to let me organize an event at their research facilities in Cambridge, MA U.S.A. 

Anyone would be encouraged to talk about

Magic Lantern Development
Using ML Video RAW
Post Processing techniques
Davinci Resolve, etc.

It would be very informal.  You don't need to be an expert!  If no one wanted to present, we could just meet and show each other stuff.

Please post if you're in the Boston area and would be interested in attending such a meet-up.  Let me know what days/times would be best for you.

For those not clear what the sensor sees before de-bayering I created this fun little video using my EOS-M, Magic Lantern, Photivo and ImageMagick.

I'm stuck between many a rock and hard place...

I want to work with the RAW files, ("focus dots" and moire issues in pre de-bayered data), and ultimately create a RAW to ProRes for the EOS-M. 

I've been working from g3gg0's C# MLVViewer which has been EXTREMELY helpful (thank you, g3ggo!).   My goal has been a RAW frame manipulation lab.

But part of me says to just create a function in raw2dng that deals with the focus dots and maybe push to the main fork one day if thought worthy.  I want to work in the spirit Alex talks about, so don't want to go down a path that may make it more difficult for others later.  My first choice would be to work with Visual Studio, which I know.

C++ is a struggle for me, C# is easier.  Anyway, should I

1. Figure out how to port any C++ to C# and just work from there
2. Work with C++ in Visual Studio
3. Man up and use MinGW or something similar?

I see many posts on development for ML, but I want to focus on post-processing.   Advice GREATLY appreciated!  If there is already a thread on post-processing development in Windows please point me to it, or any other helpful material. (BTW, have installed MinGW but already have basic configuration problems, so this is why I want to know what I'm dealing with).

[EOS-M RAW Magic Lantern "Alpha" VIDEO OVERVIEW]

EOS-M RAW Magic Lantern "Alpha" VIDEO OVERVIEW

After extensive testing I can recommend the EOS-M as a good experimental camera.  However, it is not dependable. There is no indication Magic Lantern will ever see Beta, let alone a stable release for this camera.  Current problems include a "shutter bug", screen problems if you forget to turn off custom FPS in movie mode and the fact that the camera turns off audio when shooting RAW and doesn't turn it back on if you switch to H.264  (I keep forgetting and ending up with soundless video).

Last edit: 11/17/2013

The Canon EOS-M, in crop-mode, produces a "film"-like look in wide dynamic-range (14-bit color) 1280x720 24fps RAW video. 

Caveats:

• Unlike the 50D, 5D2, 5D3 and other non "hybrid focus" EOS cameras, focus pixels "pink dots" must be interpolated around in post-production.  An extra step.  These dots can also appear in clipped areas of the image and may need special post-processing to remove.
• There is a "shutter bug" where the camera will stop taking photos.  If you're aware of the workarounds, you can get the camera to take photos again.  The bug, like all good viruses, doesn't seem to affect everyone's camera/setup so has been difficult for the devs to cure. 

With an adapter (Canon or Fotodiox), the camera will work with all EF lenses.

Recommended lens, 11-22mm; however, not for sale in U.S. yet.  One can purchase from a store in Canada.  Hopefully Canon will release in the U.S. this holiday season.

Kit lens 18-55, is good, IS is great.

22mm lens also works well, but does NOT have image stabilization (IS).

10-20mm EF lens, using adapter, works very well. 

Here are some effective focal lengths with various lens in crop mode:

Lens   Effective 3x Crop
4.5    18mm
8.0    32mm
10    40mm
15    59mm
20    79mm
24    95mm
28    111mm
40    158mm
50    198mm
60    238mm
85    337mm

ACTIVE THREADS (they start at 1st page, use links above to get to later pages)

ML Development for Camera
http://www.magiclantern.fm/forum/index.php?topic=9741.0

The "shutter bug" is discussed here:
http://www.magiclantern.fm/forum/index.php?topic=8347.0

THANKS AND ACKNOWLEDGEMENTS: 1%, A1ex, Gary, Jerrykil, Malakai, RenatoPhoto, Mountain_drew, t0910 and others.

External sound for atmosphere.  Not synced. 

One of the great benefits of RAW video is low light shooting.  Lots of noise, certainly, but a very natural look.  H.264 would of crushed half the image detail into black.

Workflow:

1. RAW to PinkDotRemover (rewind version)
2. RAW to cineform 422
3. Cineform to Sony Vegas Studio (minor adjustments)

The extra  "grading" workflow of DNGs or TIFFs is not worth it to me.  This workflow adds little time to a normal H.264 workflow, with huge improvements in dynamic range.

I bought Neat for $50.  There is noise in all the EOS-M 1280x720 video I have shot, seems to me.  Neat does a great job of allowing one to pick a balance between high noise and color flatness--however, I'm still new to it.

Here are stills I took at party using the EOS-M and a Nikon D600.

http://www.flickr.com/photos/maxotics/sets/72157636214440423/

Haven't posted some EOS-M Raw in a while.  Here's today's test footage.

Thanks 1%, you're really starting to kick a_ with this camera.  Unfortunately, didn't have time to try Alex's new stuff.  Thanks to Rewind too!

In order to get anything close to normal angle in crop mode I attached a $50, 0.20x adapter onto the 22mm lens. That should mean 4.4mm x 1.6 sensor crop = 7mm times Magic Lantern 3x crop = 21mm. Does it work, sort of.

But first, the 22mm lens uses servo motors for focusing. The adapter probably puts a big strain on the Canon STM M lens, and even "hunts", or gets lost, in manual focus mode. Not pleasant. I believe this adapter may SHORTEN THE LIFE of your lens. If you bumped it hard during focusing there is a good chance the weight of the adapter would strip the motor gears. In short, BE VERY CAREFUL if using this setup. I plan on using this adapter sparingly.

It is also difficult to focus.

By using crop mode you get rid of moire. The adapter gives you back barrel distortion and chromatic aberration--a lot of it.
All that said, if you want a wide angle shot, without moire, you're probably better of with this adapter. If you use a DNG based workflow you can probably clean up a fair amount of the barrel distortion of chromatic issues.

In my experience, moire on these cameras CANNOT be fixed.

These shots are 1280x270, 24fps. Conversion to Cineform 422. Then into Vegas Studio. A little bit of sharpness and contrast added.

I'd probably be more positive if there weren't always focus dots appearing in the footage. PDR works great when there are no blown-out parts of the frame. Otherwise, the dots come back and one feel helpless in not being able to remove them.

I saw a $2.69 LED keychain light at ACE Hardware with a "clicky" button.  It was near the "key" cutting section.  I think any flat LED light with a clicky button will work for this purpose.  I taped it onto my Zoom H2, and clicked it while point at my EOS-M running ML RAW.  Because the LED light is right near the microphone it makes a nice spike in the wave-form, that happens when the light goes on and off.  I synced this up on the first try.  Hopefully this method will be helpful to others. 

I added some other EOS-M RAW footage I taped afterwards. 

After a new build by 1% the Pink Dot Remover stopped working.   Rewind was kind enough to figure out the new dot-matrix locations and fix it.  In this video you can see how the dots come back in over-exposed areas.  I don't believe this is a fault in Rewind's fix, but a deeper problem with EOS-M video, which I discuss a bit here: http://www.magiclantern.fm/forum/index.php?topic=3648.msg73969#msg73969

Rewind pointed out that there is an error in my logic, about dot clusters, in that TIFFs have interpolated Bayer patterns.  Nevertheless, as you can see from this video, it's an open issue about the number and significance of these dots in the 1280x720 area of the sensor used in crop mode.

Today it looked like some users may have come close to fixing the "shutter-bug" problem with the 18-55mm IS lens.  Until that is solved, I don't see getting a 10-20mm IS lens from Canada.  It may have the same problems.

I was very enthusiast about this camera a couple of weeks ago but am now wary.  There seems to be only one dev working on it and he seems to be split between many projects.   I would not buy the EOS-M over any other Canon camera at this point.  The builds are still alpha and are not documented.  I went days where I didn't shoot video because I wasn't sure I'd ever be able to remove the pink dots. 

If it wasn't for the fact (I believe) of the 50D having to crop 5x and the EOS-M only 3x, I'd probably have changed my experimental focus to the 50D. 

I'm also wondering if there can be a better fix to moire problems with the EOS-M (and other cameras) in normal mode.  Maybe the devs could alternate line skipping (HA!  Bring back interlacing).  Maybe someone could produce down-sampling software, specifically for these Canons, that minimizes it.  So many questions.  So few answers.

Like everyone else, I wanted a Blackmagic pocket cinema camera NOW.  Only NOW, I can wait. 

I spent $400 for an EOS-M on CL with a 22mm pancake and Canon Adapter.  I then bought a Sigma 10-20mm used for $300.  So for $700 I have a camera PLUS lens which takes full RAW 720p video.  The only difference between the ML EOS-M will probably be 1080p vs 720p and, I grant, the Blackmagic will be sharper and have better color saturation (and of course, built-in audio). HOWEVER, the BMCC will NOT do photography like the EOS-M or give me all kinds easy Canon lens options, and flash, and other ML goodies, etc.  That is to say, in my fanny-pack I am now carrying a complete photo/video killer-kit.

I LOVE my current setup.  Next, I'm going to try a wide angle adapter on the 22mm.  My guess is that for $250 body, $150, 22mm pancake,  $165 Century Optics .5x adpater [EDIT: Adapter does not work, can't get focus], (total $565) you can get, in crop mode, an effective 40mm cinema camera that will give you everything you want in a film look.  And an amazing APS-C sensor size photo camera!  I hope the following video shows the potential!

Go ML team!  PLEASE keep working on the EOS-M firmware.  This is a super, super hit in the making!  The only thing standing in its way is a widespread obsession with RAW resolution.  Sharpness is nice, but not necessary, to shoot beautiful film-look video today. 

In this video you can see the set-up through the EOS-M, which I also use for sound.  For the first couple of clips I used the RAWanizer Cineform 422 output. 

I processed using my VBscript which extracts DNGs using RAW2DNG and then runs DCRAW.  For the Cineform clips I used RAWanizer.  I then import in Vegas Studio.  I use the White Balance effect, then sharpening.  I do a little color work, but probably make it worse than it is.  The only real weakness I see in ML, at the moment, is that the ML LiveView, which shows crop mode in the proper frame-size, lags the video recording and is more difficult to focus with.  The Canon built in LiveView allow focus, but is zoomed in.  I was pleasantly surprised that the last clip, not in crop mode, showed little moire.

Here's a version where I take the second clip, modify each TIFF to JPG in FastStone image viewer (freeware), then ffmbc render to DNxHD.  I think that process provides better quality then doing the grading in Vegas Studio.  But who knows.

Rough test footage shot with EOS-M in camera video mode (H.264), 50D RAW (10-22 Sigma), EOS-M RAW (20mm pancake, both crop and non crop).  I just figured out how to shoot in 1920x1080p (didn't realize i couldn't set to that resolution unless camera was already in crop mode).  These 50D videos are probably  1584x892

Although I love RAWanizer, it sometimes stops working for me and I can't figure out why.  So I created a script that will do what RAWanizer does, and which I (or you) could customize.  Benefits of this script is that I can control which version of dcraw I use, or could put in any command line exe (maybe ufraw, etc).  It is written in VBscript (Visual Basic) and runs on Windows.  I chose VBscript because I already have some VBscript imagemagick and  ffmpeg processing scripts.  If I had the time, and hope to in the future, I'd write this in Python. 

PLEASE, DO NOT THINK OF USING THIS SCRIPT UNLESS YOU HAVE PROGRAMMING EXPERIENCE OF SOME KIND!  Sorry, this script needs software-development type configuration.  If in trouble, you may need to go into task-manager and kill a process or two.

Scary warning boxes will come up that you'll need to understand.

What this script does
o. After copying the script file into folder with RAW files, will...
1. Extracts DNGs from ML video RAW file
2. Create TIFFs from DNGs
3. Create highest quality MP4 from TIFFs, sharpening added

Eventually I will put this script, and more info up on my site.  I'm starting a thread here, however, because if you're like me, you may need this NOW

If you make improvements, please send them to me at [email protected]

Code Select Expand


' Created by Max Rottersman / [email protected]
' Date: 8/30/2013 v 1.1
' USE AT OWN RISK!  Feel free to copy
' Yes, I could make more elegant, but perfect enemy of good
' or what I can do in free time

' PURPOSE
' 1. Extract DNG files out of Magic Lantern video RAW files
' 2. Process DNG files into video-editor readable TIFFs
' 3. Process TIFFs into VIDEO through ffmpeg

' ****************** CONFIG ME *******************************
' >>> WHAT TO PROCESS
' CHANGE TO PROCESS ONLY 1 RAW FILE, or extract only a few DNGS
NumberOfRAWFilesToProcess = 4 ' make, say 3, for testing, or 1000000 for all
NumberOfDNGsToProcess = 1000000 ' or 10000000 for all

flagRunRAWtoDNGProcess = True
flagRunDNGtoTIFFProcess = True
flagRunTIFFStoFFMPEGProcess = True
' *************************************************************

'
' What folder is this script in, from there I start
Dim Prefix_dcraw, Suffix_dcraw
ThisFolder = left(WScript.ScriptFullName,(Len(WScript.ScriptFullName))-(len(WScript.ScriptName)))
' FILE NAMES AND FOLDER LOCATIONS
FolderRAWs = ThisFolder ' Script should be put with RAW files
FolderDNGs = FolderRAWs & "\DNGs"   ' DNGs put sub-folder here, you can change
FolderTIFFs = FolderDNGs & "\TIFFs"  ' assume TIFFs sub-folder off DNGs

' **** CONFIG dcRAW Params! *********************************
' MUST MUST MUST HAVE!
' Make this any location you want.  MUST HAVE!
MyRootFolderForRAW = "C:\Files2013_VidPhotoSoft\RAWCinema"
' WARNING: If these files aren't here, script will NOT work
raw2dng_exe = MyRootFolderForRAW & "\RAWtoDNG\raw2dng.exe"
dcraw_exe = MyRootFolderForRAW & "\DCRawLatest\dcraw.exe"
ffmpeg_exe = MyRootFolderForRAW & "\ffmpeg_latest\ffmpeg.exe"

' ARGS: raw2dng
Suffix_raw2dng = "" ' nothing needed currently
' ARGS: dcraw
Suffix_dcraw = "-w -6 -T" ' CHANGE HERE TO SUITE YOUR NEEDS
' ARGS: ffmpeg
Suffix_ffmpeg = " -i <FILEPATH>\000%3d.tiff -vcodec libx264 -r 24 -pix_fmt yuv420p -q:v 1 -b:v 20M -vf unsharp=5:5:1.5:5:5:1.5 "


'*************************************************************

ReDim xFilesRAW(0)
' Get names of RAW files in this folder that the VBS file has
' been COPIED TO!
rtn = GetFilesRAW(ThisFolder, NumberOfRAWFilesToProcess)

Set objFso = CreateObject("Scripting.FileSystemObject")

' Cycle through RAWs, Create target folder for DNGs and TIFFS
for i = 0 to ubound(xFilesRAW) -1
' STEP 1
' Come up with folder name for DNGs like RAWanizer
sFileNameRAW = xFilesRAW(i+1)
'msgbox sFileNameRAW
sFolderNameDNGs = replace(sFileNameRAW,".RAW","") & "-dng"
'msgbox sFolderNameDNGs
sFolderNameDNGs_FullPath = ThisFolder & sFolderNameDNGs ' \
'msgbox sFolderNameDNGs_FullPath
sFolderNameDNGS_FullPath_RAWFileName = sFolderNameDNGs_FullPath & "\" & sFileNameRaw
' TIFF folders
' Not calling proxy TIFFs like RAWanizer because assume
' these will be final
sFolderNameTIFFs_FullPath = sFolderNameDNGs_FullPath & "\TIFFs"

' Create DNGs folder!
If Not objFSO.FolderExists(sFolderNameDNGs_FullPath) Then
objFSO.CreateFolder(sFolderNameDNGs_FullPath)
End If

' Create TIFFs folder!
If Not objFSO.FolderExists(sFolderNameTIFFs_FullPath) Then
objFSO.CreateFolder(sFolderNameTIFFs_FullPath)
End If

' ***
' RAW BLOCK RUN?
' ***
if flagRunRAWtoDNGProcess = True then

' STEP 2
'Copy RAW file int DNG folder, we will delete copy later
objFso.CopyFile ThisFolder & "\" & sFileNameRAW, _
sFolderNameDNGs_FullPath & "\" & sFileNameRAW

' STEP 3
' Copy raw2dng to folder
' Copy RAW2DNG.exe to folder
objFso.CopyFile raw2dng_exe, sFolderNameDNGs_FullPath & "\raw2dng.exe"

' Step 4
'Run RAW2DNG (and wait for process to end)
Set objShell = WScript.CreateObject( "WScript.Shell" )
' Change Shell path to current DNG folder
objShell.CurrentDirectory = sFolderNameDNGs_FullPath
objShell.Run "raw2dng.exe " & sFileNameRAW, 1, True 'chr(34) double quotes if needed
Set objShell = Nothing

' Step 5 Clean up, remove RAW and raw2dng.exe
' Check if file exists to prevent error
If objFSO.FileExists(sFolderNameDNGS_FullPath_RAWFileName) Then
objFSO.DeleteFile sFolderNameDNGS_FullPath_RAWFileName
End If

' Step 6 Clean up, remove raw2dng.exe
' Check if file exists to prevent error
If objFSO.FileExists(sFolderNameDNGs_FullPath & "\raw2dng.exe") Then
objFSO.DeleteFile sFolderNameDNGs_FullPath & "\raw2dng.exe"
End If

' ************************************
' DNGS SHOULD HAVE NOW BEEN EXTRACTED
' ************************************

' Step 1 Copy DNGs for TIFFs folder for processing
' Create another shell, killed one above for safety
' use xcopy for speed
Set objShell = WScript.CreateObject( "WScript.Shell" )
sRun = "%comspec% /c xcopy "
sRun = sRun & chr(34) & sFolderNameDNGs_FullPath & "\*.dng" & chr(34)
sRun = sRun & " " ' space before target
sRun = sRun & chr(34) & sFolderNameTIFFs_FullPath & "\" & chr(34)
objShell.Run sRun ,1,True
Set objShell = Nothing

End if ' RAW BLOCK RUN?

' ***
' DNGs to TIFFs
' ***
If flagRunDNGtoTIFFProcess = True then

' Step 2 COPY dcraw
objFso.CopyFile dcraw_exe, sFolderNameTIFFs_FullPath & "\dcraw.exe"

' Step 3 run dcraw
' going to use create BAT file and run method so can use
' bat file for testing/configuring dcraw if necessary
ReDim xFilesDNG(0)
rtn = GetFilesDNG(sFolderNameTIFFs_FullPath, NumberOfDNGsToProcess)
' Write files to bat file
Set objBATFile = objFso.CreateTextFile(sFolderNameTIFFs_FullPath & "\convertDNG.bat")
For j = 1 to ubound(xFilesDNG) -1
objBATFile.WriteLine "dcraw " & Suffix_dcraw & " " & xFilesDNG(j)
Next
objBATFile.close()

' Okay, now run bat file
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.CurrentDirectory = sFolderNameTIFFs_FullPath
sRun = sFolderNameTIFFs_FullPath & "\convertDNG.bat"
'msgbox sRun
objShell.Run sRun, 1, True
Set objShell = Nothing

' Finally, clean up by deleting DNGs in TIFF folder
' and the dcraw.exe file
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.CurrentDirectory = sFolderNameTIFFs_FullPath
sRun = "%comspec% /c del "
sRun = sRun & chr(34) & sFolderNameTIFFs_FullPath & "\*.dng" & chr(34)
objShell.Run sRun ,1,True
Set objShell = Nothing

If objFSO.FileExists(sFolderNameTIFFs_FullPath & "\dcraw.exe") Then
objFSO.DeleteFile sFolderNameTIFFs_FullPath & "\dcraw.exe"
End If

' If you want to delete BAT file, for now I'll leave it
if false then
If objFSO.FileExists(sFolderNameTIFFs_FullPath & "\convertDNG.bat") Then
objFSO.DeleteFile sFolderNameTIFFs_FullPath & "\convertDNG.bat"
End If
end if


' run bat file
end if ' TIFF BLOCK RUN?

' ***
' run ffmpeg
' ***
If flagRunTIFFStoFFMPEGProcess = True then

sRun = ffmpeg_exe & replace(Suffix_ffmpeg, "<FILEPATH>",sFolderNameTIFFs_FullPath)
'sFolderNameTIFFs_FullPath
sOutputFile = replace(sFileNameRAW,".RAW",".mp4")
sOutputFileWithPath = ThisFolder & sOutputFile

sRun = sRun & " " & sOutputFileWithPath
msgbox sRun

' Finally, clean up by deleting DNGs in TIFF folder
' and the dcraw.exe file
Set objShell = WScript.CreateObject( "WScript.Shell" )
'objShell.CurrentDirectory = sFolderNameTIFFs_FullPath
'sRun = "%comspec% /c del "
'sRun = sRun & chr(34) & sFolderNameTIFFs_FullPath & "\*.dng" & chr(34)
objShell.Run sRun ,1,True
Set objShell = Nothing

'WScript.quit
' ThisFolder & "\" &

end if


next

' >>>>>>>>>>
' FUNCTIONS
' >>>>>>>>>>

'**************************************
' GetFilesRAW: Load RAW file names into array
'**************************************
Function GetFilesRAW(argDir, argNumberRAWFilesToProcess)
Dim fso, folder, files, NewsFile,sFolder
Set fso = CreateObject("Scripting.FileSystemObject")
Set folder = fso.GetFolder(argDir) 
Set files = folder.Files   
vCounter = 0
For each folderIdx In files
'msgbox folderIdx.Name
if right(ucase(folderIdx.Name),4) = ".RAW" Then
Redim Preserve xFilesRAW(Ubound(xFilesRAW)+1)
xFilesRAW(Ubound(xFilesRAW)) = folderIdx.Name
vCounter = vCounter + 1

' For resting, only run a few
if vCounter > argNumberRAWFilesToProcess then
exit function
end if

' *** Write file name, testing
'NewFile.WriteLine(folderIdx.Name)
End if
Next
End Function

'**************************************
' GetFilesDNG: Load DNG file names into array
'**************************************
Function GetFilesDNG(argDir, argNumberDNGFilesToProcess)
Dim fso, folder, files, NewsFile,sFolder
Set fso = CreateObject("Scripting.FileSystemObject")
Set folder = fso.GetFolder(argDir) 
Set files = folder.Files   
vCounter = 0
For each folderIdx In files
'msgbox folderIdx.Name
if right(ucase(folderIdx.Name),4) = ".DNG" Then
Redim Preserve xFilesDNG(Ubound(xFilesDNG)+1)
xFilesDNG(Ubound(xFilesDNG)) = folderIdx.Name
vCounter = vCounter + 1

' For resting, only run a few
if vCounter > argNumberDNGFilesToProcess then
exit function
end if

' *** Write file name, testing
'NewFile.WriteLine(folderIdx.Name)
End if
Next
End Function

'*********************************
' WriteBATFile
'*********************************
Function WriteBATFile(argDir, argFileNameAndPath)
Set WshShell = CreateObject("WScript.Shell")
Set objFso = CreateObject("Scripting.FileSystemObject")
Set objFile = objFso.CreateTextFile(argFileNameAndPath)
objFile.Close
End Function

'
' MISC NOTES
' About VBS batch job security issues
':: Tutorial: http://www.sevenforums.com/tutorials/182353-open-file-security-warning-enable-disable.html
' DISABLE SECURITY
'REG ADD "HKCU\Environment" /V SEE_MASK_NOZONECHECKS /T REG_SZ /D 1 /F
' ENABLE SECURITY
'REG Delete "HKCU\Environment" /V SEE_MASK_NOZONECHECKS /F




I'm think I'm getting TIFF to video conversions that are very close to TIFF quality.  Any insight (improvement to below), please  let me know!  These are the commands I'm using currently

Code Select Expand


*** DNxHD ***
ffmbc -r 24 -i 000%
3d.tiff -vcodec dnxhd -b 185M -r 24 -vf scale=1920:1080 outputDNxHD.mov

*** Proress ***
ffmbc -r 24 -i 000%
3d.tiff -vcodec prores -profile hq -r 24 -vf scale=1920:1080 outputProre
s444.mov

*** MP4 ***
ffmpeg -i 000%3d.tiff -vcodec libx264 -r 24 -pix_fmt yuv420p -qscale 2 -vf unsharp=5:5:1.5:5:5:1.5 output.mp4


I've noticed that many people think the decision is whether to use in-camera MP4 or RAW.  They both have their benefits. In this video I explain why RAW video may be appropriate for some shots, and show side-by-side clips where you should see the difference between Magic Lantern RAW and MP4. 

Shooting in 1728x586 seems good until the card starting filling up.  I switched to a lower resolution and then it continued on fine. 

First try had the pink dots, then used pink dot remover.  The 50D felt really solid, with RAW, but I believe the EOS-M ML is still in alpha.  That it works at all is tremendous!  Anyway, here is a RAW video.  Unlike the 50D, the EOS-M takes video without ML.  So I'll be curious to run some comparisons this weekend.

BTW, the camera gets very hot shooting RAW.  I've also had a couple of freezes. So I wouldn't run out and get one of these cameras just yet if you're thinking about using them in anything production related.

I tried to make the G5's AVCHD footage less contrasty, more detail, like the 50D RAW.  Couldn't do it.  Magic Lantern has NOT DROPPED a frame yet on me.  I even had my wife direct me in coloring and she couldn't get me to get the AVCHD to look right to her.  She ended up choosing the 50D RAW and she has zero interest in this stuff. 

Second day, took 50D out for walk.  Didn't understand the ML exposure settings, so exposure changes.  Syncs with sound just fine.  I continue to be wildly impressed at what ML has done!  The 50D can write data almost as fast as a 5D Mark III.  You can get the body for about $400. I see a lot of people on the forum that seem to think they have to have the latest Canon 5D Mark III.  Why? I was hot to buy the BMPCM, but now, I'm not so sure!  With ML this camera simply kicks a__.

Used Andrew Reid's EOSHD 50D Shooter's Guide.  Saved me countless hours!   

Thank you Magic Lantern team!  I can't tell you how excited I am over this!  This IS how my wife looked.  I took some quick video footage so  I could show the video look we've all become accustomed to.