MiRA-SampleGrabber is not listed in MiRA as a Source (Windows Only)

• As a first step, press play in the DAW and verify that the sound is playing as intended, the MiRA-SampleGrabber needs to process audio before it can be recognized by MiRA.
  
• If after this the SampleGrabber is still not listed in MiRA as a Source, there may be an issue with the Bonjour for Windows, the network framework used for the network discovery to find and to list the MiRA-SampleGrabber instances automatically, as well as for the communication between the SampleGrabber and MiRA.
  
  How to fix this
  • Close all applications (including your web browser).
  • Open the Windows control panel.
  • Uninstall both Flux:: Center and Bonjour for Windows if installed, using the Add / Remove Programs.
  • Install the latest version of FLUX:: Center again, now the installer should prompt and ask if you want to install the Apple Bonjour Framework, which you need to do in order to fix this.

When the installation is completed, everything should now work as intended.

No signs of signal from the MiRA-SampleGrabber plug-in in MiRA (Windows / macOS)

• Version Numbers
  First of all, please verify that the versions of MiRA and the MiRA-SampleGrabber plugin are both the latest.
  
  Finding the version number
  • To find the version number in the MiRA-SampleGrabber plugin, open the plugin, click on the small cogwheel button on the plugin user interface, and the version number is displayed there. The current correct version number should follow the format: V25.1.0.50445.
    
  • To find the version number in MiRA, simply read it at the top of the open application, in the title bar. The current correct version number should follow the format: 25.01.0.50445
    
• Network Settings
  If you still experience problems connecting the SampleGrabber plugin and MiRA, please check that both the source system where the MiRA-SampleGrabber plugin is inserted and the destination system where MiRA is installed, are connected over the same network and that they both have a valid network configuration.
  
  Both systems need to be configured with an IP network, either through a DHCP server or using manual network configuration.
  
• Firewall Settings
  If there are no signs of signal in MiRA after selecting one the MiRA-SampleGrabber instance in the source menu, please check your firewall settings and verify that both MiRA and your host software are authorized for any network communication, or specifically, for UDP access from port 46000 to 46064.

Resources

• MiRA User manual
• Flux:: Center download

The post MiRA connection issue with MiRA-SampleGrabber plugin appeared first on FLUX:: Immersive.

The post Live VS Ultimate – immersive perspective appeared first on FLUX:: Immersive.

Windows C:\Users\USERNAME\AppData\Local\FLUX\MiRA

Macos /Users/USERNAME/Library/Application Support/FLUX/MiRA

On Windows, a few other settings are stored as register keys. If you need to delete these, open the windows registry editor (type ‘regedit’ in the windows search bar) and delete the following key

        HKEY_CURRENT_USER/Software/FLUX/MiRA

The preferences folders, contains 2 folders in the Session or Studio versions, and 3 folders in the Live and Ultimate versions

Capture (Live and Ultimate only):

• Stores all your sessions (one file ” .fcap” by session).

Preferences (All verions):

• The file “current_state.json” stores the latest workspace you were working on
• The file “username.json” stores the preferences, aka the latest workspace loaded and the latest workspace path
• Ul.xml stores the Ul preferences, aka the size of the app, and its location, …
  Shell (All versions):
• Stored the previous commands entered in the terminal.

The post Preferences appeared first on FLUX:: Immersive.

With MiRA::, you can adjust existing LAYOUTS, create entirely new ones, or delete LAYOUTS from the default factory set. (note that the factory set does vary depending the MiRA version)

A WORKSPACE is a collection of LAYOUTS organised within the MiRA:: app, where it also saves all application settings, including Main/UI/IO configurations. In practice, you can design multiple WORKSPACES for specific needs. For instance, one WORKSPACE could be tailored for studio use, featuring customized LAYOUTS and IO settings, while another might cater to live events with different LAYOUTS and IO setups.

The post Workspace vs layout appeared first on FLUX:: Immersive.

The post Upgrade to MiRA – Will I loose my previous license appeared first on FLUX:: Immersive.