Posts: 7
Threads: 2
Joined: Feb 2022
Posts: 7
Threads: 2
Joined: Feb 2022
I recently did a few timelapse shots with the ProTimer 3 (firmware 28) and my EOS R5. For the first approx. 100 shots of the 700+ Timelapse it dropped one or more frames very frequently, then became very stable after about 100 frames. Here are some the details and please let me know if you need more:
ProTimer 3, Curren firmware
Timelapse Mode, 10 second interval
Holy Grail sunset directly into the sun, temperature 0C to -3 or -4C or so.
The frame dropping occurred in the first part while the sun was still in the frame--as such during this time I did not have QDDB connected. The shutter speed was 1/5000s and the aperture was f/5.6. I was using a Samyang manual 14mm. I generally do not have problems shooting an 8 second frame with a 10 second interval, so I cannot understand why I have frames dropped with a 1/5000th of a second shutter speed and a 10 second interval.
The R5's back screen was folded closed--not in use.
This has me a bit stumped. Maybe it is a weird sleep issue with the R5? Maybe it is an issue with the Samyang? But interestingly enough, the 20 frames after it stabilized at 10s intervals, the shutter was still 1/5000s of second.
Also, about the time it stabilized, I connected the USB-C cable to my android device for QDDB and probably about 20 frames later, the shutter speed started dropping (I manually dropped the shutter speed to get the exposure correct after the sun went behind Mt. Fuji) and from there the auto-holy grail took over and the interval was consistently stable at 10s until the end of the shoot.
Now that I am working through it all--I perhaps have a theory...I wonder if it is possible that with the long time time between the fast shutter and the 10 second interval, the camera went to sleep and struggled to wake up, causing the missed frames--but then once the Android was paired via USB-C and connected to QDDB, that somehow prevented the camera from sleeping? Any thoughts, have you seen this before with this combination? I could not find any writes ups about it in the forum.
I checked two other Timelapse shots I have done recently where the sun was in the frame and I started QDDB after the sun had left the frame.
---In the first one earlier this month, I had a stable interval (10s) the whole time, but the shutter speed as 1/1600th (canon EF lens+adaptor). I am not sure if the phone was attached and on from the beginning of the shot or not with this one.
---The second was the day before the first shot described above (except I was using a canon EF lens+adaptor), same location, and same approach. The phone was not connected until later and as before the 2-3 frames (and as many as 5!) were dropped between actual photos until the phone was attached, then it was stable for the remainder of the shoot.
If it would help, I can provide screen shots of the LRTimelapse showing the shutter and interval, etc.
If this theory is right, can I have QDDB connected and just not start the LRTImelapse module until I after the sun is out of the frame? If I don't tell it do anything during that time? It should not have an affect at all, right?
However--if this theory is right, what do I do for non-holy grail shots? Any ideas? Has anyone else had this issue with the R5? How do I ensure that the interval remains stable without connecting a phone?
Thanks--and I look forward to any advice, suggestions, or known solutions.
Russ