Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ChadMuffin

Pages: [1] 2 3 ... 6
1
Links no longer work...

2
Share Your Videos / Re: My experience with 5D3 MLV and VisionLOG
« on: May 02, 2015, 12:15:00 AM »
Interesting concept. Thanks for sharing!

3
Raw Video Postprocessing / Re: "Screen Tear" issue
« on: April 30, 2015, 12:55:21 AM »
Good info. Thanks!

4
Raw Video Postprocessing / Re: "Screen Tear" issue
« on: April 29, 2015, 10:41:54 PM »
Thanks for the input. I don't know if it is related but, since then I have downgraded from 5D3 1.2.3 to 1.1.3 and the issue seems to have gone away.

5
Share Your Videos / Re: My experience with 5D3 MLV and VisionLOG
« on: April 29, 2015, 10:38:54 PM »
Thanks for the input!

@NitromanX - I did not notice any flickering in the footage. I did not adjust any setting that I have found online to be adaptive, or change frame to frame. This includes Blacks, Whites, Highlights, Shadows, Contrast and Clarity. The Exposure, WB, HLS, Curves, NR, Lens Corrections are not adaptive and are okay to adjust. The grain setting does not move image to image so do not apply this.

I shot in Cinestyle as a picture style but, this is not required for RAW. A picture style is not embedded into the image when shooting RAW. I shot in Cinestyle to more properly judge my exposure at a quick glance while recording. But, this is something I like to do, no need for it.

As for sharpening, and this might be the wrong way to do it, I applied in ACR when I exported the cDNGs to DNxHD. I also applied noise reduction in this step to reduce the process time while editing and the final output.

@DeafEyeJedi - I am sure there are many benefits for using Cinelog-C compared to VisionLOG. But, my business is still growing and I do not have the budget to change my workflow in that way. Interested, but not at this time.

MLVFS would be great but, still being developed for Windows. No beef with Mac, just the cost.

@theartofweb - That is correct, I did not edit the RAW footage itself. Integrating Resolve would make working with the cDNG files easier but, I do not want to go back and forth between different applications as I tend to use After Effects and Photoshop in my edits and using the Dynamic Link makes it so much easier for me. I want real time updates with the main timeline in Premiere when I make any changes in Audition, Photoshop and After Effects. I guess it is a method to my madness and I constantly go back and change things throughout the edit

Because Premiere does not handle ML RAW the best (yet), I wanted to get the footage close, correct WB, then export it with a flat profile in a high bit-rate and bit depth file. DNxHD 175 10-bit worked great for me as I am on Windows and do not have ProRes readily available. To be honest, I am hoping for 'real' adjustments to RAW in Premiere/Speedgrade just as if I were to use Resolve but, who knows if those days will ever come. Maybe there is but, I guess I don't know enough about it.

6
Shoot preparation / Re: High Quality ML Cropmarks v1.2
« on: April 03, 2015, 10:33:06 PM »
Glad to help! Even if I am not a programmer.

7
Shoot preparation / Re: High Quality ML Cropmarks v1.2
« on: April 02, 2015, 10:17:13 PM »
Thank you for the kind words. I may be misunderstanding your questions. The cropmark for the 5x was intended to be used as a preview only to the 5x crop in its default location while at 1x crop (or no crop at all). This is becuase the 5x crop greyscale preview is slower, lower resolution and not the best. I did not base the cropmarks for the 5x zoom off of the grey scale preview. I based them off of the actual DNGs coming out of the camera due to those being the "real" crop comepared to the greyscale preview. If you use the cropmark while at 5x zoom, you will still have the cropmark over your already 5x cropped greyscale image. There are no options to change this option in ML at this time and that was not the intention. The intention was to use it as a guide, only.

8
Duplicate Questions / Re: bluescreen on my 60d
« on: April 01, 2015, 08:04:21 PM »
What he said. +1

9
Duplicate Questions / Re: bluescreen on my 60d
« on: April 01, 2015, 05:39:50 PM »
Is this a prank? Apr 1st?? This only happened to me today. I recently downgraded on my 5D3 from 1.2.3 to 1.1.3, following to procedure of uninstalling ML, disabling bootflag, installing 1.1.3, then downloading the latest ML Building for 5D3 1.1.3. The procedure on screen seems weird and unprofessional from the norm. Take a pictures of today date, Apr 1st of course, press the magic button? The trash can button? Also, when it "crashes" it still runs in the background and when you open the battery door it turns off. Normal crashes don't turn off just by opening the battery door, you have to physically pull the battery out. If it is a prank, cool, but could have been something less frustrating, especially if someone was shooting a production today. Sorry to ruin the fun if so. heh

10
Refer to this guide on the forurm:

How to Record: -- 60/50 fps RAW Video for 5D3 & others --
http://www.magiclantern.fm/forum/index.php?topic=5472.0

You can scale just the height in Premiere Pro.

Select the resolution you want in camera to fit in letterbox or just place letterboxes in your editor.

There are many video tutorials online.

11
You can go to dxomark.com where they have a ton of stats on many lenses that show when a certain lens is at its sharpest. Unsharpen mask can help it look sharper. Sounds condisending but, experiment with it.

12
Chmee has the math right. 5D3 CF slot maxes at a speed of about 100MB/s. Doesn't matter how fast of a card you have, the bottleneck is the hardware in the camera. Even if you had a CFast card, you won't get a stable speed to continuously record 1080p 30fps. With that info, the important question is your end result or platform. If it is web, the compression will be about 2MB/s. You can easily get away with 960p and probably lower resolutions and upscaling in your editor with very reasonable results. Even a side by side comparison of the videos after they have been uploaded to YouTube or Vimeo and redownloaded, you'll see how close they are. If your production is that big that you'll be on bluray or a theater, you are probably using the wrong camera for the job. And, if your audience is pixel peeping that bad, you should disregard them anyways because they are not focusing on your story. Most filmmakers are interested in getting the best quality possible while most of the audience doesn't care or doesn't understand enough and wouldn't even notice the difference between 1080p and 720p. You may, Joe Schmo off a random street corner won't.

13
Raw Video Postprocessing / "Screen Tear" issue
« on: February 01, 2015, 08:21:09 PM »
I was working on a small commercial for a marketing company local to me and I had this issue come up with one of the frames. This happens to be the take I intend to use in the final product and I was able to take some parts of the frame before and after to fix this very simple shot but, it does worry me if I were to be shooting something more complicated and wouldn't be able to do fix it and how much time I may spend trying to fix these kinds of issues in the future if it does continue.

Here is the frame in question.


I was shooting on a 5D3 1.2.3 build Aug 7, 2014. I edit on a Windows 8.1 in Adobe products. For this MLV I used raw2cdng 1.6.1, MLRawViewer 1.3.3 and MLV to DNG Batch Converter v1.9.2 all with the same issue. This leads me to believe that it is not with any of the software on the computer but ML on the camera. I did not see in the forums if anyone else had this issue and do not know if it was just a one in a million issue. I do not know what would be relevant but here are some information. I was using KB 64GB 1000x cards, the card was warmed up and I shot a few minutes before hand, fix black level was on, Use SRM job memory was on, Extra Hacks was on, Reserve card space was on. There was no warning in camera during or after recording this take. It was not split up into multiple files.

If you look closely at the image, it appears that the tear, or what ever the proper name is, is shifted over to the right and over exposed with a pink tint and green in the whites. Has anyone experienced this? Is it a know issue? Is there a fix? If anyone needs any additional information from me to diagnose it, I am sure I can get it to you.

14
Raw Video Postprocessing / Re: The CinemaDNG Discussion (raw2cdng)
« on: January 29, 2015, 06:42:08 PM »
I did a test for you. 5D3 with 1.2.3.

Appeared to work fine in raw2cdng 1.6.9 Alpha but when I pulled it into AE, error on the 50th frame, as well as in Premiere Pro. I had vertical banding and chroma smoothing on limited to 12bit.

Error in AE when importing


The 50th Frame


Importing into Premiere Pro did not give me an error through the Media Browser but, this is the 50th Frame


Here is the debug from raw2cdng 1.6.9 Alpha
Code: [Select]
------------- 1.6.9 started at 15.01.29 11:31:40 --
[init][settings] -- ffmpeg Exists: false
[drop] started
[drop] Files dropped:
[drop] ------
[drop] -- file F:\DCIM\100EOS5D\M26-2005.MLV.
[drop] ------
[drop] -- file F:\DCIM\100EOS5D\M26-2005.MLV will be analyzed now.
[drop] is MLV
[setFileinfoData] set/changed Filedata
[drop] FileinfoData set
[createMLVBlocklist] started
[createMLVBlocklist] splitFiles counted (1)
[createMLVBlocklist] filesize counted (426MB)
[createMLVBlocklist] indexing Blocks in F:\DCIM\100EOS5D\M26-2005.MLV
[getMLVAttrib] started
[getMLVAttrib] reading RAWI-Block
[getMLVAttrib] reading MLVI-Block
[getMLVAttrib] reading IDNT-Block
[getMLVAttrib] reading WBAL-Block
[getMLVAttrib] reading EXPO-Block
[getMLVAttrib] reading LENS-Block
[getMLVAttrib] reading WAVI-Block
 ***** [getMLVAttributes] audioData Object:
hasAudio=True
audioFile=
audioSamplingRate=48000
audioBitsPerSample=16
audioFormat=1
audioChannels=2
audioBytesPerSecond=192000
audioBlockAlign=4
 *****
 ***** [getMLVAttributes] metaData Object:
xResolution=1920
yResolution=1080
frames=123
bitsperSample=14
bitsperSampleChanged=0
isLog=False
colorMatrixA=System.Byte[]
colorMatrixB=
forwardMatrixA=
forwardMatrixB=
lostFrames=0
fpsNom=24000
fpsDen=1001
duration=00:05:08
dropFrame=True
fpsString=23.98
stripByteCount=3628800
stripByteCountReal=3628800
modell=Canon EOS 5D Mark III
camId=MAGIC131b4df
apiVersion=0
splitCount=1
photoRAW=False
photoRAWe=False
RGGBValues=System.Int32[]
RGBfraction=System.Int32[]
wb_R=0.69235970250169
wb_G=1
wb_B=0.410092110532639
whiteBalance=3200
whiteBalanceMode=3
whiteBalanceGM=4800
whiteBalanceBA=4800
blackLevelOld=2048
blackLevelNew=2048
whiteLevelOld=15000
whiteLevelNew=15000
maximize=True
maximizer=5.05991352686844
previewPic=
previewFrame=0
errorString=
isMLV=True
DNGHeader=
version=1.6.9
versionString=System.Byte[]
propertiesString=
verticalBandingCoeffs=
verticalBandingNeeded=False
deadSensel=System.Collections.Generic.List`1[raw2cdng_v2.point]
 *****
 ***** [getMLVAttributes] fileData Object:
fileName=F:\DCIM\100EOS5D\M26-2005.MLV
fileNameOnly=M26-2005
fileNameShort=M262005H
fileNameNum=262005
tempPath=C:\Users\Chad\AppData\Local\Temp\
sourcePath=F:\DCIM\100EOS5D
parentSourcePath=100EOS5D
basePath=
destinationPath=
extraPathInfo=
_changedPath=
outputFilename=
creationTime=1/26/2015 8:04:56 PM
modificationTime=1/26/2015 8:05:04 PM
fileSize=426
VIDFBlock=
RAWBlock=
 *****
 ***** [getMLVAttributes] lensData Object:
lens=24-70mmP4I:
focalLength=24
aperture=0
isoValue=6400
shutter=1/128s
 *****
[drop] MLV Attributes and Blocklist created and sorted. Blocks: 447
[drop] hasAudio. AUDF-List created. Blocks: 27
[drop] VIDF-List created. Blocks: 121
[readVIDFBlockData] started
[readVIDFBlockData] done: [0][1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24]
[readVIDFBlockData] done: [25][26][27][28][29][30][31][32][33][34][35][36][37][38][39][40][41][42][43][44][45][46][47][48][49]
[readVIDFBlockData] done: [50][51][52][53][54][55][56][57][58][59][60][61][62][63][64][65][66][67][68][69][70][71][72][73][74]
[readVIDFBlockData] done: [75][76][77][78][79][80][81][82][83][84][85][86][87][88][89][90][91][92][93][94][95][96][97][98][99]
[drop] VIDF-Blockdata read and created.
[drop] adding M26-2005 to batchList
[showPicture] started
[drop] calculating verticalBandingCoeefs and searching hot/dead-pixels..
[drop] NO dead sensels found
[drop] verticalBanding enabled. decision: do it
[drop] verticalBanding CoEffs: 1 0.998021254016585 0.999951270393377 1.01021137184845 0.996759966744552 0.997290595487447 0.994221241876036 0.982397019246451 1
[drop] ** Item M26-2005 imported | MLV
[drop] * res 1920x1080px | 23.98fps | 121 frames | BL2048 | WL15000
[drop] * modell Canon EOS 5D Mark III | vidfblocks 121 | has audio
[batchList_Click] showPicture
[showPicture] started
[batchList_Click] read Data from M26-2005 frame 0
[batchList_Click] * M26-2005
[previewTimer_Tick] show previewframe 15 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 29 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 26 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 29 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 33 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 25 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 18 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 16 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 18 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 19 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 23 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 25 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 28 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 34 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 41 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 45 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 50 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 53 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 56 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 60 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 66 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 70 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 74 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 76 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 77 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 78 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 79 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 80 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 82 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 84 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 86 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 87 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 90 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 92 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 94 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 96 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 98 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 100 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 101 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 102 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 103 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 104 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 106 from M26-2005
[showPicture] started
[previewTimer_Tick] show previewframe 107 from M26-2005
[showPicture] started
[convert_Click] all in all there are 121 frames to convert
[doWork] started
[doWork] 12 Cores used
[doWork] -> converting item M26-2005
[doWork] settings format 4 with BL0 WL4095 with+ maximizingvalue 5
[doWork] prefix - filename generator [F]
[doWork] destinationPath -> M26-2005
[doWork] outputFilename  -> M26-2005
[doWork] Directory C:\Users\Chad\Desktop\M26-2005 created
[doWork] took DNGtemplate and changed values
[doWork] * init frameCount for multithreaded Convert
[doWork] frameconvert Done
[saveAudio] started
 ***** [saveAudio] audioData Object:
hasAudio=True
audioFile=
audioSamplingRate=48000
audioBitsPerSample=16
audioFormat=1
audioChannels=2
audioBytesPerSecond=192000
audioBlockAlign=4
 *****
[saveAudio] bextName: Canon EOS 5D Mark III
[saveAudio] UDI: DECanMAGIC131B4DF200504714205397
[saveAudio] datetime: 2015:01:2620:05:04
[saveAudio] timeRefMultiplier: 1
[saveAudio] time2frame: 72304
[saveAudio] timeRef (samplingRate*time2frame): 3470592000
[saveAudio] fpsString: 24000/1001
[saveAudio] DF: DF
[saveAudio] subChunkSize :1010084
[saveAudio] success
[doWork] audioconvert Done -> M26-2005.wav

15
Shoot preparation / Re: High Quality ML Cropmarks v1.2
« on: January 21, 2015, 09:05:59 PM »
I do like the way you have the cropmarks with having horizontal lines. Both of those work great!

16
Shoot preparation / Re: High Quality ML Cropmarks v1.2
« on: January 18, 2015, 10:01:13 PM »
Cool. I am interested. Be careful using EF-S on EF. I have read some EF-S lenses rear element goes into the body some and could hit your mirror when taking photos.

17
Shoot preparation / Re: High Quality ML Cropmarks v1.2
« on: January 18, 2015, 08:50:40 PM »
I have updated it to include an EF-S cropmark from a full frame camera. I do not have any EF-S lenses so I was not able to properly test this. I based my tests off of what I could find online of EF-S lenses on the EF mount. It seems that the EF-S lenses can illuminate more than just the APS-C sensor size depending on the lens and the focal range. Due to this, there does not seem to be a perfect cropmark. So, I based the size difference of full frame and APS-C which is approx 66.6%. 720p is 66.6% of 1080p. This is essentially a 720p cropmark, which is easily adjustable in ML and is a great safe zone for EF-S on EF.

DOWNLOAD ML CROPMARKS v1.2
https://drive.google.com/file/d/0Bwd3r5HwGFltU3V6SEVFVWVxdnc/view?usp=sharing

18
General Help Q&A / Re: What is ML's font?
« on: January 17, 2015, 07:44:32 PM »
Thanks for the info. I ran a screenshot of the font in WhatTheFont.com and it came back with a pretty good font called Berthold Imago that I found for free. Not perfect but, close enough... and free. Thanks!

19
General Help Q&A / What is ML's font?
« on: January 16, 2015, 07:34:42 PM »
I was working on updating some crop marks here: http://www.magiclantern.fm/forum/index.php?topic=13638.msg131749#msg131749 and I wanted to create crops marks that match EF-S lenses mounted on EF and the digital zoom crop marks and wanted to label them on the .bmp image. I want to keep the text uniform in the crop mark with the rest of the displays and I do not know what font ML is using. I located the font folder in the ML files but they are .rbf and have tried and failed to open them. I was not able to locate through search here or on Google. Does anyone know what font they are or based off of?

20
Share Your Videos / Re: THE LAST BLACKSMITH - short documentation
« on: January 05, 2015, 05:43:16 PM »
More props to you for shooting in h.264 and getting it looking that good!

21
Share Your Videos / Re: THE LAST BLACKSMITH - short documentation
« on: December 31, 2014, 10:44:41 PM »
Visually awesome! Great grade all around. Nice dark look. You really took advantage of what MLV has to offer. Looks like you had some pretty good equipment with some crane shots and nice shots with sliders. Really made me feel secluded and dirty much like the person you were documenting. What was your workflow?

Music was a good choice, felt more like an feature film then a documentary. Can I ask where you got your music? Nice sound effects when he was using his tools. Added in post?

Even though I don't speak the language I think there could have been a bit more tweaking on the voice. The voice sounded a bit far-away and empty. Try playing around with an equalizer at around 160 Hz to add bass and power to the voice. I think it would fit the feel of the project. Check out this video from IQ Filmmaker for more info, he also has other great videos with more great info.

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

22
Raw Video Postprocessing / Re: The CinemaDNG Discussion (raw2cdng)
« on: December 29, 2014, 12:02:01 AM »
I did a test with all of my lenses to see if it was specific lenses or all of them. I only have a small handful of lenses to test to include Canon 15mm Fisheye f/2.8, Tamron 24-70mm f/2.8 VC, Canon 50mm f/1.4, Tamron 70-200mm f/2.8 VC. I also have the Tamron SP AF Tele-Converter. The only 2 lenses that had "f/0" were the Canon 15mm and the Tamron 24-70mm. Also, these lenses had typos in their names. "EF15mm f/2.8 Fishee" and "24-70mmP4I" The other lenses were named properly. I also tried the tele-converter on my lenses just to see and the same result happened on the same lenses. The tele-converter did not change the results. I was able to recreate this test 3 times with the same results. Your software seems to be consistent, it appears to be with specific lenses. I have included an MLV of about 3 seconds from each of my lenses and one with the tele-converter for you to check out.


https://drive.google.com/file/d/0Bwd3r5HwGFltQ1dzMUluckU3TXM/view?usp=sharing

23
Raw Video Postprocessing / Re: The CinemaDNG Discussion (raw2cdng)
« on: December 28, 2014, 06:38:40 PM »
I ran some tests and here are my results:

5D3 with raw2cdng 1.6.5 in Adobe products on Windows 8.1.

I used vertical banding and chroma smoothing 2x2 in raw2cdng (after I deleted settings.json from previous builds). raw2cdng worked great! White balance was from the camera correctly, it correctly knew my 23.976 fps, 5 fps and 48 fps. There were no black frames or green tint. It did not know my aperture from my lens though. Came back as f/0, which could be because I use Tamron lenses? Not hindering the workflow though so not really an issue. I was able to successfully view them in Windows Explorer and the native photo viewer.

After Effects read the files just fine. I had to manually set the fps from 30 fps which seems to be typical. The .wav file started at the correct point and it went a few frames after but, that is easy to just cut that part out with exporting the clip. I used a clapper board over a span of 20 sec and did not see it the waveform off beat or visual see/hear it off beat.

I pulled it into Premiere Pro and brought in the .cdngs in through the media browser. The audio was on time, did not go past the video. However, it did not know my custom fps. It is an easy fix by adjusting the speed in Premiere.

I did not use Resolve.

Everything seems to be working great on my end! If you need more info or tests, just let me know.

24
Raw Video Postprocessing / Re: The CinemaDNG Discussion (raw2cdng)
« on: December 27, 2014, 01:07:56 AM »
You may need to delete some old settings file. On windows: User\[you]\appdata\roaming named raw2cdng.settings.json. It helped me when using 1.6.3 with black frames, might help with you. Also, removed your old raw2cdngs and download the lastest stable one for you. You may need to run it as an administrator in Windows. If you are using a different OS, don't know...

25
Raw Video Postprocessing / Re: The CinemaDNG Discussion (raw2cdng)
« on: December 26, 2014, 04:18:02 PM »
Thanks for all your hard work! I'll run tests after the holiday season.

Pages: [1] 2 3 ... 6