- Camera
- Internet
- Wake_Lock
- Access_fine_location
- Write_local_storage
Camera
Camera usage is the core feature of VideOSC. Each frame of the incoming video stream is scaled down to a user-defined size and the color information (red, green, blue) is sent to a listening device in the network using a protocol called Open Sound Control.
The camera usage within VideOSC is exclusivly set up to create control data. It will never
The camera usage within VideOSC is exclusivly set up to create control data. It will never
- store information on the device's local storage that has been retrieved through the device's camera
- access information stored on the device except information stored in the apllication's settings
- send or receive information to or from devices other the one that is defined by IP address in the application's settings (see "Network Settings")
Internet
The internet permission must be granted in order to send data within the local or a global network in Open Sound Control messages. Any data transmission happens unencrypted over UDP.
A single Open Sound Control message will contain the following information:
OSC messages coming from VideOSC will in the current application's version only contain numbers. It remains, however, within the user's responsibility how this data is processed.
As already mentioned earlier, the transmission is unencrypted. Especially within public networks (e. g. open WiFi networks) it can not be guaranteed that the transmitted data is not being read by third party. It is within the user's responsibility to secure the communication between VideOSC and any connected client (e. g. by using WiFi connections that are password-protected or allow communication only between authorized IP addresses).
OSC listeners within VideOSC are only set up to print received data to VideOSC's graphical user interface. They will never try to store or modify information outside VideOSC.
A single Open Sound Control message will contain the following information:
- A timestamp, indicating when the message was sent
- The message, containing the command name (a string like '/vosc/blue1') and one or more values (currently only numbers are sent and strings and numbers may be received)
- The IP address and port from which the message has been sent
- The port on which the message was received
OSC messages coming from VideOSC will in the current application's version only contain numbers. It remains, however, within the user's responsibility how this data is processed.
As already mentioned earlier, the transmission is unencrypted. Especially within public networks (e. g. open WiFi networks) it can not be guaranteed that the transmitted data is not being read by third party. It is within the user's responsibility to secure the communication between VideOSC and any connected client (e. g. by using WiFi connections that are password-protected or allow communication only between authorized IP addresses).
OSC listeners within VideOSC are only set up to print received data to VideOSC's graphical user interface. They will never try to store or modify information outside VideOSC.
Access_fine_location
VideOSC may transmit the current geo location of the device over OSC.
Write_external_storage
Android 7 (Nougat) seems to request that permission when trying to interact with the preferences database.
Wake_Lock
The Wake_Lock permission is used to prevent the device from being sent to sleep while VideOSC is running.
Aside from the afore described technical details VideOSC will never try to store any data outside its own settings. It will never try to make connections other than to IP addressses explicitely defined within the network settings of the application. It will not try to access data stored outside VideOSC.