Skip to main content

Get used to vertical photos and videos

Integrating cameras into mobile devices has been going on for quite a number of years now.  In that time the cell phone [mobile] camera has become quite a convenient feature.  However, an unexpected side-effect is that the perception of a "normal" orientation for a picture or a video is shifting. The expectation is that at some point in the near future the "natural" orientation of our photo and video content will switch to vertical instead of the far more practical, and pleasing, horizontal.

It's almost as though the first camera appeared in a cell phone simply because the creators thought to do it.  Then, after the fact, the uses for the shooter were realized.  Today, people snap pictures on their mobile devices of nearly everything, and new services have sprung up around the Internet to cater to this doohickey.  Thanks to the mobile camera we have shots and footage of nearly everything now.  And as we continue to find new uses for our mobile cameras, we're finding new ways to misuse them too.

Currently, the chief offender has to be photos and video shot with the camera (read phone) held vertically instead of rotating it sideways (artistic flare aside).  So now, besides wildly shaky video and blurry pictures, we get to enjoy them as though we were peering through a cracked closet door too.  In spite of HD cameras being embedded in so many mobile devices, we're continuing to build an endless supply of even more terrible content simply by holding our devices wrong.


UPDATE:  This video does a nice job of making the same point, just in a more satirical way.

Vertical Video Syndrome - A PSA
http://www.youtube.com/watch?v=Bt9zSfinwFA

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more