Unfortunately, none of the CHDK developers (whoever they are) took-up your suggestion to discuss a 'basic' PTP feature.
That's not entirely true, but I guess the point is that there is nobody with the authority and responsibility to make "real" decisions. That's just the nature of this project.
Do we know what aspects of PTP cause problems and which features are reported as working on all cameras tested ?
I'm not aware of any actual PTP problems. For something like "my" minimal extension I'd say the only difficult issue is possibly the mode switching. I don't really have a good overview of the different methods in use and whether there's one that works for all cameras (or for all cameras one, for that matter).
There might be some additional issues for the CHDKCAM extensions, but from what I've seen I don't think there really are any.
I see that you propose leaving-out mode switching, I assume there is no problem working in record mode, even for file uploading ?
Well, I propose
moving mode switching from the PTP code to scripting. Again, I'm not aware of any problems, but that doesn't mean much.
We have discussed Lua support previously and in my opinion it attracts a 'certain type' of individual to CHDK.
The general public would not even be happy with uBasic, but at least some would.
With my proposal both could be supported and easily made compile-time conditional. I can't really see this as an issue.
On your Wiki, many people would not understand the comments about disabling services.
I just took that from this thread as I know nothing about it. Also, it's not mine, it's everybody's.
@mweerden: files seem to be loaded into RAM before written to disk.
This might cause problems for videos.
It's true that
ptpcam stores the file in memory first. You should see the tool as a proof of concept; I just took whatever seemed easiest to make work. The original code only provided a function to get all data at once, so that's what I used.
