(Last document update 7th August 2019)            



NOTE: the Change Log (the list of  fixes and changes after the first open beta) is at the end of this document.



What is new in Mistika Ultima and Mistika Boutique v8.10 



Preliminar notes


Important note: This version is still in beta testing stage. It may contain significant software bugs


Important note: This version does not support Suse 11 OS anymore. Linux systems using that OS will need to migrate to CentOS 7.4.  (Meanwhile, the support for Windows and Mac operating system versions does not change.  It is currently supported on Windows 10, macOS High Sierra and Mojave)


Important note:  Systems using NVidia boards need recent NVidia drivers, from June 2019 or later.



New features in Mistika Ultima / Mistika Boutique v8.10 (Compared to Mistika v8.8) 


A small introduction to most of the new features is in this video:


https://www.youtube.com/watch?v=hJej9NgAl3g&feature=youtu.be&mc_cid=62726e417b&mc_eid=b9b0322ec7 



IMAGE FORMATS AND CODECS


New NVIDIA "cudanew" decoding for RED R3D formats, up to several times faster depending on the system:  


This format has been accelerated in several ways, including a new GPU decoding mode developed by RED  (Cuda-new) and Mistika special optimizations for it. 


The old decoding modes are still working (they can be selected in the Mistika Config -> Codecs -> RED section) . Use them if your GPU does not support the Cuda-new mode 


Cuda-new is supported on Linux and Windows (at the date of this document Apple does not support Cuda decoding).


Cuda-new requires a modern NVidia board with more than 3GB of graphics memory (but 8 GB or more are highly recommended) . Chose a different decoding mode if you experience decoding failures (typically shown as chequerboard). Also make sure to install the latest NVidia drivers, otherwise Cuda-new may fail with similar symptoms (checkerboard images) or it can failover to other decoding modes.


An important parameter is the Mistika Config -> Codecs -> RED -> GPU frames.  For Cuda-new we recommend a value of 1, expect for very modern NVidia boards with a lot of GPU memory, which can use a value of 2 for faster performance (but decrease this value to 1 if you observe decoding failures).    Please note that the older GPU decoding modes (Cuda old / openCl) require less memory and can still use a value of 3, but more than 2 is not recommended for the Cuda new (using 3 will not provide significant benefits and it will use a lot of memory that is better to leave available for other effects )


The other important paratemer to adjust is the Mistika Config -> Codecs -> RED -> GPU memory. If it is too low the GPU will need to do more swapping with system RAM, thus reducing the performance. If it is too high there will not be added benefits and you may waste graphics memory that could me more useful for other Mistika effects. Logically it also depends on the Timeline content, so you will need to experiment to find the optimal values for your project.


Please note that the exact performance gains will also depend on each system, as the previous decoding modes required a lot of CPU.   PCs with average CPUs  may experience typical speed gains between x2 and x4  when using Cuda-new, while for the case of top class dual Xeon workstations the difference may be much smaller, as they were already very fast thanks to the high amount of CPU cores.  However, even in these cases the interactivity gain in still mode should be very noticeable with the Cudanew mode,  and there is also the advantage that the CPUs will be free for other tasks (like transcoding to CPU intensive codecs). So it is recommended to select Cudanew by default.


Note: If you do not experience any speed gain with the new mode it may be that the RED decoder is doing a failover to other decoding modes. If you see a high CPU usage that is what is happening, as Cudanew only use low CPU resources. If that is the case please check that you hvae the latest  NVidia driver,  and that your GPU model matches the minimum specs specified by RED.


 

Dolby Vision support. Given HDR images color graded for an HDR display,  this system permits to produce other versions for SDR target displays and for HDR target displays of a inferior NITS capability.  


With this system the target versions can be created and adjusted interactively in Mistika,  and then exported as metadata files in Dolby Vision XML format.  


Both hardware CMU (eCMU) and internal software CMU (iCMU) are supported.  


In the Mistika side, the Dolby Vision integration plugin comes with the Mistika distribution, but it requires a Dolby license to activate it (which needs to be obtained directly from Dolby).  Without this license the basic parts of the Dolby software will still work, but not the advanced features like the TRIM capabilities (the exact features to activate will depend on Dolby and they can not be documented here)


The Dolby Vision support in Mistika is explained in this document:


https://docs.google.com/document/d/1Vge-IvEr9UPlBAd-YApeyUxn5zu6EobD1SO_bUKzUmY/edit?usp=sharing


And a video tutorial is here (beta version):


https://www.youtube.com/watch?v=ReqMuN4_erU&feature=youtu.be&mc_cid=62726e417b&mc_eid=b9b0322ec7 




VIDEO IO


Blackmagic Decklink support. This version supports Blackmagic Decklink boards.  Mistika v8.10 supports YUV 10bit modes up to 4K / UHD 60p.   No RGB modes are supported in the current version.


To configure it just select it in Mistika Config. No additional drivers are required.



INTERFACE


New Subtitle interface. It appears when loading a subtitle file into the Timeline, and it provides all the common options to configure the sibtitles before adding them to the Timeline


Support for Digital Vision Precision panel on Mistika Boutique (for Windows and Mac, previously  it was only available for Linux)


Support for user remaping of Tangent panels, uby sing the Tangent software directly.





OTHERS


Integration with external render farms (Smedge, Deadline,...). Trough the  new configurable button Output->Render->Add to queue. Permits to submit render jobs to external render managers, or to send the rnd files to user scripts for customized export workflows



Automatic Path translation. Each Mistika system maintains a configuration file with path substitution pairs, so now they can find the same media under different mount points, even if the systems have different operating systems (Linux / Windows / Mac.)  You can edit the path translation file manually, or simply tell Mistika to remember your path translation decisions when using the relink tool.



Mistika software folder structure reorganization, for a better integration with the rest of the Mistika product line (using same base folders  under a coherent structure.  all under the  SGO Apps & SGO AppData folders).  For a more detailed description please check this article



The "shared" folder (SGO AppData/shared) which contains all the shareable user settings can now be shared between all Mistika products and also between different systems . This folder is now definable in Mistika Config (mConfig) not only for Mistika Ultima but also for Mistika Boutique.  So it can be shared in a network drive to share user settings like the format presets, render targets,  LUTS,  user hotkeys,  display filters, etc.


Several bugs from previous versions are fixed.  (the list below only mention bugs officially reported by users,  some other bugs found on internal tests are also fixed but they not appear in this list).  Some minor change requests (not strictly "bugs") also appear in this list


License server improvements: Now If the connection with the license server is lost  then  Mistika will offer to save your work rather than crashing.  In addition the whole licensing process  has been revised to make it more robust and predictable.



Change Log (list of fixes and changes in version 8.10  since the first beta version) 


Bug fixes on v8.10 open beta 7th August:


  • 2153 Improved Stereo 3D Dual link when outputting to UHD/4K resolutions in MacOS version.
  • 2313 ‘Use Insta360Pro calibrate’ option in the VR Stitch effect is now working properly.
  • 2402  Mute button in Window Tab when using Tangent Panels is now working correctly.
  • 2296 Improved importing of AAFs with Sapphire Effects in Default Configuration.
  • 2297 Improved importing of AAFs with Sapphire Effects with the Import unsupported effects parameter activated.
  • 2418 Fixed compositing with Comp3D effect.
  • 2305 Fixed Vector Paint working with Alpha Channel. 
  • 2306 Added Time Editor shape parameters in Vector Paint. 
  • 2310 Shortcuts added for bypass function in the Node Graph.
  • 2387 Floating window now shows accordingly to display resolution. 
  • 2437 Exporting EDL, EDL 2, filename and saving the file now working properly. 
  • 1964 When exporting EDL2 now use correct Record Timecode.
  • 2434 Improved behaviour of DNG raw files in Color and Framing. 
  • 2407 Fixed rendering of DPX clips. 
  • 2341 Improved behaviour of Paths while importing media. 
  • 2379 Second Video Output from S3D live mode to Dual Link now working properly. 
  • 2206 EDL 2 STC export issue fixed. 
  • 2426 Improved functionality of the CPL when preparing DCPs. 
  • 2328 Fixed rendering to ProRes 444. 
  • 2423 Support for ProRes on MXF files working properly now. 
  • 2397 TC now set correctly  in DPX clips. 
  • 2417 Fixed TC reading Avid MXF files. 
  • 2239 Relink of image sequences when conforming XMLs now working correctly. 
  • 2441 TC display in Global timecode ruler (in Time space) now working properly.
  • 2211 Improved when loading Canon decoder.


Known problems on v8.10 open beta 7th August:

  • Tangent mapping management not working properly.
  • ACES-ODT not working correctly on macOS.
  • The shared folder content (General->FilePaths->Shared settings) can be lost (overwritten) when connecting a new Mistika system to the same shared folder over the network (fixed in beta 12th August).


Known problem in all beta versions of Mistika Boutique v8.10:  When doing a software upgrade the installer may fail to install some .dll libraries.  If this situation is detected by the installer then some error meessages will be shown during the installation, but it can also pass unnoticed (in which casse Mistika will crash on start).  This problem has been detected in all beta versions since 4th August 2019. It will be fixed before the final 8.10 version, but meanwhile this is the procedure to fix it:


1 Uninstall the previous version


2 Reboot the system


3 Install the new beta.