You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I totally overlooked the need to do the MJPEG compression. Still, it does seem to have some sort of capture ASIC and I feel like MJPEG would be an obvious built-in feature, and 2M is not... a large image. That probably wouldn't explain the weird sharpening for 720p though.
The MJPEG is definitely done in hardware, but that IP block might be underpowered. Or maybe it's a bitrate thing. Or a limitation of the pixel interface or some other layer.
Sadly there isn't firmware to poke through to see more about the data flow.
Are the captured frames the same or similar for p30 and p60 input ? An intermediate 960x1080p60 with half the pixel clock could explain the artifacts, but then I don't know how it could transform into 1080p30 without any DRAM.
It needs RAM to stream YUV frames slower anyway... And only having 1 megapixel worth of built-in RAM would explain the limitation too.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
