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.

Messages - Icaab

Pages: 1 [2] 3
No, the attached build is a different version from what you have tested before. So, again, do a clean install with this build (format SD card on PC then install the build):

Report back, then let's chat.

Yes, already several times overloaded the camera and ISOless LV ERR(2)no longer. WONDERFUL! Thank you!
Also tested the included "Dual ISO" with "RAW video" and yes - they conflict with each other.

Hi Icaab, I didn't mention that I fixed "ISOless LV err(2)" on 650D.

Well, if you are asking for a fix, try this build and report back please:
If you attached the firmware that was posted on May 25, I installed it. Problems with Dual ISO can only be solved this way:
Turn on P mode on camera
Camera turns off
Battery removed and inserted back
Video mode starts
Switches to manual mode (M) and everything works until the camera restarts

You can tell me how to take photos with the following combination of modules:
Dual ISO + Intervalometer + Silent Picture(Burst MLV) + Raw Video + Crop rec v1 or v2(Full-Res 1:1)

When I turn on "Raw Video", my camera hangs during the photographing, and with "Raw Video (MLV)" everything works, but in MLVApp is not recognized Dual ISO.


Hello. Installed new firmware on 650d. Dual iso "ISOless LV err(2)" error periodically appears.

Is there a method in the program to remove the flickering on a substandard light source?


The footage looks good, you aren't using Dual ISO correctly, procced files will always have the low ISO exposure (then in Post you can raise exposure and you will have clean shadows).

Why your footage looks dark? because it's underexposed in first place, and in your case (the MLV file you shared) you don't need to use Dual ISO (your scene is flat, no much required dynamic range), there is no reason to start with 100 ISO in this case, you can start with 400 or 800 ISO and you probably won't have blown highlights.

Simple way to use Dual ISO correctly: You probably want to use Dual ISO only in contrasty scenes when you have bright highlights and dark shadows, expose your shot correctly (e.g expose for highlights), let's say you used 100 ISO as base, now turn on Dual ISO and set second ISO to 800 to get clean shadows recovery in post.

For example, take a look in these photos:
Okay. I realized my mistake.
I’m sorry, but can you drop the link to some instruction that describes how to shoot a timelapse with a dual ISO and a silent picture? (intervalometer doesn't work with these modules)

Also for a silent picture : I choose ful-res and shutter speed on frames always 1/4, whichever I choose. Am I to understand that this can only be fixed with an nd-filter?

And if I get a dng photo, how do I remove vertical stripes in mlvapp?

I've just finished testing with the isoless build, everything works perfectly,
Dual Iso + Crop rec (1x3 uhd) + Raw v1: great for video
Dual Iso + Crop rec V2 (1:1 5000x3500) + Silent pics (burst) + Raw MLV: great for pics

It's amazing what you did with a entry level camera,

5K, 10bit, 2:35, 23,976 Continuous raw with dual iso, it's amazing, Thank you
Hello. How did you manage to take a photo with a crop that appears when you turn on the module Crop rec V2? (my camera 650d)


For 700D you have two different builds, one of them might work for you, from the first post:
Have you tried both? does the two build have the shutter issue on your 700D?

Mind share a short MLV sample (maximum of 5 seconds) which has the problem? You can cut the affected MLV file in MLVApp, export it as MLV "Fast pass".

Okay, I’ve got a raw source attached

By the way, is there any way to remove the stripes that appear when dual Iso is enabled?
Focus harder
1636369645574" border="0

And here’s a picture where I have 100 ISO without dual iso

1636369645559" border="0

Hello. Installed the latest version of the firmware on 650d. Decided to use a Dual ISO. Original ISO 100, Recovery 1600.
I open in mlvapp. Normal exposure. When I start correcting, the video is so dark, it’s like I only shot 100.
Where can I go wrong?
Screenshot-1149" border="0

Hello. I haven’t been following the branch update recently and I have a question: will the 650d support the Viltrox monitor DC-90HD 4k ? Will everything be qualitatively displayed with firmware magic lantern on this monitor?

I suggest to download MLVApp 1.13 again, extract it in new empty folder, import your MLV clips and try exporting, does it work (do you have your exported clips)?

If not, what's your export settings? do you have a CMD running while exporting?
I apologize: it turns out in my path the folder with the program contained a cyrillic. After the renaming everything worked as if nothing had happened.
Thank you :)

My bet: you deleted ffmpeg from MLVApp path. Otherwise more information needed.
I did not close anything at the time of export and ffmpeg is present.

Took again mlvapp v13 and replaced the following files: ffmpeg , libraw.dll , MLVApp , pixel_maps , raw2mlv .
To no avail.

Hello. I came across a bug: No file appears when you export in any format. Export successfully ( Inscription - Export is ready), but I can’t find the output file (latest version mlvapp).

Hi @NykkyC, thanks for the values, try this build:

Does the shutter issue solved?

Does this build works on your 650D without the shutter issue?

I tried your first tips. Shutter speed with some modules does not work, as I noticed when they were turned off. (looks like most of it)

Installed your new firmware. Without modules included, everything works, and how it turned them on is the same problem.

But there is a way around it: go into photo mode. Shutter speed is displayed correctly.

The red stripe: comes from the camera preset. E.g. you can crop it in post.
I used your receipt with all your settings, nothing else.
I exported a single frame as JPG. The processing engine (for processed output of all codecs) is always the same.
I still see no problem and/or understand the problem.
I understand. Thank you for your help. Perhaps the codec is a problem when exporting. I’ll try others.

No problem with the receipt, I can load it, but here all looks clean. Thanks for the MLV. Here I get this with the MLV and your receipt:

Is it the same you get? Do you find your "distortion" here too?
I can’t say for sure right now, because you can see it better on video. However, in the photo only I see a red stripe at the bottom, which somehow appears at the bottom of the frame if the white surface, and comparing it to a previously attached photograph of the last renderer - problems have disappeared that have troubled me.
I don’t know where I could be wrong. I didn’t see that distortion in the playback.
Did you apply the same corrections I applied?
Can you send your receipt too?
What kind of debayer do you use to view the video?
Export settings are the same as mine?
(I used then h265 12bit,but now think it is better to use prores to speed up the renderer)

You mean the bright pixels in the edges? Must have to do something with your MLV (which you did not upload?!), because with your receipt I can't reproduce on any of my clips.

The original video mlv weighs a lot. I kept his piece in the same format, without applying any corrections:
Strange: I can open .marxml settings through the import receipt . Then let me attach this screen:

@Icaab: What kind of distortion do you mean? Could you please give a hint? I just see some shaking, probably because you hit the record button.
Yes, the box must move XD
On the corners of the video there are distortions in colors, and on the image of the camera(on the box) and the box there are large pixels.
(You can download the video to your computer using the mega link. This will show you better)
Before that, with minimal processing of the original video - this was not the case, and after adding sharpness and small changes (and rendering in full resolution that was received on the cameras, that is, in 4.3k) - discovered such oddities.



I also attached processing parameters (.marxml). Can you look?

Hello. I noticed a strange distortion in the received video after exporting in the format h265 12 bit.

(For visual purposes, see the video)
I haven’t read the details of the latest program updates, and I may be making mistakes somewhere.
Attach the original video, preset the renderer settings and properties:


Hi @Icaab

You can already do time-lapses with crop_new (Crop mode V2) which works greatly, do you have any issue with it?

Let's fix the shutter issue on your camera, assuming you have my crop_rec_4k build on your SD card:

1- Download adtg_gui module from here
2- Put it in ML/modules folder in SD card
3- Load "" from "Modules" tab in ML settings, restart the camera
4- From "Debug" tab in ML settings, turn ON "ADTG Registers"
5- Highlight "ADTG Registers" then Press Q button

Now you should see bunch of ADTG2[XXXX] registers, you need to find two registers which are:

1-ADTG2[805F] N
2-ADTG2[8061] N

Highlight the first register and give me these numbers in the yellow box (write them down, or take a picture with your smartphone)

Do the same thing for the second register, and give me the numbers

Yes, there is a little problem with it: I stopped using it because the real-time preview is transmitted distorted, flattened. (pixel binning 1x3)

Posting photos of registers:
1627151288002" border="0
1627151288010" border="0

Bilal, hey.
Tell me: Is there such a opportunity that in the future in the firmware 650d/700d it will be possible to shoot timelapse with video so that all settings are flexibly adjusted ( shutter speed, for example) as on EOS M?

Hello. I have a problem: if you try to record a video with a microphone (boya by-m1) connected, the recording of the sound is disabled during the recording. Without a microphone, the sound is recorded and included in the raw settings.
(It’s probably not a firmware problem, but I don’t have any way to test it with another device right now. That’s why I’m interested, just in case.)

The problem was easily resolved. You can delete this unnecessary message :).

Welcome :)

Yeah, I disabled the ability to use autofocus when crop_rec "Crop mode" is ON due to stability reasons, which modes you want to use autofocus with?

Autofocus might be stable only with 1440p 1:1 and 3K 1:1 modes, so I may re-enable autofocus with these modes.

Okay, we need to check your camera shutter registers addresses, I will write another post regarding this and how to it.

Picture style doesn't affect RAW data, only H.264 video and LiveView

Shooting a monitor is a nightmare for cameras, popular solution is to make the monitor out of focus (using camera lens) a bit, but in your case there are many subjects in the frame, so you probably need to change monitor position, or use a wider aperture . .

1:1 modes (have higher crop) might help to reduce aliasing/moire on monitor . . I have no idea if optical low pass filter can deal with monitor aliasing/moire . .
Thank you.
I’m going to do a different composition, and I’m going to use focus advice to shoot the monitor.

And one more question:
In my artistic design, it is necessary to shoot in the scene a computer monitor turned on.
When you look at the footage, you see a little aliasing on the monitor.
(I shoot and in 1x3 and procedure in MLVApp, as is required, so that in other cases the muar and aliasing do not manifest)
Can do anything other than buy optical low pass filter?

Hello. I have a question: I understand perfectly well how to use the modules for shooting in Crop mode and RAW, but again, I would like to clarify the profile for the camera:
When shooting with such modules - the profiles do not work and we get the image in RAW as you see when the standard style is turned on ,but there is a certain sharpness there.
I take it I have to put it down at the very least, so the video can be even better for post-production? Or does it not make any sense and in RAW format still comes a certain sharpness?

I have the ISOless PH err(2) error with Dual ISO on my 650d, but it seems there is the solution
Thank you for your decision. I hope they will correct this error in the new update.

Pages: 1 [2] 3