Messages

vyskocil, any update regarding your pull request and FPS override implementation?

can you post links to that amazon seller?

"simply wont work" is not going to get you a lot of useful answers.

Indicate in a detailed step by step order what happens when you process a file more than 4gig.

I have to say that I have recorded tons of footage over the 4 gig limit and never experienced a gap between the 4 gigs. I thought I was seeing skipped frames at a time when watching <4 gig footage in MLRawViewer, but found out that it was only MLRV that jumped to the next file at every 4 gig mark. When merged and exported, there was nothing wrong with the footage.

rick_ford55 was inquiring about using it in "normal" mode so I assumed this meant h264. the 1 sec gap I implied to only applies to h264 footage via auto restart. No gap with raw.

why no one is answering this thread?

Because its a question that has been asked and answered over and over in this forum. You would have known if you bothered to do a search and read. And you should have understood that since this post was transferred to duplicate questions section.

Rainmanwalking,

It was done using features only found in TL which is not yet ported back into ML nightlies.

vyskocil, already submitted a pull request as stated here;
http://www.magiclantern.fm/forum/index.php?topic=9848.msg116516#msg116516

hopefully it will be reviewed and ported into ML soon.

between the 3? The 5D mk3 if money is not a problem.

There is no stable, only nighties and Dual ISO module is included there. To find out what is covered or not, refer to
http://builds.magiclantern.fm/#/features

Ciao
Walter

I am just using the 5d in normal mode with ML installed and I am unsure about the continuos recording mode ML offers.... I understand I can turn movie restart and when the 4gb buffer is reached the camera will restart..... Will the camera just do that itself? Are there any known issues with this, heat issues etc?

Note that while this is automatic, there would still be a approx 1 or less than 1 second gap between the 4gig clips. Heat issues is still the same as with stock firmware.

5D2 it is?

yes.

please upload the .mlv as i dont get such effects.

Ok, since I already deleted the mlv for that wav, I did another batch test.

Here is the link to an approx, 10 second MLV file. https://www.dropbox.com/s/ir84sa4vnkpuu4m/M28-2329.MLV

This is the first clip recorded after doing an in-camera format.
AGC is OFF
Sound source -internal mic.

Are you getting the dummy file created on the card (with Reserve Card Space active)?

the mlv_rec.tmp file.

Thanks for this forum and for all the outstanding work done by the Magic Lantern crew.   I've been considering buying a monitor to help me see well enough to pull a good focus.   I would like to make sure that when recording raw video the hdmi output is functional with the 7D?  I'm sure it's been discussed but I can't sort it out enough to be sure so I apologize in advance.   ST

even without ML the 7D maintains HD resolution via hdmi during record. Note that unlike the 5d3, when you plug an hdmi monitor on the 7d the camera lcd is off, so you only view via hdmi.

@g3gg0

Testing May 23 NB and the static/buzzing noise I reported here: http://www.magiclantern.fm/forum/index.php?topic=7122.msg115953#msg115953

is still present.

I tested both with agc ON and agc off.

Here is a link to one wav file extracted from an MLV recording.

https://www.dropbox.com/s/3w0babsv9eqprop/M28-1205.wav

this one with agc OFF  using internal mic.

In a series of batch tests, it appears 8x out of 17 clips.

Also, I have read a lot about fps override not working, but I'm able to select 24p from canon menu and it displays as such in MLRaw module as well. I used to have to used FPS override on 50D to get 24p, (or 23.976) I  guess I don't need it here since 7D natively supports 24p?

fps override is not yet implemented on the current ML for 7D.

what kind of resolution are you using? On average, say 1728x972 @ 24fps is only around 7min give or take on a 32gig cf. And if I recall, around 12 or 13 min on a 64gig cf.
The file manager works only within the camera and cannot be used across a usb connection. You probably need to buy more CF cards.

This has been my workflow for the last 2 months or so. So far, it's working out well.

do you understand the post I made above yours?

For questions, answers and info regarding raw post processing pls post here:  http://www.magiclantern.fm/forum/index.php?board=54

can you do an in-camera format and see if it will still be 256gig after format? The 256gig KB 1200x we tested will be reduced in capacity after an in-camera format.

Ok, I actually did a sort a systematic test so I'll detail my test report method in the mlv thread where I posted the problem first (linked in my post above). This post will just be a heads up to 5d2 users in general.
Link to updated post with test method. http://www.magiclantern.fm/forum/index.php?topic=7122.msg115953#msg115953

Caution to those using sound recording with raw.
Testing latest build May 19 (I think this is the same with builds before and after May 14) and found some problems with audio. Static buzzing would show at random in the WAV file. The dngs are not affected.
Its worse when AGC is ON.

Reporting this behavior here: http://www.magiclantern.fm/forum/index.php?topic=7122.msg115921#msg115921

If shooting raw with new nightlies, I recommend use separate sound recording until this is fixed.

@g3gg0

ran some batch tests with AGC ON and AGC OFF, 6 clips each, twice.

With AGC ON 8 clips out of 12 had static mostly the loud buzzing, 3 of these had the low variety.

With AGC OFF only 2 clips out of 12 had low static and a blank portion.

Below is a screenshot illustrating the Loud, low volume, and blank kinds of corruption.



Pardon the typo, its meant to read "LOW VOLUME"

The batch tests runs as follows;
-Format CF card
-record 10 sec(clip1)
-record 10 sec(clip2)
turnLV off/on
-record 10 sec(clip3)
-record 10 sec(clip4)
turn cam off/on
-record 10 sec(clip5)
-record 10 sec(clip6)

batch 1 AGC ON
clip1. OK
clip2. 2-loud buzz
clip3. 1-loud buzz
clip4. OK
clip5. 3-low vol buzz
clip6. 2-low vol buzz

batch 2 AGC OFF
clip1. OK
clip2. OK
clip3. OK
clip4. OK
clip5. 1-low vol buzz
clip6. 3-low vol buzz

batch 3 AGC ON
clip1. 2-loud buzz
clip2. 2-loud buzz
clip3. OK
clip4. 1-loud buzz
clip5. OK
clip6. 2-low buzz

batch 4 AGC OFF
clip1. OK
clip2. OK
clip3. OK
clip4. OK
clip5. OK
clip6. OK

Using [f](_) convention and testing using just 2 files still will not link properly using autosync.

resulting files is named as:

WAV file = M16-2036.wav
DNG file(1stframe) = M16-2036_00000.dng

try
[F](_)

Tried this and the wav files are still not linked correctly. Strange thing is that some files are ok, some are not.

it was a long shot advice, I recalled installing ML on a mkIII using v123 and saw the exposure in LV seemed to be in auto when I change fps override. You answered that;

"On 5D3, only the low light FPS override will change the exposure (and the change is a linear scaling). All the other modes will keep the same exposure." -this was your reply last April, so I was thinking the OP was having the same issues, maybe I'm getting drowsy here and did not understand fully his problem...