Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
Hi everyone I'm new to posting.

On my T4i/650d with your crop_rec_4k latest build I get the shutter issue and ISOless LV err(2)

While having the shutter issue, these were the photos of my ADTG registers:

ADTG2[805f] N -> 4049fa18


ADTG2[8061] N -> 4049fa1c
32
New builds are posted in the first post for 650D/700D

Changes:

crop_rec:
-Fixed a regression with "720p50 3x3" preset, now it works fine.
33
Yes, there is a little problem with it: I stopped using it because the real-time preview is transmitted distorted, flattened. (pixel binning 1x3)

You asked for time-lapses, "Crop mode V2" is the perfect module for that, for preview you must use "Framing" preview from "RAW video" submenu.

Which resolution are you looking for to do time-lapses?

As far as I know, EOS M has 4080x3000 preset for time-lapses with real-time cropped preview (x5 preview), this preview would be valid for focusing but not for framing, in "Crop mode V2" x10 preview isn't patched you can use it for focusing before recording, then get back to x1 or x5 mode with "Framing" preview and start recording your time-lapse, I tried it and it works fine . .

Are you looking for something else maybe I am missing? please describe it with details or give me a link showing it so I can improve my future builds . .


Thanks for the pictures, weird, the addresses from your camera is exactly what we are using in our 650D custom builds (Me and Danne), the two builds had issue with shutter value in ML settings on your 650D.

Not sure why the stuck shutter problem is only presented on your 650D, doesn't make sense . . I will try to see if I can do something about it.

Edit: Do you have the shutter problem both in none-crop and crop modes? e.g. unload all modules, restart the camera, select 1080p24 from Canon menu, do you have shutter issue? now get into x5 mode by pressing zoom button, do you have shutter problem in this mode?

Use FPS override to 12 FPS in both 1080p and x5 mode, same problem?
34
Raw Video / Re: AI algorithms for debinning
« Last post by mlrocks on July 24, 2021, 10:02:20 PM »
For the 650D, I did a quick test, with 4.5k 1x3, 10-bit color depth, 14-bit lossless compression, AR 2.67, 24 fps, the data rate calculated by ML was about 36 MB/s for a complex scene. So 5.2k 1x3, 10-bit color depth, 14-bit lossless compression, AR 2.67, 24 fps, seems continuous on 650D with SD card overclocking at 240 hz if such a preset is implemented. 5.2k 1x3 anamorphic will use the full APS-C/super 35mm sensor width, so there will be a lot of benefits. The resolution of this 5.2k 1x3 may be close or even indistinguishable to native 4k 1x1.
35
Raw Video / Re: AI algorithms for debinning
« Last post by mlrocks on July 24, 2021, 09:59:32 PM »
I just did a quick test on my 5D3, with card spanning on and sd card overclocking off. The following modes are continuous for 1 minutes on a relative complex scene, then I manually turned off the recording. The data flow calculated by ML was about 110 MB/s for both modes for the scene. So overheating can be avoided totally.

1. 10 bit color depth, 14-bit lossless compression, 5.7k 1x3 anamorphic raw, AR 2.67, 24 p
2. 10 bit color depth, 14-bit lossless compression, centered 3.5k 1x1 raw, AR 2.67, 24 p

The centered 3.5K is good for specific reasons, because this mode has a super 35mm/APS-C image circle, so EF-S lenses and lenses designed for super 35mm can be used in this mode, like Sigma 18-35 f1.8 and Canon 10-18mm F5.6 IS. 3.5k on super 35mm is actually the most optimized resolution, more than this number other side effects may show up. Arri Alexa Classic uses a 3.4k super 35mm sensor, the latest Arri LF uses two of the same sensor, and the Arri 65 uses three of the same sensor. It seems that Arri considers 3.4k is the resolution limit for a super 35mm sensor size. And 5D3 has a 3.5k super 35mm sensor within.
36
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 "adtg_gui.mo" 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
37
General Development / Re: Canon Basic scripting (DIGIC 8, DIGIC X models)
« Last post by names_are_hard on July 24, 2021, 03:25:10 PM »
Don't know why I had it in my brain as hours, seconds does make a lot more sense!  Basically, for the RP, we don't really know what these numbers mean.  There are some fields where we can make some obvious guesses, and likely be right, but that's about it.

Don't recall which precise field it is for 200D, point being, it was negative so I don't put it past them to apply a negative offset to one of the other fields (plus code for some existing cams already applies a fix for this, I've seen it somewhere).
38
General Development / Re: Canon Basic scripting (DIGIC 8, DIGIC X models)
« Last post by j1080 on July 24, 2021, 01:44:08 PM »
So there might be something weird going on with the TotalShutter integer type of the RP's firmware versions.

@names_are_hard Wasnt expecting that, just mentioned as i didnt belive that its brandnew and been wondering about those numbers.
                            TotalRunningTime is reported in seconds, tested that, but still 13+ hours.

@kitor The box itself wasnt sealed, but all the items inside. The body itself had a packaging with some kind of aluminium-sticker on it.
           I dont belive its new, even if sold as.



39
General Development / Re: Canon Basic scripting (DIGIC 8, DIGIC X models)
« Last post by kitor on July 24, 2021, 09:49:56 AM »
Quote
Since the CameraInfo part is already available in the Powershot firmware

This was a good point anyway. I was unaware of that coming to us from Powershot world (like Basic did).

Quote
reported a negative TotalShoot when I first had it!
Are you sure TotalShoot and not shutter_count_plus_lv_actuations? We have three* different counters, not two!:

On "old" cameras (up to D7, PROP_SHUTTER_COUNTER):
buf[0] -> shutter_count = number of still shots with physical shutter actuations
buf[1] -> shutter_count_plus_lv_actuations = number of physical shutter actuations, including enter/exit LV which does open/close shutter

on "new" cameras (D8+)
PROP_MECHA_COUNTER (TotalShutter) -> equivalent of shutter_count*
PROP_RELEASE_COUNTER (TotalShoot)  -> above + number of silent pictures (with no physical shutter actuations)

I believe you write about shutter_count or shutter_count_plus_lv_actuations, not TotalShoot.


*We still need to confirm that on D8 DSLR, as either:
- PROP_MECHA_COUNTER is equivalent of shutter_count_plus_lv_actuations and not shutter_count (would make sense by prop name)
- there's additional prop that is equivalent of one "missing" on D8, which is missing just on mirrorless
40
General Development / Re: Canon Basic scripting (DIGIC 8, DIGIC X models)
« Last post by c_joerg on July 24, 2021, 08:36:40 AM »
Okay, but your comments about different cams, in a Digic 8 and X thread were confusing and don't seem relevant.

Sorry for the confusion.
Since the CameraInfo part is already available in the Powershot firmware, I assumed that this part also ended up in the firmware of the R and was only expanded.
Pages: 1 2 3 [4] 5 6 ... 10