Replace all jpg images on SPAT Revolution by png ones

en_US/spat-revolution/Ecosystem_&_integration_Automation.qmd

@@ -2,7 +2,7 @@
 
 Almost all _SPAT Revolution_ parameters can be continuously controlled in real time using SPAT's high resolution _automated control_ features.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperAutomation2.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperAutomation2.png)
 
 Control data can be sent via _Open Sound Control_ (**OSC**) or through multiple _SPAT Revolution_ plug-ins in your **DAW**. 
 Parameter control can be played back from precomposed timelines, or performed, generated and captured in various ways.
@@ -19,6 +19,6 @@ If you are using _Figure53 Qlab_ for show control, spatial effects can be sent a
 
 Suppose you are working with algorithmic gesture generators and modulators. In that case, your control signals can be easily sent into the SPAT Renderer via OSC to distribute and control spatial sound sources in real time using your own control programs.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Generic/OSCIntegrationDiagram.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Generic/OSCIntegrationDiagram.png)
 
 **Get creative with spatial sound design using OSC and Spat!**

en_US/spat-revolution/Ecosystem_&_integration_Using_Hardware_IO.qmd

@@ -4,7 +4,7 @@
 
 When you have a high channel count hardware IO connected to your SPAT Revolution workstation, it is possible to receive signals from the hardware unit physical inputs into SPAT at the top of the setup environment and route to the units physical outputs at the bottom of the setup graph - these are labeled as 'Hardware' IO in SPAT.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/InputBlockLine.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/InputBlockLine.png)
 
 Hardware input connections could include:
 
@@ -22,7 +22,7 @@ Hardware input connections could include:
 
 Hardware input formats could be mono, stereo or a format with any number of channels. Channels could be set up as single virtual sources, or as group multichannel sources using only one input/source module.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/InputBlockFormat.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/InputBlockFormat.png)
 
 ## Distributed Hardware Workflow
 

en_US/spat-revolution/Spat_Environment_Master_Section_Modules.qmd

@@ -4,7 +4,7 @@
 
 The **Sum** row of modules is used to mix the output of two or more rooms of the same output configuration and in some contexts, to sum inputs directly without the use of room.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/ChannelBasedSession.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/ChannelBasedSession.png)
 
 The **Sum** module can handle different input configurations.
 It will Sum channels based on their channel names, so a correct naming convention is important.

en_US/spat-revolution/Spatialisation_Technology_Scene_based_streams.qmd

@@ -14,7 +14,7 @@ Ambisonic, as opposed to other surround and spatial techniques and methods, does
 
 When Ambisonics is played back on speakers, all the speakers contribute to the directional content, what one is hearing is not the sound coming from a specific speaker but from a specific direction.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperHOA3DTrack.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperHOA3DTrack.png)
 
 :::{.callout-note}
 Overview of a fifth-order HOA 3D Ambisonic File created by Tine Surell Lange.

en_US/spat-revolution/ThirdParty_BlackTrax.qmd

@@ -5,15 +5,15 @@ This provides a way to map BlackTrax tracking beacons with SPAT source objects a
 To do this, you will need to configure the output configuration of a BlackTrax system and have your SPAT (or multiple SPAT) computers networked on the same third-party network interface (NIC) of the BlackTrax server hardware.
 In the BlackTrax software, press on the output configuration button or access output configuration via the menu bar in the Settings section (shortcut ```Ctrl + T```).
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfigurationButton.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfigurationButton.png)
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxSettingsMenu.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxSettingsMenu.png)
 
 In the Output Configuration window, you must create with the ```+``` sign 1 (or multiple if running a main and a backup SPAT computer engine) output that will send tracking RTTrPM data to SPAT.
 Clicking the ```+``` sign will give you an edit window.
 
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfiguration.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfiguration.png)
 
 In the edit window, you will first label your output to the desired name (ex: SPAT Main).
 The output type will be RTTrPM, the third-party motion protocol of BlackTrax.
@@ -30,7 +30,7 @@ The port number should be left to the default port # ```24002``` as it is the Bl
 Press ```Apply``` and you are set with this step.
 
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWindows.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWindows.png)
 
 Pressing the Advanced button will give you some advanced options.
 Your default Coordinate System should be ```Stage```.
@@ -41,18 +41,18 @@ In the Active Output window, select your SPAT Main output.
 On the bottom right, select the Beacon you want data sent to and press Enable Selected.
 You can multi-select when pressing the ```CTRL``` key or select all with ```CTRL + A```.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWidonwsAdvancedSettings.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWidonwsAdvancedSettings.png)
 
 When done with all operations with BlackTrax, you want to ```Apply``` the changes to the system.
 You can, at this point, close the Output Configuration window and go back to the main BlackTrax page.
 You will want to apply the changes to the system.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWidonwsAdvancedSettingsApply.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxEditWidonwsAdvancedSettingsApply.png)
 
 You can confirm that you are sending data by returning to the Output Configuration page.
 The status will give you this information.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfigurationPage.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BlackTraxOutputConfigurationPage.png)
 
 Now let’s go and configure the SPAT software.
 In the preference page accessible by clicking on the top right button, you can scroll down to the BlackTrax preference
@@ -71,15 +71,15 @@ In the option are now Tracking options and a pull-down menu to choose the Tracki
 The list will be based on your Max Beacon preference.
 It is possible to have the same Index for multiple sources, allowing multiple sources to track a single beacon.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/SourceInspector.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/SourceInspector.png)
 
 Your second option is to assign a Beacon ID to an actual room to track the listener's position. Selecting a room will give you the room menu options.
 In the option are now Tracking options with a pull-down menu to choose the Tracking Index (the beacon ID number you want for this room listener).
 The list will be based on your Max Beacon preference. 
 A Tracking Scale setting is as well provide which would allow to scale the incoming data to adjust to your speaker output setup size if needed.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/RoomInspector.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Setup/RoomInspector.png)
 
 In the actual room output parameters in the room view, you will also see a tracking option become available.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Room/OutputTracking.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Room/OutputTracking.png)

en_US/spat-revolution/Third_Party_Bitwig_Studio.qmd

@@ -14,21 +14,21 @@ When using the Local Audio path (LAP), the buffer size and sample rate must be m
 In SPAT, you do this in the preferences, and in Bitwig, in the audio engine settings.
 If they don't match at first, you _may_ need to restart both applications to get the correct green sync status between the apps.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigPreferences.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigPreferences.png)
 
 ![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/Preference/HardwareIO.png)
 
 **Setting Up Tracks in BitWig**
 
 One good way to work with Bitwig and SPAT is to set Bitwig tracks to output their audio to _Effect Track_ types - like Aux busses in other software. You do that routing from an audio track output assignment settings.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigSend.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigSend.png)
 
 **Setting Up SPAT SEND in BitWig**
 
 Put the SPAT SEND plug-ins on individual _Effect Tracks_, and enable the local audio path with **THRU** set off, so all audio streams are rendered to output in SPAT Revolution.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigSendMainSetup.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigSendMainSetup.png)
 
 Like in all Local Path Audio workflows, you should see SPAT SEND inputs appearing in the SPAT Environment Setup, which relate directly to the plug-ins hosted in the other software environment, reflecting their TrackName and channel count.
 
@@ -39,7 +39,7 @@ Now the fun starts - on the Bitwig Send tracks, which host the SPAT SEND plug-in
 
 Use the Bitwig ```+``` to open the Device Parameter Modulators and assign the many and varied modulation sources to control Azimuth, Distance, or other Source Parameters.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigModulators.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/BitwigModulators.png)
 
 **Setting Up Controllers in BitWig**
 

en_US/spat-revolution/Third_Party_Cockos_Reaper.qmd

@@ -46,13 +46,13 @@ Please follow this link for more information on [ReaVolution -@sec-reavolution].
 As described in section **[SPAT PI : Local audio path -@sec-lap]**, when using the Local Audio path, the buffer size and sample rate must be matched in both _SPAT Revolution_ and Reaper.
 In SPAT, you set this in the preferences and in Reaper in the Audio Device preferences.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPreferencesDevice.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPreferencesDevice.png)
 
 ## Setting Up Tracks
 
 Working with Track Folder structure for your organisation is a good idea.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperTrackFolder.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperTrackFolder.png)
 
 In the above screenshot, the B-Format Master has been set to be a Folder Parent with 4-Track Channel.
 Reaper channel routing is set on a track by track basis, using the _TrackIO Route_ button of each Track.
@@ -63,7 +63,7 @@ The Y Track is assigned to Parent Channels 3-4 and hard panned left and so on.
 Alternatively, an interleaved 4-channel audio file (B-Format audio in this example) can be placed on one Child Track, which has been specified to have 4 channels.
 
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperBFormat.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperBFormat.png)
 
 Now different interleaved files in the same format can overlap and be composed on the same Track, and they will be summed to the Folder track, and therefore to the same virtual source/object in SPAT.
 All automation for that source should happen in the Envelope Lanes of the Parent Folder track.
@@ -90,7 +90,7 @@ If all is well, you will see the SEND appear as an input at the top of the setup
 If you do not see it, you can try clicking on _Get send/return_ on the top actions or in *Setup/Pipes/Get send return* to force SPAT to look for virtual IO.
 
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperSendBFormat.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperSendBFormat.png)
 
 In the above screenshot, the Orange ' _BFormat_ ' Send input is the one being routed by the SEND plug on the Parent Track on the previous example.
 At first, it will appear in SPAT as a Channel Based input by default - in this case it appeared as a 4.0 QUAD.
@@ -122,13 +122,13 @@ There are a couple of things to make sure to optimize the integration and avoid
  Disable **Full Plug-in State** set by default in Plug-in Compatibility Preferences.
 :::
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPreferencesCompatibility.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPreferencesCompatibility.png)
 
 :::{.callout-warning}
  "Prevent Anticipative FX" should be enabled on tracks where SEND / RETURN are inserted.
 :::
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPerformanceOptionsMenu.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperPerformanceOptionsMenu.png)
 
 Also, by default, REAPER does not process automation messages when the plug-in GUI is not open. You can change this behaviour globally by going to the Preferences menu, in Plug-ins, VST. In the "Parameter notification automation" line, select "Process all notifications".
 
@@ -151,36 +151,36 @@ Here the B-Format source is being introduced from a distance automating _Apertur
 In Reaper, mapping any MIDI controllers (including 14-bit) to a Plug-In parameter is easy.
 This is a great way to control source properties like _Azimuth_ or _Yaw_ using external MIDI controllers, so you can control some sources live by hand during a performance or while mixing for example.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperMIDI.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperMIDI.png)
 
 In the Automation parameter list for SPAT SEND just click on the ```LEARN...``` button to manually assign an external controller that you have set up in the Reaper Controller preferences.
 
 From this page by clicking on the ```MOD...``` button of an automatable parameter, it is also possible to animate sources with independent LFOs that run all the time in the background, quick and dirty way to spatialise live inputs sources with autopan type effects for example.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperLFO.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperLFO.png)
 
 ## Setting up SPAT RETURN
 
 Now, to render the scene from the multichannel room output to disk as an interleaved 3rd Order HOA, for example, we need to add a RETURN plug-in.
 We can calculate that 3HOA3D needs 16 channels.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperTrackChannels.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperTrackChannels.png)
 
 First, set up a Track in Reaper that can handle 16 channels simultaneously. Then add a SPAT RETURN plug-in on this track. It should automatically inherit the channel count, if not do it manually using the IO config of the plug-in, available from the little cog wheel in the top corner of SPAT RETURN.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperReturn.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperReturn.png)
 
 Enable the Local Audio Path: a Return output module should appear in the SPAT Setup Environment. Connecting it to the 3HOA3D stream output from the Room (or Rooms in a mixer/transcoder) and it should inherit the format.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperSessionExample.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperSessionExample.png)
 
 ## Recording Immersive creation.
 
 To do this, it is necessary to make Reaper record the software OUTPUT of the audio track:
 
 - the audio coming into the Track is a virtual audio path through the SPAT RETURN plug-in, so it will _not_ appear at the _Inputs_ list of the Track. Right-click on the track's record arm button, and the Track record contextual menu will appear.
 
-![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperRecordOutputMenu.jpg)
+![](https://media.githubusercontent.com/media/FLUX-SE/doc_images/main/SpatR/ThirdParty/ReaperRecordOutputMenu.png)
 
 Arm the track to record, press play and render the scene to a 3HOA3D interleaved 16-channel WAV file (avoid using FLAC for higher than 8 channels). This is done in realtime.