Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Here´s original vs 5 passes:Damn this is incredible Danne ! Thank u! Wonder how it look in the video
tif originals:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/tifcleaning.zip
Original
5 passes
So this is on the 6D running the latest crop_rec_4k build? We're getting off topic. I'll point to this from the 6D topic because it hasn't been reported on any other camera that I know of.No this is from the 10-12 bit build of Jan 13. I did not try the crop_rec_4k build yet. I hesitate on posting on the 6D topic or here seen that this is the build I'm using . And my apologies if I went off topic or made it confusing
Ok--got it.Alright I'll give it a try. Thanks again @dfort
I would recommend using the crop_rec_4k builds on the 6D. It has everything that is in the 10/12bit build and a whole lot more. The 6D has relatively recently started working with lossless compression so you might want to try that out too.
If, after a certain exposure level, the LiveView does not brighten any more, or if the brightening is applied in the processing pipeline after the raw data (happens at very long exposures), Auto ETTR may believe the image is underexposed and keep raising the exposure settings.Yeah I though of that but actually i'm not doing 10 second exposure i'm just setting the maximum slow shutter for the AETTR, and the prob is that when the image gets a bit dark instead of having slower shutter speed it's resetting the value I set it in the begging and it's raising the ISO. I also tried setting it to 6 sec as slowest shutter speed same thing.
Ok--got everything ready. I need someone to run a test on the 6D. First of all let's start with the current Nightly build.
The way to run the test is fairly simple. Turn on both the mlv_rec and mlv_snd modules and activate those modules. I prefer to reduce the frame to the smallest size because we're only checking for an audio issue. The first time you record an MLV clip the audio meters should work normally. What I'm interested in is what happens on the second through the forth clip. Make sure not to restart the camera between takes. Do the audio meters continue to operate normally?
Please report back then continue on with some test builds. Instead of repeating myself just follow the instructions on the following post only substituting 6D for 7D:
http://www.magiclantern.fm/forum/index.php?topic=9848.msg191123#msg191123
Thanks in advance!
[EDIT] I just realized that if you've been following this test closely you'll see that there is a slight difference between the 6D and 7D. The 6D actually uses StopASIFDMAADC to stop the audio but it is hacked so that SoundDevShutDownIn uses the address for StopASIFDMAADC. The 7D doesn't have that hack and uses SoundDevShutDownIn to stop the audio. That means that the "A" build for the 6D has SoundDevShutDownIn commented out while the 7D has StopASIFDMAADC commented out in the "A" build.
It might seem strange to fix something that is currently working albeit with an ugly hack. I'd like to get rid of that hack in order to make it easier to implement improvements like g3ggo's new sound system branch.
I'm not using the latest experimental build, so can't reproduce what you're saying.I was thinking the same but the exposure works well in normal mode it's just when u x5.
Are you in M mode on the mode dial ?
And I'm wondering, what does your display on top of your 6d say for shutter time ?
Could it be just a wrong number in the ML interface ? I'll always trust on the shutter time which is displayed on the top display of the Canon 6d.
@KeepersDungeonHello, thanks for you reply.
Quote from: keepersdungeon on August 26, 2017, 12:03:25 PM
I've downloaded the latest experiment version for the 6D (21august)
1-When u activate the FPSoverride the whole image becomes brighter and overexposed , and looks like shutter speed
doesn't affect it the only thing that worked was going to f8 or f16, didn't have that prob with previous version (Jul03)
**FPS settings: 24fps, fix, and the rest didn't touch it
In FPSoverride do You have "OptimizeFor" set to "LowLight" ~ If so switch to some other pram' & see it that helps ~
ORR ~ DeanB
I've downloaded the latest experiment version for the 6D (21august)So nobody is having the errors mentioned above? If I'm missing something would really like some help from you guys.
1-When u activate the FPSoverride the whole image becomes brighter and overexposed , and looks like shutter speed doesn't affect it the only thing that worked was going to f8 or f16, didn't have that prob with previous version (Jul03)
**FPS settings: 24fps, fix, and the rest didn't touch it
2-I'm also getting this error every time I start recording on an empty SD card (error was in both versions jul03 and august21)
"FAILED: "WBAL3: queued:7 failed: 1 (requeued)" and I only get it once it doesn't seem to affect the video though or WB, and have a feeling I only get it when there's nothing on the SD card and I hit Record
@ keepersdungeon, replied your message about the lagging video.
Using adtg_gui for crop mode recording is a pain in the ... you have to alter several settings/registers with adtg_gui and then it works, BUT as far as I know, you can't save these register/settings and therefore you would have to rechange them every time you turn on your camera.
For crop mode I use the 5x zoom, with magic lantern slow low resolution grayscale preview, for framing my shot. And for the recording I use the 10x zoom, which gives me nice high resolution live view, although not the correct framing( more zoomed in.
I'm downloaded the latest experiment version for the 6D (21august)
1-When u activate the FPSoverride the whole image becomes brighter and overexposed , and looks like shutter speed doesn't affect it the only thing that worked was going to f8 or f16, didn't have that prob with previous version (Jul03)
**FPS settings: 24fps, fix, and the rest didn't touch it
2-I'm also getting this error every time I start recording on an empty SD card (error was in both versions jul03 and august21)
"FAILED: "WBAL3: queued:7 failed: 1 (requeued)" and I only get it once it doesn't seem to affect the video though or WB, and have a feeling I only get it when there's nothing on the SD card and I hit Record
Hi, my 6D is updated to firmware 1.1.7. Before installing and using ML 2.3 I wanted to know if there are any issues and if someone has tried ML with this Firmware.This firmware is not supported yet u need to downgrade to 1.1.6.
I would not have any problems, I'm new to this.
Thanks Greg,
I can get 3xzoom/crop mode on 6d by overriding the following registers:
1080p 10xzoom 3xzoom(1:1 crop)
ADTG2-805f 2b0 13c No change needed
ADTG2-8061 2b0 13c No change needed
CMOS[6] 400 d0 d0 (=Changing the "d" moves horizontal position on the sensor)
CMOS[7] 0 208 206 (Lowering the 8 to 6 moves the white bar outside 16:9 view)
ADTG2-800c 2 0 0 (vertical lines to skip)
ADTG2-8000 6 5 5 (Don't know what it does, if it is 6 you get some vertical interlaced looking footage...)
With these settings I get 3xzoom/crop mode, correct preview in live view on the 6d
Raw recording works, gives correct framing.
I can even record canon "native" h.264 with it, and it works too!
Sorry Andy600 don't understand. I mean after I have applied color correction, any DNG or CDNG sequences that I output looks nothing like what I have done. I also experienced this in MLRawViewer.DNG and CDNG files are raw format. No color grading or filters will be applied. You can use it and then color grade in another software like resolve or any other
Also if you use MLVFS and mount the MLV's the DNG already look like they have had contrast and saturation applied to them.
If I output another type of file eg. ProRes the color correction that I apply are what was seen in the viewer.
What is your settings for H.264 export?I tried H.264 4:2:2 and also tried H.264 RGB and both did not open in resolve. was able to play them both in an external player but no in resolve.
It will, because ProRes is not a RAW format. It won't be applied if you do it in a RAW format (DNG / CDNG).Hmm Coz I tried same editing with H.264 4:2:2 and with ProRes 4:4:4 and the H264 was sharper that's why I asked
