Introducing Kandao Meeting 360° All-in-one conference camera

Kandao Meeting, the 360° conferencing camera combines two high-quality fisheye lenses, 8 mics array and speaker together. It can be put in the center of a meeting room to capture all the attendees, while automatically focus on the people as they speak.

-Learn More: https://kandaovr.com/kandao-meeting/

Beetle-mounted camera streams insect adventures - BBC News

https://www.bbc.com/news/technology-53445772 

Tiny Camera Backpack Turns Beetles Into FPV Inspection Robots - Hackster.io

https://www.hackster.io/news/tiny-camera-backpack-turns-beetles-into-fpv-inspection-robots-278132d940a3 

PEAK QUALITY 3D 180 IMMERSIVE VIDEO IN OCULUS GO AND GEAR VR

http://echeng.com/articles/peak-quality-3d-180-oculus/


Skybox VR, Virtual Desktop, Pixvana SPIN Player

Excellent article and I am collecting FFMPEG commands to try to understand how to do this sort of encoding.

ffmpeg -i "in.mov" -vf "scale=4096x2048:out_range=full:out_color_matrix=bt709" -c:v libx264 -preset fast -crf 18 -pix_fmt yuv420p -c:a copy -g 60 -movflags faststart "out.mp4"

Finally, I used Facebook Spatial Workstation’s FB360 Encoder to mux the video and audio, outputting in “FB360 Matroska” for Oculus headsets, and in “YouTube Video (with 1st order ambiX”) for other players like Pixvana SPIN Player.

Create a WebRTC P2P Shooting App with the Ricoh THETA Plug-in

https://community.theta360.guide/t/create-a-webrtc-p2p-shooting-app-with-the-theta-plug-in/4050/2


Has links for an Open Source Java based websocket communications to stream data from the camera.

Nageru: Taking free software video mixing into 2016 (FOSDEM 2016)

https://nageru.sesse.net/

Nageru (投げる), a modern free software video mixer

Nageru (a pun on the Japanese verb nageru, meaning to throw or cast) is a live video mixer. It takes in inputs from one or more video cards (any DeckLink PCI card via Blackmagic's drivers, and Intensity Shuttle USB3 and UltraStudio SDI USB3 cards via bmusb), mixes them together based on the operator's desire and a theme written in Lua, and outputs a high-quality H.264 stream over TCP suitable for further transcoding and/or distribution. Nageru is free software, licensed under the GNU General Public License, version 3 or later.

Nageru aims to produce high-quality output, both in terms of audio and video, while still running on modest hardware. The reference system for two 720p60 inputs is a ThinkPad X240, ie. an ultraportable dual-core with a not-very-fast GPU. Nageru's performance scales almost linearly with the available GPU power; e.g., if you have a GPU that's twice as fast as mine (which is not hard to find at all these days; desktop GPUs are frequently more like 10x), going to 1080p60 will only cost you about 10% more CPU power.

Various real-world examples of videos produced by Nageru:

• The stream at Solskogen 2016–2018 was made with Nageru (in collaboration with other software and some hardware); you can view a copy of the 2016 streams and 2017 streams at YouTube (although YouTube doesn't seem to deal properly with 50/60 fps switches, causing jerkiness in some videos).
• Fyrrom in 2016, and again in 2017.
• All videos from Trøndisk 2017 (an example of multi-camera and overlay graphics), Norwegian ultimate championships 2018 (same, but with the newer native CEF support), and Trøndisk 2018 (also with Futatabi integration).
• The Norwegian municipality of Frøya is live streaming all of their council meetings using Nageru (Norwegian only).
• Breizhcamp, a French technology conference, used Nageru in 2018 and 2019. If you speak French, you can watch their keynote about it (itself produced with Nageru) and all their other video online.

Futatabi (再び), a multi-camera free software instant replay system with slow motion

Futatabi is a multi-camera instant replay system with slow motion. It supports efficient real-time interpolation using optical flow, making for full-framerate output without having to use special high-framerate cameras. (Of course, interpolation can only take you so far, and the results will depend on the type of content.) Futatabi is currently in alpha. It is distributed and built together with Nageru.

Documentation

Nageru and Futatabi have extensive documentation at https://nageru.sesse.net/doc/. In addition, you can see the FOSDEM 2016 talk introducing Nageru, although it covers only 1.0.0 and a lot of things have happened since then:

• Slides
• Slides with speaker notes (you probably want this version)
• Video (YouTube)

There was a talk about Futatabi at FOSDEM 2019, too (covering 1.8.2):

• Slides (with video)
• Slides with speaker notes (you probably want this version, but it's without video)
• Video (YouTube)

https://nageru.sesse.net/doc-1.8.6/streaming.html

High-Fidelity Generative Image Compression

https://hific.github.io/

We combine (GAN) Generative Adversarial Networks with learned compression to obtain a state-of-the-art generative lossy compression system. In the paper, we investigate normalization layers, generator and discriminator architectures, training strategies, as well as perceptual losses. In a user study, we show that our method is preferred to previous state-of-the-art approaches even if they use more than 2× the bitrate.

360° VR TRANSCODING LIVE | ON DEMAND

https://cubemap.io/

360° TRANSCODING
LIVE | ON DEMAND
Cubemap optimizes video for Virtual Reality by stitching videos faster, and more efficiently than any other solution, no GPU required.

H.266 (VVC) New Codec Announced: Laying the Groundwork for 8K Streaming

https://ymcinema.com/2020/07/10/h-266-vvc-new-codec-announced-laying-the-groundwork-for-8k-streaming/


The Fraunhofer Institute for Telecommunications, Heinrich Hertz Institute (HHI) has announced the standardization of a new codec called H.266 or VVC (Versatile Video Coding) which allows half of the bit rate compared to H.265 (HEVC) without a reduction in quality. The goal: To lay the groundwork for 8K streaming.

Support ultra-high-resolution: Up to 16K
The VVC should support resolutions from 4K to 16K as well as 360° videos, as well as support YCbCr 4:4:4, 4:2:2, and 4:2:0 with 10 to 16 bits per component




The Versatile Video Coding (VVC) Standard on the Final Stretch by Benjamin Bross

https://news.ycombinator.com/item?id=23747626

Focal Surface Displays - Varifocal displays

https://en.wikipedia.org/wiki/Varifocal_lens

https://www.oculus.com/blog/oculus-research-to-present-focal-surface-display-discovery-at-siggraph/

https://www.oculus.com/blog/introducing-the-team-behind-half-dome-facebook-reality-labs-varifocal-prototype/

ffmpeg stereo 3d VR180

Sorry, this is some raw notes and highlights here.


https://ffmpeg.org/ffmpeg-filters.html#stereo3d

‘hequirect’

Half equirectangular projection.

target_geometry

The target geometry of the output image/video. The following values are valid options:

‘rectilinear (default)’

‘fisheye’

‘panoramic’

‘equirectangular’

‘fisheye_orthographic’

‘fisheye_stereographic’

‘fisheye_equisolid’

‘fisheye_thoby’

‘dfisheye’

Dual fisheye.

‘fisheye’

Fisheye projection.

11.223.1 Examples

• Convert equirectangular video to cubemap with 3x2 layout and 1% padding using bicubic interpolation:

  ffmpeg -i input.mkv -vf v360=e:c3x2:cubic:out_pad=0.01 output.mkv
  

• Extract back view of Equi-Angular Cubemap:

  ffmpeg -i input.mkv -vf v360=eac:flat:yaw=180 output.mkv
  

• Convert transposed and horizontally flipped Equi-Angular Cubemap in side-by-side stereo format to equirectangular top-bottom stereo format:

  v360=eac:equirect:in_stereo=sbs:in_trans=1:ih_flip=1:out_stereo=tb
  

https://trac.ffmpeg.org/wiki/Stereoscopic

ffmpeg -i top-and-bottom.mov -vf stereo3d=abl:sbsl -c:a copy side-by-side.mov


ENCODING VR 360 AND 180 IMMERSIVE VIDEOS FOR OCULUS MEDIA STUDIO AND SIDELOADING INTO OCULUS QUEST AND GOhttps://echeng.com/articles/encoding-for-oculus-media-studio/

Exploring the Kanda QooCam 4K - pass1

I was hoping  to get live streaming off this camera, and it would appear if you have a 64 Bit android device their app can see a live video feed?

There is a Live option on the windows app that appears to do nothing.

 The USB doesn't show up as a video driver.


You can connect with the device over Wifi

To do this power on the device and wait for the power up tune to play.

one well timed (approx 1 second) power button push and it will beep and the blue wifi like will come on.

Scanning your wifi network SSID's, and you will see something like:

QOOCAM-06515

your camera id will vary based on the last 5 digits of the serial number.

password is : 12345678




From Linux, this command works but I was seeing many errors.
ffplay  rtsp:192.168.1.1:554/live

sokol@nuc2:~/Desktop/vr180$ ffplay  rtsp:192.168.1.1:554/live
ffplay version 2.8.15-0ubuntu0.16.04.1 Copyright (c) 2003-2018 the FFmpeg developers
  built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
  configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
  libavutil      54. 31.100 / 54. 31.100
  libavcodec     56. 60.100 / 56. 60.100
  libavformat    56. 40.101 / 56. 40.101
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 40.101 /  5. 40.101
  libavresample   2.  1.  0 /  2.  1.  0
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc    53.  3.100 / 53.  3.100
[h264 @ 0x7f95580008c0] RTP: missed 129 packetsKB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 37 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] left block unavailable for requested intra mode at 0 44
[h264 @ 0x7f95580008c0] error while decoding MB 0 44, bytestream 659
[h264 @ 0x7f95580008c0] concealing 1969 DC, 1969 AC, 1969 MV errors in P frame
[h264 @ 0x7f95580008c0] RTP: missed 28 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 41 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 31 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 27 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 121 packetsKB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 65 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 29 packets0KB sq=    0B f=0/0 
Input #0, rtsp, from 'rtsp:192.168.1.1:554/live': sq=    0B f=0/0 
  Metadata:
    title           : H.264 Video. Streamed by iCatchTek.
    comment         : H264
  Duration: N/A, start: 0.801333, bitrate: N/A
    Stream #0:0: Video: h264 (High), yuv420p, 1920x960, 15 fps, 14.99 tbr, 90k tbn, 30 tbc
[h264 @ 0x7f955812a200] left block unavailable for requested intra mode at 0 44
[h264 @ 0x7f955812a200] error while decoding MB 0 44, bytestream 659
[h264 @ 0x7f955812a200] concealing 1969 DC, 1969 AC, 1969 MV errors in P frame
[h264 @ 0x7f95580008c0] RTP: missed 41 packets9KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 65 packets1KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets2KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 41 packets
[h264 @ 0x7f95580008c0] RTP: missed 33 packets
    Last message repeated 1 times
[h264 @ 0x7f95580008c0] RTP: missed 161 packetsKB sq=    0B f=1/1   

$ nmap -v -sN 192.168.1.1
Starting Nmap 7.70 ( https://nmap.org ) at 2020-07-06 08:11 ric
Initiating ARP Ping Scan at 08:11
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 08:11, 2.16s elapsed (1 total hosts)
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-s
ervers
Initiating NULL Scan at 08:11
Scanning 192.168.1.1 [1000 ports]
Completed NULL Scan at 08:11, 6.23s elapsed (1000 total ports)
Nmap scan report for 192.168.1.1
Host is up (0.018s latency).
Not shown: 997 closed ports
PORT     STATE         SERVICE
21/tcp   open|filtered ftp
554/tcp  open|filtered rtsp
9200/tcp open|filtered wap-wsp
MAC Address: CC:4B:73:35:B4:2E (Ampak Technology)

Read data files from: C:\Program Files (x86)\Nmap
Nmap done: 1 IP address (1 host up) scanned in 15.72 seconds
           Raw packets sent: 1004 (40.148KB) | Rcvd: 998 (39.908KB)



$ nmap -v -A 192.168.1.1
Starting Nmap 7.70 ( https://nmap.org ) at 2020-07-06 08:12 ric
NSE: Loaded 148 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 08:12
Completed NSE at 08:12, 0.00s elapsed
Initiating NSE at 08:12
Completed NSE at 08:12, 0.00s elapsed
Initiating ARP Ping Scan at 08:12
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 08:12, 2.46s elapsed (1 total hosts)
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-s
ervers
Initiating SYN Stealth Scan at 08:12
Scanning 192.168.1.1 [1000 ports]
Discovered open port 554/tcp on 192.168.1.1
Discovered open port 21/tcp on 192.168.1.1
Discovered open port 9200/tcp on 192.168.1.1
Completed SYN Stealth Scan at 08:12, 3.94s elapsed (1000 total ports)
Initiating Service scan at 08:12
Scanning 3 services on 192.168.1.1
Completed Service scan at 08:12, 6.01s elapsed (3 services on 1 host)
Initiating OS detection (try #1) against 192.168.1.1
Retrying OS detection (try #2) against 192.168.1.1
Retrying OS detection (try #3) against 192.168.1.1
Retrying OS detection (try #4) against 192.168.1.1
Retrying OS detection (try #5) against 192.168.1.1
NSE: Script scanning 192.168.1.1.
Initiating NSE at 08:13
Completed NSE at 08:13, 10.04s elapsed
Initiating NSE at 08:13
Completed NSE at 08:13, 0.00s elapsed
Nmap scan report for 192.168.1.1
Host is up (0.0042s latency).
Not shown: 997 closed ports
PORT     STATE SERVICE    VERSION
21/tcp   open  tcpwrapped
554/tcp  open  rtsp       DoorBird video doorbell rtspd
9200/tcp open  tcpwrapped
MAC Address: CC:4B:73:35:B4:2E (Ampak Technology)
No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).
TCP/IP fingerprint:
OS:SCAN(V=7.70%E=4%D=7/6%OT=554%CT=1%CU=34247%PV=Y%DS=1%DC=D%G=Y%M=CC4B73%T
OS:M=5F02CF11%P=i686-pc-windows-windows)SEQ(CI=I%II=RI)ECN(R=N)T1(R=Y%DF=N%
OS:T=FF%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=FF%W=E420%
OS:S=A%A=S%F=AR%O=%RD=0%Q=)T5(R=Y%DF=N%T=FF%W=E420%S=A%A=S+%F=AR%O=%RD=0%Q=
OS:)T6(R=Y%DF=N%T=FF%W=E420%S=A%A=S%F=AR%O=%RD=0%Q=)T7(R=Y%DF=N%T=FF%W=E420
OS:%S=A%A=S+%F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPC
OS:K=G%RUCK=G%RUD=G)IE(R=Y%DFI=S%T=FF%CD=S)

Network Distance: 1 hop
Service Info: Device: webcam

TRACEROUTE
HOP RTT     ADDRESS
1   4.20 ms 192.168.1.1

NSE: Script Post-scanning.
Initiating NSE at 08:13
Completed NSE at 08:13, 0.01s elapsed
Initiating NSE at 08:13
Completed NSE at 08:13, 0.01s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 52.54 seconds
           Raw packets sent: 1241 (60.438KB) | Rcvd: 1047 (43.282KB)
$

Video Forensics Made Easy

Import your CCTV and other footage into VideoFOCUS and quickly reveal the truth.

https://www.salientsciences.com/





This was 11 years ago.

Mass. DAs adopt Salient Stills for crime scene video processing

.

John,

Salient Stills today announced the MDAA - Massachusetts District Attorneys Association - has adopted the company’s video forensics system to secure, capture, and process evidence from crime scene videos. This frees the DAs from relying on other law enforcement agency crime labs to conduct video forensics, and enables seven of the 11 MDAA offices to more quickly process video evidence and advance investigations, arrests and prosecutions.

Background – The MDAA, headquartered in downtown Boston, is an independent state agency that supports the eleven elected Massachusetts District Attorneys and their combined staff of 1,500 employees, who collectively prosecute approximately 300,000 cases annually. Funding for the systems was provided by a U.S. Department of Justice (DOJ) Community Oriented Policing Services (COPS) technology grant.

The official news release is here: http://www.salientstills.com/news/pr-080811.html

SALIENT STILLS SUPPORTS MASSACHUSETTS DISTRICT ATTORNEYS

DAs Conduct Video Forensics With VideoFOCUS Pro

BOSTON, August 8, 2011 - Salient Stills, the leader in video forensics and image enhancement, today announced the Massachusetts District Attorneys Association (MDAA) has licensed VideoFOCUS Pro to seven of the eleven Massachusetts DA offices, enabling its members to conduct hands on video forensics to secure, capture, and process evidence from video samples. Funding for the systems was awarded to the MDAA by a U.S. Department of Justice (DOJ) Community Oriented Policing Services (COPS) technology grant.

More and more investigations and prosecutable cases have videos as part of the evidence. Unfortunately, these videos can be of poor quality, hard to export from proprietary security camera systems, and combined with other video streams, making it difficult to locate, isolate and extract the most helpful sequences and stills, said Pat Alfieri, Chief Information Officer for MDAA. By deploying VideoFOCUS Pro among our members, the DAs and their investigators can quickly process video evidence and advance investigations, arrests and prosecutions.

“Video forensics is a powerful tool for law enforcement agencies, helping them identify suspects and place them at the scene of a crime, establishing a chain of events, and, ultimately, supporting successful prosecutions,” said Laura Teodosio, president and CEO of Salient Stills. “With access to the latest video forensics technology in VideoFOCUS Pro, local DAs can process video faster, freeing time for other important activities.”

MDAA is an independent state agency that supports the eleven elected Massachusetts District Attorneys and their combined staff of 1,500 employees, who collectively prosecute approximately 300,000 cases annually. The agency manages statewide business technology services and administers grants in the areas of Violence Against Women, Motor Vehicle Crimes, and federal technology grants. MDAA also produces publications for prosecutors and victim-witness advocates, hosts dozens of prosecutor trainings annually, and provides information on budgetary, criminal justice and public safety issues to the executive and legislative branches.

Designed for use by law enforcement officers and using innovative processing algorithms, VideoFOCUS Pro dramatically improves the ability to capture and export fuzzy or grainy video from videotape, CCTV systems, digital video cameras, cell phones and proprietary DVR formats. The system generates higher resolution stills and videos to help identify suspects and produce other leads. VideoFOCUS Pro is in use by hundreds of investigative agencies in over 20 countries and throughout the United States.

About Salient Stills
Founded in 1997, Salient Stills is a leading video forensics and image enhancement software company. Salient Stills introduced its technology to answer the need for an efficient and effective video image enhancement solution. VideoFOCUS Pro and VF Source are video forensics solutions in use by law enforcement, security and military and intelligence agencies. For more information on Salient Stills visit www.salientstills.com.

Salient Stills today announced the MDAA - Massachusetts District Attorneys Association - has adopted the company’s video forensics system to secure, capture, and process evidence from crime scene videos. This frees the DAs from relying on other law enforcement agency crime labs to conduct video forensics, and enables seven of the 11 MDAA offices to more quickly process video evidence and advance investigations, arrests and prosecutions.

Background – The MDAA, headquartered in downtown Boston, is an independent state agency that supports the eleven elected Massachusetts District Attorneys and their combined staff of 1,500 employees, who collectively prosecute approximately 300,000 cases annually. Funding for the systems was provided by a U.S. Department of Justice (DOJ) Community Oriented Policing Services (COPS) technology grant.

The official news release is here: http://www.salientstills.com/news/pr-080811.html

I have started an Open Facebook discussion group, Video Technology

Please Join us: 

https://www.facebook.com/groups/608389670074687/

Best Oculus Quest Settings for 360 / VR180 Video Rendering in Premiere/F...

FROM : https://www.youtube.com/watch?v=iBGjn4rmFJU

What are the MAX resolutions and best render settings for 360° and VR180 content creators on the brand new Oculus Quest? This tutorial will give you a step by step guide on how to export your 360VR or 3D 180 videos and sideload them onto Oculus Quest for the best viewing experience with Adobe Premiere OR FFmpeg using both H.264 and H.265 (HEVC). Make sure to stay tuned and subscribe! My full review video for the HOTTEST headset of the year is coming out very soon!

⏰Timestamps for your viewing convenience:
2:57 - all MAX resolutions for Oculus Quest
4:23 - all my MAX 60fps resolutions (beyond Oculus recommendation)
6:12 - how to sideload videos onto Oculus Quest and the best way to play them
9:26 - Premiere rendering workflow with AfterCodecs
12:28 - FFmpeg workflow for BEST quality VR videos

➡️Oculus Quest MAX resolution (official)
360 / 360VR
2880x2880 60fps H264 H265
4096x2048 60fps H264 H265
3840x3840 30fps H264 H265
4096x4096 30fps ---- H265
5120x2560 30fps H264 ----
5760x2880 30fps H264 ----

3D-180 / VR180:
5120x2560 30fps H264 ----
2880x5760 30fps H264 H265

💻The command for monitoring drop frames:
adb logcat -s VideoPlayerAnalytics

💻The command for FFmpeg for 360VR video render:
ffmpeg -y -i "input.mov" -c:v libx265 -preset fast -crf 21 -vf "scale=4096x4096:out_range=full" -pix_fmt yuvj420p -aspect 1:1 -movflags faststart "output.mp4"

💻The command for FFmpeg for VR180 max resolution:
ffmpeg -y -i "input.mov" -c:v libx265 -preset fast -crf 21 -vf "stereo3d=sbs2l:abl, scale=2880x5760:out_range=full" -pix_fmt yuvj420p -aspect 1:2 -movflags faststart "output.mp4"

test videos are available to download here:
http://bit.ly/2MHmHKO
#oculusquest #adobepremiere #360 #vr180 #ffmpeg


Also read:
Encoding High-Resolution 360 and 180 Video for Oculus Quest and Oculus Go [Updated to Include h.265 Support]
  https://creator.oculus.com/blog/encoding-high-resolution-360-and-180-video-for-oculus-go/?locale=en_US

h.264, 30fps (side-by-side 3D-180 video):

ffmpeg -i "input.mp4" -c:v libx264 -preset fast -crf 18 -x264-params mvrange=511 -maxrate 50M -bufsize 25M -vf "scale=5120x2560" -pix_fmt yuv420p -c:a aac -b:a 160k -movflags faststart "output_h264.mp4"

h.265, 30fps (side-by-side 3D-180 video re-arranged to over/under):

ffmpeg -i "input.mp4" -c:v libx265 -preset fast -crf 18 -maxrate 50M -bufsize 25M -vf "stereo3d=sbs2l:abl, scale=2560x5120" -pix_fmt yuv420p -aspect 1:2 -c:a aac -b:a 160k -movflags faststart "output_h265.mp4"




5 Inch Video Card

Huya - the Chinese Twitch.tv : Stream VR Panoramic video live.

https://www.huya.com/

This is a really cool site if you can read Mandarin or have the google translator plugin that will make it english.

Anyhow I just stumbled on this when researching streaming Live 360VR for the Qoocam.  I assume there is a big lag in it. 

What is Huya Live

Huya live broadcast is a barrage interactive live broadcast platform that young people like. It mainly focuses on interactive live broadcast of games, and continues to introduce a variety of live broadcast content, such as e-sports live broadcast, outdoor live broadcast, entertainment interactive live broadcast, etc., to provide users with quality live broadcast viewing Experience. At present, Huya Live is supported by professional e-sports teams 4AM, TYLOO, 619, YTG, 1246, and well-known popular anchors Wei Shen, Miss, Uzi, Sao Nan, etc. Uninterrupted throughout the year, continue to provide players with a wonderful live broadcast feast!

How to watch live games on Huya Live?

1. Log in to www.huya.com with a browser on your computer , watch live chatter on the big screen, and enjoy a lively interactive feeling.

2, mobile phone download eye teeth live APP , anytime, anywhere, want to see, wonderful live in your palm.

This VR watch live, Watch panorama live.  

How do you conveniently get this in to your VR headset I have no idea. 

VR180 "VR Ready" cameras.

https://arvr.google.com/vr180/ 

Looking for the specs,

Protocols,  maybe a wireshark tcpdump of a clear text session 

 Can it be simulated from a pi with a t265 Intel realsense tracking camera with 2 perfectly eye spaced 175deg wide angle cameras?

Or some code libraries to connect into one?

--

John Sokol

http://johnsokol.com

669-500-2329

john.sokol@gmail.com

VR180 Open Source Tools

NOTE: I am still looking and updating.  Let me know if you have anything I should add.

180 Stereo Photo Viewer

A VR180 photo viewer that works on a web browser.

You can try it here. https://chiqden.github.io/180-stereo-photo-viewer/

Supported photo formats
VR180 photos (vr.jpg)
180 stereo side by side photos

A VR180 photo viewer that works on a web browser.
https://github.com/chiqden/180-stereo-photo-viewer

based on A-Frame

VR180

NOTE: I am still updating this page.

How to publish VR180

https://www.blog.google/products/google-vr/how-publish-vr180/

VR180: NEW FORMAT AIMS TO EXPAND IMMERSIVE MARKET

VR180 Creator

Introducing VR180 Creator, simplifying the video editing process

VR180 cameras allow creators to shoot three-dimensional, immersive photos and videos using affordable cameras that are small enough to fit in your pocket.

And to make it even easier for you to create and edit high quality VR videos, we’re launching VR180 Creator on Mac and Linux. This desktop tool lets anyone edit VR180 footage with existing VR video tools.

VR180 Creator currently offers two features for VR videos. “Convert for Publishing” takes raw fisheye footage from VR180 cameras like the Lenovo Mirage Camera and converts it into a standardized equirect projection. This can be edited with the video editing software creators already use, like Adobe Premiere and Final Cut Pro. “Prepare for Publishing” re-injects the VR180 metadata after editing so that the footage is viewable on YouTube or Google Photos in 2D or VR.



Convert your VR180 footage into a standardized format so you can edit it with leading editing tools like Adobe Premiere and then re-inject the appropriate metadata for publishing.

https://arvr.google.com/vr180/apps/   DOWNLOAD HERE



VR180 Creator release notes
https://support.google.com/vr180/answer/9049949


Google’s VR180 Creator Tool Makes it Easier to Edit VR Video on Linux
https://www.omgubuntu.co.uk/2018/06/google-vr180-creator


https://itsfoss.com/vr180-creator/

https://fstoppers.com/originals/introduction-vr180-format-440235

DNxHR was listed as an output option instead of mpeg4. This is something I wasn't familiar with.
I have yet to try it on anything.

Avid DNxHR, which stands for "Digital Nonlinear Extensible High Resolution", is a lossy UHDTV post-production codec 
https://en.wikipedia.org/wiki/DNxHR_codec

Cameras

 Z-Cam

http://www.z-cam.com/180-vr-camera-k1-pro/

Kandao qoocam

VR180 Video Format

1. Introduction

VR180 cameras are a new category of VR camera that use two wide angle cameras to capture the world as you see it with point and shoot simplicity. This document describes the video format output by these devices. The choice considers the following aspects:

FOV: VR180 cameras capture sub-360 FOV rather than full 360. It is important to retain the original pixel density of the camera sensors in order to provide high pixel density for VR viewing.
Projection: Different versions of VR180 cameras may have different lens and different camera projections. As such the file format should be camera-independent.
Motion: The cameras can often be non-stationary due to unintentional shakes or intentional motion, for example, handheld capture of events or people. To avoid motion sickness, camera motion metadata should be saved for stabilized playback.
Playback: The file format should be friendly enough for local playback so that manufacturers can easily build their apps. Android and iOS should have an easy way to play the raw video.
VR180 videos contain two types of metadata to jointly define the projection from video frames to their partial viewports within a spherical coordinate system.

A global static projection that defines the mapping from the pixels to local spherical coordinate systems, typically to only a sub-180 FOV part. The Spherical Metadata V2 Spec is adopted here to encode this global metadata. (See details in section 2).
A dynamic orientation stream that defines the rotation between the local coordinate system of each frame and the world coordinate system. A new Camera Motion Metadata track is created for encoding such per-frame metadata. (See section 3).

https://github.com/google/spatial-media/blob/master/docs/vr180.md

Spherical Video V2 RFC

This document describes a revised open metadata scheme by which MP4 (ISOBMFF) and WebM (Matroska) multimedia containers may accommodate spherical videos. Comments are welcome by discussing on the Spatial Media Google group or by filing an issue on GitHub.

Metadata Format
MP4 (ISOBMFF)
Spherical video metadata is stored in a new box, sv3d, defined in this RFC, in an MP4 (ISOBMFF) container. The metadata is applicable to individual video tracks in the container. Since many spherical videos are also stereoscopic, this RFC also defines an additional optional box, st3d, to specify metadata specific to stereoscopic rendering.

As the V2 specification stores its metadata in a different location, it is possible for a file to contain both the V1 and V2 metadata. If both V1 and V2 metadata are contained they should contain semantically equivalent information, with V2 taking priority when they differ.

Stereoscopic 3D Video Box (st3d)

https://github.com/google/spatial-media/blob/master/docs/spherical-video-v2-rfc.md