Quote from: reddeercity on July 07, 2013, 08:29:49 PM
Thanks
Tried to watch you video but, said its Private
Sorry About that, I Fix it
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
Show posts MenuQuote from: reddeercity on July 07, 2013, 08:29:49 PM
Thanks
Tried to watch you video but, said its Private
Quote from: reddeercity on July 06, 2013, 09:10:46 PM
On the 5D2 the Max-with from the sensor is 1880
Canon upscale the image to 1920 for h264 with software.
It really depends on what your Project calls for.
Being that the image is very scale able meaning , re-framing, punching-in.
I like to use Max amount of the sensor then crop out sides .
the other reason i like it is because of the reduce height for a more Film look & feel !
It also easier to Write to the card @ 68.5 MB/s
That's at lest in my case, I think if with can keep frame data close to the best Hexadecimal
it should write quicker, but i'm Not a programmer so that a guess.
But with 1856x1003 it very close to HD @ 1:85.1 AR
that would be the ticket, there again re-framing etc...
I will settle for 1856x1003 for HD Work & for Documentary
I would use 1880x854 or even 1880x940 if you can do it.
Stop thinking about line skipping and all the stuff, you will always have problems
with that line skipping for panning etc..
But think of you camera as a "Film camera" to capture Positive Film Stock (but More)
It's Not a Video Camera, because with are capturing Frames like "true Film" Stock
I personally turn off everything on the camera & use manual focus,
use proper exposing Technics, "Use Meter on camera" i don't use the "ETTR" function.
but i have a Variable ND and Stop it up or down for scene.
Quote from: reddeercity on July 06, 2013, 07:54:48 AM
Ok,
my camera never when off "continuous ok" it always said "continuous ok"
But i understand what you are saying,
i have always had better numbers then what i have read in this forum.
i will try the 1728x972 AR and see if this problems is still there.
But in the Short term i can record 1856x1003 for 14,000 frame ! that's 9.7 Mins
Update:
I just check the DNG's from the 64 GB full card record @ 1880x854 24p, 22,571 frames
Frame over ride on, small hack on , Photo small jpeg , ETTR = Off,
and i had the last 3 Images are corrupt, pink garbage frames
So i call that success ! with 22,568 Good frames 15.67 minutes on lexar 1000x 64GB card
If only i can get 1856x1003 to do 64 GBs (max is 42GB)
Quote from: noisyboy on May 22, 2013, 11:18:21 PM
By the way when I say shooting h264 is easy I just mean you deal with the clipping coz you have no choice so you just accept it
Quote from: noisyboy on May 22, 2013, 11:02:27 PM
Okay, so I know a lot of people are new to shooting raw footage now that we have been gifted with the power by everyone's favourite Canon DSLR "hack" so I thought it might be a good time to start a discussion about actually shooting with it
There is a great thread going regarding post processing raw but what about the shoot itself. What are the best practices when shooting raw and what tools do people use for getting the best exposure? Shooting h.264 is easy. You expose the subject and light to match (if you are lucky enough to be able to control your lighting) but what about if you want to gain maximum dynamic range from a dynamic scene?
I personally am a photographer who (of course) always shoots raw but even after years of experience doing this I still find myself exposing my raw video incorrectly.
Also, it would be really nice to start seeing some real world examples of exposed scenes instead of pushing the raw data to the extremes just for the sake of showing that it CAN do it.
Please feel free to share your techniques and experience with the rest of us
*ps. If this is already being discussed in another thread, feel free to move me along
Quote from: lagunak47 on July 03, 2013, 04:25:03 AM
where did the audio recording go off to?
also i really wish you guys could bring back the resolution selection of when this first came out. I was shooting anamorphic and a resolution between 4:3 and 1:1 would be great 4:3 gives me 2.66:1 and 11 gives me 16:9 on the old version you didnt have to select an aspect ratio, you could just select width and height. Great work though, cant wait to see how far this will go! Been using magic lantern ever since i bought my first canon (t2i) back in 2010.
Quote from: ted ramasola on June 29, 2013, 10:11:20 PM
At first few frames the EXPECTED frames would say CONTINUOUS OK but after several thousand frames it would change to a much lower number. You have to see if,
1. It would stop when card capacity is reached.
or
2. It would change and stop before reaching card capacity.
I was misled during a couple of my tests when I immediately saw, CONTINUOUS OK then i stopped recording, when on my subsequent tests it would significantly lower.
I have ran 1872 x 1012 several times and it never would fill up my card.
This is with GD=ON, preview=Auto, since in production scenario you need them to be ON.
GD=off, preview=hacked makes no difference in 27 and 29 build.
Quote from: Doyle4 on July 02, 2013, 11:49:29 AM
You want the latest build, your build doesn't have Small Hacks on the build, this helps alot, and also the new Card Warm up seems to be nice, i found writing 128mb to the card on boot up to be best so far.
Quote from: ted ramasola on June 29, 2013, 10:11:20 PM
At first few frames the EXPECTED frames would say CONTINUOUS OK but after several thousand frames it would change to a much lower number. You have to see if,
1. It would stop when card capacity is reached.
or
2. It would change and stop before reaching card capacity.
I was misled during a couple of my tests when I immediately saw, CONTINUOUS OK then i stopped recording, when on my subsequent tests it would significantly lower.
I have ran 1872 x 1012 several times and it never would fill up my card.
This is with GD=ON, preview=Auto, since in production scenario you need them to be ON.
GD=off, preview=hacked makes no difference in 27 and 29 build.
Quote from: ted ramasola on June 29, 2013, 06:04:25 PM
Can you confirm that with your card? With a 3sgig 1000x At that resolution with that build its not continuous. I only averaged between 2400 - 4600 frames, Same with jun 29 build.
For now its 1872 x 936, 1872 x 850, 1856 x 928, 1728 x 972, 1472 x 1104 and lower that can give you continuous recording.
Quote from: ted ramasola on June 29, 2013, 04:20:03 AM
Better yet, they should just include it within the code and ON at default and should not even be an option to be ON or OFF.
Quote from: ted ramasola on June 27, 2013, 06:56:10 PM
Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.
For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.
Quote from: Doyle4 on June 27, 2013, 03:17:04 PM
Thats for 5D mkii direct from A1ex himself
Quote from: Doyle4 on June 27, 2013, 11:59:54 AM
im currently using 5d2-fac94f686d23-pink-debug which A1ex posted earlier, so far so good best one so far, not all features there but i added the ETTR module my self and seems a'ok, nice n stable.
Quote from: ted ramasola on June 27, 2013, 09:30:34 AM
Comparing Vanilla (5d2-fac94f686d23-pink-debug ) and a.d. pink fix jun 25 (d07dab0ba6c2)
Ran tests 2 times consecutive for each resolution except in 1856 x 928, ran it 4 times
Resolution -- A1ex -- a.d. jun 25 pink fix
Vanilla jun 25
1X
1872 x 1054 -- 390/528 -- 395/501
1872 x 1012 -- 840/709 -- 882/822
1872 x 936 -- 3667/2009 -- 2389/3359
1872 x 850 -- continuous -- continuous
1856 x 1044 -- 510/436 -- 612/573
1856 x 928 -- 3989/5177 -- 8675/2445
/3321/6452 /9101/9927
1728 x 972 -- continuous -- continuous
1472 x 1104 -- continuous -- continuous
3X Crop mode
2144 x 1076 -- 188/235 -- 234/237
2144 x 1072 -- 221/218 -- 211/241
2144 x 974 -- 487/376 -- 353/373
1920 x 1076 -- 416/386 -- 402/411
1856 x 1044 -- 736/748 -- 677/794
1728 x 972 -- continuous -- continuous
Results are close except for that in 1856 x 928
Quote from: reddeercity on June 25, 2013, 10:36:15 PM
Thanks guy for use my workflow to upscale.
Tiff can carry any embedded profiles that you can embed , or use Camera raw.
The Biggest think you must do is maintain the dpi, (240) Very important ! this is
where the image makes it or brakes it, I have been Working with PS & AE If you try to upscale in AE
it will look Bad, because AE dose not see the image as Photo image but as Frame image @ 72 dpi.
Plus i have play around with "Film Color Space" in Photoshop & After Effects.
i have been embedding the PanaLog "Panavision Genesis Tungsten Log"
in the Tiff image , i think that would be great for 2K or 4K "B" roll
Panavision Genesis Tungsten Log (Embedded LUT)or ICC for Photoshop
YouTube is the only ones that stream True 2K & 4K in the original Quality setting tab.
Quote from: NewHourFilm on June 25, 2013, 08:46:08 PM
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem
Quote from: NewHourFilm on June 25, 2013, 08:46:08 PM
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem
Quote from: a1ex on June 25, 2013, 12:33:59 PM
I can't reproduce the pink frame issue at all.
Straight from my card: http://a1ex.magiclantern.fm/bleeding-edge/5D2/5d2-fac94f686d23-pink-debug.zip
Write down the black levels (they appear in the top area on the screen, when starting and when stopping recording) and post them, along with the result (whether the recorded frames were pink or not).
Quote from: NewHourFilm on June 25, 2013, 04:17:52 PM
Just a simple upscaling test with the Photoshop Image Processor. DNG (1880x854) to TIFF (3072x1307). No Post-Sharpening etc.
It is not exactly RED-3K, but you can work with it.
Thanks to Reddeercity for providing the infos on the workflow
1880x854 32GB Transcend 1000x
06/13/2013 Build
Page created in 0.089 seconds with 14 queries.