US20140147099A1

US20140147099A1 - Video headphones platform methods, apparatuses and media

Info

Publication number: US20140147099A1
Application number: US14/092,059
Authority: US
Inventors: Stephen Chase
Original assignee: Stephen Chase
Current assignee: Soundsight Ip LLC
Priority date: 2012-11-29
Filing date: 2013-11-27
Publication date: 2014-05-29
Also published as: JP6622588B2; JP2016509380A; CN105027206A; EP2926338B1; EP2926338A1; US20140161412A1; KR20150092220A; EP2926338A4; EP3637419A3; EP2926338B8; US20200245048A1; US10652640B2; EP3637419A2; WO2014085610A1; JP2020096354A

Abstract

A request to record a user's world view video may be received. The world view video may be recorded via video headphones and adjusted based on user instructions. The adjusted world view video may be shared with the user's social network.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on, and claims priority to U.S. Provisional Application No. 61/731,126, filed Nov. 29, 2012, the entire contents of which being fully incorporated herein by reference.
This disclosure describes VIDEO HEADPHONES PLATFORM METHODS, APPARATUSES AND MEDIA (hereinafter “VHP”). A portion of the disclosure of this patent document contains material which is subject to copyright and/or mask work protection. The copyright and/or mask work owners have no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserve all copyright and mask work rights whatsoever.

FIELD

The present disclosure is directed generally to video headphones.

BACKGROUND

Many different types of headphones currently exist on the market. Some headphones concentrate more on providing optimal sound reproduction (e.g., high fidelity sound reproduction), while others concentrate on portability (e.g., small size, light weight, foldable). Headphones may obtain an audio signal from an audio source (e.g., a portable music player) either via an audio cable or via a wireless receiver.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures and/or appendices illustrate various exemplary embodiments in accordance with the present disclosure.

FIG. 1 shows a logic flow diagram illustrating a world view sharing (WVS) component in one embodiment of the VHP. This is an exemplary VHP world view sharing (WVS) component.

FIG. 2 shows a data flow diagram in one embodiment of the VHP. This is an exemplary VHP data flow.

FIG. 3 shows a block diagram illustrating an exemplary VHP coordinator in one embodiment of the VHP. This is an exemplary VHP coordinator.

FIGS. 4 to 20 illustrate additional exemplary embodiments of the VHP.

DETAILED DESCRIPTION

Introduction

The VHP empowers users to record, edit and share their world view with their social networks. A user may record a video through a video camera embedded in the user's headphones. Audio may also be recorded through one or more microphones, which are installed into the headphone cable control unit and/or located underneath the video camera. Once the user finishes recording the video, the user may add music, apply filters, make audio and/or video adjustments, provide a description of the video, and/or the like. After the user finishes editing the video, the video may be shared with the user's social networks.

Detailed Description of the VHP

FIG. 1 shows a logic flow diagram illustrating a world view sharing (WVS) component in one embodiment of the VHP. In FIG. 1, a request to share a world view video may be received at 101. For example, a world view video may be a video showing what may be seen and/or heard by a user (i.e., the view from the user's eye level). In one embodiment, the request to share a world view video may be received based on activation of a record button on video headphones (e.g., the record button may be integrated into a headphone cable) by the user. In another embodiment, the request to share a world view video may be received based on activation of a record button of a VHP mobile app (e.g., running on the user's smart phone) by the user.
The VHP may facilitate video recording via video headphones at 105. In various embodiments, video headphones may be headphones with an embedded and/or attached video camera. In various implementations, video headphones may include features such as HD premium quality sound, pivoting ear pads for multi-angle recording, one or more HD (e.g., 1080p) video cameras, one or more dynamic microphones, audio and/or video controls (e.g., record video, adjust volume, skip forward and/or back, mute) integrated into a headphone cable, and/or the like. In one implementation, the video headphones may include a video camera on one of the earpieces, and the video camera may have a microphone (e.g., located underneath the video camera). In another implementation, the video headphones may include two video cameras, one on each earpiece, and each video camera may have a microphone. A video camera and/or the accompanying microphone, if the video camera has a microphone, may pivot and/or swivel (e.g., 360 degrees in any direction) to allow the user to record video in any direction. For example, a user may angle the video camera up to record a video of a bird in a tree. In another example, the user may point one video camera straight ahead and the other video camera towards the back to record a split screen of what is in front and behind the user. In yet another example, the user may position both video cameras in such a way (e.g., both video cameras pointing in the same direction) as to allow three dimensional (3D) video recording. The video headphones may be connected (e.g., via a headphone cable, via a wireless technology capable of transmitting HD video) to the user's client (e.g., a smart phone, a portable media player, a tablet) and may record and transmit the video (e.g., including video and/or audio) to the client (e.g., via the VHP mobile app). For example, the video may be stored locally on the client. In another example, the video may be stored remotely (e.g., on a remote server). In one implementation, the video may be of any desired length. In another implementation, a minimum and/or a maximum length for the video (e.g., 15 seconds) may be specified.
A determination may be made at 110 whether the user wishes to trim the recorded video. In one embodiment, this determination may be made by prompting the user to indicate whether the user wishes to trim the video (e.g., via a “would you like to trim the video?” prompt). In another embodiment, this determination may be made by displaying a video selection widget via the VHP mobile app and allowing the user to trim the video via the video selection widget if the user chooses to do so.
If the user wishes to trim the video, a desired video segment may be determined at 115. In one embodiment, the user may trim the video by dragging a video selection widget of the VHP mobile app to select a video segment of a predetermined size (e.g., a 10 second video segment). In another embodiment, the user may trim the video by expanding and/or shrinking the size of a video selection widget of the VHP mobile app to select a desired video segment. In yet another embodiment, the user may combine multiple videos (e.g., the current video and one or more previously recorded videos) into one video. The video may be trimmed to the desired video segment at 120.
A determination may be made at 125 whether the user wishes to add audio to the video. In one embodiment, this determination may be made by prompting the user to indicate whether the user wishes to add audio to the video (e.g., via a “would you like to add audio?” prompt). In another embodiment, this determination may be made by facilitating user selection of audio via the VHP mobile app and allowing the user to add audio to the video if the user chooses to do so.
If the user wishes to add audio to the video, the VHP may facilitate audio selection at 130. In one embodiment, the user may select audio (e.g., music) from the user's audio collection (e.g., by pressing a “My Music” button of the VHP mobile app). In one implementation, the user may select a music album and/or track (e.g., a song) and/or a playlist from the user's music collection. The user may also utilize an audio selection widget to select the desired portion of the selected audio to be added to the video. For example, the length of the selected audio portion may be set to be equal to the length of the video. In another implementation, the VHP may suggest audio to the user that well matches actions in the video. For example, the VHP may suggest songs and/or playlists and/or audio portions whose tempo matches the actions in the video. In another embodiment, the user may select audio from the VHP's audio collection (e.g., by pressing a “VHP Library” button of the VHP mobile app). For example, the user may purchase music albums and/or songs and/or audio effects via the VHP mobile app. In one implementation, the user may select audio and/or a portion of the audio from the VHP's audio collection in a similar manner as described above with regard to the user's audio collection. In another implementation, the user may select audio from the VHP's audio collection based on suggestions from the VHP made in a similar manner as described above with regard to the user's audio collection.
A determination may be made at 135 whether the user wishes to adjust the audio. In one embodiment, this determination may be made by prompting the user to indicate whether the user wishes to adjust the audio (e.g., via a “would you like to adjust the audio?” prompt). In another embodiment, this determination may be made by facilitating user selection of audio adjustments via the VHP mobile app and allowing the user to adjust the audio if the user chooses to do so.
If the user wishes to adjust the audio, the VHP may facilitate desired audio adjustments at 140. In one embodiment, the user may adjust the audio by speeding up and/or slowing down the audio. For example, the user may utilize “Slow Down” and/or “Speed Up” buttons of the VHP mobile app to adjust audio speed (e.g., in discreet chunks, such as 2× or 3× faster or slower; continuously, such as based on the length of time that a button is pressed). In this embodiment, the length of the selected audio portion may vary based on the speed of the audio. For example, if the user speeds up a song, the user may be able to select a longer portion of the song. In another example, the user may choose to have an entire song play during the duration (e.g., 2 minutes) of the video, and the speed at which the song is played back may be adjusted accordingly (e.g., so that the entire song is played back in 2 minutes) by the VHP. In another embodiment, the user may adjust the audio by auto tuning the audio. For example, the user may utilize an “Auto Tune” button of the VHP mobile app. In yet another embodiment, the user may adjust the audio by adding sound effects to the audio. For example, the user may utilize a sound effects selection widget of the VHP mobile app.
The audio may be added to the video at 145. In one embodiment, the added audio may replace audio recorded in the video. In another embodiment, the added audio may be combined with audio recorded in the video. In some embodiments, the user may post artist credit (e.g., via a “Post Artist Credit” button of the VHP mobile app) for audio (e.g., a song) being used in the video. For example, the artist credit may scroll in a specified location (e.g., across the bottom of the video).
A determination may be made at 150 whether the user wishes to add video effects to the video. In one embodiment, this determination may be made by prompting the user to indicate whether the user wishes to add video effects to the video (e.g., via a “would you like to add video effects?” prompt). In another embodiment, this determination may be made by facilitating user selection of video effects via the VHP mobile app and allowing the user to add video effects to the video if the user chooses to do so.
If the user wishes to add video effects to the video, the VHP may determine desired video effects at 155. In one embodiment, the user may select desired video effects (e.g., sepia filter, black and white filter, monochromatic filter, a light filter, a frame around the video, speed up and/or slow down the video) via a video effect selection widget of the VHP mobile app. In another embodiment, the user may wish to add various video elements (e.g., a video start element, a video end element, a transition element, a comments element) to the video. For example, the user may wish to insert a comment into the video after an amusing scene in the video. The desired video effects may be added to the video at 160.
A description of the video may be obtained from the user at 165. In one embodiment, the description may include a title. In another embodiment, the description may include the user's description for the video. In some implementations, the description may have a minimum and/or a maximum size. For example, a title may have to be at least 1 character long and no more than 50 characters long. In another example, the user's description for the video may have to be no more than 148 characters. In yet another example, the minimum and/or the maximum size for the description may correspond to those specified by social networks on which the video may be shared (e.g., a maximum of 140 characters for Twitter).
The video may be added to the user's video library at 170. For example, the video may be stored (e.g., on the client, on a remote server) and added to the user's VHP profile. If the user chooses to share the video with other VHP users, the other VHP users may comment on the video, mark the video as favorite, forward the video to others, and/or the like. The user may also see how many times the video has been viewed, post comments, and/or the like.
A determination may be made at 175 whether the user wishes to share the video via one or more social networks (e.g., Facebook, Tumblr, Twitter, Instagram, Pinterest, Vimeo, YouTube). In one embodiment, this determination may be made by prompting the user to indicate whether the user wishes to share the video (e.g., via a “would you like to share the video?” prompt). In another embodiment, this determination may be made by facilitating user selection of social networks on which to share the video via the VHP mobile app and allowing the user to share the video if the user chooses to do so.
If the user wishes to share the video, social networks on which the user wishes to share the video may be determined at 180. In one embodiment, the user may select desired social networks via appropriate buttons of the VHP mobile app and press a “Share Now” button to initiate sharing on the selected social networks. In another embodiment, the user may specify default desired social networks (e.g., via the user's profile settings) so that the default desired social networks are preselected for the user, and the user may press a “Share Now” button to initiate sharing on the selected social networks. The video may be shared on the selected social networks at 185 (e.g., via appropriate APIs provided by the social networks).
FIG. 2 shows a data flow diagram in one embodiment of the VHP. FIG. 2 provides an example of how data may flow to, through, and/or from the VHP. In FIG. 2, a user 202 may provide a command to initiate video recording 221 to the client 210 (e.g., a smart phone, a portable media player, a tablet). In one embodiment, the user may provide the command to initiate video recording by pressing a record button on the user's video headphones 206. In another embodiment, the user may provide the command to initiate video recording by pressing a record button of a VHP mobile app on the client.
The client may send a video data request 225 to the video headphones. For example, the video data request may be in XML format and may include data such as a command to initiate video recording, video parameters (e.g., video resolution, video aspect ratio, audio quality), video recording length, and/or the like. The video headphones may begin and/or end video recording based on the video data request.
The video headphones may send a video data response 229 to the client. For example, the video data response may be in XML format and may include data such as the recorded video (e.g., including video and/or audio), video information (e.g., date and/or time of recording, location of the video), and/or the like.
The client may output an adjustments request 233 to the user. In various embodiments, the adjustments request may prompt the user to trim the video, to add audio to the video, to adjust audio in the video, to add video effects to the video, to provide a description of the video, to share the video, and/or the like. For example, the adjustments request may be output via a GUI of the VHP mobile app.
The user may input an adjustments response 237 into the client. In various embodiments, the adjustments response may indicate whether and/or how the user wishes to trim the video, to add audio to the video, to adjust audio in the video, to add video effects to the video, to describe the video, to share the video, and/or the like. For example, the adjustments response may be input via the GUI of the VHP mobile app.
If the user wishes to add audio (e.g., from the VHP's audio collection) to the video, the client may send an audio data request 241 to a VHP server 214. For example, the VHP server may store songs available from the VHP (e.g., in an audio data store 330 c). For example, the audio data request may be in XML format and may include data such as the user's identifier and/or password, an identifier of a requested song and/or album and/or playlist, audio parameters (e.g., audio format, audio quality in kbps), a payment method, and/or the like.
The VHP server may send an audio data response 245 to the client. For example, the audio data response may be in XML format and may include data such as the requested song and/or album and/or playlist, audio parameters, a payment confirmation, and/or the like. The client may add the obtained audio to the video and/or adjust the obtained audio and/or the video based on user instructions.
If the user wishes to share the video, the client may send a share request 249 to a social network 218. The share request may include the video and instruct the social network to post the video via the user's social network account. For example, the share request may be sent via the social network's API command and may include data such as the user's identifier and/or password on the social network, the video, the description of the video, video information (e.g., date and/or time of recording, location of the video obtained via the client's GPS), and/or the like. The social network may send a share response 253 to the client. For example, the share response may be sent via the social network's API command and may indicate whether the video was shared on the social network successfully.
The client may provide a video output 257 to the user. For example, the video output may inform the user whether the user's video has been stored (e.g., in a videos data store 330 d), added to the user's profile, shared on one or more social networks, and/or the like.

Detailed Description of the VHP Coordinator

FIG. 3 shows a block diagram illustrating an exemplary VHP coordinator in one embodiment of the VHP. The VHP coordinator facilitates the operation of the VHP via a computer system (e.g., one or more cloud computing systems, grid computing systems, virtualized computer systems, mainframe computers, servers, clients, nodes, desktops, mobile devices such as smart phones, cellular phones, tablets, personal digital assistants (PDAs), and/or the like, embedded computers, dedicated computers, a system on a chip (SOC)). For example, the VHP coordinator may receive, obtain, aggregate, process, generate, store, retrieve, send, delete, input, output, and/or the like data (including program data and program instructions); may execute program instructions; may communicate with computer systems, with nodes, with users, and/or the like. In various embodiments, the VHP coordinator may comprise a standalone computer system, a distributed computer system, a node in a computer network (i.e., a network of computer systems organized in a topology), a network of VHP coordinators, and/or the like. It is to be understood that the VHP coordinator and/or the various VHP coordinator elements (e.g., processor, system bus, memory, input/output devices) may be organized in any number of ways (i.e., using any number and configuration of computer systems, computer networks, nodes, VHP coordinator elements, and/or the like) to facilitate VHP operation. Furthermore, it is to be understood that the various VHP coordinator computer systems, VHP coordinator computer networks, VHP coordinator nodes, VHP coordinator elements, and/or the like may communicate among each other in any number of ways to facilitate VHP operation. As used in this disclosure, the term “user” refers generally to people and/or computer systems that interact with the VHP; the term “server” refers generally to a computer system, a program, and/or a combination thereof that handles requests and/or responds to requests from clients via a computer network; the term “client” refers generally to a computer system, a program, a user, and/or a combination thereof that generates requests and/or handles responses from servers via a computer network; the term “node” refers generally to a server, to a client, and/or to an intermediary computer system, program, and/or a combination thereof that facilitates transmission of and/or handling of requests and/or responses.
The VHP coordinator includes a processor 301 that executes program instructions (e.g., VHP program instructions). In various embodiments, the processor may be a general purpose microprocessor (e.g., a central processing unit (CPU)), a dedicated microprocessor (e.g., a graphics processing unit (GPU), a physics processing unit (PPU), a digital signal processor (DSP), a network processor, and/or the like), an external processor, a plurality of processors (e.g., working in parallel, distributed, and/or the like), a microcontroller (e.g., for an embedded system), and/or the like. The processor may be implemented using integrated circuits (ICs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and/or the like. In various implementations, the processor may comprise one or more cores, may include embedded elements (e.g., a coprocessor such as a math coprocessor, a cryptographic coprocessor, a physics coprocessor, and/or the like, registers, cache memory, software), may be synchronous (e.g., using a clock signal) or asynchronous (e.g., without a central clock), and/or the like. For example, the processor may be an AMD FX processor, an AMD Opteron processor, an AMID Geode LX processor, an Intel Core i7 processor, an Intel Xeon processor, an Intel Atom processor, an ARM Cortex processor, an IBM PowerPC processor, and/or the like.
The processor may be connected to system memory 305 via a system bus 303. The system bus may interconnect these and/or other elements of the VHP coordinator via electrical, electronic, optical, wireless, and/or the like communication links (e.g., the system bus may be integrated into a motherboard that interconnects VHP coordinator elements and provides power from a power supply). In various embodiments, the system bus may comprise one or more control buses, address buses, data buses, memory buses, peripheral buses, and/or the like. In various implementations, the system bus may be a parallel bus, a serial bus, a daisy chain design, a hub design, and/or the like. For example, the system bus may comprise a front-side bus, a back-side bus, AMD's HyperTransport, Intel's QuickPath Interconnect, a peripheral component interconnect (PCI) bus, an accelerated graphics port (AGP) bus, a PCI Express bus, a low pin count (LPC) bus, a universal serial bus (USB), and/or the like. The system memory, in various embodiments, may comprise registers, cache memory (e.g., level one, level two, level three), read only memory (ROM) (e.g., BIOS, flash memory), random access memory (RAM) (e.g., static RAM (SRAM), dynamic RAM (DRAM), error-correcting code (ECC) memory), and/or the like. The system memory may be discreet, external, embedded, integrated into a CPU, and/or the like. The processor may access, read from, write to, store in, erase, modify, and/or the like, the system memory in accordance with program instructions (e.g., VHP program instructions) executed by the processor. The system memory may facilitate accessing, storing, retrieving, modifying, deleting, and/or the like data (e.g., VHP data) by the processor.
In various embodiments, input/output devices 310 may be connected to the processor and/or to the system memory, and/or to one another via the system bus.
In some embodiments, the input/output devices may include one or more graphics devices 311. The processor may make use of the one or more graphic devices in accordance with program instructions (e.g., VHP program instructions) executed by the processor. In one implementation, a graphics device may be a video card that may obtain (e.g., via a connected video camera), process (e.g., render a frame), output (e.g., via a connected monitor, television, and/or the like), and/or the like graphical (e.g., multimedia, video, image, text) data (e.g., VHP data). A video card may be connected to the system bus via an interface such as PCI, AGP, PCI Express, USB, PC Card, ExpressCard, and/or the like. A video card may use one or more graphics processing units (GPUs), for example, by utilizing AMD's CrossFireX and/or NVIDIA's SLI technologies. A video card may be connected via an interface (e.g., video graphics array (VGA), digital video interface (DVI), Mini-DVI, Micro-DVI, high-definition multimedia interface (HDMI), DisplayPort, Thunderbolt, composite video, S-Video, component video, and/or the like) to one or more displays (e.g., cathode ray tube (CRT), liquid crystal display (LCD), touchscreen, and/or the like) that display graphics. For example, a video card may be an AMD Radeon HD 6990, an ATI Mobility Radeon HD 5870, an AMD FirePro V9800P, an AMD Radeon E6760 MXM V3.0 Module, an NVIDIA GeForce GTX 590, an NVIDIA GeForce GTX 580M, an Intel HD Graphics 3000, and/or the like. In another implementation, a graphics device may be a video capture board that may obtain (e.g., via coaxial cable), process (e.g., overlay with other graphical data), capture, convert (e.g., between different formats, such as MPEG2 to H.264), and/or the like graphical data. A video capture board may be and/or include a TV tuner, may be compatible with a variety of broadcast signals (e.g., NTSC, PAL, ATSC, QAM) may be a part of a video card, and/or the like. For example, a video capture board may be an ATI All-in-Wonder HD, a Hauppauge ImpactVBR 01381, a Hauppauge WinTV-HVR-2250, a Hauppauge Colossus 01414, and/or the like. A graphics device may be discreet, external, embedded, integrated into a CPU, and/or the like. A graphics device may operate in combination with other graphics devices (e.g., in parallel) to provide improved capabilities, data throughput, color depth, and/or the like.
In some embodiments, the input/output devices may include one or more audio devices 313. The processor may make use of the one or more audio devices in accordance with program instructions (e.g., VHP program instructions) executed by the processor. In one implementation, an audio device may be a sound card that may obtain (e.g., via a connected microphone), process, output (e.g., via connected speakers), and/or the like audio data (e.g., VHP data). A sound card may be connected to the system bus via an interface such as PCI, PCI Express, USB, PC Card, ExpressCard, and/or the like. A sound card may be connected via an interface (e.g., tip sleeve (TS), tip ring sleeve (TRS), RCA, TOSLINK, optical) to one or more amplifiers, speakers (e.g., mono, stereo, surround sound), subwoofers, digital musical instruments, and/or the like. For example, a sound card may be an Intel AC'97 integrated codec chip, an Intel HD Audio integrated codec chip, a Creative Sound Blaster X-Fi Titanium HD, a Creative Sound Blaster X-Fi Go! Pro, a Creative Sound Blaster Recon 3D, a Turtle Beach Riviera, a Turtle Beach Amigo II, and/or the like. An audio device may be discreet, external, embedded, integrated into a motherboard, and/or the like. An audio device may operate in combination with other audio devices (e.g., in parallel) to provide improved capabilities, data throughput, audio quality, and/or the like.
In some embodiments, the input/output devices may include one or more network devices 315. The processor may make use of the one or more network devices in accordance with program instructions (e.g., VHP program instructions) executed by the processor. In one implementation, a network device may be a network card that may obtain (e.g., via a Category 5 Ethernet cable), process, output (e.g., via a wireless antenna), and/or the like network data (e.g., VHP data). A network card may be connected to the system bus via an interface such as PCI, PCI Express, USB, FireWire, PC Card, ExpressCard, and/or the like. A network card may be a wired network card (e.g., 10/100/1000, optical fiber), a wireless network card (e.g., Wi-Fi 802.11a/b/g/n/ac/ad, Bluetooth, Near Field Communication (NFC), TransferJet), a modem (e.g., dialup telephone-based, asymmetric digital subscriber line (ADSL), cable modem, power line modem, wireless modem based on cellular protocols such as high speed packet access (HSPA), evolution-data optimized (EV-DO), global system for mobile communications (GSM), worldwide interoperability for microwave access (WiMax), long term evolution (LTE), and/or the like, satellite modem, FM radio modem, radio-frequency identification (RFID) modem, infrared (IR) modem), and/or the like. For example, a network card may be an Intel EXPI9301CT, an Intel EXPI9402PT, a LINKSYS USB300M, a BUFFALO WLI-UC-G450, a Rosewill RNX-MiniN1, a TRENDnet TEW-623PI, a Rosewill RNX-N180UBE, an ASUS USB-BT211, a MOTOROLA SB6120, a U.S. Robotics USR5686G, a Zoom 5697-00-00F, a TRENDnet TPL-401E2K, a D-Link DHP-W306AV, a StarTech ET91000SC, a Broadcom BCM20791, a Broadcom InConcert BCM4330, a Broadcom BCM4360, an LG VL600, a Qualcomm MDM9600, a Toshiba TC35420 TransferJet device, and/or the like. A network device may be discreet, external, embedded, integrated into a motherboard, and/or the like. A network device may operate in combination with other network devices (e.g., in parallel) to provide improved data throughput, redundancy, and/or the like. For example, protocols such as link aggregation control protocol (LACP) based on IEEE 802.3AD-2000 or IEEE 802.1AX-2008 standards may be used. A network device may be used to connect to a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a personal area network, the Internet, an intranet, a Bluetooth network, an NFC network, a Wi-Fi network, a cellular network, and/or the like.
In some embodiments, the input/output devices may include one or more peripheral devices 317. The processor may make use of the one or more peripheral devices in accordance with program instructions (e.g., VHP program instructions) executed by the processor. In various implementations, a peripheral device may be a digital camera, a video camera, a webcam, an electronically moveable pan tilt zoom (PTZ) camera, a monitor, a touchscreen display, active shutter 3D glasses, head-tracking 3D glasses, a remote control, an audio line-in, an audio line-out, a microphone, headphones, speakers, a subwoofer, a router, a hub, a switch, a firewall, an antenna, a keyboard, a mouse, a trackpad, a trackball, a digitizing tablet, a stylus, a joystick, a gamepad, a game controller, a force-feedback device, a laser, sensors (e.g., proximity sensor, rangefinder, ambient temperature sensor, ambient light sensor, humidity sensor, an accelerometer, a gyroscope, a motion sensor, an olfaction sensor, a biosensor, a chemical sensor, a magnetometer, a radar, a sonar, a location sensor such as global positioning system (GPS), Galileo, GLONASS, and/or the like), a printer, a fax, a scanner, a copier, a card reader, and/or the like. A peripheral device may be connected to the system bus via an interface such as PCI, PCI Express, USB, FireWire, VGA, DVI, Mini-DVI, Micro-DVI, HDMI, DisplayPort, Thunderbolt, composite video, S-Video, component video, PC Card, ExpressCard, serial port, parallel port, PS/2, TS, TRS, RCA, TOSLINK, network connection (e.g., wired such as Ethernet, optical fiber, and/or the like, wireless such as Wi-Fi, Bluetooth, NFC, cellular, and/or the like), a connector of another input/output device, and/or the like. A peripheral device may be discreet, external, embedded, integrated (e.g., into a processor, into a motherboard), and/or the like. A peripheral device may operate in combination with other peripheral devices (e.g., in parallel) to provide the VHP coordinator with a variety of input, output and processing capabilities.
In some embodiments, the input/output devices may include one or more storage devices 319. The processor may access, read from, write to, store in, erase, modify, and/or the like a storage device in accordance with program instructions (e.g., VHP program instructions) executed by the processor. A storage device may facilitate accessing, storing, retrieving, modifying, deleting, and/or the like data (e.g., VHP data) by the processor. In one implementation, the processor may access data from the storage device directly via the system bus. In another implementation, the processor may access data from the storage device by instructing the storage device to transfer the data to the system memory and accessing the data from the system memory. In various embodiments, a storage device may be a hard disk drive (HDD), a solid-state drive (SSD), a floppy drive using diskettes, an optical disk drive (e.g., compact disk (CD-ROM) drive, CD-Recordable (CD-R) drive, CD-Rewriteable (CD-RW) drive, digital versatile disc (DVD-ROM) drive, DVD-R drive, DVD-RW drive, Blu-ray disk (BD) drive) using an optical medium, a magnetic tape drive using a magnetic tape, a memory card (e.g., a USB flash drive, a compact flash (CF) card, a secure digital extended capacity (SDXC) card), a network attached storage (NAS), a direct-attached storage (DAS), a storage area network (SAN), other processor-readable physical mediums, and/or the like. A storage device may be connected to the system bus via an interface such as PCI, PCI Express, USB, FireWire, PC Card, ExpressCard, integrated drive electronics (IDE), serial advanced technology attachment (SATA), external SATA (eSATA), small computer system interface (SCSI), serial attached SCSI (SAS), fibre channel (FC), network connection (e.g., wired such as Ethernet, optical fiber, and/or the like; wireless such as Wi-Fi, Bluetooth, NFC, cellular, and/or the like), and/or the like. A storage device may be discreet, external, embedded, integrated (e.g., into a motherboard, into another storage device), and/or the like. A storage device may operate in combination with other storage devices to provide improved capacity, data throughput, data redundancy, and/or the like. For example, protocols such as redundant array of independent disks (RAID) (e.g., RAID 0 (striping), RAID 1 (mirroring), RAID 5 (striping with distributed parity), hybrid RAID), just a bunch of drives (JBOD), and/or the like may be used. In another example, virtual and/or physical drives may be pooled to create a storage pool. In yet another example, an SSD cache may be used with a HDD to improve speed.
Together and/or separately the system memory 305 and the one or more storage devices 319 may be referred to as memory 320 (i.e., physical memory).
VHP memory 320 contains processor-operable (e.g., accessible) VHP data stores 330. Data stores 330 comprise data that may be used (e.g., by the VHP) via the VHP coordinator. Such data may be organized using one or more data formats such as a database (e.g., a relational database with database tables, an object-oriented database, a graph database, a hierarchical database), a flat file (e.g., organized into a tabular format), a binary file (e.g., a GIF file, an MPEG-4 file), a structured file (e.g., an HTML file, an XML file), a text file, and/or the like. Furthermore, data may be organized using one or more data structures such as an array, a queue, a stack, a set, a linked list, a map, a tree, a hash, a record, an object, a directed graph, and/or the like. In various embodiments, data stores may be organized in any number of ways (i.e., using any number and configuration of data formats, data structures, VHP coordinator elements, and/or the like) to facilitate VHP operation. For example, VHP data stores may comprise data stores 330 a-d implemented as one or more databases. A users data store 330 a may be a collection of database tables that include fields such as UserID, UserName, UserPreferences, UserVideos, UserSocialNetworks, and/or the like. A clients data store 330 b may be a collection of database tables that include fields such as ClientID, ClientName, ClientDeviceType, ClientScreenResolution, and/or the like. An audio data store 330 c may be a collection of database tables that include fields such as AudioID, AudioAlbum, AudioPlaylist, AudioFormat, AudioQuality, AudioPrice, and/or the like. A videos data store 330 d may be a collection of database tables that include fields such as VideoID, VideoTitle, VideoDescription, VideoResolution, VideoEffects, VideoSharingSettings, and/or the like. The VHP coordinator may use data stores 330 to keep track of inputs, parameters, settings, variables, records, outputs, and/or the like.
VHP memory 320 contains processor-operable (e.g., executable) VHP components 340. Components 340 comprise program components (including program instructions and any associated data stores) that are executed (e.g., by the VHP) via the VHP coordinator (i.e., via the processor) to transform VHP inputs into VHP outputs. It is to be understood that the various components and their subcomponents, capabilities, applications, and/or the like may be organized in any number of ways (i.e., using any number and configuration of components, subcomponents, capabilities, applications, VHP coordinator elements, and/or the like) to facilitate VHP operation. Furthermore, it is to be understood that the various components and their subcomponents, capabilities, applications, and/or the like may communicate among each other in any number of ways to facilitate VHP operation. For example, the various components and their subcomponents, capabilities, applications, and/or the like may be combined, integrated, consolidated, split up, distributed, and/or the like in any number of ways to facilitate VHP operation. In another example, a single or multiple instances of the various components and their subcomponents, capabilities, applications, and/or the like may be instantiated on each of a single VHP coordinator node, across multiple VHP coordinator nodes, and/or the like.
In various embodiments, program components may be developed using one or more programming languages, techniques, tools, and/or the like such as an assembly language, Ada, BASIC, C, C++, C#, COBOL, Fortran, Java, LabVIEW, Lisp, Mathematica, MATLAB, OCaml, PL/I, Smalltalk, Visual Basic for Applications (VBA), HTML, XML, CSS, JavaScript, JavaScript Object Notation (JSON), PHP, Perl, Ruby, Python, Asynchronous JavaScript and XML (AJAX), Simple Object Access Protocol (SOAP), SSL, ColdFusion, Microsoft .NET, Apache modules, Adobe Flash, Adobe AIR, Microsoft Silverlight, Windows PowerShell, batch files, Tcl, graphical user interface (GUI) toolkits, SQL, database adapters, web application programming interfaces (APIs), application server extensions, integrated development environments (IDEs), libraries (e.g., object libraries, class libraries, remote libraries), remote procedure calls (RPCs), Common Object Request Broker Architecture (CORBA), and/or the like.
In some embodiments, components 340 may include an operating environment component 340 a. The operating environment component may facilitate operation of the VHP via various subcomponents.
In some implementations, the operating environment component may include an operating system subcomponent. The operating system subcomponent may provide an abstraction layer that facilitates the use of, communication among, common services for, interaction with, security of and/or the like of various VHP coordinator elements, components, data stores, and/or the like.
In some embodiments, the operating system subcomponent may facilitate execution of program instructions (e.g., VHP program instructions) by the processor by providing process management capabilities. For example, the operating system subcomponent may facilitate the use of multiple processors, the execution of multiple processes, multitasking, and/or the like.
In some embodiments, the operating system subcomponent may facilitate the use of memory by the VHP. For example, the operating system subcomponent may allocate and/or free memory, facilitate memory addressing, provide memory segmentation and/or protection, provide virtual memory capability, facilitate caching, and/or the like. In another example, the operating system subcomponent may include a file system (e.g., File Allocation Table (FAT), New Technology File System (NTFS), Hierarchical File System Plus (HFS+), Universal Disk Format (UDF), Linear Tape File System (LTFS)) to facilitate storage, retrieval, deletion, aggregation, processing, generation, and/or the like of data.
In some embodiments, the operating system subcomponent may facilitate operation of and/or processing of data for and/or from input/output devices. For example, the operating system subcomponent may include one or more device drivers, interrupt handlers, file systems, and/or the like that allow interaction with input/output devices.
In some embodiments, the operating system subcomponent may facilitate operation of the VHP coordinator as a node in a computer network by providing support for one or more communications protocols. For example, the operating system subcomponent may include support for the internet protocol suite (i.e., Transmission Control Protocol/Internet Protocol (TCP/IP)) of network protocols such as TCP, IP, User Datagram Protocol (UDP), Mobile IP, and/or the like. In another example, the operating system subcomponent may include support for security protocols (e.g., Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), WPA2) for wireless computer networks. In yet another example, the operating system subcomponent may include support for virtual private networks (VPNs).
In some embodiments, the operating system subcomponent may facilitate security of the VHP coordinator. For example, the operating system subcomponent may provide services such as authentication, authorization, audit, network intrusion-detection capabilities, firewall capabilities, antivirus capabilities, and/or the like.
In some embodiments, the operating system subcomponent may facilitate user interaction with the VHP by providing user interface elements that may be used by the VHP to generate a user interface. In one implementation, such user interface elements may include widgets (e.g., windows, dialog boxes, scrollbars, menu bars, tabs, ribbons, menus, buttons, text boxes, checkboxes, combo boxes, drop-down lists, list boxes, radio buttons, sliders, spinners, grids, labels, progress indicators, icons, tooltips, and/or the like) that may be used to obtain input from and/or provide output to the user. For example, such widgets may be used via a widget toolkit such as Microsoft Foundation Classes (MFC), Apple Cocoa Touch, Java Swing, GTK+, Qt, Yahoo! User Interface Library (YUI), and/or the like. In another implementation, such user interface elements may include sounds (e.g., event notification sounds stored in MP3 file format), animations, vibrations, and/or the like that may be used to inform the user regarding occurrence of various events. For example, the operating system subcomponent may include a user interface such as Windows Aero, Mac OS X Aqua, GNOME Shell, KDE Plasma Workspaces (e.g., Plasma Desktop, Plasma Netbook, Plasma Contour, Plasma Mobile), and/or the like.
In various embodiments the operating system subcomponent may comprise a single-user operating system, a multi-user operating system, a single-tasking operating system, a multitasking operating system, a single-processor operating system, a multiprocessor operating system, a distributed operating system, an embedded operating system, a real-time operating system, and/or the like. For example, the operating system subcomponent may comprise an operating system such as UNIX, LINUX, IBM i, Sun Solaris, Microsoft Windows Server, Microsoft DOS, Microsoft Windows 7, Apple Mac OS X, Apple iOS, Android, Symbian, Windows Phone 7, Blackberry QNX, and/or the like.
In some implementations, the operating environment component may include a database subcomponent. The database subcomponent may facilitate VHP capabilities such as storage, analysis, retrieval, access, modification, deletion, aggregation, generation, and/or the like of data (e.g., the use of data stores 330). The database subcomponent may make use of database languages (e.g., Structured Query Language (SQL), XQuery), stored procedures, triggers, APIs, and/or the like to provide these capabilities. In various embodiments the database subcomponent may comprise a cloud database, a data warehouse, a distributed database, an embedded database, a parallel database, a real-time database, and/or the like. For example, the database subcomponent may comprise a database such as Microsoft SQL Server, Microsoft Access, MySQL, IBM DB2, Oracle Database, and/or the like.
In some implementations, the operating environment component may include an information handling subcomponent. The information handling subcomponent may provide the VHP with capabilities to serve, deliver, upload, obtain, present, download, and/or the like a variety of information. The information handling subcomponent may use protocols such as Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), Telnet, Secure Shell (SSH), Transport Layer Security (TLS), Secure Sockets Layer (SSL), peer-to-peer (P2P) protocols (e.g., BitTorrent), and/or the like to handle communication of information such as web pages, files, multimedia content (e.g., streaming media), applications, and/or the like.
In some embodiments, the information handling subcomponent may facilitate the serving of information to users, VHP components, nodes in a computer network, web browsers, and/or the like. For example, the information handling subcomponent may comprise a web server such as Apache HTTP Server, Microsoft Internet Information Services (IIS), Oracle WebLogic Server, Adobe Flash Media Server, Adobe Content Server, and/or the like. Furthermore, a web server may include extensions, plug-ins, add-ons, servlets, and/or the like. For example, these may include Apache modules, IIS extensions, Java servlets, and/or the like. In some implementations, the information handling subcomponent may communicate with the database subcomponent via standards such as Open Database Connectivity (ODBC), Java Database Connectivity (JDBC), ActiveX Data Objects for .NET (ADO.NET), and/or the like. For example, the information handling subcomponent may use such standards to store, analyze, retrieve, access, modify, delete, aggregate, generate, and/or the like data (e.g., data from data stores 330) via the database subcomponent.
In some embodiments, the information handling subcomponent may facilitate presentation of information obtained from users, VHP components, nodes in a computer network, web servers, and/or the like. For example, the information handling subcomponent may comprise a web browser such as Microsoft Internet Explorer, Mozilla Firefox, Apple Safari, Google Chrome, Opera Mobile, Amazon Silk, Nintendo 3DS Internet Browser, and/or the like. Furthermore, a web browser may include extensions, plug-ins, add-ons, applets, and/or the like. For example, these may include Adobe Flash Player, Adobe Acrobat plug-in, Microsoft Silverlight plug-in, Microsoft Office plug-in, Java plug-in, and/or the like.
In some implementations, the operating environment component may include a messaging subcomponent. The messaging subcomponent may facilitate VHP message communications capabilities. The messaging subcomponent may use protocols such as Simple Mail Transfer Protocol (SMTP), Internet Message Access Protocol (IMAP), Post Office Protocol (POP), Extensible Messaging and Presence Protocol (XMPP), Real-time Transport Protocol (RTP), Internet Relay Chat (IRC), Skype protocol, AOL's Open System for Communication in Realtime (OSCAR), Messaging Application Programming Interface (MAPI), Facebook API, and/or the like to facilitate VHP message communications. The messaging subcomponent may facilitate message communications such as email, instant messaging, Voice over IP (VoIP), video conferencing, Short Message Service (SMS), web chat, and/or the like. For example, the messaging subcomponent may comprise Microsoft Exchange Server, Microsoft Outlook, Sendmail, IBM Lotus Domino, Gmail, AOL Instant Messenger (AIM), Yahoo Messenger, ICQ, Trillion, Skype, Google Talk, Apple FaceTime, Apple iChat, Facebook Chat, and/or the like.
In some implementations, the operating environment component may include a security subcomponent that facilitates VHP security. In some embodiments, the security subcomponent may restrict access to the VHP, to one or more services provided by the VHP, to data associated with the VHP (e.g., stored in data stores 330), to communication messages associated with the VHP, and/or the like to authorized users. Access may be granted via a login screen, via an API that obtains authentication information, via an authentication token, and/or the like. For example, the user may obtain access by providing a username and/or a password (e.g., a string of characters, a picture password), a personal identification number (PIN), an identification card, a magnetic stripe card, a smart card, a biometric identifier (e.g., a finger print, a voice print, a retina scan, a face scan), a gesture (e.g., a swipe), a media access control (MAC) address, an IP address, and/or the like. Various security models such as access-control lists (ACLs), capability-based security, hierarchical protection domains, and/or the like may be used to control access. For example, the security subcomponent may facilitate digital rights management (DRM), network intrusion detection, firewall capabilities, and/or the like.
In some embodiments, the security subcomponent may use cryptographic techniques to secure information (e.g., by storing encrypted data), verify message authentication (e.g., via a digital signature), provide integrity checking (e.g., a checksum), and/or the like by facilitating encryption and/or decryption of data. Furthermore, steganographic techniques may be used instead of or in combination with cryptographic techniques. Cryptographic techniques used by the VHP may include symmetric key cryptography using shared keys (e.g., using one or more block ciphers such as triple Data Encryption Standard (DES), Advanced Encryption Standard (AES); stream ciphers such as Rivest Cipher 4 (RC4), Rabbit), asymmetric key cryptography using a public key/private key pair (e.g., using algorithms such as Rivest-Shamir-Adleman (RSA), Digital Signature Algorithm (DSA)), cryptographic hash functions (e.g., using algorithms such as Message-Digest 5 (MD5), Secure Hash Algorithm 2 (SHA-2)), and/or the like. For example, the security subcomponent may comprise a cryptographic system such as Pretty Good Privacy (PGP).
In some implementations, the operating environment component may include a virtualization subcomponent that facilitates VHP virtualization capabilities. In some embodiments, the virtualization subcomponent may provide support for platform virtualization (e.g., via a virtual machine). Platform virtualization types may include full virtualization, partial virtualization, paravirtualization, and/or the like. In some implementations, platform virtualization may be hardware-assisted (e.g., via support from the processor using technologies such as AMD-V, Intel VT-x, and/or the like). In some embodiments, the virtualization subcomponent may provide support for various other virtualized environments such as via operating-system level virtualization, desktop virtualization, workspace virtualization, mobile virtualization, application virtualization, database virtualization, and/or the like. In some embodiments, the virtualization subcomponent may provide support for various virtualized resources such as via memory virtualization, storage virtualization, data virtualization, network virtualization, and/or the like. For example, the virtualization subcomponent may comprise VMware software suite (e.g., VMware Server, VMware Workstation, VMware Player, VMware ESX, VMware ESXi, VMware ThinApp, VMware Infrastructure), Parallels software suite (e.g., Parallels Server, Parallels Workstation, Parallels Desktop, Parallels Mobile, Parallels Virtuozzo Containers), Oracle software suite (e.g., Oracle VM Server for SPARC, Oracle VM Server for x86, Oracle VM VirtualBox, Oracle Solaris 10, Oracle Solaris 11), Informatica Data Services, Wine, and/or the like.
In some embodiments, components 340 may include a user interface component 340 b. The user interface component may facilitate user interaction with the VHP by providing a user interface. In various implementations, the user interface component may include programmatic instructions to obtain input from and/or provide output to the user via physical controls (e.g., physical buttons, switches, knobs, wheels, dials), textual user interface, audio user interface, GUI, voice recognition, gesture recognition, touch and/or multi-touch user interface, messages, APIs, and/or the like. In some implementations, the user interface component may make use of the user interface elements provided by the operating system subcomponent of the operating environment component. For example, the user interface component may make use of the operating system subcomponent's user interface elements via a widget toolkit. In some implementations, the user interface component may make use of information presentation capabilities provided by the information handling subcomponent of the operating environment component. For example, the user interface component may make use of a web browser to provide a user interface via HTML5, Adobe Flash, Microsoft Silverlight, and/or the like.
In some embodiments, components 340 may include any of the components WVS 340 c described in more detail in preceding figures.

The Embodiments of the VHP

The entirety of this disclosure (including the written description, figures, claims, abstract, appendices, and/or the like) for VIDEO HEADPHONES PLATFORM METHODS, APPARATUSES AND MEDIA shows various embodiments via which the claimed innovations may be practiced. It is to be understood that these embodiments and the features they describe are a representative sample presented to assist in understanding the claimed innovations, and are not exhaustive and/or exclusive. As such, the various embodiments, implementations, examples, and/or the like are deemed non-limiting throughout this disclosure. Furthermore, alternate undescribed embodiments may be available (e.g., equivalent embodiments). Such alternate embodiments have not been discussed in detail to preserve space and/or reduce repetition. That alternate embodiments have not been discussed in detail is not to be considered a disclaimer of such alternate undescribed embodiments, and no inference should be drawn regarding such alternate undescribed embodiments relative to those discussed in detail in this disclosure. It is to be understood that such alternate undescribed embodiments may be utilized without departing from the spirit and/or scope of the disclosure. For example, the organizational, logical, physical, functional, topological, and/or the like structures of various embodiments may differ. In another example, the organizational, logical, physical, functional, topological, and/or the like structures of the VHP coordinator, VHP coordinator elements, VHP data stores, VHP components and their subcomponents, capabilities, applications, and/or the like described in various embodiments throughout this disclosure are not limited to a fixed operating order and/or arrangement, instead, all equivalent operating orders and/or arrangements are contemplated by this disclosure. In yet another example, the VHP coordinator, VHP coordinator elements, VHP data stores, VHP components and their subcomponents, capabilities, applications, and/or the like described in various embodiments throughout this disclosure are not limited to serial execution, instead, any number and/or configuration of threads, processes, instances, services, servers, clients, nodes, and/or the like that execute in parallel, concurrently, simultaneously, synchronously, asynchronously, and/or the like is contemplated by this disclosure. Furthermore, it is to be understood that some of the features described in this disclosure may be mutually contradictory, incompatible, inapplicable, and/or the like, and are not present simultaneously in the same embodiment. Accordingly, the various embodiments, implementations, examples, and/or the like are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims.
This disclosure includes innovations not currently claimed. Applicant reserves all rights in such currently unclaimed innovations including the rights to claim such innovations and to file additional provisional applications, nonprovisional applications, continuation applications, continuation-in-part applications, divisional applications, and/or the like. It is to be understood that while some embodiments of the VHP discussed in this disclosure have been directed to world view sharing video headphones, the innovations described in this disclosure may be readily applied to a wide variety of other fields and/or applications.

Further Disclosures

With a video headphone as disclosed herein users will be able to record video through a small camera embedded in the headphones themselves. Audio can also be recorded through microphones, which can be installed into the headphone cable control unit and also located underneath the video camera.
Once a user has finished recording video, audio can be added, music can be selected for the video and filters added. After the editing process has been completed, audio and video can be seamlessly synced and the output can be shared to desired social networks.
A video headphone as disclosed herein may be configured for use and with suitable wired interfacing to connect to an audio source as well as a SmartPhone USB connector.
The video headphone may stream audio and video signals to a SmartPhone for storage and later editing and/or uploading through a wire with audio and video controls on the controls that connects from video headphone to smartphone.
The video headphone may be worn and/or used by the user such that the camera's view may be adjusted to monitor what may be seen by the user and it's signal output may be combined with the audio source feed, such as that which is monitored by the user, and provided to an external SmartPhone.
Specific audio performance desired for the headphone device are those typical in professional use, i.e. bandwidth of 20 Hz to 20 kHz. Specific video performance desired for the camera attachment to the video headphone device shall permit image motion captures of 25 fps or better with a resolution adequate and similar to that which is commonly downloaded to SmartPhone devices from various video streaming and downloadable sources with typical formats such as MP4, FL V, MPEG, etc.
Packaging may include 3 connection types from headphone to various inputs of smartphone models. Connection 1 may be a Micro-USB to Apple iPhone, iPhone 3G, iPhone 4, iPhone 4S 30-Pin Style Charger Adapter Tip. Connection 2 may be a 3.5 mm Auxillary Cable Sync Connector. Connection 3 may be a Micro USB Cable.
An app for use with a video headphone may:

- Add filters to videos (e.g., sepia filter, black and white filter, monochromatic filter).
- record video (e.g., any length, for up to 15 seconds.)
- Provide the user with the ability to edit video by shortening timeline.
- Add various frames around video.

Audio features of a system according to the present invention may include:

- Ability to import songs from a user's playlist to video recording.
  - Ability to store the user's playlist locally on the user's device or on a web server.
  - WAY, AIFF, AU or raw header-less PCM; Formats with lossless compression, such as FLAC, Monkey's Audio (filename extension APE), WavPack (filename extension WV), TTA, ATRAC Advanced Lossless, Apple Lossless (filename extension m4a), MPEG-4 SLS, MPEG-4 ALS, MPEG-4 DST, Windows Media Audio Lossless (WMA Lossless), and Shorten (SHN), and/or the like audio formats may be supported.
- ability to sync the audio and video recording from any point in timeline to record final output.
- ability to upload final video to Facebook, Tumblr, twitter, instagram, pinterest, vimeo, youtube.
- ability to edit audio sound speed 2×, 3× faster or slower via a button.
- ability to edit audio sound with auto tune feature with a single button.
- ability to press a single button to post artist credit for song being used. The artist credit will scroll across video. Process is controlled by a one button process.

A system according to the present invention may:

- Provide a user with the ability to create a profile. This includes username, location, sex, age, email address.
- Provide ability to store user profile data at a central web database server using REST API.
- Provide Audio/video sync software to time to actions in video.
- Provide playlist suggestions of songs from users playlist that have the same tempo as the actions in video.
- Provide the ability for user to pay for audio and video features (e.g., video filters and audio enhancements).
- Provide the ability to combine 2 videos into one, edit music and make one video.

Claims

1. A processor-implemented method to share a world view video, comprising:

receiving via a processor a request to record a user's world view video;

recording via video headphones the world view video;

adjusting via the processor the world view video based on user instructions; and

sharing via the processor the adjusted world view video with the user's social network.

2. The method of claim 1, wherein the video headphones comprise audio headphones with an embedded video camera and a microphone.

3. The method of claim 1, wherein the adjusting the world view video comprises trimming the world view video.

4. The method of claim 1, wherein the adjusting the world view video comprises adding audio to the world view video.

5. The method of claim 1, wherein the adjusting the world view video comprises adding video effects to the world view video.