One other thing to remember: all else being equal, 8K video will be consuming four times as much power and generating four times as much heat as 4K video, which will be consuming four times as much power and generating four times as much heat as 1080p video. In short, not all 1080p or 4K or 8K or whatever is created equal. There are enormous trade-offs involved here, and one chip may produce files twice the size and half the quality of another chip even with the same sensor and lens-to say nothing of the variation possible in sensors and lenses! If I record 1080p on my Surface Book with its rear-facing camera, for example, it runs quite a bit hotter than a typical phone with very similar optics, but produces substantially better quality for a given bit rate-in doing rough visual comparison earlier this year, I estimated that it was producing obviously better results at a quarter of the file size, comparing it to a mid-range phone of a generation two or three years newer than it.Īlso the other aspect of resolution not being everything is the optics my Sony α6100’s 1080p is miles ahead of most phones’ 1080p in quality, and I think there’s a high chance it’d be better than a $100 4K video camera’s 4K. You are quite wrong, ignoring both the megapixel wars and how video encoding works. Also, some companies require tech support staff to respond to a certain minimum number of tickets per hour (effectively penalizing personnel for doing anything beyond provided checklists, which consulting part specs definitely would be). A mass manufacturer probably doesn’t want to give an impression that they encourage a way of using the units not explicitly mentioned in the manual to avoid any complaints/lawsuits. It’s more likely they just wouldn’t tell for whatever reason. “In theory this camera can support up to N triggers per second, which is the limit for part X, but you will need your storage to sustain writes at speed S or the buffer will fill up, and by the way this wasn’t tested end-to-end and will void your warranty.” Responding to such a query could (should?) be as easy as checking the specs. Each component in the chain, from trigger button to storage I/O, had presumably been tested and its tolerances documented. It worked splendidly.Īny manufacturer that’s even remotely serious wouldn’t need to test their own product to find out how it works. I ended up using a continuous signal and having my program listen to the remote flash connector. Reluctantly, he forwarded the question to their technical support, who never answered. I tried, to no avail, to explain that it was a computer sending the signal and it could do so (with the hardware I had) a thousand times per second. Their support tech insisted it was irrelevant since I couldn't possibly press the button that fast. I contacted Canon support to confirm that the 10 pics per second was only when given a continuous signal and to ask which speeds it could reach when taking separate pictures via remote trigger. The timeline was pretty tight, so I had to begin development before I had the camera. The images were then processed by a series of tools I'd helped develop the previous year. The idea was to use its ability to take ten pictures a second to take a rapid succession of images with very different lighting. In 2008 I was hired by a game studio to build a HW/SW system for synchronizing a Canon EOS 1D Mark III and a series of studio flashes. This reminds me of a loosely related tale.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |