And on Reddit a photographer said "if anyone is still looking for a wired intervalometer for USB-C, you can use a Godox Xpro3 trigger and a 2.5mm to USB C. It works wonders as it’s tactile"
rd4tile wrote:
I used the old Sony RMT-P1BT Wireless Remote Commander via bluetooth for the FW shots above.
I just paired my old blue tooth Sony RMT-P1BT to the A7RVI, seems working so far. I also ordered a JJC wired remote (USB-C) from eBay, supposedly it works with the A7RVI. Will find out in few weeks when it arrives from China. I like to have two working remote controls just in case.
Does anyone have the slightest understanding why, or even speculation why, this legacy feature of the slower USB port (USB port 2) is an undocumented function of the camera? All the old wired remotes do is pull one terminal or the other low to trigger focus and shutter (short one or the other to ground). Apparently the old functionality exists and obviously no harm is done, but for some reason Sony doesn't want it promoted. It's a total mystery to me.
AZSteve wrote:
Does anyone have the slightest understanding why, or even speculation why, this legacy feature of the slower USB port (USB port 2) is an undocumented function of the camera? All the old wired remotes do is pull one terminal or the other low to trigger focus and shutter (short one or the other to ground). Apparently the old functionality exists and obviously no harm is done, but for some reason Sony doesn't want it promoted. It's a total mystery to me.
This is common in complex product development. While the Sony product management decides which features to build, document and support, the reality is that Sony cannot design & manufacture every component of a camera. They work with OEM partners who supply them with the components as long as they conform to the product specification. It's common for a supplied part to support MORE than the product spec called for. Sometimes the extra functionality is disabled. But when it can't be done, it's simply not mentioned/documented.
Another possible reason would be the obsolescence planning. If their product people believe that a certain functionality will not be used/needed in a distant future, but the future is too distant to discontinue the support right away, they choose the "soft landing" path when the feature is retained but no longer talked about, in order to gradually "drain the usage" among users prior to eventual discontinuation.
