Messages

1

crop_rec and derived builds / Re: Levas' crop_rec_4k experiments for 6D

« on: August 06, 2020, 10:55:31 PM »

There will still be skipping lines, but the mode is the same as normal 1824x1026 raw recording. (3x3 (horizontal binning, vertical lineskipping, no stretching needed)
For absolutely no lineskipping and pixelbinning, you should try the 48fps preset that is in the 1:1 pixel readout crop preset.
There is a preset in there 1840x908 @ 48 fps (no need to switch camera to 720p mode) only caveat, crop factor is about 3x.
So your 35 mm lens will become about 100 mm 

I'm working at a new structure for high fps modes.
The same like I did for 1:1 and 3:1 readout presets.
I want to have all fast fps under one preset, with resolution and fps options in a submenu.
This way I could easily add more fast fps presets, like 48/50/60 fps options and also max resolution in 40fps etc.

But isn't the 720p mode much nicer to begin with in terms of moire and aliasing? Could this preset be tuned to 24/25 fps in theory, or is that too low to be stable?

Awesome work on the new presets by the way!

2

crop_rec and derived builds / Re: Levas' crop_rec_4k experiments for 6D

« on: June 24, 2020, 12:50:33 PM »

Hey! First of all, thank you Levas for keeping the 6D alive and kicking - good stuff still happening here!

I just wanted to post something here that perhaps others have asked themselves and I couldn't quite find a definite answer on the forum so I just tested it:

With the current Version of ML for the 6D you can use the HDMI out (while recording raw) and connect to a monitor and have perfect liveview on a bigger monitor. It works with overlays for both the "normal" 1080p lossless mode and also for the 50fps setting. Didn't test the crop_rec settings yet, but I figured that probably not too many people know that this works absolutely fine for "normal" recording situations. To me, that makes a world of a difference in terms of real world usability. So there you go. ML is awesome.

Cheers,
David

3

crop_rec and derived builds / Re: Levas' crop_rec_4k experiments for 6D

« on: January 09, 2020, 03:41:18 PM »

Right - as stated above, no binning mode was a bit of a missleading statement. I specifically meant bilals further advancements on the 700d like getting it to work with 10 bit lossless compression and having liveview (albeit stretched). In a similar vein, I was asking about 24p modes because hey, a frame less is a frame less on the cards buffer. Also, there's no way to switch it if you are on a 24p timeline. By the way, are the crop_rec modes on all camera models with greyscale framing/preview only still? I havent quite kept up with the developements in the last half year or so and there are so many topics and threads to read through by now that I don't no what the state of crop_rec is, so to speak. What's awesome by the way is the 50p mode - easily the most useable "new" preset for everyday filmmaking.

4

crop_rec and derived builds / Re: Levas' crop_rec_4k experiments for 6D

« on: January 06, 2020, 09:55:03 PM »

Yes - No binning modes was probably the wrong wording. No resolutions bigger than 1824pixels in 1x1 liveview mode to be precise (at least I think this hasn't been achieved yet...^^). It doesn't matter anyway, the advancements have been great this year, plenty of options to go out and make something beautiful, I wasn't trying to sound dismissive.

5

crop_rec and derived builds / Re: Levas' crop_rec_4k experiments for 6D

« on: January 06, 2020, 02:01:07 PM »

Hey! A while back I reported that I am having issues with the crop_rec module as well. I noticed something very interesting. When my lens (the APSC Sigma 30mm 1.4 Art - works great on a 6D by the way) was switched to AF when I powered the camera, half shutter press would not show me a framing preview, it would start focusing. However, once I switch it to manual and then BACK to AF, it shows a preview as it should with a half shutter press - even in AF mode. Incidentally, once I did this, 1x3 binning modes became available to me, when they would show a "raw detect error" or similar before. Strange stuff, especially the second part. Nevertheless, now everything works. Is there a way to include 24fps modes in this whole build or do I just need to switch to NTSC for that anyway? Great build, shame that the pixel binning modes (anti - aliasing modes really  )  that bilal got working for the 700D havent made it to the 6D. We have slow mo and we have extended resolutions, but 1080p without aliasing and without crop would be killer. Hopefully this is helpful to one person or another. Thanks again Levas and all the other fine devs .

6

Camera-specific Development / Re: Canon 6D

« on: August 31, 2019, 01:02:44 PM »

No, sadly this doesn't change anything - no matter which bitdepth, PAL or NTSC mode in canon menu, 24 or 25p in Canon menu, or other settings I select seem to make a difference - I always get an onscreen "data corruption" message and the LOG file posted above! Let me know if you have an idea how to test for specific things if you have any ideas. Am I really the only 6D user this happens to (because to me that always suggests that a user error is still the most likely scenario here^^)

7

Camera-specific Development / Re: Canon 6D

« on: August 29, 2019, 02:32:06 PM »

Hey there! I did a few tests with the new presets, but I get a "compression error" every time I try to record a clip in any other than the 50p mode (that one works just fine, oddly enough) I'll attach the error messages I get. Is this a known user error (i.e. Am I doing anything wrong?).

Code: [Select]

ML ASSERT:
0
at mlv_lite.c:2753 (compress_task), task compress_task
lv:1 mode:0

compress_task stack: 1e3338 [1e33c8-1e23c8]
0x0044C9B0 @ c23bfc:1e3368
0x0044C478 @ 44ca0c:1e3338

Magic Lantern version : Nightly.2019May19.6D116
Mercurial changeset   : 6c6f37e9adfc+ (crop_rec_4k_mlv_snd_isogain_1x3_presets) tip
Built on 2019-05-19 13:23:44 UTC by magic_lantern@Vasses-iMac.
Free Memory  : 378K + 2241K


8

Camera-specific Development / Re: Canon 70D

« on: March 09, 2019, 10:56:57 AM »

Excellent! Let's give this a try:

Code: [Select]

    else if (is_camera("70D", "1.1.2"))
    {
        CMOS_WRITE = 0x26B54;
        MEM_CMOS_WRITE = 0xE92D41F0;
       
        ADTG_WRITE = 0x2684C;
        MEM_ADTG_WRITE = 0xE92D47F0;

Put up a test build on my downloads page. The way to test this is to first turn on only the crop_rec module. Put your camera in 1280x720/50 or 60 (depending if you're set up for PAL or NTSC) and try recording some H.264 video. The LiveView will probably look stretched vertically.

We know that mlv_lite isn't working yet because we need to figure out the lossless recording but maybe mlv_rec will work? You should be able to record video using 3x3 sampling at 60fps. Well, the card will limit how large of an image you can continuously record at that speed but it does give you another option to play with.

@Danne Yes - I believe this build, along with the register changes I described in post 3194 results in a proper crop_rec file. It ONLY works however when it's on the PAL setting, as I also described, 60fps is just too much. I am going through my notes, sorry I can only point to past achievments but it's been almost a year since I played with that stuff.

VERY important note: I could also lower the fps from 50 to around 21fps with this build, but I needed to change TWO, not one register:

c0f0 6014
c0f0 6024

Unfortuntaley I never got behind a way to increase the resolution past the 1824x626 I started with, because I could not manage to find the right registers to change resolution. I remember the cam was very sensitive to the order/way in which the registers were changed - fps changes were stable but every time I tried something else it kept locking up.

Here is what @nikfreak had to say about all this

Hey Dave,

fps override was always problematic for me. TimerA always worked to modify but Timer b was causing problems and disco-like effects on the LCD. Now that you found out that 70D needs two registers for Timer B namely

• c0f06014
• c0f06024

you need to update fps-engio.c to get it working. Just out of my head:

#define FPS_REGISTER_A 0xC0F06008
#define FPS_REGISTER_B 0xC0F06014
#define FPS_REGISTER_B_DUALPIXEL 0xC0F06024

Afterwards "grep" fps-engio.c for all register_b related code and modify it to work for 70D by defining code for it. I would suggest you make a request at bitbucket if you can't handle it yourself but you need that additional register 0xC0F06024 for 70D from what I understand

As always, hope this is helpful.

9

Camera-specific Development / Re: Canon 70D

« on: March 08, 2019, 09:16:58 PM »

Hello fellow 70D users! Just thought since the last breakthrough that @ArcziPL made with lossless recording, it might be the right time to pick up on pixel binning patterns and higher frame rates on the 70D again. Post 3194 and 3206 explain my register changes to achieve 50fps footage in 3x3 binning that doesnt need post production stretching, from a custom build @dfort provided me with. I am just bringing this up so maybe someone with more intimate knowledge of 70D specific registers and the crop_rec branch can take the lead from there and make something useful out of it. Awesome find on the lossless comp!

10

General Chat / Re: Canon EVF-DC2 on DSLRs?

« on: September 24, 2018, 08:07:26 PM »

Right. Thanks for clarifying, at least now when somebody uses the search bar in the future they'll find a definite answer

11

General Chat / Canon EVF-DC2 on DSLRs?

« on: September 24, 2018, 06:18:08 PM »

Hey everyone!

I was wondering if there is a definite verdict on hot shoe communication? Is the hot shoe from the EOS M series different from the DSLR models so that it can be used with the EVF-DC viewfinders or is it just the communication protocol that is different? If so, is there a theoretical possibility to send the Live View image to the hot shoe and a EVF or is that definitely not possible? Just asking out of curiosity because I couldn't seem to find a discussion on this particular topic with the search function. I'm guessing its not possible or else ML wizards would have jumped on it already .


I played with a Manual Lens and focus peaking today and every time I do I notice that the eye pressed against the viewfinder as point of contact as well as shooting with the camera away from the body really bums me out. Which is why I looked at  EVF style solutions for DSLRs, but they are all super bulky and not the "real deal" somehow.

Regards,
Davd

12

Scripting Corner / Re: Lua Scripting (lua.mo)

« on: September 20, 2018, 11:36:06 PM »

Here's the log for 70D! Looks pretty similar to what was posted before...

Code: [Select]

ML/SCRIPTS/API_TEST.LUA - 2018-9-20 22:41:54
===============================================================================

Strict mode tests...
Strict mode tests passed.

Generic tests...
arg = table:
  [0] = "API_TEST.LUA"
camera = table:
  shutter = table:
    raw = 115
    apex = 7.375
    ms = 6
    value = 0.006024
  aperture = table:
    raw = 21
    apex = 1.625
    value = 1.7
    min = table:
      raw = 21
      apex = 1.625
      value = 1.7
    max = table:
      raw = 72
      apex = 8.
      value = 16
  iso = table:
    raw = 80
    apex = 6.
    value = 200
  ec = table:
    raw = 0
    value = 0
  flash = true
  flash_ec = table:
    raw = 0
    value = 0
  kelvin = 2500
  mode = 3
  metering_mode = 3
  drive_mode = 0
  model = "Canon EOS 70D"
  model_short = "70D"
  firmware = "1.1.2"
  temperature = 155
  gui = table:
    menu = false
    play = false
    play_photo = false
    play_movie = false
    qr = false
    idle = true
  shoot = function: 0xc0a3a4
  bulb = function: 0xc0a5d8
  wait = function: 0xc092d0
  burst = function: 0xc0a658
  reboot = function: 0xc0a378
event = table:
  pre_shoot = nil
  post_shoot = nil
  shoot_task = nil
  seconds_clock = nil
  keypress = nil
  custom_picture_taking = nil
  intervalometer = nil
  config_save = nil
console = table:
  hide = function: 0xc07c54
  show = function: 0xc07c64
  clear = function: 0xc07c44
  write = function: 0xc07cf8
lv = table:
  enabled = false
  paused = false
  running = false
  zoom = 1
  overlays = false
  stop = function: 0xc0a7f0
  info = function: 0xc0ab84
  pause = function: 0xc0ae88
  start = function: 0xc0a7e0
  wait = function: 0xc0b248
  resume = function: 0xc0ae78
lens = table:
  name = "18-35mm"
  focal_length = 23
  focus_distance = 540
  hyperfocal = 16423
  dof_near = 525
  dof_far = 555
  af = true
  af_mode = 0
  focus = function: 0xc0bef4
  autofocus = function: 0xc0bd2c
display = table:
  idle = nil
  height = 480
  width = 720
  line = function: 0xc0d70c
  clear = function: 0xc0c68c
  pixel = function: 0xc0d9d4
  print = function: 0xc0dba0
  off = function: 0xc0c770
  notify_box = function: 0xc0c834
  load = function: 0xc0ca64
  rect = function: 0xc0d3a8
  draw = function: 0xc0c91c
  circle = function: 0xc0d0d8
  on = function: 0xc0c780
  screenshot = function: 0xc0c69c
key = table:
  last = 10
  wait = function: 0xc0e0b0
  press = function: 0xc0e378
menu = table:
  visible = false
  get = function: 0xc0fb44
  open = function: 0xc0e6f0
  new = function: 0xc107a0
  block = function: 0xc0e8e0
  set = function: 0xc0f964
  select = function: 0xc0f890
  close = function: 0xc0e6d8
movie = table:
  recording = false
  stop = function: 0xc0c2f4
  start = function: 0xc0c388
dryos = table:
  clock = 49
  ms_clock = 49459
  image_prefix = "IMG_"
  config_dir = table:
    exists = true
    create = function: 0xc11a94
    children = function: 0xc1194c
    files = function: 0xc11830
    parent = table:
      exists = true
      create = function: 0xc11a94
      children = function: 0xc1194c
      files = function: 0xc11830
      parent = table:
        exists = true
        create = function: 0xc11a94
        children = function: 0xc1194c
        files = function: 0xc11830
        parent = nil
        path = "B:/"
      path = "ML/"
    path = "ML/SETTINGS/"
  ml_card = table:
    drive_letter = "B"
    dcim_dir = table:
      exists = true
      create = function: 0xc11a94
      children = function: 0xc1194c
      files = function: 0xc11830
      parent = table:
        exists = true
        create = function: 0xc11a94
        children = function: 0xc1194c
        files = function: 0xc11830
        parent = table:
          exists = true
          create = function: 0xc11a94
          children = function: 0xc1194c
          files = function: 0xc11830
          parent = nil
          path = "B:/"
        path = "B:/DCIM/"
      path = "B:/DCIM/100CANON/"
    file_number = 6459
    folder_number = 100
    free_space = 30385
    image_path = function: 0xc11c70
    type = "SD"
    path = "B:/"
    _card_ptr = userdata
  shooting_card = table:
    drive_letter = "B"
    dcim_dir = table:
      exists = true
      create = function: 0xc11a94
      children = function: 0xc1194c
      files = function: 0xc11830
      parent = table:
        exists = true
        create = function: 0xc11a94
        children = function: 0xc1194c
        files = function: 0xc11830
        parent = table:
          exists = true
          create = function: 0xc11a94
          children = function: 0xc1194c
          files = function: 0xc11830
          parent = nil
          path = "B:/"
        path = "B:/DCIM/"
      path = "B:/DCIM/100CANON/"
    file_number = 6459
    folder_number = 100
    free_space = 30385
    image_path = function: 0xc11c70
    type = "SD"
    path = "B:/"
    _card_ptr = userdata
  cf_card = nil
  sd_card = table:
    drive_letter = "B"
    dcim_dir = table:
      exists = true
      create = function: 0xc11a94
      children = function: 0xc1194c
      files = function: 0xc11830
      parent = table:
        exists = true
        create = function: 0xc11a94
        children = function: 0xc1194c
        files = function: 0xc11830
        parent = table:
          exists = true
          create = function: 0xc11a94
          children = function: 0xc1194c
          files = function: 0xc11830
          parent = nil
          path = "B:/"
        path = "B:/DCIM/"
      path = "B:/DCIM/100CANON/"
    file_number = 6459
    folder_number = 100
    free_space = 30385
    image_path = function: 0xc11c70
    type = "SD"
    path = "B:/"
    _card_ptr = userdata
  date = table:
    isdst = false
    hour = 22
    month = 9
    year = 2018
    min = 41
    wday = 5
    yday = 263
    day = 20
    sec = 54
  call = function: 0xc1104c
  rename = function: 0xc11250
  directory = function: 0xc11390
  remove = function: 0xc11324
interval = table:
  time = 10
  count = 0
  running = false
  stop = function: 0xc126b0
battery = table:
  level = 99
  id = 0
  performance = 3
  time = nil
  drain_rate = 33
task = table:
  create = function: 0xc12e98
  yield = function: 0xc12d18
property = table:
Generic tests completed.

Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
SD card (B:/) present
- free space: 30385 MiB
- next image: B:/DCIM/100CANON/IMG_6460.JPG
- DCIM dir. : B:/DCIM/100CANON/
File I/O tests completed.

Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Canon GUI tests completed.

Testing ML menu API...

ML/SCRIPTS/API_TEST.LUA:390: assertion failed!
stack traceback:
[C]: in function 'assert'
ML/SCRIPTS/API_TEST.LUA:390: in function 'test_menu'
ML/SCRIPTS/API_TEST.LUA:1476: in function <ML/SCRIPTS/API_TEST.LUA:1467>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1467: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1506: in main chunk

13

General Chat / Re: Begging for assistance with what camera to get

« on: September 20, 2018, 11:18:33 PM »

Another 70D user chiming in. I got 50fps in mv720 mode at 1824x626 working, but not a coder at all so I cant really implement this in a build - but there is progress!

I am saying this because the 70D has one feature NO OTHER CAM THAT RUNS ML HAS. Dual Pixel Auto-Focus. And despite it not being a "professional" feature, you can pull off pretty neat "Steadicam" Shots on a cheap glidecam etc. for which you would otherwise need an expensive follow focus system.

BUT. Especially for the pricerange you are looking for, the 700D is a great choice. Most amazing ML video features at the moment and its got that flippy screen you kinda need for videography . As dfort mentioned, 100D and EosM are perhaps the other serious contenders.

14

Camera-specific Development / Re: Canon 70D

« on: September 13, 2018, 11:13:05 PM »

Yes! Programming the delay differently did the trick !

Now everything worked as expected! Aaand once again, here are the DNGs haha.

https://we.tl/t-9hLb7ZFFOO

With the crop_rec experiment, I am once again not able to find the right reigsters to mess with vertical resolution. Should I in theory be able to expand the vertical resolution in the "normal" 720 mode or is this only possible in 5xZoom and with raising timer B? Is it possible that 636x 1824 is the maximum I can achieve, like on the 6d?

15

Camera-specific Development / Re: Canon 70D

« on: September 13, 2018, 08:11:04 PM »

Here's a short video of the process. As you can see, triggering silent zoom bracket takes 1 picture in 1080p mode for me and 2 in 720p mode, none of them in zoom mode. As always I happily invite everyone to point out my stupidity if I'm simply not getting it!

https://we.tl/t-qunk4YGu3R

16

Camera-specific Development / Re: Canon 70D

« on: September 13, 2018, 04:47:19 PM »

Yes, I figured that much, but still - somehow the module doesnt take 2 different pictures. If it makes any difference here are the 1080p, 720p and 720 3x3 again. In 1080p it only took 1 picture, but at leastbecause of the timer I didnt touch the cam when Photo was taken. In the 720p modes the module took 2 pictures each but not with a zoom^^. in this case it is always the second picture I am providing because I thought it couldn't hurt^^. are the 5x required for the kind of work you want to do?
https://we.tl/t-lNZHfc0xN1

17

Camera-specific Development / Re: Canon 70D

« on: September 13, 2018, 12:47:26 PM »

Somehow the silent zoom bracketing doesnt quite do what it's supposed to. When I don't turn on MLV_REC it takes the 1080p but not the 5x zoom picture and when I DO turn on MLV_REC it takes the 5xzoom but not the regular one. It never takes both  ?

18

Camera-specific Development / Re: Canon 70D

« on: September 11, 2018, 07:58:02 PM »

No, not with the 3x3 mode. I can retake the others with silent zoom bracketing tomorrow if that makes a diffenrence!

19

Camera-specific Development / Re: Canon 70D

« on: September 11, 2018, 07:37:59 PM »

I hope I did this test  thoroughly enough to do some real pixel peeping, what's apparent either way (at least for me) is 2 things. First, 3x3 binning or whatever this crop_rec magic module does produces insanely less moire than regular 720p mode which is all over the place. But secondly, sadly, it seems I have an offset in the framing in this mode, it's shifted to the top. Here's the DNGs!

https://we.tl/t-ZOLCNmhmPV

20

Camera-specific Development / Re: Canon 70D

« on: September 11, 2018, 11:24:01 AM »

Yes! Will do in the evening when I have time to print/set up. I am curious to see the results myself, from my experience (had a 600D before) I'd say that moire really is a little worse, even in regular 1080p mode.

For now, I can also report that I fixed the ghosting in fps override! turns out i forgot to override the line skipping factor before...  . Anyway, here's a frame from 3x3 in 720p mode at 21fps. Sorry for the weird aspect ratio, forgot to change it in ML menu, the frame is not stretched just 1824x466 ^^. This mode (fps override enabled) requires different changes than if I leave timer B untouched.

21

Camera-specific Development / Re: Canon 70D

« on: September 11, 2018, 11:01:54 AM »

I'll let others eveluate if this is really what I hope it is but I think I had a minor breakthrough! Sometimes the simplest solutions are the best. I thought, well if 60fps is causing too much lag and 25fps works fine, maybe 50fps is low enough in order for things to work properly. So I switched to PAL video mode in canon menu and redid my original changes (without messing with timer A and B) AND IT WORKED!

The vertical resolution is limited to 626 pixels at the moment (I think was to be expected without the timer changes, right?) BUT, the files are not strechted and there is (stretched) real time preview and recording! For me personally (and everyone else with a 70D) this means that slow-mo recording has become at least moire free and the resolution is good enough in 2.35:1 to be incorporated into a 1080p project (in my opinion) !

Here's a frame!

22

Camera-specific Development / Re: Canon 70D

« on: September 11, 2018, 12:37:30 AM »

The new atdg_gui works nicely, thanks!

With every new possibility it seems there are some new mysteries to be uncovered. The positive first: It seems indeed that my "stuttering" problems in crop mode were related to fps issues. Because, I was able to change fps to roughly 25fps and now I have an (almost) perfect 3x3 crop_rec mlv file!. There is minor ghisting going on but the preview and file are stutter free. However, and here the mysteries begin:

I could not see/find a C0F0 [6008], but a C0F0 [6014] and [6024] which had the same value. I needed to change BOTH of them in order for the image not to freeze. In this manner, I was able to lower the fps in the crop_rec module AND in regular 1080p, but I could only lower fps, not increase.

Needless to say, changing fps also messed up the way I originally changed the CMOS registers to get normal frames in crop_rec. Now all I had to do was change CMOS (b) from 800 -->300 and leave CMOS [a] alone.

There are some minor ghosting effects in this MLV, otherwise it is fine.

As always, hope this somehow helps more than it complicates matters 



Here's a frame that shows the defect.

23

Camera-specific Development / Re: Canon 70D

« on: September 10, 2018, 08:32:59 PM »

Ok, no I can definitely not see the Timer A and B registers. I think part of the problem may be that the adtg_gui build I have is a custom build that @dfort provided me with back in March. Now I have the problem that crop_rec_4k doesn't compile for me

Code: [Select]

#error FIXME: please define FRAME_SHUTTER_BLANKING_READ
and the branch that does compile (crop_rec_4k_mlv_snd) doesn't allow me to make adtg_gui.mo. I am also not able to use the adtg_gui.mo from the download page with this build. Am I right in assuming that this is because the 70D isn't really fully integrated into one of the main branches? Either way, pretty much stuck with regard to the crop_rec  720p 60fps experiment .

24

Camera-specific Development / Re: Canon 70D

« on: September 09, 2018, 12:30:06 PM »

Also, could somebody point me in a direction with regard to the 720p 60fps 3x3 experiment? dfort advised me to lower the fps, but as far as I know, fps overrider doesn't work on the 70D. So I guess I'd have to manually mess with timer A and B, right? Are the timer registers known on the 70D? Because I cant seem to find C0F0[6000] or [6008], which are the registers for other cams if I'm not mistaken?

Should this measure fix the lagging/temporarily freezing recording and preview?
Seems like I'm not too far off but since I know so little about image processing in general I can't really gauge if I'm close or if there are other substantial parts missing in order for this to work.

25

Camera-specific Development / Re: Canon 70D

« on: September 09, 2018, 10:17:12 AM »

Here's the test results! Pretty ähm.. interesting  .

But almost like you expected, right?
https://we.tl/t-BykEItcY9C