Hi,
I'm not sure if this was already mentioned somewhere, but I'm using one of the latest nightly build (not sure which one, not near my camera at the moment) and tried shooting a timelapse using the fps override set to 0.5 and optimizing for 'Exact FPS'.
Everything operates like it should but when I start recording I cannot stop it. The only 'safe' way is to open the SD card door and wait a while, there is a 'busy' notification in the corner but eventually it does safe the movie and I can again operate the camera normally once shutdown and I start it again by closing the card door.
The weird thing is that this doesn't happen in other override modes. I've reset to ML defaults, only changing the FPS override settings.
I've looked at the commits and I'm wondering if it is directly related to any FPS override implementation since the most recent changes don't seem to be related to 600d. If anybody has any ideas on how to use/test it, I'm open for it.
I'm not sure if this was already mentioned somewhere, but I'm using one of the latest nightly build (not sure which one, not near my camera at the moment) and tried shooting a timelapse using the fps override set to 0.5 and optimizing for 'Exact FPS'.
Everything operates like it should but when I start recording I cannot stop it. The only 'safe' way is to open the SD card door and wait a while, there is a 'busy' notification in the corner but eventually it does safe the movie and I can again operate the camera normally once shutdown and I start it again by closing the card door.
The weird thing is that this doesn't happen in other override modes. I've reset to ML defaults, only changing the FPS override settings.
I've looked at the commits and I'm wondering if it is directly related to any FPS override implementation since the most recent changes don't seem to be related to 600d. If anybody has any ideas on how to use/test it, I'm open for it.