How to install sView on Linux mint 18.03
To install sView on Linux mint 18.03
sView is an easy to use cross-platform stereoscopic 3D media player which can be used to view 3D images, videos, CAD models, etc. It deploys an independent application with a customized user-friendly interface. When it comes to the 3D Image Viewer of sView, you can use images of many popular formats such as JPEG, PNG, Web, etc. Also, the 3D Movie Player of sView is capable of playing several formats such as MKV, WebM, OGM, AVI, FLAC, and many others. In this tutorial, we will cover the installation of sView on linuxmint-18.03.
Installation
Add the repository of sView by using PPA.
linuxhelp ~ # add-apt-repository ppa:sview/stable
You are about to add the following PPA:
This is an official repository for sView project.
sView is an open-source cross-platform media player / viewer with additional features for displaying stereoscopic content.
It supports 360-degrees spherical and cubemap panoramas, images and videos in side-by-side / over-under stereoscopic formats,
and many other features.
.
.
.
hkp://keyserver.ubuntu.com:80
--recv-keys
E0F37BC3
gpg: requesting key E0F37BC3 from hkp server keyserver.ubuntu.com
gpg: key E0F37BC3: public key "Launchpad PPA for gkv311" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
Let's first start with updating the system repositories.
linuxhelp ~ # apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.canonical.com/ubuntu xenial InRelease [11.5 kB]
Get:3 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease [23.9 kB]
Ign:4 http://packages.linuxmint.com sylvia InRelease
Get:5 http://archive.canonical.com/ubuntu xenial/partner amd64 Packages [3,156 B]
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
.
.
.
Get:53 http://archive.ubuntu.com/ubuntu xenial-backports/universe i386 Packages [7,104 B]
Get:54 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [3,996 B]
Fetched 6,372 kB in 10s (589 kB/s)
Reading package lists... Done
Install the sView application run the following command.
linuxhelp ~ # apt-get install sview -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libconfig++9v5
The following NEW packages will be installed:
libconfig++9v5 sview
.
.
.
upgraded, 2 newly installed, 0 to remove and 440 not upgraded.
Need to get 7,373 kB of archives.
After this operation, 12.5 MB of additional disk space will be used.
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for mintsystem (8.3.4) ...
Setting up libconfig++9v5:amd64 (1.5-0.2) ...
Setting up sview (17.10-1~xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Once Installation is done you can access the application from the Menu as shown here.
Now, you can able to use the sview image viewer application.
Now, you can able to use the sview media player application.
The version of the sview image viewer.
The version of sview media player.
With this, the method to install sView on Linuxmint-18.03 comes to an end.
OS X stores application settings in XML format at “~/Library/Preferences/sview/” directory.
On other systems (e.g. Linux) sView uses libconfig+ library and stores all settings at “~/.config/sview/”.
Another reason might be a lack of GPU memory. Aero interface itself requires a significant amount of memory and driver might decide to release these resources in favor of 3D application has been launched by the user. This is not an issue for modern hardware equipped with gigabytes of dedicated GPU memory, but might be an issue for old ones with less than 256 MiB memory. Notice that most drivers also switch off Aero when any 3D application goes into full-screen mode regardless of the amount of on-board GPU memory.
However, sView doesn’t use video decoding APIs like DXVA, VDPAU or any other. The main reason is that such APIs do not fit well into existing video decoding/playback pipeline, requiring the significant redesign. With other issues like non-guarantied image quality, strict limitations on video codecs and dimensions, and the fact that most modern CPUs are fast enough to decode most popular video formats - there no reason to make these efforts for decoding on GPU (save the low-end PCs).