Messages

Ok,
I took 5 shots one after the other 7 min each 1920x1080 24 fps with audio. temp now is at 55c (annoying orange background)  but camera perform good.

Something i noticed that happened twice out of four, is if i format the cf card on cam (komputerbay 64gb 1000x) when i come back to lv screen becomes black and i have to pull the battery out to get it work again.

i think it happened after cf card got full and record stopped. going to try to reproduce and report.

Also after recording 7 min it does not show the right remaining space on card - 64gb card does not supposed to have 59.4 gb of free space after 7 min recording.

maybe i did something wrong.

using last build.

Anyway regard the temp, looks like its a no issue.

Best
David.

You need to read the thread and decide for yourself... but please try to search the forum/internet and find a melted camera or one destroyed by heat. You won't be able to because it's a non issue.

ML RAW has been around close to a year if it was a problem it'd be well known by now....

I wrote you after i read the thread,

I searched the forum for "temperature" and "5d3" but this thread didnt showed up. thank you for showing this to me.

i think ml should give the user the option to view the temp on lv or not.

Best
David

Here you go you can read though this to see averages and what not... in all the reading and time I've been on here I've yet to see a post where a camera has melted down or been damaged from heat.

You're not the first to do extended recording....


http://www.magiclantern.fm/forum/index.php?topic=9673.0

Post 8 has graphs by camera model. You're well below the average.
Also see post 30 where it discussed the temps are highly unreliable and assumed to display higher than they really are.

Personally I don't think twice about the temp displayed... the camera will regulate it's self. I think it's a case of give someone more information than they'd normally see and they'll turn it into a big deal.

Thank you so much Stedda for that link...
Well after reading i can say  - to bad that this temp info shown the way it shown.
if its highly unreliable why get people worried for nothing?

Going to do some heavy duty test, shoot something like 5 takes of 7 min long shots one after the other and see whats happened.

Best
David.

please let us know how it go
<sup>Thank you Steda,
well when you have an orange background around 50c on the ml menu you get worried...

I am about to go on production of 5 days narrative shooting using 5d3 1.2.3

So how should i address this info?

Best
David</sup>

Well if i wont fill confident i will not go with this version and then there will be nothing let you know

The camera has it's own thermal protection... as in Canon firmware.


I would not worry about 44C... electronics heat up in use. If the camera is on it's going to generate heat.

Also if you do a search you'll find many people with readings around 50+ C and it is thought that the sensor being read is not 100% accurate or correct.

Thank you Steda,
well when you have an orange background around 50c on the ml menu you get worried...

I am about to go on production of 5 days narrative shooting using 5d3 1.2.3

So how should i address this info?

Best
David

   

Temperature is climbing up even when i dont shoot or taking pictures.

5d3 1.2.3
latest build 2014-04-24 22:25:04 +0300
komputerbay 64 gb x1000

camera start at 22-26c , after 10 min when camera is on it shows  44c

Any ideas?

Best
David

Is there any way to use dual iso and end up with a cdng file?

5d3 1.2.3
mac osx mavericks

Best
David

I'm a little bit lost. 
Some month before I got it to work, but now I lost the red line.
I recorded MLV files and use MLRaw 1.1.5 to get DNGs. That's ok. Now I want to improve DNGs a little bit bit and create a movie from it.
I have CS5, so I like to use PS5. The new DNGs are not readable by PS5 anymore. But I updated Camera Raw for PS5 so I could open them again. But what next? Can I create a MOV directly with CS5 or do I have to cnonvert them to TIFF and later on use QT Player for putting TIF to MOV?

And how this is got to do with MlRawViwer?

Save as tiff and then render to prores mov with qt is not a bad solution. but why dont you render straight to mov from mlRawViewer? prores is quit decent format for color grading.

Best
David

When trying to convert from cdng to mov application crash.

macbook air
i5 4gig ram
osx mavericks.

Best
David.

@Danne, @DavidSh

Many thanks for testing out the build and taking time to report the issues.

Testing and reporting is the least i can do for you and this great app

Thought about something from day one i saw this app:
Hiding overlays by pressing a key,
The overlays dissolve is nice and slick, But when previewing a shot on the field or even on the edit table it takes time until they disappear. sometimes they are hiding an area that a user want to see and until they disappear, camera move or shot ended.

Btw,
Do you know on some way using dual iso and export to cdng?

Thanks man
David.

I shoot a Raw video last day with my canon 5d mark iii but some shots are green. Why???

try disable "fix black level" on the mlv menu on camera

crashes:
1.application crashes/not responding when hitting "w" to set export directory
*update - this does not happened if i launch the app and then choosing a file to open, it happened when double clicking an mlv to launch the app and then hitting "w".
*Update - after using "w" to set output folder "e" (file name to render) and "y" (render progres)  overlays not showing up but the export happened.
  Also after hitting "w" it takes something like 3-5 sec for dialog box to show up.
 
2.application crashes/not responding when in full screen mode trying to leave app while it rendered or pause rendered - not happening when not full screen - looks like maybe something with the dialog box event.

macbook air
i5 4 gig ram
mavericks

The batch processing use the c key works great for dng and mov.
rendered 7 mlv files

noticed:
1.when finish the pool, record icon stay pressed, so when using c again it start next batch immediately and not waiting for user to press.
2.also if hitting "c" again it ads the same pool again and again - maybe check if pool already aded and inform user to prevent user mistakes.
3.when leaving the app i get the dialog box even after i hit "x" or "z" and cancel or clear the pool.

so far no crashes when rendering both mov and dng.

specs:
5d3 1.2.3
90mps sd card (yes i know the cf are on the way
macbook air i5
4gig ram
mavericks

Best
David

MlRawViewer 1.1.5
Thanks!

You are the man Baldand,
Going to test it right now.

Just thought if you already use the metadata why dont you show shot name and take number when using ime module, it would be great.
Also maybe add option to export the files naming after shot name and take number from metadata.

this two adds can save a lot of time and frustration during post.

There are not enough words to describe my appreciation for what you are doing.

David

Very impressive video.

I use mlRawViewer on mac to convert mlv to cdng
Then i use cr2hdr to process the dual iso file but the output is DNG not CDNG

Any Ideas?

Best
David

Thank you nigel and MGerard for fast and direct answer.

Best
David

You should get something between 10-12 minutes with these settings.

I had a number of Komputerbay 1000x / 1066x 128 GB cards here to test but none of them was remotely capable of continuous 1080 24p recording.

Thanks MGerard,
So Is there other brand 128 Gb size that can handle 1080 24p?

The 64gb versions are more consistent with speed. But I'm not dismissing the 128 gb entirely. 24 fps is possible. Think about the offloading too.

Thanks nigel,

Can you tell me the number of minutes i have with 1080p 24fps+audio on 64gb?

Hi guys,
After a lot of reading and a lot of opinions, I looking for a straight answer from experience...

For production use...
Can i count on komputerbay for continues 1080p 24fbs+Audio?

I use:
5d3 1.2.3 ML

Best
David

Great News!

No, SG just doesn't read the matrix even if the tags are there. It requires you to input it or the raw white balance values.

So why it does not do that when you open it using direct link from premiere?

I personally love Speedgrade and the way it handles RAW. It serves me the images as Linear as they are. All green, very ugly and extremely unusable, initially. However, I can do ANYTHING to them that I want - a developers dream. And I don't need to work against any Lightroom, Da Vinci Resolve Linearization Curves. It is easier to apply to a linear RAW, the amount of Gamma or whatever one needs than to try and take it off those auto-pilot algorithms. Resolve to me is like Lightroom - Automatic as H*** and I don't like that. SG (I am NOT working for adobe) is IMO the most fantastic software I have ever used.
Weird and ugly interface, almost no documentation but with a POWER and potential that no other app has ;-)

So if anyone wants to learn, get a premature heart attack, get unprecedented development possibilities and have fun all at the same time, try Speedgrade ;-)

:-)
Thank you for that...
why is that ugly green? and what is the best way to get rid off? (when i use direct link from premiere its not there...)

RAW is like negatives... You need a good developing-Lab to get good results.

Very nice analogy.

Applying a logarithmic curve to an image does NOT, as above implies, convert RAW to Log. The image is STILL RAW, it is just being 'lifted' / 'Compressed' into a diff. gamma space.

This is what I mean, all this false word-mangling - to confuse a subject which at this present moment is about THE most confused topic on the web... (Next to how to keep a retina display clean)....

A REAL great advantage of a LOG Curve is when debayering is done In-Camera.... Before 'Converting' RAW to a Codec or 'Baking in' the linearization curve. When working with RAW files, it is pointless to use any ONE standard linearization curve (Log). It is VERY limiting, in fact. It would be like trying to apply ONE color-correction to each and every other clip. Which any colorist would know would be non-sense.

I LOVE working with RAW, as I don't have to work against any LOG Curve previously applied to the image. And I ALWAYS start with the linear representation of the image. Then I'll apply gamma to that. And to imply that applying an Rec709 workspace-LUT to a RAW-image will make it look like 'This and That' and adhere to this or that standard, is simply put; Wrong. After 'Putting' something into another 'Space' does NOT imply NOT having to further apply gamma, gain, offset etc. to that particular image... Gamma IS a logarithmic curve or function if you will...

When shooting RAW - the Canon Camera does NOT apply ANY Linearization Curve to the image. Hence RAW.... When shooting H.264 is DOES apply a curve to the image. And in THIS case of in-cam-debayering, the LOG Curve becomes important... CineStyle was a GREAT example of that. Technicolor KNOW what they are doing. But it would be UTTERLY non-sense to shoot RAW and then i.e. in Lightroom apply the Cinestyle LOG Space to the RAW-image. When shooting RAW, you HAVE to realize that you have the FULL DNA of the date, RIGHT THERE in your hands with all its might at your disposal. Simply loading a LUT with a generic LOG-Curve and apply that to each image, would be limiting yourself in EVERY regard.

Understanding RAW and how to develop it, is paramount for anyone shooting it. RAW is wonderful and just as wonderfully misunderstood and therefor, easy to make money off of.

Anyone, NOT 100% sure of what RAW is and how to handle it, should spend their good money on a good tutorial or book, rather than a LUT ;-)

Dear CF,
Thank you for your very detailed explanation,
As one who do not know about raw as you...
Why is there log space tab in speedgrade let say, containing rec709 and arri alexa and red etc'  if log space is not needed?