Hence commercial scientific cameras cannot be used.
This seems quite incredible. Maybe you mean that the cost is more than you want to pay, or the engineering to integrate them is more difficult that you would like ?
It is a microimager, something like MAHLI on MSL, but much more sophisticated.
A lofty goal.
As an aside, have you verified you can operate the sx110 without the lens hardware ? If so, this is definitely something other members of the forum would be interested in. If not, then you might want to do that before you invest too much time in other stuff.
Because I have a publication pending, that is all I can say in a forum. If we chat privately, I can tell you more.
You can PM me on the forum if you like. I have no specific need to know about it, but if I find the project interesting I might be more willing to spend time supporting it.
I did the scaling in the center panel to test a simple hypothesis and demonstrate the results to you (and to me too). The final objective would be for the liveview to provide a crisp image, not to take CHDKPTP out.
I understand that. My suggestion was to take the scaling done by CHDKPTP out of the equation, so you can see if that is responsible for the image quality difference.
It is strange that Canon chose this archaic TV format.
Technically, I guess we should say YCbCr rather than YUV. It's very common in all sorts of digital video and imaging.
Nonetheless, could something in your routines related to the conversion have an impact on image quality, and give clarity a little boost?
Sure, it's possible. I'm not aware of any specific problems, but I'm not an expert in this sort of thing either. One question in my mind is how the UV pair relates to the four Y values. Currently each Y in a given UYVYYY chunk uses the same U and V values, but it's possible the Ys on the ends should blend the U and V values from the neighboring blocks (with special cases for the line ends...) However, this should only affect chroma, which doesn't really seem like your issue.
Would I be able to see the results, or at least a difference that points to a good direction in CHDKPTP right away?
If you enter
set gui_verbose=2
in the console, changes in the live view dimensions will cause the frame buffer description to be printed out in the console. You can set this in the same file as the contest plus option. If you are using viewport 1:1 the difference should also be fairly visible if you go from ~200 lines to ~400.
If so, how can I make the camera go into movie mode from the command line in CHDKPTP, and back again to still mode?
In the gui, there's a dropdown on the right side that lets you change mode.
In the command line, you can get to manual still mode using something like
lua require('capmode').set('M')
and to movie with
lua require('capmode').set('VIDEO_STD')
You can get the exact names from the dropdown.
Note on the A540 at least, the low resolution video modes reduce the viewport width.