NIGHTLY BUILDS FOR 5D3 are now available at
Nightly Builds - try the very latest stuff here
http://www.magiclantern.fm/forum/index.php?topic=3072.0
If you use Nightly Builds please delete all old files and replace with the new including ML directory.
Nightly builds for all supported cameras are also being maintained here : http://www.magiclantern.fm/forum/index.php?topic=3072.0
Some cameras are being developed separately from the main Unified build. Some of those builds will have certain features available which may not be available through the nightly build. You can explore the individual RAW development threads for additional builds; of course AT YOUR OWN RISK.
----------------------------------------
All general discussion regarding Raw recording.
The builds can be found in this thread (http://www.magiclantern.fm/forum/index.php?topic=6362.0)
Please read through the many sticky posts here if you need information and help about installing these builds.
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
Current raw video capabilities - All ML cameras (http://www.magiclantern.fm/forum/index.php?topic=6215.0)
PostProcessing -- Beginners Guide (http://www.magiclantern.fm/forum/index.php?topic=5654.0)
(Auto) ETTR (Exposure to the Right): -- History & Beginners Guide (http://www.magiclantern.fm/forum/index.php?topic=5693.0)
Latest build:
...and yes I searched before asking.
Any chance someone could explain me why does the raw rec window shows I record at 94mb/s at 1920x1080, 1920x1152, 1920x1280 even though theoretically the recording speed is different (for example when I choose resolution i want to shoot on, it still shows that 1920x1080 will be recorded at 83mb/s and the rest res in different speeds). Thank you!
I'm not sure of the exact details. But I have seen other users posting about this, so you're not alone in experiencing it.
I'm pretty sure there was some discussion at the end of this thread (http://www.magiclantern.fm/forum/index.php?topic=5413.500).
You get the card speed and the idle percentage (so you know how fast it can go). Do the math.
e.g. if your resolution needs 75MB/s, ML will write at 94MB/s with a 80% duty cycle, so it will not write to card 20% of time (idle=20%).
This trick lets ML estimate how many frames you will get on subsequent recordings, even at different resolutions.
Thank you both Audionut and a1ex! Now it makes total sense to me.
New build June 10th(ed914b3) works fine.
1920 x1080 25fps works fine with global draw on (unlimited) except when raw zebras ON (130 frames only); For zebra, luma fast ON works great. As default ML set up is Raw zebra ON, check with Raw zebra OFF, it would go really faster.
Lexar 64GB 1000x card
a1ex just pushed this (https://bitbucket.org/hudson/magic-lantern/commits/c5d0218e7669f3f49b4505e326a9d236f450c886).
QuoteSlowed down zebras while recording (should improve write speed)
Compile yourself or wait for new builds to test.
Quote from: Audionut on June 11, 2013, 11:06:12 AM
or wait for new builds to test.
The wait is over! I just posted a new build for you to test. You can check the Nightly builds with Raw recording support thread.
Alex, you had mention that when recording RAW vid in photo mode with the new build that exposure is messed up correct? Reason I record in photo mode is I get about 5 mbs faster write speed compared to movie mode. In the build you said to make sure you put on exposure override when using photo hack. Does this help correct the exposure in photo mode? Thanks.
I don't want to support this hack, and I'll disable it completely in future builds, for usability reasons.
If you can show me two videos of the camera display while recording, with CPU usage enabled (Debug: Show CPU usage: Busy tasks, REL), I may figure out what's the difference between the two modes and squeeze some more speed. On my 5D3 I don't see any difference, but it may be some Canon setting.
I will. Thanks Alex. Does changing the exposure overide to on fix the exposure issues wheb recording in photo mode though?
11th June Build. Seems to be squeezing a bit more juice out of the write. Results shortly.
Maybe the card is just warming up, I didn't do any optimizations in the last few days :)
My Card also seems to be writing much better on the latest 5Dmkii 10th June build, crazy how dropping frames shown as made such an improvement! (not recording frames but the little bit at the top that tells how many are been written)
Is there an 11th June for 5Dmkii? not seen if there is.
Cheers!
I have a question
while 1080p raw rec , focus peaking works?? (5d mark3)
Any chance we're going to get the feature everyone would kill for... saved raw_rec settings, and raw_rec at startup? :-)
May I ask the developers to update RAW recording in 5D3 to enable this
CONSISTANT FRAME SKIP/DROP to match up the SPEED while SMOOTHLY RECORDING AND DROPPING/SKIPPING.
Option 1: Capture 1, Drop 1 (Take 1 of 2)
Frame 1 - Take
Frame 2 - Drop
Frame 3 - Take
Frame 4 - Drop
Frame 5 - Take
Frame 6 - Drop
etc
And also: Option 2: Capture 1, Drop 2 (Take 1 of 3) consistently
F1 - Take
F2 - Drop
F3 - Drop
F4 - Take
F5 - Drop
F6 - Drop
F7 - Take
F8 - Drop
F9 - Drop
F10 - Take, ... ETC
this to maintain smooth take RAW at 3592 x 1200, smoothly 10FPS (from 30fps, where drop/ skip frame consistently)
Than ;Dks
Why not just setting FPS override to 10?
Quote from: sksmseks on June 12, 2013, 01:03:52 PM
I have a question
while 1080p raw rec , focus peaking works?? (5d mark3)
Seems to be working for me.
With the newest commit of
5b666df
xml_cfg: a module XML config save using mxml library
Does this mean that when I turn on raw video and set aspect ratio, when I turn off my camera and turn it back on, Raw video and the aspect ratio that I set before I turned it off should still be set???
Quote from: aaphotog on June 13, 2013, 05:20:06 AM
With the newest commit of
5b666df
xml_cfg: a module XML config save using mxml library
Does this mean that when I turn on raw video and set aspect ratio, when I turn off my camera and turn it back on, Raw video and the aspect ratio that I set before I turned it off should still be set???
No... appears that the basic infrastructure to support recalling module settings upon startup has just been put into place. So far, only the Bolt module supports it.
backup.raw file?
I just recorded a 64GB file, and there is no footer information (June 13th build) but there is a "backup.raw" file.
Unfortunately I don't see any footer information in the file.
While I can repair this with my hex thread (need to update it now for 64GB files) has something changed?
Was running an older build (June 5 I believe) that automatically saved the footer information for me.
http://www.magiclantern.fm/forum/index.php?topic=5732.msg50692#msg50692
This 64GB footer fixed it...
Something very screwy with the June 13th build.
Problem: Recording 64GB files.
Short files are fine.
In two separate instances I recorded 64GB files. - I had to replace the footer on each. Both had corrupt dng files. Almost every dng file was purple/corrupt.
Using 24FPS (23.976) override, optimized for "low light".
Recording separate wav file.
Reverted back to June 05 build with exact same settings - 64GB file was fine.
Also, on the May 29th build I tried a 64GB recording and the footer was saved automatically. Not so with June 5th or 13th.
Can anyone try this with the June 13 build? Shoot a long movie, replace the footer with the info in this thread:
http://www.magiclantern.fm/forum/index.php?topic=5732.msg50692#msg50692
See if your dng files are corrupt as well.
Shawn
My June 14th build works with a1ex last commit.
I just recorded one large file 62,473,153 KB file size that filled the card. It opens up fine. The last 12 pictures are corrupted, but not too much of a concern for me.
Canon 5DMKIII
June 13th build got one footer format mismatch with clip over 4GB, from the 40 clips made under 4GB three only showed blank dngs, Raww2dng version 1 used to convert.
June 14th build footer format mismatch with clip over 5GB, no other clips made.
5D III - BUILD JUNE 14 - Stop recording with global ON and OFF, with memory hacked.
Computer BAY 64. Never before.
I checked the right card.
The only thing I changed was Load Module in startup.
June 13th update ---
For some reason I am not able to actually record any RAW video.
After pressing the record button (Live View), the camera shows that it is starting to record.
It finishes recording after I press the record button once again and even previews the file. However, when I plug it in to offload the files they do no exist.
When I turn the camera back on they have also disappeared.
Is anyone else experiencing the same issues?
new makefile build system works fine.
changing the convention for MAGIC.SYM to be the platform will be much less confusing going forward.
i added a zipwithmodules for myself in Makefile.inc so i could put out builds for 50D including the raw_rec and ettr modules.
if that's a useful option for others, i can commit that back.
looks like the build system commits are moving in the direction of automated builds for raw video on supported platforms.
ennkay - record button is now moved to the set button.
50D build seems OK today - continuous recording at 1585x1058 24p and 1728x920 24p files play back in camera and can access them on computer - though i did see a file footer error when attempting to playback one file and i am able to get into the menus while the video continues to record.
I am using a 5d3, i tried pressing the SET button but it does not work. When I press the live view button it records but just does not save the file permanently
Quote from: ennkay on June 15, 2013, 06:22:12 AM
I am using a 5d3, i tried pressing the SET button but it does not work. When I press the live view button it records but just does not save the file permanently
take off the battery and use an old build. This is like this to the DEV decide to finish the alpha. Sorry, i am in the same place.
Quote from: lourenco on June 14, 2013, 02:28:47 PM
My June 14th build works with a1ex last commit.
I just recorded one large file 62,473,153 KB file size that filled the card. It opens up fine. The last 12 pictures are corrupted, but not too much of a concern for me.
Not here. Just recorded a single 64GB file - the activity light on the camera never shut off and the footer wasn't saved on the resultant file. There was a separate backup.raw saved on the card as well.
Still happening with the June 14 build for me.
The footer isn't being saved either. Still getting corrupt dng files when I extract them.
Lourenco - when you insert a clean 64 GB card and record a single card-filling file, does your camera activity light ever shut off? Mine doesn't. Only thing I can think of that might be different is I'm running ML on the CF card itself and not the SD card.
Lourenco -
Just formatted both cards, reinstalled a virgin June 14 build, this time I'm running it from the SD card.
Same thing - The recording says "Stopped automagically" but the 5d3 activity light never goes off, and if I then go into the ML menu it says "Raw Video...stopping".
Only variation from the default build is I'm using the FPS override with 23.976 and recording audio in the raw video menu.
What if you try without audio?
Quote from: a1ex on June 15, 2013, 09:45:30 AM
What if you try without audio?
Good morning A1ex.
Just tried it with FPS override turned off, and it worked perfectly. I turned audio off too. I'll do 2 more - 1 with audio and FPS override disabled, and a 2nd with FPS override ON and audio disabled (beep only). This way we can isolate the variable.
Results for June 14 - audio off, FPS override off, Raw is fine, DNG's are fine.
Audio on, FPS override off, Raw is corrput (even after replacing footer) DNG's are corrupt.
Audio off, FPS override ON, Raw is fine, DNG's are fine.
This is for a single 64GB file.
So....this begs the question (well 2 questions actually)
1. What has changed with the audio recording, and
2. There's an option in the FPS override for audio disable/enable - how is this different from recording a separate wav file in the Raw video menu, and why have 2 places in ML that you can enable/disable audio?
Also, the file browser will not delete the 64GB file with the card full. It appears to delete it, and it shows a 3.6GB file (even though it's 64GB) and once you delete it / hit set, it now shows 0KB, but still says "card 1 full" once you switch back to the main menu.
*Edit* It did delete it, but you have to power the camera off and back on again to clear the "Card 1 full" message.
Audio recording is something separate from video, they don't talk to each other.
Back then, FPS override had to disable sound in H.264 videos. So, it has an option to record separate wav.
Raw video is bleeding edge, and it looks like you are expecting it to be as polished as Canon's H.264.
Quote from: a1ex on June 15, 2013, 11:04:16 AM
Audio recording is something separate from video, they don't talk to each other.
Back then, FPS override had to disable sound in H.264 videos. So, it has an option to record separate wav.
Raw video is bleeding edge, and it looks like you are expecting it to be as polished as Canon's H.264.
LOL you guys are light years ahead of the H264. I appreciate everything you guys have done; I'm just confused as to why the audio is still out of sync when I see new modules like "lightning bolt" recording - to me that's way less important than having a reference audio track. Rarely if ever would I record a straight 12+ minute clip straight so I'm not worried about it getting corrupt - I also think it's fair to point out that if Joe user enabled audio and just hit the record button with a 64GB card he's at least have a file he could work with - with the current build (and audio enabled) the raw file is hosed.
Please don't take anything I've said as demands or expectations - they're not. Just trying to help out testing what little I can.
Shawn
Hum... does this mean g3gg0 should not try to capture thunderbolts because you want perfect audio first?
Quote from: a1ex on June 15, 2013, 11:43:37 AM
Hum... does this mean g3gg0 should not try to capture thunderbolts because you want perfect audio first?
Not perfect audio, just audio that doesn't skip 1-2 frames per second and get out of sync. You guys are the creators of this and can do what you want though - who am I to say otherwise? ;)
Quote from: a1ex on June 15, 2013, 11:04:16 AM
as polished as Canon's H.264.
:o
Maybe it would be better to disable audio during raw recording seeing as it goes out of sync. Some people just expect it to work and come crying to us when it doesn't.
I shot a 20+ take narrative scene syncing external sound to the beep and syncing it in post wasn't a problem. I bought a new slate too (lost the old one). Pluraleyes does save time so it would be cool if you could get sound and raw video to sync at some point in the future but it's certainly not essential except to people who think they can get a good recording from a camera mounted mic ::).
Not a Thor fan Shawn? :D
Quote from: squig on June 15, 2013, 12:01:52 PM
Not a Thor fan Shawn? :D
It doesn't storm here often enough..
Also I think the onboard audio is pretty good, especially when you use it as a reference track. Not all of us are shooting major motion pictures here, and for run and gun I have to choose between using an external LCD or the zoom h1n shock-mounted on the shoe unless I grab the cage. It's quite nice for random clips to have synched up audio...
I guess all of us have different needs of course - I'm a selfish bastard and could care less if ML works on anything but the 5d3. It's all about me of course, and my needs. :P
I don't see much point going to the trouble to record raw video and syncing it with a low quality onboard audio recording. A reference track is all the onboard sound is good for. Good Mic placement is crucial for everything.
Quote from: squig on June 15, 2013, 12:21:07 PM
I don't see much point going to the trouble to record raw video and syncing it with a low quality onboard audio recording. A reference track is all the onboard sound is good for. Good Mic placement is crucial for everything.
Again Squig, some of us are shooting run and gun stuff....natural light, single man operation. We all have different needs.
posted new build for 50D simply unified at ee70e9d44745
did encounter the inability to record issue at times - seemed to happen when in an sub menu and then half pressing shutter to get to live view. full shutter press to take a jpg usually returned to normal with graphics draw showing info.
clips played back in camera - converted a couple to DNG without difficulty and all frames look OK.
camera did seem hotter than usual hitting 49 - i don't check this regularly but it is typically around 43 when i look after shooting.
Quote from: Shield on June 15, 2013, 09:42:58 AM
Only variation from the default build is I'm using the FPS override with 23.976 and recording audio in the raw video menu.
Audio on, FPS override off, Raw is corrput (even after replacing footer) DNG's are corrupt.
I just notice your updated post. Interesting your saying corrupted DNG with audio on and fps off.
Thinking to remove audio support until the issues will be solved (it may take a while).
Any objections?
Quote from: a1ex on June 15, 2013, 03:05:04 PM
Thinking to remove audio support until the issues will be solved (it may take a while).
Any objections?
abort:
bmp_printf( FONT_MED, 30, 90,
"Movie recording stopped automagically"
);
if (sound_rec != 1)
{
beep_times(2);
}
break;
Fixes it.
Good catch. It won't fix audio sync issues though.
I haven't been following closely, but how bad are the sync issues. If it's loosing sync part way through, imo that's a pretty serious issue. I agree that it's probably best served to just remove it, until it's polished enough not to generate a bug report every other day. If it just requires manually syncing the start positions, I don't really see what the problem is.
Sure, in a perfect world, audio synchronization with raw would be nice, but if audio synchronization is such a problem that you need it out of the box, "shoot Canon H.264" should be a sufficient answer.
And while I understand the need for "run and gun" shooting, with one device (not using a separate mic), considering the post work that must be done when shooting raw, start syncing audio is childs play.
June 14th build working fine. I have not been using the sound recording at all, better just to use a slate and sync with high quality recorder. It should be removed, better to concentrate on the gorgeous RAW images we are getting from the 5D3. Huge thanks to all the developers at Magic Lantern. :)
Quote from: a1ex on June 15, 2013, 03:05:04 PM
Thinking to remove audio support until the issues will be solved (it may take a while).
Any objections?
I can't think of any benefit keeping it while it goes OOS.
BTW has anyone told you the beep is off by a few frames?
How can i set more high resolution than 1920 at low fps ?
I wanna set 2.5k? at very low fps.. but i can't choose 1920+ ... (june 14th)
Quote from: squig on June 15, 2013, 06:20:53 PM
I can't think of any benefit keeping it while it goes OOS.
BTW has anyone told you the beep is off by a few frames?
What I do in Adobe after effects is sync the beep at 0:00 at then bring the left starting mark in about 4-6 frames. Sometimes I just play the zoom wav file back first to get the exact idea at what time the beep begins.
Today, I recorded about 12gb(seperate clips to equal 12) on a 16gb card(formatted ExFat).
When I hit the record button again, I got about 30 frames before it stopped and stated something about not recording because the card was full. Then, without touching the camera for a minute or so, a message popped up saying "card 1 full"
I should have had another 4 gigs left. Thinking that maybe it was a mistake in how much space I had left, I tried moving a one gigabyte file over to the SD card(with file manager). Once I did that, my card still showed that it was full. The entire time, using canons normal menu, it showed that only 12GB was used on this card. Any idea of what this may have been? Using the ML nightly from the 14th
I had a similar ghost data issue with the June 6 build. I think switching between LV and photo mode triggered it but I couldn't repeat it.
Quote from: squig on June 16, 2013, 02:52:14 AM
I had a similar ghost data issue with the June 6 build. I think switching between LV and photo mode triggered it but I couldn't repeat it.
That is probably what happened. I dont recall if I did the photo before or after.
How did you fix it? Reinstall ML?
Can't remember :-\ First try deleting everything on the card and remount it on your comp. If there isn't 16Gb available reformat the card.
It was quite a nasty bug, it somehow corrupted the file system and I lost some recordings and some of the ML files.
Quote from: squig on June 16, 2013, 03:33:40 AM
Can't remember :-\ First try deleting everything on the card and remount it on your comp. If there isn't 16Gb available reformat the card.
It was quite a nasty bug, it somehow corrupted the file system and I lost some recordings and some of the ML files.
I mounted it to computer first. It did read that the card was a 16gb card. I went ahead and grabbed the files(not sure if they're ok as I haven't tested them). Then I deleted the contents on the card and placed back in cam. Seems to be recording ok now, but I haven't recorded 16GB worth of data just yet.
With the last 2 compiles for the 5D III I can no longer get the Modules to load.
Maybe it's me but thats why I'm posting, I've never had an issue before. I went back to the last working build (14th) and tried to recopy several times but no luck.
They are set to Autoload
Error = At the bottom of the M Tab "Linking Failed"
When I try to manually load a Module =
tcc: error: undefined symbol 'memmove'
tcc: error: undefined symbol 'strtod'
All Modules Failed....
any ideas?
Last build for MKIII / same thing for me: stuck after the smiley "enable boot disk". L.
Quote from: larsenlupin on June 16, 2013, 04:29:42 PM
Last build for MKIII / same thing for me: stuck after the smiley "enable boot disk". L.
Make sure you enable boot disk on the card with ML.
Use eoscard http://wiki.magiclantern.fm/3rd_party_software
I feel dumb now, this happened once before... I had two sets of files old and new in the Modules Folder... thanks for the PM lourenco
Quote from: lourenco on June 15, 2013, 04:30:28 PM
abort:
bmp_printf( FONT_MED, 30, 90,
"Movie recording stopped automagically"
);
if (sound_rec != 1)
{
beep_times(2);
}
break;
Fixes it.
If it records sound like before it could be useful as for catching ambient sound that don,t necesserally needs syncing?
June 16th 5d3 Lourenco build has the autoexec file inside the ML folder, is that right? Its usually in the main directory.
Also it seams the magic.sym was replaced with the 5D3_113.sym. What was the change?
Quote from: hjfilmspeed on June 16, 2013, 07:20:56 PM
June 16th 5d3 Lourenco build has the autoexec file inside the ML folder, is that right? Its usually in the main directory.
Also it seams the magic.sym was replaced with the 5D3_113.sym. What was the change?
autoexec goes to root directly. I updated the zip file to fix this. The magic.sym is now replaced with 5D3_113.sym.
With the new builds (from the June 11th to 17th), the way the ISO is displayed is different when Raw Rec is OFF (ISO 640 buy example) and when Raw Rec is ON (ISO 800eq with the same example).
Does it change something or is it just the way the ISO appears now?
And in the file browser, the files have a wrong size (always smaller than it supposed to be).
By example, M17-2340.raw is 2.9 GB instead of 7.5 GB
Is there any reason?
ISO now prints the value at which you are recording.
File browser uses 32-bit code, I have no idea how to get the 64-bit file size.
Sorry A1ex, I'm not sure to understand about the ISO:
Does it mean that ISO 800eq is the value at which I'm recording when the Canon is at ISO 640?
And why the ISO in Raw is different to the ISO in H.264?
Quote from: Sthirasukha on June 18, 2013, 12:29:38 AM
Sorry A1ex, I'm not sure to understand about the ISO:
Does it mean that ISO 800eq is the value at which I'm recording when the Canon is at ISO 640?
And why the ISO in Raw is different to the ISO in H.264?
I believe because the iso in normal canon software has BASE ISO's (100/200/400/800...) and then to get the intermediate values, the software PUSHES these iso's. But with ML it only keeps the base iso's instead of doing a software push.
Maybe Im completely wrong, but I read something about that here on the forums.
Ok, I've got it now. I knew that I have better result when I shoot at multiples of ISO 160 (only available if Highlight Tone Priority is disabled) as said most of the directors using the 5D MKII-MKIII but I didn't get the exact explanation. I've found this (http://blog.vincentlaforet.com):
"Technically, the camera is native on the ISO's that are multiples of 100. For the ISO's in-between, the camera digitally pushes or pulls one of these native ISO's. For instance, ISO 125 is really ISO 100 with a digital exposure push, and ISO 160 is really ISO 200 with a digital exposure pull. As a result, 160 and its multiples look the "cleanest" because its really a native ISO rating with the exposure pulled down, which hides more of the digital noise".
Thank you A1lex and Aaphotog
Quote from: Sthirasukha on June 18, 2013, 07:30:41 AM
For instance, ISO 125 is really ISO 100 with a digital exposure push, and ISO 160 is really ISO 200 with a digital exposure pull. As a result, 160 and its multiples look the "cleanest" because its really a native ISO rating with the exposure pulled down, which hides more of the digital noise".
No that only applies to H.264, the opposite is true recording raw, multiples of 100 are cleaner.
@squig: this is the 10th reminder to update your tests. In raw, the intermediate ISOs are identical to multiples of 100.
Quote from: a1ex on June 18, 2013, 01:15:39 PM
@squig: this is the 10th reminder to update your tests. In raw, the intermediate ISOs are identical to multiples of 100.
Yeah I heard ya, I'm a little busy ATM.
Quote from: lourenco on June 16, 2013, 08:05:54 PM
autoexec goes to root directly. I updated the zip file to fix this. The magic.sym is now replaced with 5D3_113.sym.
Thank you!!!
Hello,
There seem to be a bug.. even few. .. correct me if I am wrong
1) When camera has 24 fps set... lantern does record as 25fps.FPS ovveride is off.
I have found this issue with a help of the sound. So here how to test: Enable sound recording.. put camera to 24 fps and record raw with sound when somebody is speaking, so that the lips are visible in the frame. At least for 10 seconds or so.
Now take video as 23,976 and put sound .. and you will see that is synchs at the begining and then fails more and more to the end.
IF I take and conform video as 25 fps.. and put it with the same sound.. everything synchs perfectly for the whole length of the clip.
Seems like a bug ,no?
2) Weird stuff.. but when SD with lantern in on and loaded.. And I start to record regular h264.. it records only about 30 seconds and then load buffer icon appears and it stops... That is with 1000x Lexar card.. Then I remove lantern SD and start usual h264 record and everything goes smooth as always. Any idea why? Seems like lantern is setting much higher bitrate for h264.. but where can this be checked and tested?
For the first time since May 22nd version of ML my 5D Mk III crashes (: crash log
ASSERT: 0
at ./Memory/Memory.c:568, task RscMgr
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun22.5D3113
Mercurial changeset :
Built on 2013-06-22 10:41:56 by magiclantern@magiclantern-VirtualBox.
Free Memory : 294K + 3595K
UPDATE: Redownloaded the June 22nd build. Reinstalled it on the SD card and now it works fine. False alert.
June 25th build
Where's the file manager ? I can't find it (maybe it's only my bad eyesight ?)
Quote from: frenchps49 on June 25, 2013, 02:43:18 PM
June 25the build
Where's the file manager ? I can't find it (maybe it's only my bad eyesight ?)
Quote from: frenchps49 on June 25, 2013, 02:43:18 PM
June 25th build
Where's the file manager ? I can't find it (maybe it's only my bad eyesight ?)
and Soundrecording and ETTR are missing too.
The module Screen says wrong version OldAPI and that it expected version 2.0 instead of 1.3
I thought i did someting wrong.
I can't have 1/47 shutter speed. It's 1/50.
They must be experimenting with something...
Apparently Lourenco (the guy or the gal who compiles for us and who should be thanked for that) will post an updated build later.
Quote from: mauerfuchs on June 25, 2013, 06:15:05 PM
and Soundrecording and ETTR are missing too.
The module Screen says wrong version OldAPI and that it expected version 2.0 instead of 1.3
I thought i did someting wrong.
Ya. I did make a mistake and somehow copy over a old version of the ettr, fileman, and pic_view. Sorry guys. It is fixed now.
No problem, Lourenco. Thanks.
Quote from: advent2 on June 23, 2013, 11:29:37 AM
H
2) Weird stuff.. but when SD with lantern in on and loaded.. And I start to record regular h264.. it records only about 30 seconds and then load buffer icon appears and it stops... That is with 1000x Lexar card.. Then I remove lantern SD and start usual h264 record and everything goes smooth as always. Any idea why? Seems like lantern is setting much higher bitrate for h264.. but where can this be checked and tested?
I can confirm this, too.
Shooting raw is perfect, but when i do h.264 on my komputerbay 64GB, it stops after a few seconds with full buffer icon. when i put in my Lexar card, everything is fine.
Quote from: lourenco on June 26, 2013, 02:43:07 AM
Ya. I did make a mistake and somehow copy over a old version of the ettr, fileman, and pic_view. Sorry guys. It is fixed now.
...and about bolt rec? ..the same wrong version...
Thanks
I have a 5D III with a 16GB CF and 2GB SD
I do step by step but i dint work.
I have only a normal CF Card its Ultra Fast SanDisc 90mb's sec. 16GB
can anyone help me?
5. From the Magic Lantern package copy the 5D3-113-bootflag.fir file to the root folder
___of the SD card.
6. Place the SD card in your camera, switch it on and go to the firmware update in the
___camera menu. Do the update which will "turn" your camera's bootflag. Whatever that
___means.
7. The camera now loads weird overlays, wait until it's finished. Switch the camera off.
8. Get the SD card back in the Computer. DELETE 5D3-113-bootflag.fir file from the SD!
9. Copy the autoexec.bin and "ML" folder onto the SD card.
10. Download Macboot and the Mountain Lion fix (if you're on a Mountain Lion Machine)
___(for Windows see here: LINK).
11. Open only the ".command" file (for Mountain Lion) and insert your password in the
___Terminal window that pops up.
12. The Macboot app should open. Select "DSLR Bootable" and press "prepare card".
___It should now display a "success" note.
13. Click "Eject Card".
14. The SD card goes back into the 5D mark III together with the Komputerbay CF card.
15. Switch camera on.
16. Now press the "trash button" on the camera to activate Magic Lantern. The Magic
___Lantern menu should load.
Quote from: acid2006 on June 27, 2013, 07:14:04 AM
...and about bolt rec? ..the same wrong version...
Thanks
The bolt rec currently does not work. Given it is not compatible with the newer raw_rec. g3gg0 the developer for bolt rec noted it does not work with the new version of raw_rec. You have to go back to previous build if you want this feature for now.
Quote from: advent2 on June 23, 2013, 11:29:37 AM
Hello,
There seem to be a bug.. even few. .. correct me if I am wrong
1) When camera has 24 fps set... lantern does record as 25fps.FPS ovveride is off.
I have found this issue with a help of the sound. So here how to test: Enable sound recording.. put camera to 24 fps and record raw with sound when somebody is speaking, so that the lips are visible in the frame. At least for 10 seconds or so.
Now take video as 23,976 and put sound .. and you will see that is synchs at the begining and then fails more and more to the end.
IF I take and conform video as 25 fps.. and put it with the same sound.. everything synchs perfectly for the whole length of the clip.
Seems like a bug ,no?
I wonder if this is what's been up with the audio all along. Will test this immediately!
Shawn
Wow... imagine that you solved it... this is why 600D would record audio with flush rate and all that junk at 25 fps. Guess it holds true for all cameras... defaults to 25fps "sync".
QuoteI can't have 1/47 shutter speed
You never could... it was lies... looking at frame shutter timer... real shutters are different from what canon tells you... maybe they are right for a snapped photo but not for the electronic shutter. Probably lets you pick some closer shutters from ML menu.
Quote from: 1% on June 27, 2013, 06:43:06 PM
Wow... imagine that you solved it... this is why 600D would record audio with flush rate and all that junk at 25 fps. Guess it holds true for all cameras... defaults to 25fps "sync".
I just recorded the most boring 4 minutes of my life of me standing, talking and clapping. Will report in shortly. This will be sweet if so - should just be able to drag a 25fps clip onto the timeline and render as 23.976. :)
While I'm waiting for this crap to render, I'm curious if my card(s) can handle 25FPS in 1:1 mode. As a point of reference, the "idle time" going from 23.976 to 25.0001 FPS went from 10% to 5%. Will report back in.
*Edit* The 1:1 mode @ 25.0001 FPS override was no problem. 7% idle. With audio.
zzzz still rendering....
Quote from: Shield on June 27, 2013, 07:28:21 PM
While I'm waiting for this crap to render, I'm curious if my card(s) can handle 25FPS in 1:1 mode. As a point of reference, the "idle time" going from 23.976 to 25.0001 FPS went from 10% to 5%. Will report back in.
*Edit* The 1:1 mode @ 25.0001 FPS override was no problem. 7% idle. With audio.
zzzz still rendering....
thanks. what build are you using for this ?
I shouldn't do this when I'm tired. Will report back in (had stupid 23.976 interpreted footage!!) @#$@#$%@$%
New raw_rec works great! 2560x1090 at 23.976fps over 1200 frames before skipping 108.5MB/S.
Quote from: lourenco on June 28, 2013, 03:37:36 AM
New raw_rec works great! 2560x1090 at 23.976fps over 1200 frames before skipping 108.5MB/S.
Wow, it does!
I belive the raw_rec that you compiled when he originally came up with the variable buffering got me about 260 frames??? now I'm getting about 380 with all of the hacks on at 2560x1090 (2.35 ratio)
this is with a 600x sandisk card.
how do i pick 2560x1090? i get not possible in current video mode
Quote from: Jakobmen on June 28, 2013, 05:08:53 AM
how do i pick 2560x1090? i get not possible in current video mode
Use one of the zoom modes.
I do not think rendering 25 at 24 is a solution.. it is often gives artifacts as frames are changed. It would be better to fix this bug in Lantern itself.. ]
Quote from: advent2 on June 28, 2013, 10:15:43 AM
I do not think rendering 25 at 24 is a solution.. it is often gives artifacts as frames are changed. It would be better to fix this bug in Lantern itself.. ]
Well it doesn't matter anyway - the audio was worse recording and rendering at 25p. For a 4 minute clip, the audio was about 10 seconds short, and not synched at the beginning either - I had to move the audio about a second ahead in the beginning to sync. Then it quickly went out of sync - seemed to be off 2-3 seconds easily per minute of recording.
Going back to 23.976. Good idea though.
Can we get 2k, I think is 2048 x 1080 resolution, exactly? In the menu, an option 2K
It´s an standard of movies, when you have to send a movie to a festival, and always we are changing the resolution - except you use an Arri or RED or sth like that.
Question for lourenco mainly ... when I look at my Modules based on the June 27th build, the CF ACC one has OldAPI listed. Is this an issue? It seems to work OK but I just want to make sure it's all optimized.
Hi guys, I am new to all this and have searched but am not finding the exact answers i'm after. So I have two questions....
1) How do i format my CF card to ex fat so i can record over the 4gb limit?
2) I just went to the latest build for ML raw 5dmk3 and am wondering if I just download the files and drop them on my SD card? Or do I have to download another ML version first?
Quote from: regnis on July 02, 2013, 11:06:54 AM
Hi guys, I am new to all this and have searched but am not finding the exact answers i'm after. So I have two questions....
1) How do i format my CF card to ex fat so i can record over the 4gb limit?
2) I just went to the latest build for ML raw 5dmk3 and am wondering if I just download the files and drop them on my SD card? Or do I have to download another ML version first?
Wrong thread! You can find all information in sticky threads in the same RAW section. You just have to look better.
I'm getting an issue with judder on the first 4-6 frames on my 1920x1080 23.976fps recordings using both June 25th and 27th builds. It can be fixed manually but it's a pain to do it.
It's not just on the first recordings - it's on many, but not quite all, of the recordings I'm making. I guess unless there's a lot of movment at the start of the clip I'm not seeing it or bothered by it.
I'm using 1000x Lexar 32GB card that I've benchmarked above 90MB/s in 24p mode with GD on.
I'm using the latest raw2dng to convert to .dng.
An example raw file is here:
https://www.dropbox.com/sh/6nxghy5rtfc4lnz/oQLgEHG8Ay
using same 3ecd254bdba1 (a1ex last commit) hudson/unified code
https://bitbucket.org/hudson/magic-lantern/commits/3ecd254bdba1907110eb72a98b2b9aeb2785a3a5
on 50D and 5D3 -
how come ML Grayscale looks so much better on the 50D ?
on 5D3 ML Grayscale is blocky and pixelated (so bad i am forced to go to 10x to focus).
on 50D, the display is Canon color until record then a smooth grayscale image.
also, couldn't get digital dolly to work on either camera with it enabled. strangely joystick could pan albeit jerky when digital dolly was disabled. perhaps i am missing a setting.
That means it's not working on 50D and falls back to Canon display ;)
ML grayscale is for correct framing only, not for focusing. Press half-shutter for best quality. If you can make it faster, feel free to do so.
thanks for the info.
5D3 when in ML Grayscale
half shutter press is showing the Canon info display (at bottom exposure iso setting) - not disabling the the Grayscale
btw - tried the auto-ettr and flicker free sidecars for a timelapse and it worked very well.
you have a real achievement in camera software design with these features.
https://vimeo.com/69576183
waiting for clear skies at night this is a test dawn sequence where i adjusted the focus, framing and aperture.
(wanted to try workflow and evaluate location)
5D3 (unified.80e3ca539891) shooting greater that 2k produces frames with black right borders
2880x1320 ends up more like 2770x1320
if this is not a known issue and anyone would like DNGs of any flavor, left me know.
(http://50.56.67.113/ml-07july13/M03-2040_00020.jpg)
Didn't change anything lately.
Maybe it depends on focus box position?
I have same results/thing/issues when shooting in a crop mode greater than 2K. I didn't really freak out about it since I thought that's how it should be, right? Let me know if I'm wrong. I just cropped that black bar every time.
Not sure if this happens in all crop modes, but I made a couple of recording in the 5x(3x?) crop mode at a resolution of 2240x954
I used raw2dng(mac gui 0.13 made by scrax) to get the dng files, pulled them into Adobe After effect, I have a black bar at the right of the image as seen below. This is for every clip recorded at this resolution. Not sure if it happens in higher resolutions or not. BUT, when I record WITHOUT crop mode, at the 1920x818 resolution everything is fine. So, I'm not sure if this issue is to do with the crop mode, or the higher than 1080 resolution. Any ideas?
PS. I used FPS override set to 23.976
(http://i43.tinypic.com/vdh0zl.png)
@aaphotog
Maybe this doesn't answer the question; but I see you have several different compositions there. Are you sure you haven't used the comp settings from another imported file on one recorded with a smaller frame dimension?
If I am totally on the wrong track here just ignore my stupidity! ::)
Quote from: mageye on July 04, 2013, 04:39:23 PM
@aaphotog
Maybe this doesn't answer the question; but I see you have several different compositions there. Are you sure you haven't used the comp settings from another imported file on one recorded with a smaller frame dimension?
If I am totally on the wrong track here just ignore my stupidity! ::)
ill double check it, but I imported each clip seperately, then right clicked on each and selected(create new composition from this file) so each comp should have been created based on the dngs it was created from. In theory at least, right?
Edit: just opened one of the DNGs from the clip with the black side, in photoshop. The dng even shows the black line in photoshop, so it can't just be my sequence settings.
PS. If it helps, the resolution that clip was recorded at was 2240x954, but it also happened at 2560x1090.
Does the 5d3 not have that wide of an area on the sensor? Could that be it?
I am on the 5DMKII and have not experienced what you are getting; so I have no idea what could be causing that? I feel fortunate that I don't get that problem.
Maybe someone else could bring some enlightenment? :(
Quote from: mageye on July 04, 2013, 05:19:31 PM
I am on the 5DMKII and have not experienced what you are getting; so I have no idea what could be causing that? I feel fortunate that I don't get that problem.
Maybe someone else could bring some enlightenment? :(
I hope so as well. I appreciate your effort though!
Quote from: a1ex on July 04, 2013, 09:27:40 AM
Didn't change anything lately.
Maybe it depends on focus box position?
OK - will try different focus box positions- still haven't used digital dolly - so i thought i'd take a large image and pan in post.
had been demoing raw video for some LA cinematographers who were very impressed with both 50D and 5D3.
they were running 2 5D3's in time lapse for this shot and wanted to know more about 2K - so that's why i'm trying it out.
raw->cinemadng(via rawmagic)->gimp (ufraw) -> jpg (no processing)
(http://50.56.67.113/ml-07july13/M02-2244_00057.jpg)
Quote from: aaphotog on July 04, 2013, 04:44:34 PM
PS. If it helps, the resolution that clip was recorded at was 2240x954, but it also happened at 2560x1090.
Does the 5d3 not have that wide of an area on the sensor? Could that be it?
hi @aaphotog
in this example,
it happened at:
2880x1320
2560x1320
2240x1260
5D3 has crop mode maximum horizontal resolution of 3584 (based on LiveView) - so something may be off in the frame position or frame grab in crop mode at higher resolutions - moving around the focus box could affect this -so when i can test and report issue more precisely i'll do so.
Quote from: GregoryOfManhattan on July 04, 2013, 07:47:27 PM
hi @aaphotog
in this example,
it happened at:
2880x1320
2560x1320
2240x1260
5D3 has crop mode maximum horizontal resolution of 3584 (based on LiveView) - so something may be off in the frame position or frame grab in crop mode at higher resolutions - moving around the focus box could affect this -so when i can test and report issue more precisely i'll do so.
Thank you so kindly. When in crop mode, I didn't move the box at all before recording, should I have? I know it used to be a 17 up and to the left or something, but it's changed so much. I thought with the new hack, it automatically centered correctly when hitting the magnifying glass
hi @aaphotog - moving the focus box would be for a diagnostic test to see if different positions lead to a different number of black pixels on the right. it may or may not have any affect.
we pay dearly for every pixel recorded, so we don't want to waste any precious bitrate on black.
for 2880x1320 looked like about 110 pixels of black (needs to be precisely measured)
110x1320x(14bit/8bit/btye/frame)x24frame/s -> 5.8 MB/s of black waste
here are some DNGs in which the black pixels could be measured.
2880x1320: http://50.56.67.113/ml-07july13/M03-2040_raw2dng.dng
2560x1320: http://50.56.67.113/ml-07july13/M03-2041_raw2dng.dng
2240x1260: http://50.56.67.113/ml-07july13/M03-2042_raw2dng.dng
The black bar doesn't look very well, did you enable anything related to ADTG?
I've just tried with 3ecd254bdba1 (didn't update to latest stuff yet) and these 3 resolutions look normal here, without any black border. Focus box was perfectly centered; the focus box snap trick was not enabled.
Quote from: a1ex on July 04, 2013, 08:53:19 PM
The black bar doesn't look very well, did you enable anything related to ADTG?
I've just tried with 3ecd254bdba1 (didn't update to latest stuff yet) and these 3 resolutions look normal here, without any black border. Focus box was perfectly centered; the focus box snap trick was not enabled.
What would I have to select to enable anything related to ADTG?
I was using the 3ecd254 build, built by Lourenco.
Could this have been caused by the latest 0.13 Mac gui of Raw2DNG?
EditI tried extracting the .raw file with rawmagic, and it produces files with the same black bars.
That one is an experimental module for investigating low-level sensor parameters.
http://www.magiclantern.fm/forum/index.php?topic=6751
Does the black bar show up if you play the raw video directly in the camera? (that's how I've tried).
Quote from: a1ex on July 04, 2013, 09:07:01 PM
That one is an experimental module for investigating low-level sensor parameters.
http://www.magiclantern.fm/forum/index.php?topic=6751
Does the black bar show up if you play the raw video directly in the camera? (that's how I've tried).
I didn't select anything like that in the menu.
Update. I turned the camer on, clicked the magnification button(to go to crop mode) then I hit the joystick button in the center. When I did that, my view moved a slight bit. So maybe I was just off center when recording? Could that be a possibility or would it automatically center me when I clicked the center joystick so that shouldn't have been the issue?
Update 2: after going to crop mode, I hit the center of the joystick(which centers the image) and recording... same outcome Black bars :-(
Quote from: GregoryOfManhattan on July 04, 2013, 08:37:38 PM
hi @aaphotog - moving the focus box would be for a diagnostic test to see if different positions lead to a different number of black pixels on the right. it may or may not have any affect.
we pay dearly for every pixel recorded, so we don't want to waste any precious bitrate on black.
for 2880x1320 looked like about 110 pixels of black (needs to be precisely measured)
110x1320x(14bit/8bit/btye/frame)x24frame/s -> 5.8 MB/s of black waste
here are some DNGs in which the black pixels could be measured.
2880x1320: http://50.56.67.113/ml-07july13/M03-2040_raw2dng.dng
2560x1320: http://50.56.67.113/ml-07july13/M03-2041_raw2dng.dng
2240x1260: http://50.56.67.113/ml-07july13/M03-2042_raw2dng.dng
Im shooting 2.35:1
I cropped the black bars from the image so all I have are the black bars. It might not be EXACT, but this is what the bar measures on the 2240x954 image 110(wide)x954(tall)
the black bar in the first image you posted looks to be 110 as well( I didn't download the others). are these your photos? If so, how did you fix it?
Quote from: a1ex on July 04, 2013, 08:53:19 PM
The black bar doesn't look very well, did you enable anything related to ADTG?
I've just tried with 3ecd254bdba1 (didn't update to latest stuff yet) and these 3 resolutions look normal here, without any black border. Focus box was perfectly centered; the focus box snap trick was not enabled.
haven't enabled (to my knowledge) any ADTG or other debug settings.
for these shots had default values.
Preferences-> Focus Box Settings -> Snap Points -> Center (off)
will try the 5x zoom setting.
Quote from: a1ex on July 04, 2013, 09:07:01 PM
That one is an experimental module for investigating low-level sensor parameters.
http://www.magiclantern.fm/forum/index.php?topic=6751
Does the black bar show up if you play the raw video directly in the camera? (that's how I've tried).
Played back in camera. I cant be SURE(the edges are black either way where the picture isnt), but it does look like it plays back with the black bars IN camera. I dont see ANY black on the left side of the picture, but I DO see black on the right side, top, and bottom(it should show black on top and bottom)
Can you take a silent picture in that mode?
Also take a screenshot so I can see the focus box position.
Quote from: GregoryOfManhattan on July 04, 2013, 09:28:40 PM
haven't enabled (to my knowledge) any ADTG or other debug settings.
for these shots had default values.
Preferences-> Focus Box Settings -> Snap Points -> Center (off)
will try the 5x zoom setting.
Thanks for posting this. My focus box setting WAS
Preferences-> Focus Box Settings -> Snap Points -> Center (off)
I've changed it to
Preferences-> Focus Box Settings -> Snap Points -> center to x5 RAW
and did a new recording. hit the magnify button, the hit the joystick to center(this time the box centered waaaaay left) and then recorded. I only played back IN camera, but NO black bar that I can see...
Alex, I thought you fixed it a week or so back that wherever the box was, it would sample that part of the sensor and record correctly(ie foocus box in middle, would record REALLY close to that and no black bar)
Here, with focus box centered and Snap Points -> Center (off), it records without any black bars at these 3 resolutions. Even at max res (3.5K), the image is perfect.
So... I'm looking for a way to reproduce the problem.
Quote from: a1ex on July 04, 2013, 09:34:12 PM
Can you take a silent picture in that mode?
Also take a screenshot so I can see the focus box position.
Which mode do you want a silent picture in, and how do I take it?
Alex let me know what to do too and I will do it. Since I'm seeing those black bars too (doesn't matter whether raw2dng converted or rawmagic converted). I've never really used 3x mode before, but not so long ago tried it and got same results as aaphotog. I can post screenshots and make even a video of the screen.
Alex, could it be in my Raw module settings?
Resolution: 2560x1090
Aspect Rattio: 2.35:1
Preview: Auto
Digital Dolly: OFF
Frame Skipping: OFF
Card Warm-up: OFF
Memory Hack: OFF
Small hacks: ON
Playback
Alex, try this
turn on your cam load up the raw module with my settings as above.
now, when you go back to the live view(without crop mode on), hit the joystic button so that your focus box gets square directly in the middle.
then, hit the crop mode, now take a look on the right side of your screen(should be no need to even record). Do you see the black bar?
It seems when I follow these stepes I get the black bar every time, but if I move the joystick to the left some(while still in crop mode) the bar goes away. It's a bit odd.
Maybe later I can record a video of the screen with my iphone.
Quote from: aaphotog on July 05, 2013, 05:45:42 PM
Alex, try this
turn on your cam load up the raw module with my settings as above.
now, when you go back to the live view(without crop mode on), hit the joystic button so that your focus box gets square directly in the middle.
then, hit the crop mode, now take a look on the right side of your screen(should be no need to even record). Do you see the black bar?
It seems when I follow these stepes I get the black bar every time, but if I move the joystick to the left some(while still in crop mode) the bar goes away. It's a bit odd.
Maybe later I can record a video of the screen with my iphone.
When you move the joystick 5 steps to the left from the middle in crop mode the black bar is gone, no matter which resolution you chose after that it's gone till you turn of the camera. That's with the 5DMKIII.
Quote from: jpjp on July 05, 2013, 07:05:49 PM
When you move the joystick 5 steps to the left from the middle in crop mode the black bar is gone, no matter which resolution you chose after that it's gone till you turn of the camera. That's with the 5DMKIII.
Ok. I was under the impression that Alex implemented something to where no matter where that focus box was on the screen, when you hit the magnify button, it would be able to record fine without issue.
Quote from: aaphotog on July 05, 2013, 05:45:42 PM
... then, hit the crop mode, now take a look on the right side of your screen(should be no need to even record). Do you see the black bar?...
yes i see it as well. don't have time / gear with me to verify that when you see the black bar on screen you will get it on a raw video. (have loaded in the last a1ex commit based build 3ecd25)
Quote from: jpjp on July 05, 2013, 07:05:49 PM
When you move the joystick 5 steps to the left from the middle in crop mode the black bar is gone, no matter which resolution you chose after that it's gone till you turn of the camera. That's with the 5DMKIII.
thanks you - easy workaround - you could also activate and NOT use digital dolly.
does it seem to you that the right side black bar happens when you are exactly centered and going left or right the right side black bar goes away?
it also appears at the end of a digital dolly.
Quote from: aaphotog on July 05, 2013, 07:12:11 PM
I was under the impression ... it would be able to record fine without issue.
alpha open source software - find and accurately report bugs - enjoy what you can get - test builds in advance for your specific photo/video application - be careful on projects.
https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha (https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha)
Quote from: GregoryOfManhattan on July 05, 2013, 08:16:10 PM
yes i see it as well. don't have time / gear with me to verify that when you see the black bar on screen you will get it on a raw video. (have loaded in the last a1ex commit based build 3ecd25)thanks you - easy workaround - you could also activate and NOT use digital dolly.
does it seem to you that the right side black bar happens when you are exactly centered and going left or right the right side black bar goes away?
it also appears at the end of a digital dolly.
alpha open source software - find and accurately report bugs - enjoy what you can get - test builds in advance for your specific photo/video application - be careful on projects.
https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha (https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha)
Of course, but I remember first alex set it up to where when you hit the magnifying glass, the box would jump where it needed to be. Then he put in place where when you hit the magnifying glass and recorded crop, it would be able to correctly sample the sensor wherever the focus box already was(maybe just a bit off but it would move on it's on) was that messed up in one of the last previous builds? I don't remember crop mode ever given me black bars, and I've NEVER had to situate the focus box to get a good crop recording.
Anyone build the newest nightly build from today for the 5d3 and care to post it?
There were no changes relevant to this.
Can you record a video showing the camera screen?
What would you like for me to show in the recording, Alex?
There's something thats got to be wrong
I just recorded in crop mode again(forgetting about the black bar)
I pull up the clip graded and all, but when I went to play it back i noticed that the black bar was there on the right side. The crazy thing about it, was that on the first second or two of the clip, the black bar is NOT there? I never moved the recording area using the joy stick so I don't know.
Could it be possible that something is just wrong with Lourenco's build for the 5d3? anyone else have an updated build that they are willing to upload?
EDIT: Playing back the clip frame by frame 2 frames AFTER the black line shows up, the exposure gets darker(I think I did change exposure during recording) could this have something to do with it? The other videos where I talked about this issue in earlier posts I dont believe I changed exposure while recording though. Also, this time, the first couple frames where the black bar shows up, they have a few red vertical lines in them.
I converted this particular raw with raw magic
EDIT 2: nevermind the exposure change. I didn't change exposure, it was just lightning that was happening
It seems that all of the Raw builds have been updated except for the 5D3. Does anyone have a newly compiled build from today that they are willing to upload?
2 things I've noticed.
I am using a tablet as field monitor. But its hooked up to my camera(5D3) through USB.
One thing I've noticed is that I'm getting MUCH less frames at 2560x1090
When the tab is NOT connected to the camera, I get about 950 frames at that resolution.
When the tablet IS connected to the camera, I'm only getting about 320-340 frames
Any plans to make this better?
Also, when recording at 2560x1090, I noticed that after about the 3rd recording, I start to get less frames as well. Sometimes it's 100 less, sometime 2-300 less frames.
I haven't done MANY tests, but the few that I have, that's what happened. Im using Lourencos latest build.
BAKUP.RAW file when CF filled up.
At the moment of the exhaustion of place on СF - is obtained BACKUP.RAW file, last recorded file don't recognize with raw2dng/RAWmagic. What the matter?
https://www.dropbox.com/s/ztoenodfpurulcp/BACKUP.RAW%20file.png
Quote from: jake badlands on July 19, 2013, 01:51:38 AM
BAKUP.RAW file when CF filled up.
At the moment of the exhaustion of place on СF - is obtained BACKUP.RAW file, last recorded file don't recognize with raw2dng/RAWmagic. What the matter?
https://www.dropbox.com/s/ztoenodfpurulcp/BACKUP.RAW%20file.png
Already find how to fix the problem with HEX editor...
But entire problem remains: when CF completely is filled up - last file is corrupt.
I hope my opinion it will be useful.
Thanks!
Quote from: jake badlands on July 19, 2013, 01:16:29 PM
Already find how to fix the problem with HEX editor...
But entire problem remains: when CF completely is filled up - last file is corrupt.
I hope my opinion it will be useful.
Thanks!
hi Jake, i have filled up several cards - 2 without problem and 1 with the issue below where the card was almost full at the same time the battery warning was flashing (lost a couple of seconds at the end of a 5 minute shot). so in this case it wrote a correct footer, but had frame errors which crashed rawmagic.
is this a consistent issue on your camera?
Quote from: GregoryOfManhattan on July 16, 2013, 05:01:13 PM
Thomas,
thank you - rawmagic is working well. wanted to let you know that i have 1 clip (actually span of 8 files) which crashes rawmagic 1.0 beta 7b. please let me know if you'd like any crash logs, DNGs, or other information. the battery was running low as the card was filling up - so its not surprising there are errors.
raw2dng can process all the frames. the last 44 frames are corrupted in an alternating pattern of 80% good top image 20% pink followed by a frame 80% pink corrupted top portion with bottom 20% OK.
~/bin/raw2dng M02-244-concatted.RAW
Resolution : 1920 x 1080
Frames : 7532
Frame size : 3629056 bytes
Frame skip : 1
FPS : 0.000
Processing frame 7532 of 7532...
Done.
Quote from: aaphotog on July 05, 2013, 05:30:10 PM
Alex, could it be in my Raw module settings?
Resolution: 2560x1090
Aspect Rattio: 2.35:1
Preview: Auto
Digital Dolly: OFF
Frame Skipping: OFF
Card Warm-up: OFF
Memory Hack: OFF
Small hacks: ON
Playback
Yes, this is the setting I need for my movies! Tell me if you can! I'm not good with software...
This thread has slowed down a lot. Has the latest build discussion moved somewhere else?
Good question .. there´s lots of open questions .. but I´m not sure if the developers are following.
Installed the build from August 21st .. everything seems to work - besides audio recording when shooting raw video. It just does not write a single wav file even if recording audio is enabled under the fps settings in raw video. Anyone has an idea how to get sound back?
Can I ask and sorry if this has been addressed earlier in this or another thread.
When regular h264 recording
Has auto restart been removed from the latest build?
It wasnt working on the aug6 build , now i just cant find it under movie tweeks at all.
Also perhaps i should know this but why is the iso/kelvin set controls going off every time i press rec?
I know we are in alpha but these are settings i really need for work (and its nice to have raw there for the odd shot)
Thanks as usual
Quote from: Grifter on August 26, 2013, 02:47:42 AM
When regular h264 recording
Has auto restart been removed from the latest build?
Yes it has.
https://bitbucket.org/hudson/magic-lantern/commits/d49971f8b452581e6ae111753d3cee9b90856450
It wasn't working so it shouldn't be an option. It would be nice if it was working, but with the current list of things todo, it's priority is very low.
Quote from: Grifter on August 26, 2013, 02:47:42 AM
Also perhaps i should know this but why is the iso/kelvin set controls going off every time i press rec?
Could you describe this better?
Sure , thanks Audionut.
With my other cameras when I have the shortcut controls set to iso/kelvin and press (picture style on the 5d2 ) and disp on the crop bodies) it comes on and stays on.
With the new 5d3 when I activate it with the rate button, it only stays on until I press record at which point it dissapears and needs to be activated again by pressing rate again.
its basically not staying up on screen after rec
BTW is there any version of ML (even without raw) that auto restart works on 5d3?
Actually i just realised there is a 30 min recording time limit compared to the 12 of old so no prob there.
Thanks to ML guys for all your work.
True catalysts.
I confirm, audio recording with RAW video does not work.
I tried "Preferred card" ON and OFF
"FPS override" always ON : 23.976
I also tied going back to August 6th (32338f9) & then July 22nd(00ea74a) but still does not work.
I remember that it worked before and wrote .wav files to the SD card.
It is not vital for me but would be handy.
wav only build in last June.