Mistika VR projects can be loaded on Mistika Ultima (version 8.7 and later)  for advanced post production tasks that are not possible in Mistika VR, among others:


- Stereo3D advanced adjustments & Depth Grading

- VR compositing 

- Animated VR shapes

- Motion Tracking  

- VR Color grading 

- Client attended sessions with live streaming to VR helmet

- Conform tools for EDL, AAF, XML.

- Paint, Warp, Morph, Titling 

- Finishing and VFX workflows.

- Faster than realtime rendering with Mistika Totem multiGPU technology


For integrated workflows, the  important aspect is to use versions of both products from similar dates.  The version build date is mentioned in the distributions of both products, and also in the About menu (Mistika VR) and status bar (in Mistika Ultima).  



Sending VR projects to Mistika Ultima:


1 - Bring the Mistika VR project to a Mistika Ultima system, and load the .vrenv file on it.  


2 - If neccesary, use the Mistika Ultima Relink tool to find the media files in their new locations (see next point for a more automated workflow and automated path translations)


Alternatively, in Mistika VR you can use the VR->Render->AddToQueue to send rnd files to a Mistika Ultima, which also support path translations. This can be used to render them with BatchManager or to open the rnd files in Mistika Ultima and continue working with them without the need of relink. This is explained in this other document



Integration though the Mistika BatchManager:


In Mistika VR, the render panel provides an Add To Render Queue button.  Among other options, this tool permits to send .rnd render jobs to a Mistika BatchManager, which is the batch manager that comes with Mistika Ultima.  You can use this tool in two ways:


- To  render your rnd jobs with Mistika Ultima renderfarm (or any  other supported render farms).


- When you finish a sitching job, you can send it in an rnd file to Mistika Ultima for additional conform and post processing tasks.  The workflow would be identical  to the previous case,  but just choosing  an inactive queue (no render done)


One advantage of this method is that it permits to apply automated path translations as neccesary, thus avoiding the need for the relink tool on multiplatform environments.  For more details check the document about Add To Render Queue


Scripting:


The .vrenv contain all the work that you have done in MistikaVR.  As the .vrenv are text files you can also do custom scripts easily in order  to automatise your workflows. The syntax is pretty obvious, although you can get more information in the  Mistika Ultima scripts syntax article.


Other resources:


- If you are  a Mistika Ultima user:  At the date of this document Mistika Ultima 8.7 (first version with VR support) is still beta.  Mistika Ultima betatesters should contact SGO support if they plan to use combined workflows to ensure that they use compatible versions.


- If you are a Mistika VR user:  If you want to receive Mistika Ultima services without purchasing it, you can ask in the SGO forums or SGO support for available Mistika Ultima facilities in your area.  Many Mistika Ultima facilities around the world are already offering advanced post-production services for Mistika VR files.