Problem: With the advent of the IPhone X and the Windows fall creators update people are moving toward a widespread usage of augmented reality applications. If Wikipedia doesn't start to prepare for the future now, people may at some point still read texts that originate from wikipedia, but are presented by social media platforms and presented with non-free media, that was not uploadad to Wikipedia, but to proprietary non-free repositories.
Who would benefit: Photographers and Videographers, who can start to contribute content for future AR use, authors who can use VR content, readers, who can view Wikipedia in 3D, deverlopers, who have access to a large repository of 3D content
Dem Wahren Schönen Guten (Click image to view in 3D)
Proposed solution:
add media type jps to allowed upload formats in commons.
tag uploaded videos in cardboard, sbs and ttb formats in Commons as 3D.
turn toollabs Stereoskopie into a mediawiki extension
support viewing of 3d media in MediaViewer
make the android app functional (modes for single device, 2 devices, viewing of content)
add apps for iOS and the discontinued WinMobile and Blackberry platforms (or create a Arduino HID project to release cameras via KeyEvent.Volume_Up)
Stereoscopy has always suffered from two problems: The sparse availability of affordable cameras. And the problem, that the recording system had to match the viewing system - and for both parts there always was a large number of systems to choose from. This proposal addresses both fields:
An app is offered, that turns every camera, that can be controlled with bluetooth or wifi into a stereoscopic camera. And every pair of pictures (old stereoscopic pictures already available at commons, pictures that have been taken with a single camera, that has been moved between to takes) can be converted into a jps-file with the desktop-app.
One source (an image in the standard jps-format, a video in sbs, cardboard or top&bottom format) can be played out in basically every thinkable 3D-system (cardboard, 3DTV, pol (cinema system), prisma, anaglyph with any color code and also with systems, that do not require glasses at all: lenticular, crossed eyes and holographic pyramid). New playout-variants can be added and will work with existing content.
The Stereoskopie project is unfinished. A conversion to PHP, load scaling, robust caching and a Wiki-CI UI will need to be made. Content on the demo page will be added before voting starts.
For the moment the tool on toolforge is mostly broken. It will show the Winterimpression video in sbs mode, it may show the slideshow in cardboard mode after tweaking the URL. --𝔊 (GradzeichenDiſk✉Talk) 10:29, 20 November 2017 (UTC)[reply]
Small note, the GIFs on this page, while great for attention grabbing, might constitute an accessibility problem for people prone to vertigo or epilepsy. I suggest we disable them. —TheDJ (talk • contribs) 11:04, 23 November 2017 (UTC)[reply]
The difference between my development environment persisting of a local medawiki with many but not all extensionsn of WMF-wikis and a standalone Tomcat8, and toolforge grid's Tomcat7 is to big, to get the tool to work, before voting ends. You can still view the configuration pages (probably very different to that of an extension) and load the apps and sources. The app generates non-animated thumbs also, some can be found at c:category:Gradzeichen Stereoskopie Project/orga/2dthumb. An extension might use different thumbs, probably with opt-in for thumbs and an opt-out to view full-size content in 2d.
Oppose as illustrated here; no one want to see annoying jiggling images in articles. If this could be implemented without awful animation effects, then maybe. — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 07:55, 4 December 2017 (UTC)[reply]
@SMcCandlish: Have you read the proposal? It is by no means about jiggling images. It is about giving people a way to create 3D content (by showing ways to turn any photo/video equipment into 3d-cameras)l. It is about making it possible to upload such content to commons (by allowing jps and tagging sbs and cardboard, because content of recent incidents is either uploded soon or never. If wikimedia has no way, it ends up in social media with incompatible licences). It is about building a way to present 3D in WP (this will take a year or more. By that time much more people will be using VR and AR because of Iphonex and Windows AR tools.) It is about an interface, that support any method of stereoscopic presentation. But it is not about how a preview image on a device that not natively supports 3D should look like. That can be an animation, or a glasses symbol or anything else. It can be with opt in or opt out (because of vertigo, epilepsy, ...) But that is something that might be decided by a RfC once the technology to support it, is there! (another remark: There are people, who because of a medical condition do not have 3d-view, even so they are not one-eyed. As I found out, these people can for a short time experience 3d-vision with VRglasses (but the visual centre of the brain will give an 3d impression only for a short time, because of getting tired of the unfamiliar task). --𝔊 (GradzeichenDiſk✉Talk) 09:20, 4 December 2017 (UTC)[reply]
I understand what the proposal is, but the illustrated "here's what it'll look like" demo is horrifying. PS: I think this and the panoramic images proposal should be combined, since this one at least partially presupposes that one. — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 10:43, 4 December 2017 (UTC)[reply]
Support at least for adding media type jps to allowed upload formats in commons and tagging uploaded videos in cardboard, sbs and ttb formats in Commons as 3D. The need of toollabs to view the content isn't perfect but a (very) minor problem in my view, as long as it's accessible from all devices. X:: black ::X (talk) 09:50, 11 December 2017 (UTC)[reply]
Support --Liuxinyu970226 (talk) 13:15, 28 November 2017 (UTC)
Oppose as illustrated here; no one want to see annoying jiggling images in articles. If this could be implemented without awful animation effects, then maybe. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 07:55, 4 December 2017 (UTC)
