Adding VA icons, also restructuring download section

parent ce1d9051
......@@ -82,78 +82,25 @@
<div class="container">
<header class="major">
<h2>Download section</h2>
<p>Donwload Virtual Acoustics (VA) ready-to-use portable binary packages </p>
<p>Get Virtual Acoustics (VA) for Windows </p>
</header>
<div class="row 150%">
<div class="7u 12u$(medium)">
<!-- Content -->
<section id="content">
<h3>Preface</h3>
<p>From the very beginning, Virtual Acoustics has been used under <b>Windows</b> platforms. If you are a <b>Linux, Mac OSX or any other platform user</b>, <a href="#otherplatforms">read this</a>.
<br /><br />
VA is always in development and we constantly add new features or components. Therefore, we chose the version identifier to reflect the release year and added an ascending alphabetic character, like <code>v2018a</code>. This makes it easier to determine the release time, just like in Matlab and other applications.
<br /><br />
We <b>can not guarantee compatibility among VA versions</b>! The reason is, that we still update the interface for new powerful features. This is unfortunate, but can not be achieved with the resources we can afford. If you are interested in new features, you will have to pay the price and update everything, including the bindings you use.
<br /><br />
We adopt naming conventions for platforms and compiler versions from <a href="developers.html#ViSTA">ViSTA VR Toolkit</a>. This way, one can easily extract the target platform, such as <code>win32-x64</code> for a Windows operating system using a mixed 32 bit and 64 bit environment, or <code>vc12</code> to indicate that the binary package was built using the Microsoft Visual C++ Compiler Version 12. If you are missing redistributable libraries you can identify the required Microsoft installer by this suffix.
</p>
</section>
<section id="windows">
<h3>Latest release for 64-Bit Windows (v2018a)</h3>
<p><a href="download/VA.v2018a_win32-x64.vc12.zip">VA.v2018a_win32-x64.vc12</a><br />
+ VABase, VANet and VACore C++ developer package <br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAUnity and VAUnityExtensions <br />
+ VAServer command line interface application <br />
+ Redstart VA GUI application [BETA] <br />
- VAPython binding * <br />
<span style="font-size: 0.6em">* not available for this compiler version and Python 3.6</span> <br />
</p>
<p><a href="download/VA.v2018a_win32-x64.vc14.zip">VA.v2018a_win32-x64.vc14</a><br />
+ VABase and VANet C++ developer package <br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAPython binding for Python 3.6 <br />
+ VAUnity and VAUnityExtensions <br />
- VAServer command line interface application * <br />
- Redstart VA GUI application [BETA] * <br />
- VACore C++ developer package * <br />
<span style="font-size: 0.6em">* not available for this compiler version</span><br />
</p>
</section>
<!--
<section id="windows_archive">
<h3>Archive for Windows</h3>
<h4>v2018a</h4>
<p></p>
</section>
-->
<section id="otherplatforms">
<h3>Linux, Mac OSX and other platforms</h3>
<p>If you do not have a Windows system, you can still use VA. Unfortunately, we are not experienced in building binary packages for other platforms than Windows, hence you will have to build it from the source code. For more information, read the <a href="developers.html#otherplatforms">developer section</a> and get help from the <a href="help.html#community">community</a>.
<br /><br>
A common alternative way is to run the VA server application on a dedicated remote Windows PC with a proper ASIO interface, and control it from any other platform. This way, only the remote control part of VA has to be build on your platform. You will require no further third-party libraries except for the binding interface you choose (usually Matlab or Python). You can also run a Jupyter notebook along with VA on the Windows machine and remotely control everything using a web browser on any mobile device connected to the same network.
</p>
</section>
</div>
<div class="5u$ 12u$(medium)">
<!-- Sidebar -->
<section id="sidebar">
<section>
<h3>Windows portable builds</h3>
<p><a href="download/VA.v2018a_win32-x64.vc12.zip">VA.v2018a_win32-x64.vc12</a><br />
+ VABase, VANet and VACore C++ developer package <br />
<h3 align="center">Download full VA package for Windows</h3>
<p align="center">
<a style="margin-left: 20px; border-bottom: solid 0px" href="download/VA_full.v2018a_win32-x64.vc12.zip"><img src="images/VA_Redstart_for_windows.png" width="30%"></a><br />
</p>
<p>
<b>Build name: <a href="download/VA_full.v2018a_win32-x64.vc12.zip">VA_full.v2018a_win32-x64.vc12</b></a><br />
<i>Includes Redstart, VAServer, VC12 C++ programming libraries, all bindings (except Python) and Unity scripts.</i><br />
<br />
<b>Quick user guide</b>:<br />
Unpack to any location and run the batch scripts from the root folder to start a server application.<br />
<br />
<b>Details</b>:<br />
+ VABase, VANet and VACore C++ developer packages for Visual C++ Compiler Version 12 (Visual Studio 2013)<br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAUnity and VAUnityExtensions <br />
+ VAServer command line interface application <br />
......@@ -161,8 +108,23 @@
- VAPython binding * <br />
<span style="font-size: 0.6em">* not available for this compiler version and Python 3.6</span> <br />
</p>
<p><a href="download/VA.v2018a_win32-x64.vc14.zip">VA.v2018a_win32-x64.vc14</a><br />
+ VABase and VANet C++ developer package <br />
<hr />
<h3 align="center">Download VA binding package for Windows</h3>
<p align="center">
<a style="margin-left: 20px; border-bottom: solid 0px" href="download/VA_bindings.v2018a_win32-x64.vc12.zip"><img width="30%" src="images/VA_bindings_for_windows.png"></a><br />
</p>
<p>
<b>Build name: <a href="download/VA_bindings.v2018a_win32-x64.vc14.zip">VA_bindings.v2018a_win32-x64.vc14</a></b><br />
<i>Includes VC14 C++ programming libraries (except VACore), all bindings and Unity scripts, but no applications.</i><br />
<br />
<b>Quick user guide</b>:<br />
Unpack to any location. Add paths to <code>include</code>, <code>lib</code> and <code>bin</code> folders for C++ programming. For bindings, make sure the environment (Matlab, Python, C# framework) finds the corresponding folders.<br />
<br />
<b>Details</b>:
<br />
+ VABase and VANet C++ developer packages for Visual C++ Compiler Version 14 (Visual Studio 2015)<br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAPython binding for Python 3.6 <br />
+ VAUnity and VAUnityExtensions <br />
......@@ -171,14 +133,36 @@
- VACore * <br />
<span style="font-size: 0.6em">* not available for this compiler version</span><br />
</p>
<hr />
<h3>Linux, Mac OSX and other</h3>
<p>We have no experience in the distribution of binary packages for other platforms than Windows. But not all is lost! You can use VA if you build it for your platform, see <a href="developers.html">developer section</a>.<br />
</p>
<pp>If you do not have a Windows system, you can still use VA. Unfortunately, we are not experienced in building binary packages for other platforms than Windows, hence you will have to build it from the source code. For more information, read the <a href="developers.html#otherplatforms">developer section</a> and get help from the <a href="help.html#community">community</a>.
<br /><br>
A common alternative way is to run the VA server application on a dedicated remote Windows PC with a proper ASIO interface, and control it from any other platform. This way, you can use the Windows download package and you only have to build the remote control part of VA (the C++ interface libraries and/or bindings). You will require no further third-party libraries except for the binding interface you choose (usually Matlab or Python). You can also run a Jupyter notebook along with VA on the Windows machine and remotely control everything using a web browser on any mobile device connected to the same network.
</p>
</section>
<hr />
</section>
</div>
<!-- Content -->
<section id="content">
<h3>Some hints on VA packages</h3>
<p>From the very beginning, Virtual Acoustics has been developed and used under <b>Windows</b> platforms. With some efforts made, it is now also available for other platforms, but we have only few experience with Linux and can't guarantee smooth performance on other systems.
<br /><br />
VA is always in development and we constantly add new features or components. Therefore, we chose the version identifier to reflect the release year and added an ascending alphabetic character, like <code>v2018a</code>. This makes it easier to determine the release time, just like in Matlab and other applications.
<br /><br />
We <b>can not guarantee compatibility among VA versions</b>! The reason is, that we still update the interface for new powerful features. This is unfortunate, but can not be achieved with the resources we can afford. If you are interested in new features, you will have to pay the price and update everything, including the bindings you use.
<br /><br />
We adopt naming conventions for platforms and compiler versions from <a href="developers.html#ViSTA">ViSTA VR Toolkit</a>. This way, one can easily extract the target platform, such as <code>win32-x64</code> for a Windows operating system using a mixed 32 bit and 64 bit environment, or <code>vc12</code> to indicate that the binary package was built using the Microsoft Visual C++ Compiler Version 12. If you are missing redistributable libraries you can identify the required Microsoft installer by this suffix.
</p>
</section>
</div>
</div>
</div>
......
......@@ -96,6 +96,8 @@
<h2>What is Virtual Acoustics?</h2>
<p>Virtual Acoustics is a software that was created at the Institute of Technical Acoustics (ITA) at RWTH Aachen University in Germany over a decade ago as an auralization application - one of the first of its kind.<br />
<br>Now, after contribution of numerous bachelor, master and PhD theses, it has been reinvented to meet state-of-the-art standards in audio rendering and spatial audio reproduction.</p>
<p><img src="images/VA_logo_white_circle_white.png" align="center" width="20%" />
</p>
</header>
</div>
</section>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment