Similar to the post of 8-6-11 ("Restart video recording when time limit is reached (FAT32 4gb) automatically"), what about the possibility of making long videos greater than the 4gb/60min. limit automatically continuing into subsequent video files without stopping so there is a seamless (or as close as possible) transition from one video file to the next when imported sequentially into a video editing program?
1. The 60 minute limit seems to be set in firmware, and can be overcome - at least for some cameras: http://chdk.setepontos.com/index.php?topic=6711.15
2. None of the scripts I've seen so far for simulating indefinite video recording length address the 4GB limit directly; they instead record video for a predetermined amount of time, then stop recording for a short amount of time, and then start recording again (possibly on a loop)
3. I dislike two things about these scripts: (A) that they use elapsed time rather than current video file size as the basis for determining when to begin a new video file, and (B) that they stop and restart, instead of just switching seamlessly from appending video data to one file, to appending it to the next file.
4. In order to be able to record indefinitely long videos up to the capacity of the memory card, not only would the duration limit need to be set in firmware to the maximum possible (see point 1, above), but points A and B, above, would also need to be addressed, so that when the current video file's size nears the filesystem's limit, the video data is diverted into a new file.
5. Although I've used CHDK a few times on my IXUS 80IS (SD1100), I've never written a script for it, and I don't yet know if there are functions available to CHDK scripts that would allow A and B to be addressed.I'm looking forward to hearing what more experienced CHDK folks have to say about this
By all means, please feel free to fix this on other cameras.Seems like that's better than nothing. Again, feel free to code and submit a better script.A full refund of everything you have paid for these scripts is available from their authors. Please post your improved version.When you work this out, please post so we can all do this.Me too. Oh wait ...
Quote from: sampablokuper on 23 / March / 2012, 22:43:513. I dislike two things about these scripts: (A) that they use elapsed time rather than current video file size as the basis for determining when to begin a new video file, and (B) that they stop and restart, instead of just switching seamlessly from appending video data to one file, to appending it to the next file.The reason it is done this way is that the alternatives would require much deeper reverse engineering of the canon firmware. It certainly could not be done with a script. It might be theoretically possible, but it would take a lot experimentation and digging in the firmware disassembly.
Holy sarcasm, waterwingz! :-p
Seriously: I was just trying to pull my research into one place (to save time for others who might be looking for the same information), draw some reasonable conclusions, and suggest avenues to be pursued. In other words, I was trying to be helpful! Perhaps I should have phrased things differently, but I certainly didn't intend to express any ingratitude.
- I could go it alone. This could fail completely, because not only am I right at the bottom of the relevant learning curve, I also can't justify committing an indefinite amount of time to a project: I'd have to give myself a budget of a certain number of hours, and if I didn't succeed within that time, I'd have to stop; so this approach is a gamble.
- I could leave it up to others. This might be faster, because an experienced dev could probably iterate towards a working solution (or, alternatively, a conclusive proof that A and B aren't solvable) much more quickly than a newbie, but it might also be slower, because perhaps no experienced devs would decide to give it a go; so this approach is also a gamble.
- We could collaborate. This seems to me to be the best option; and, indeed, to be the whole point of having forums. A more experienced CHDK coder could give me pointers (i.e. mentor me). If the more experienced coder knows from the start that solving A and B is physically impossible, then (s)he could say so and this would be constructive since it would avoid time being wasted. Alternatively, if the more experienced coder knows which approaches might be most likely to solve A and B then (s)he could say so, and I'd try them out and report back, which would speed me on my way much faster than if I were having to work it all out for myself. So this approach is much less of a gamble.
- We could collaborate. This seems to me to be the best option; and, indeed, to be the whole point of having forums. A more experienced CHDK coder could give me pointers (i.e. mentor me)
Since I'm clearly not the only person interested in having this functionality
Started by Graystar
General Discussion and Assistance
Started by Johng
General Help and Assistance on using CHDK stable releases
Started by PhyrePhoX
General Discussion and Assistance
Started by fudgey
Started by Wolfox
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)