Minimal HDMI remote for testing 1 micro or mini HDMI to standard HDMI adapter1 HDMI standard to DVI female adapter1 paper clip
I used a HDMI C plug that has a small PCB (see picture) to make soldering easier.
All my cameras (G1x, S110, SX230, M3) have 5 volts on the HDMI port in playback and recording mode.With the G1X and S110 I've tried HDMI ChangePowerState and EnableHDMIPower /DisableHDMIPower in both playback and recording modes, in no case has the output changed.Would be interesting if someone could confirm ....
Would it really be possible for cameras with a hot shoe to switch the flash contact?
Tried 3 of my cameras - m10, sx280, ixus115. Only the sx280 reacted to EnableHDMIPower and DisableHDMIPower, and this was also the only cam that switched the 5V off in rec mode.
but I don't know how often the cam would allow you to "flash".
What can the 5V voltage drive?
Definitely enough to run an ARDUINO Nano with OLED display ...
The HDMI connector provides a pin allowing the Source to supply +5.0 Volts to the cable and Sink.All HDMI Sources shall assert the +5V Power signal whenever the Source is using the DDC or TMDS signals. The voltage driven by the Source shall be within the limits specified for TP1 voltage in Table 4-22. An HDMI Source shall have +5V Power signal over-current protection of no more than 0.5A.All HDMI Sources shall be able to supply a minimum of 55 mA to the +5V Power pin.A Sink shall not draw more than 50 mA of current from the +5V Power pin. When the Sink is powered on, it can draw no more than 10mA of current from the +5V Power signal. A Sink shall assume that any voltage within the range specified for TP2 voltage in Table 4-22 indicates that a Source is connected and applying power to the +5V Power signal.A Cable Assembly shall be able to supply a minimum of 50mA to the +5V Power pin to a Sink, even when connected to a Source supplying no more than 55mA.The return for the +5V Power signal is DDC/CEC Ground signal.
Spoofing analog A/V detect:It might be desirable to provide something like usb_force_active for the A/V detect. This should allow A/V out while also using the detect signal as a remote trigger, which would potentially be useful for FPV applications. Using the USB remote for triggering would also work in this situation, but a full splitter cable is harder to make.
elph180 is 720x480? in play, (vs 240 normal). It doesn't support video out in REC, switching causes it to switch back to camera LCD. SetVideoOutType(1) does enable AV out in rec, vp resolution is 720x240 as normal. Shooting and video recording works (previous thread about enabling video out on cams without Canon FW support https://chdk.setepontos.com/index.php?topic=11439.0) Note I called the underlying function (ffb93458) directly, rather than registering event procs.
The cameras that are normally 240 but 480? above in playback get cut off in PTP live view, since the viewport height is hard coded (? because I haven't check if they are exactly 480). elph130 in rec gets a squished half-height display, since physcal_height is hard coded. These would also affect zebra, histogram etc in AV out.
It would be nice to make load_chdk_palette null safe on the the platforms that have it. It's pretty much copy / paste, so finding a way to make it generic might be worthwhile.
I would be tempted to drop the whole thing, but crashing on real analog AV would be nice to fix.
Well, that's a nice find. I tried it on the cam mentioned in the other thread (a3400) and indeed, it works. Apparently FA.Create is causing too many side effects.This should perhaps be turned into a feature.
QuoteIt would be nice to make load_chdk_palette null safe on the the platforms that have it. It's pretty much copy / paste, so finding a way to make it generic might be worthwhile.One issue with that (commonly used) code is that it requires 13 or more consecutive unused palette entries which is not always available. But, any affected port could then have its own, custom routine. I don't remember actually making such a modified version, only considering it.
QuoteI would be tempted to drop the whole thing, but crashing on real analog AV would be nice to fix.Which whole thing? The Lua function seems useful, the crashing issues are real.