Author Topic: Canon EOS M  (Read 926523 times)

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3800 on: December 06, 2019, 06:13:26 AM »
@Danne , any chance of adding 0.25 and 0.5 options for the movie mode intervalometer ? Or maybe 0.20 0.40 0.60 0.80 would be better if achievable. My favourite for fps override is 2.5 fps for certain subjects. So the 0.40 should achieve that.
How do you mean? If you want 0.5 you enable fps override and then add intervalometer? Or what do you mean?
Besides that. If you you run frameburst mode and then average let's say 49 images you'll get the long exposure look but without the laggy screen.

IDA_ML

  • Hero Member
  • *****
  • Posts: 731
Re: Canon EOS M
« Reply #3801 on: December 06, 2019, 07:21:25 AM »
I think it will be playing with the intervals depending on the subjects/scene you are shooting to reach a happy place. I'm confident this could be the way forward (rather than using silent modes or overexposed fps override).
My favourite for fps override is 2.5 fps for certain subjects. So the 0.40 should achieve that.

If you want smooth cinematic timelapse videos, setting long enough frame to frame intervals is not enough.  You also need long exposure times.  If, for example, you choose 2.5 fps for a certain scene, you need 0,4 s shutter speed to get this smooth motion blur of the moving objects in the scene and this is what causes the overexposure in day light.  You need a variable ND filter to compensate for that.  Unfortunately, there is no way around it, no matter what method you use.  If you use, say 1/30 s, your smoothness is gone.  In my experience, fairly cheap no name VND filters do a decent job with timelapses.

About half a year ago, Danne brought timelapse shooting functionality on the 100D to perfection.  4k and 5k resolutions in combination with the correct fps rates and reciprocal slow shutter speeds, as well as a nice fast preview for focusing upon half shutter press make timelapse shooting really fast, easy and a lot of fun.  I have been enjoying it tremendously last summer - one more reason for me to keep my 100D.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3802 on: December 06, 2019, 07:29:40 AM »
About half a year ago, Danne brought timelapse shooting functionality on the 100D to perfection.  4k and 5k resolutions in combination with the correct fps rates and reciprocal slow shutter speeds, as well as a nice fast preview for focusing upon half shutter press make timelapse shooting really fast, easy and a lot of fun.  I have been enjoying it tremendously last summer - one more reason for me to keep my 100D.
Please reread my last message about averaging files for long exposure results.

bakersdozen

  • Freshman
  • **
  • Posts: 86
Re: Canon EOS M
« Reply #3803 on: December 06, 2019, 08:13:14 AM »
How do you mean? If you want 0.5 you enable fps override and then add intervalometer? Or what do you mean?
Besides that. If you you run frameburst mode and then average let's say 49 images you'll get the long exposure look but without the laggy screen.

I meant a lower minimum interval than 1 second on the intervalometer could be selected. ie. If 0.20 was a choice, we would get 2.5 frames in a second just by using intervalometer.
EOS M + 5D3

bakersdozen

  • Freshman
  • **
  • Posts: 86
Re: Canon EOS M
« Reply #3804 on: December 06, 2019, 08:20:01 AM »
If you want smooth cinematic timelapse videos, setting long enough frame to frame intervals is not enough.  You also need long exposure times.  If, for example, you choose 2.5 fps for a certain scene, you need 0,4 s shutter speed to get this smooth motion blur of the moving objects in the scene and this is what causes the overexposure in day light.  You need a variable ND filter to compensate for that.  Unfortunately, there is no way around it, no matter what method you use.  If you use, say 1/30 s, your smoothness is gone.  In my experience, fairly cheap no name VND filters do a decent job with timelapses.

About half a year ago, Danne brought timelapse shooting functionality on the 100D to perfection.  4k and 5k resolutions in combination with the correct fps rates and reciprocal slow shutter speeds, as well as a nice fast preview for focusing upon half shutter press make timelapse shooting really fast, easy and a lot of fun.  I have been enjoying it tremendously last summer - one more reason for me to keep my 100D.
Thanks mate. Yes I've got heaps of variable nd's for this exact purpose :) I was really just trying to push this a little further to try out a different method of timelapses using intervalometer only. If it's not possible, that's cool, just wanted to try and see what resulted.
EOS M + 5D3

LeandroFreitas

  • New to the forum
  • *
  • Posts: 6
Re: Canon EOS M
« Reply #3805 on: December 06, 2019, 08:52:49 AM »
I got great news! I got continuous recording with (2.5K) 2520x1054 Ratio 2.39:1 14bit with SanDisk Extreme PRO 128gb 170Mb i got 57.9MB/s as top speed with Kill Global Draw . Very good card i got on Blackfriday.
I notice there is a bug for 2.5k that if you set  to 24 exact fps it show like its not using correct the sensor its black on the right.
Iam running Danne version crop_rec_4k_mlv_snd_raw_only_2019Dec05.EOSM202.zip
I running this setup with Viltrox EF-M speedbooster with Sigma art 18-35 F1.8 that gives me F 1.2 doenst give you vignette.





Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3806 on: December 06, 2019, 09:00:16 AM »
Your images are too big. Lower resolution to around 700-900 pixels
EDIT: lowered, thanks

Where´s the black? Could you upload a sample. Will take a look later.

LeandroFreitas

  • New to the forum
  • *
  • Posts: 6
Re: Canon EOS M
« Reply #3807 on: December 06, 2019, 06:55:04 PM »
Your images are too big. Lower resolution to around 700-900 pixels
EDIT: lowered, thanks

Where´s the black? Could you upload a sample. Will take a look later.


Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3808 on: December 06, 2019, 07:07:32 PM »
Sample mlv file.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3809 on: December 07, 2019, 02:23:48 PM »
New version:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

- intervalometer
- recording delay


Refined my lua script but still a work in progress. Mission is to be able to fully control a few functions such as being able to program the camera to independently delay start, specify recording time, stopping and looping the programmed set up. Thanks to dmilligan examples from uploaded test scripts here http://davidmilligan.github.io/ml-lua/index.html I could start my experiments.

Usage:
1 - Load movie tlapse & rec_delay from Scripts section
2 - Choose intervalometer or recording delay from Movie tab section

Functions:
rec delay - start recording with a delay
recording time - stop recording after specified amount of time
loop this - loop this setup x many times, need recording time enabled

Of course one can still keep it simple and i.e set interval time and run halfshutter trigger and skip the rest of the settings. Treat them as advanced mode. Feedback and testing welcome.









Lua script in full here:
Code: [Select]
-- movie tlapse & rec_delay

--[[
Dedicated movie preset intervalometer
--]]

  console.hide()
  menu.close()

if camera.model_short ~= "EOSM" then
   display.notify_box("Only eosm for now")
   do return end
end

  displaybox = 0
  interval = 0
  delay_value1 = 0
  stop_value1 = 0
  delay_value2 = 0
  stop_value2 = 0
  stop_after = 0
  loop_this = 0

-- loop this function
function restart()
  main()
end

function restart2()
  main2()
end

function main()
  console.hide()
  menu.close()
  interval =  mymenu.submenu["interval"].value + 1
  delay_value1 = mymenu.submenu["rec delay"].value + 1
  stop_value1 = mymenu.submenu["recording time"].value

-- warning
if camera.mode ~= MODE.MOVIE then
  display.notify_box("enable MOVIE mode")
  do return end 
end

-- if rec delay set
 if delay_value1 > 1 then
  display.notify_box("push display to disable rec delay")
  msleep(1000)
  display.notify_box("push display to disable rec delay")
  msleep(1000)
 end

-- rec delay set?
    while delay_value1 > 1 do
      if menu.visible then
      do return end
      end
      delay_value1 = delay_value1 - 1
      display.notify_box("recording delay "..delay_value1)
      msleep(1000)
    end

  menu.set("raw video", "Rec trigger", "Half-shutter: pre only")
  msleep(1000)
  menu.set("raw video", "Pre-record", "1 frame")
  menu.set("presets", "frame burst", "OFF")
  menu.set("presets", "iso average", "OFF")
  display.notify_box("push rec to disable")
  msleep(1000)
  display.notify_box("push rec to disable")
  msleep(1000)
  key.press(KEY.REC)
  msleep(1000)

-- starting the timelapse loop
 while interval > 0 do

      interval = interval - 1
      msleep(1000)

   -- share displaybox with stop function 
     if displaybox < 8 then
      display.notify_box("interval "..interval)
   -- check if stop function is enabled
      if stop_value1 > 0 then displaybox = displaybox + 1 end
     end

      if interval == 0 then
   -- reload interval
      interval =  mymenu.submenu["interval"].value + 1
      key.press(KEY.HALFSHUTTER)
      key.press(KEY.UNPRESS_HALFSHUTTER)
      end

   -- to be able and stop while running
      if menu.visible then
do return end
      end

      if movie.recording == false then
      menu.set("raw video", "Rec trigger", "OFF")
       if mymenu.submenu["loop this"].value < 1 then
do return end
       end
      end

-- stop function
   if stop_value1 > 0 then
      stop_value1 = stop_value1 - 1

   -- share displaybox with interval function
     if displaybox > 7 then
      display.notify_box("recording time "..stop_value1)
      displaybox = displaybox + 1
      if displaybox == 16 then
      displaybox = 0
      end
     end

      if stop_value1 == 0  and mymenu.submenu["recording time"].value > 0 then
      msleep(1000)
      displaybox = 0
      key.press(KEY.REC)
      msleep(1000)
      menu.set("raw video", "Rec trigger", "OFF")
        if mymenu.submenu["loop this"].value > 0 then
        mymenu.submenu["loop this"].value = mymenu.submenu["loop this"].value - 1
        restart()
        else
        do return end
end
      end
   end
 end

end

function main2()
  console.hide()
  menu.close()
  interval =  mymenu.submenu["interval"].value + 1
  delay_value1 = mymenu.submenu["rec delay"].value + 1
  stop_value1 = mymenu.submenu["recording time"].value

-- warning
if camera.mode ~= MODE.MOVIE then
  display.notify_box("enable MOVIE mode")
  do return end 
end

-- if rec delay set
 if delay_value1 > 1 then
  display.notify_box("push display to disable rec delay")
  msleep(1000)
  display.notify_box("push display to disable rec delay")
  msleep(1000)
 end

-- rec delay set?
    while delay_value1 > 1 do
      if menu.visible then
      do return end
      end
      delay_value1 = delay_value1 - 1
      display.notify_box("recording delay "..delay_value1)
      msleep(1000)
    end

  display.notify_box("push display to disable")
  msleep(1000)
  display.notify_box("push display to disable")
  msleep(1000)
-- starting the timelapse loop
 if interval > 0 then
    key.press(KEY.REC)
    msleep(1000)
 end

  while interval > 0 do
      interval = interval - 1
      msleep(1000)

   -- share displaybox with stop function 
     if displaybox < 8 then
      display.notify_box("interval "..interval)
   -- check if stop function is enabled
      if stop_value1 > 0 then displaybox = displaybox + 1 end
     end


      if interval == 0 then
   -- reload interval
      interval =  mymenu.submenu["interval"].value + 1
      key.press(KEY.REC)
      end

   -- to be able and stop while running
      if menu.visible then
do return end
      end

-- stop function
   if stop_value1 > 0 then
      stop_value1 = stop_value1 - 1

   -- share displaybox with interval function
     if displaybox > 7 then
      display.notify_box("recording time "..stop_value1)
      displaybox = displaybox + 1
      if displaybox == 16 then
      displaybox = 0
      end
     end
   end

-- enter and exit loop
      if stop_value1 == 0 and mymenu.submenu["recording time"].value > 0 then
      msleep(1000)
      displaybox = 0
        if mymenu.submenu["loop this"].value > 0 then
        mymenu.submenu["loop this"].value = mymenu.submenu["loop this"].value - 1
        restart2()
        else
        do return end
end
      end

  end
end

mymenu = menu.new
{
    parent = "Movie",
    name = "intervalometer",
    help = "Movie preset intervalometer",
    submenu =
    {
        {
            name = "interval",
            min = 0,
            max = 600,
    value = 10,
            unit = UNIT.TIME,
            update = function(this) mymenu.value = this.value end,
    help = "default is 10 seconds",
        },
        {
            name = "run halfshutter trigger",
    select = function(this) task.create(main) end,
    help = "records single frames in a MLV chunk. enables REC trigger mode",
        },
        {
            name = "run rec key trigger",
    select = function(this) task.create(main2) end,
    help = "use with frame burst or iso average",
        },
        {
            name = "rec delay",
            min = 0,
            max = 10000,
            unit = UNIT.TIME,
            update = function(recd) recd.value = recd.value end,
    help = "start recording with a delay",
        },
        {
            name = "recording time",
            min = 0,
            max = 10000,
            unit = UNIT.TIME,
    help = "stop recording after specified amount of time",
        },
        {
            name = "loop this",
            min = 0,
            max = 10000,
            unit = UNIT.DEC,
    help = "loop this setup x many times, need recording time enabled",
        },

    },

}


-- starts movie recording after a delay

function recdelay_main()
  console.hide()
  menu.close()
  delay_value1 = recdelay_menu.submenu["rec delay"].value
  stop_value1 = recdelay_menu.submenu["recording time"].value
  delay_value2 = recdelay_menu.submenu["rec delay"].value
  stop_value2 = recdelay_menu.submenu["recording time"].value
  loop_this = recdelay_menu.submenu["loop this"].value - 1

-- rec delay needs to be specified
if delay_value1 == 0 then
  display.notify_box("set rec delay")
  msleep(1000)
  display.notify_box("set rec delay")
  msleep(1000)
  display.notify_box("set rec delay")
  msleep(1000)
do return end
end

-- rec delay set?
    while delay_value1 > 0 do
      msleep(1000)
      if menu.visible then
      do return end
      end
      delay_value1 = delay_value1 - 1
      display.notify_box("recording delay "..delay_value1)
    end
   key.press(KEY.REC)
      msleep(1000)

    while stop_value1 > 0 do
      msleep(1000)
      if movie.recording == false then
      do return end
      end
      stop_value1 = stop_value1 - 1
      display.notify_box("recording time "..stop_value1)

      if stop_value1 == 0 then
      key.press(KEY.REC)
      msleep(1000)
      end
    end

-- check for loop this
 while loop_this > 0 and stop_value2 > 0 do

-- rec delay set?
    while delay_value2 > 0 do
      msleep(1000)
      if menu.visible then
      do return end
      end
      delay_value2 = delay_value2 - 1
      display.notify_box("recording delay "..delay_value2)
    end
   key.press(KEY.REC)
      msleep(1000)

    while stop_value2 > 0 do
      msleep(1000)
      if movie.recording == false then
      do return end
      end
      stop_value2 = stop_value2 - 1
      display.notify_box("recording time "..stop_value2)

      if stop_value2 == 0 then
      key.press(KEY.REC)
      msleep(1000)
      end
    end

-- reset for next loop
   delay_value2 = recdelay_menu.submenu["rec delay"].value
   stop_value2 = recdelay_menu.submenu["recording time"].value

-- check for loop this
  loop_this = loop_this - 1
  display.notify_box("loops left "..loop_this)
  msleep(500)
 end

end

recdelay_menu = menu.new
{
    parent = "Movie",
    name = "recording delay",
    help = "start movie recording after a delay",
    submenu =
    {
        {
            name = "rec delay",
            min = 0,
            max = 10000,
            unit = UNIT.TIME,
            update = function(recd) recd.value = recd.value end,
    help = "start recording with a delay",
        },
        {
            name = "recording time",
            min = 0,
            max = 10000,
            unit = UNIT.TIME,
    help = "stop recording after specified amount of time",
        },
        {
            name = "loop this",
            min = 0,
            max = 10000,
            unit = UNIT.DEC,
    help = "loop this setup x many times, need recording time enabled",
        },
        {
            name = "Run",
            select = function(this) task.create(recdelay_main) end,
            help = "start the delay count down now",
        },
    },
}


Intervalometer easy mode:
1 - activate tlapse lua script then enter intervalometer. Set your preferred interval(default is 10)
2 - select run halfshutter trigger. A one chunk mlv file will be created containing x amount of dng frames
Done!

Averaging idea:
If you want to create a sequence of frames separated into individual mlv file instead select run rec key trigger. But see to it that you select a setting from either frame burst or iso average first. This will produce mlv files suitable for averaging in Mlv App.

I recently added two personal presets in the intervalometer script called rec delay + 3 frames and rec delay + 2 frames. Just skip those.

Advanced stuff:
rec delay - simply will delay the start of the selected set up. You can set it to start like after an hour or more if you like.
recording time - a global setting which will tell how long you want your set up to run. You can set it to run your script for 2 hours or so. If not set your script set up will be active until your battery drains.
loop this - If you created a workflow that you know works and included recording time you can here restart the exact set up x amount of times by selecting loop this. For instance. You want the camera to start recording with a rec delay of one hour nad you want the recording time to run for 2 hours and then end. If loop this is set it restarts the procedure, 1 hour delay, two hours recording time etc...






procopy

  • New to the forum
  • *
  • Posts: 6
  • Spaceships Porn Director
Re: Canon EOS M
« Reply #3810 on: December 07, 2019, 03:31:13 PM »
Hi, gents. What are your touch focus settings and generally what is your experience with it? I had quite a decent experience with the previous build I was using, but can't really say the same about the latest nightly build. What I'm looking for is just be able to switch focal point without the servo interfering all the time as I move and it seems it just does not work this way anymore. Yes, there is rack focus, but that unnecessarily complicates things for me. Or did the rack focus replace touch focus in newer builds? Or am I doing something wrong?

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3811 on: December 08, 2019, 07:20:10 PM »
Testing results:

using the Dec 07 build, firstly I've checked the new feature - intervalometer for video
I tested only the mv1080p rew interval script / video mode
this works with the preset aspect ratio 2.39:1
Ratio set to 16:9 - cam crasches sometime, have to pull battery
Ratio to off - doesn`t work, meaning maybe it does record once, but then the interval isn't over (10sec) and the recording starts and dont stop


I also have a problem with the mv1080p rew in 3x zoom - the top part of the LV is corrupted which also shows up in the recording, this is since some builds back the case
Also since some time, the GD LV item indicating remaining capacity of sd card doesn't update anymore. It updates only after powering cam off and on

As always, thanks to Danne and others for developing ML further




Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3812 on: December 08, 2019, 07:44:19 PM »
Can´t reproduce. x3zoom is working as before here.
Intervalometer is very specific with certain additions depending what you setting you choose. You describe very vaguely so hard to say what´s going on.
I would need a sample mlv in x3zoom to understand better since a ton of info is missing if you want me to reproduce.
Thanks 

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3813 on: December 08, 2019, 08:44:27 PM »
Can´t reproduce. x3zoom is working as before here.
Intervalometer is very specific with certain additions depending what you setting you choose. You describe very vaguely so hard to say what´s going on.
I would need a sample mlv in x3zoom to understand better since a ton of info is missing if you want me to reproduce.
Thanks
3x zoom , Ratio off - here one sample file (only a week from now available)
I have this issue since nov 16th. then I noticed it the first time
https://we.tl/t-Oc5xgYbBAb
Intervalometer : withthe fresh build installed, mv1080p, 14bit, 2.39:1 - nothing changed - Works for the testing (4 x repeat of 4 second clips)
changing the RAtio to off it breaks, changing from there to 16:9 its still broken, cam can lock up
I hope this helps Danne

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3814 on: December 08, 2019, 08:57:43 PM »
In your provided clip it says 25fps. Are you using fps override? Use set 25fps instead from Movie menu. Even if your camera is set to 25fps in canon menu. I also recommend to have camera set to 24 fps in canon menu as starting point.

About your issues with intervalometer. I really need to see full settings in your camera. Maybe you can do a screen recording? I still don´t know which function you tested in the tlapse script so I still am far from being able to reproduce.

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3815 on: December 08, 2019, 09:51:04 PM »
So, yes, I have switched to PAL in canon menu, and there to 1920x1080@25 pfs
No FPS override

I've switched now (still pal) to 1920x1080@24fps, restarted the cam and Yes! no problems.

so the 3x issue seems solved:
1.-in CANON menu choose (maybe either PAL or NTSC) 1920x1080@24FPS and restart


intervalometer script:
I've used the fresh build install and Just changed in movie (ML) menu Ratio to Off
then started the script (run) and changed the setting from the movie-intervalometer menu to
4 secs record time, repeat 4 times

Testing the intervalometer once more after this abovementioned settings change to 24FPS video in Canon menu
firstly I reseted the ML settings and restarted the cam, then changed the ratio to off and pressed Menu Button three times, nothing else changed
Then did run script  and still in ML menu -> movie tab -> intervalometer I've changed
1. recording time to 4s
2. loop this to 4
3. run rec key trigger

 yes now it records, the cam starts recording right away, the countdown (from 10) counting and again recordings stops after 5-6 secs, starts again, stops and this is all

So thanks Danne to clarify the setting to 24FPS

But the intervalometer doesn't work as expected, if I let the Ratio setting at OFF.

Edit: if I run the intervalometer the recording starts right away, the LV display shows the countdown, but recording still running. then it stops, then starts again, then stops, then start and has to be manually stoped. in between the counter counts down, then a message is shown - push display to disable, it records two clips (have set it to loop 4x), then stops, sometimes recording doesn't stop






Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3816 on: December 08, 2019, 10:15:45 PM »
Run it without looping etc. Will it work with 10s interval. Please test more and I would really like a screen recording if possible.

Oh. You run rec key trigger. I hope you follow the advice in help text or else it won't work.

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3817 on: December 08, 2019, 10:58:00 PM »
did take a while, have only a bad screen recording, sorry for that.
I did reset the ML settings before starting screen recording

Looking in mlvapp on the clips - the first 5 are all round about 135 frames, the sixt is 500 frames, have to stop it. as You can maybe see on this screenrecording, I have set duration to one second and loop to 10. it did record more than one second, and only 5 clips out of 10, the sixt one would run until card full or battery drained.

so then now it works better then before (before the 24fps setting in canon menu previously)
but its not working for 10 clips, which would be necessary for timelapse
the counter (10-0) is counting on it self somehow, regardless if cam isn't recording, which I would expect, or if the cam is recording, which doesn't make sense

link
https://we.tl/t-kTuNgaHVdZ

edit
now testing the "recording delay" function with "run"



Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3818 on: December 08, 2019, 11:13:42 PM »
You are doing it wrong. Tve firat setting runs one frane at the time. The rec trigger needs additional settings enabled. Read help text.

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3819 on: December 08, 2019, 11:14:13 PM »
recording delay preset

did choose :
delay 5
recording 1
loop 10

this did work much better, it recorded 10 clips with 35-37 frames each
very nice!

I really don'T understand why there are two scripts. maybe I choosed the wrong one? maybe the intervalometer is for silent picture or burst, bracketing, sorry if I did missed this.

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3820 on: December 08, 2019, 11:41:14 PM »
recording delay function is to record separate x clips of x seconds each with a delay between them, is this right?
intervalometer function
used only with the new frameburst and iso average? (movie-preset-submenu)

Thanks





 

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3821 on: December 09, 2019, 09:49:32 AM »
Not easy to find time to build scripts and also explain all functions but I will try here.

Intervalometer easy mode:
1 - activate tlapse lua script then enter intervalometer. Set your preferred interval(default is 10)
2 - select run halfshutter trigger. A one chunk mlv file will be created containing x amount of dng frames
Done!

Averaging idea:
If you want to create a sequence of frames separated into individual mlv file instead select run rec key trigger. But see to it that you select a setting from either frame burst or iso average first. This will produce mlv files suitable for averaging in Mlv App.

I recently added two personal presets in the intervalometer script called rec delay + 3 frames and rec delay + 2 frames. Just skip those.

Advanced stuff:
rec delay - simply will delay the start of the selected set up. You can set it to start like after an hour or more if you like.
recording time - a global setting which will tell how long you want your set up to run. You can set it to run your script for 2 hours or so. If not set your script set up will be active until your battery drains.
loop this - If you created a workflow that you know works and included recording time you can here restart the exact set up x amount of times by selecting loop this. For instance. You want the camera to start recording with a rec delay of one hour nad you want the recording time to run for 2 hours and then end. If loop this is set it restarts the procedure, 1 hour delay, two hours recording time etc...




AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #3822 on: December 09, 2019, 01:51:16 PM »
Thanks Danne for the little explanation. Got it.
Will do more testing.
What is the explanation of the "recording delay" function? (intervalometer function and recording delay function)

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6262
Re: Canon EOS M
« Reply #3823 on: December 09, 2019, 01:59:22 PM »
It should be selfexplanatory by now. What is it you don't understand about it? Help text says it all I think.

2blackbar

  • Senior
  • ****
  • Posts: 307
Re: Canon EOS M
« Reply #3824 on: December 12, 2019, 03:20:14 AM »
Danne is it possible to bring back old 10 bit mode from june builds , there was one menu with 10bit nd 12 bit that is current one, and there was other one that had  something like 8-11 bit ,  10 bit and 12 bits which had better 10 biut mode without color loss/bading in darkest areas , in current 10 bit mode highest resolutions im getting a bit of green, heres example:

There was no banding in 10 bit mode from july builds , i recorded mostly 10 bits back then and i had banding only in 8 bits.
Thhats like the main reason i stay away from current 10 bit mode.
---
Strangely i tested now and 10 bit looks kinda ok, Ill retest in daylight like original video this image is from cause i dont see it, maybe it was fixed somehow in recent builds when i didnt used 10 bits...