Miguel Angel Doncel

This is fixed in the coming beta available next week. it includes a software H264 codec. cheers

This is fixed for the coming beta available next week cheers

Hi, the latest Open Beta is almost ready. If everything goes as expected, it should be available next week. Main News in that Beta: New Frame.IO node. it allows to upload files to Frame.IO. If a file with the same name already exists in the selected Folder, the new file is uploaded as a new Version. New Checksum Node supporting md4, md5 and SHA1. Quality param added to H26X. and now bitrate and Quality appears only when the selected codec supports it non GPU H264 Codec added for OSX systems without nvidia card New Copy Node to support multiple inputs. New Move Node. New Trash Node. Fixed: autocompleting Python console failing because of case sensitivity. Fixed: Files locked during processing in Windows. Fixed: Python exposes now more Qt classes. Fixed: unexpected ./ appearing in file some Paths Fixed: Online help URL not working Fixed: tar output connector not working Fixed: EXR render to Prores crashing Fixed: Timecode mismarches Fixed: Single frame sequences not being rendered properly Fixed: EXR sequences not populating frames property. We are still working to improve the metadata extraction from files. That may not be finished for this Beta but for next one. We are also working to improve the codec recognition, in cases such us DNxHD in mov containers. Again, not sure if this will be fixed in this beta or next one.

Ok, yes it was a bug in our code. it is fixed for the coming Beta. Thanks for reporting it Hendrik. You should find a lot more Qt modules on it

You are right Hendrik, we did not realize until now many of the classes are missing. I is probably a bug. please let us check it

ATM only way is via the related node, but we need to check why you are not accesing the correct metadata. we will tell you something about that ASAP

the connections are managed by a class called Cconnector (Mistika.classes.Cconnector). that class has a function called universalPath. it gives you a class called CuniversalPath (Mistika.classes.Mistika.CuniversalPath) wich manages file sequences. at the moment we have not implemented a path for the metadata, so it has to be asked directly to the parent node, but we plan to add a special path for that. At the moment, the actual pixels info can not be intercepted, The best way to manipulate the images is using Display Filters coming from Mistika Boutique. We could export a class to access them if customers find that functionality useful. But ATM it is not possible, and that functionality will not happen before release. Please, let me know if you need deeper information about any of those classes kindly yours Miguel

It is a bug. we will fix it. thanks for reporting it! Roger that, we will change it for next beta That could interfere with other focus management events in the app. let us check if we can do that easily. import Mistika it has 3 modules for Qt: Mistika.Qt Mistika.QtCore Mistika.QtGui that should give you access to all the functionality. if you miss anything, let us know

Hi all, I am resuming the requests we have had from users to improve the functionality of the Open Beta. we are working to implement this functionalities during the open beta process. To add include and exclude filters to the watch folder. New Node to generate checksum files (md5) New Node to validate checksums (md5) the copy node to allow moving and not only copying Node to delete contents frame.IO integration to add quality param to the H26X codec. these functionalities (or mist of them) will probably be added in the next open beta We have also received some suggestions about managing audio, and spanned sequences, etc. Those ideas will have to wait a bit longer, as we need to analize them more in detail. thanks everyone for the great feedback you are giving us!

Hi, the Nvidia H264 and H265 parameters are defined automatically according to the table available in this link: https://es.wikipedia.org/wiki/H.264/MPEG-4_AVC So, when you define a resolution, frames per second, bitrate and the Bitrate, the system selects the best level and profile to fit those settings. At the moment, we do not allow changing them directly to avoid generating files out of the standard, as they could not be supported by all the players. I hope this info helps you to understand how the codec works. kindly yours Miguel

by default, all the transcoders will write the output in the same folder where the input is located you can select any other folder, just selecting it in the URL property of the transcoding node or using drag and drop of the desired folder into the transcoding node you have a small tutorial where you can see the process in this video: Please let us know if you need any further support on this subject

Hi, please give us few days and we will upload some details about how to set up the H265 codification.

Hi Andy, pls open a support ticket in support.sgo.es giving us a couple of dates/times good for you, and we will organize it.

It looks like a Python problem. Workflows uses Python 2.7. what Py version do you have in your system? if you want, we can schedule a remote support session for one of our engineers to take a look and try to fix the problem.

What OSX version are you using? could you please launch the app from a console and send us the output? that could help us to understand what is going wrong.

Thanks for your nice comments. The prores support is the oficial one in all O.S. windows/Mac and Linux. please let us know if you need any support with the product, or if you have indeas and/or requirements you think we could implement

Hi all, here you have a simple example of Py node with comments to help you understanding how to create your own Nodes: First, lets see the whole example: from Mistika.classes import Cconnector def init(self): self.addConnector("myInput",Cconnector.CONNECTOR_TYPE_INPUT,Cconnector.MODE_REQUIRED) self.addConnector("myOutput",Cconnector.CONNECTOR_TYPE_OUTPUT,Cconnector.MODE_OPTIONAL) self.addProperty("myProperty","default value") return True def isReady(self): return True def process(self): i=self.firstConnectorByName("myInput") o=self.firstConnectorByName("myOutput") print "input: "+i.url() print i.universalPath().files() print "myProperty: "+self.myProperty o.setUrl(i.url()) return True now lets examine de sections: from Mistika.classes import Cconnector included to avoid writing the whole path to access the Cconnector constants in the code. The initialization function: init(self) def init(self): self.addConnector("myInput",Cconnector.CONNECTOR_TYPE_INPUT,Cconnector.MODE_REQUIRED) self.addConnector("myOutput",Cconnector.CONNECTOR_TYPE_OUTPUT,Cconnector.MODE_OPTIONAL) self.addProperty("myProperty","default value") return True this function initializates the node. It can be used to create the connectors and properties to be used in the node. the parameter received is the node itself. The function to create the connectors is: addConnector (name, type, mode) the parameters are: The Connector Name. The connector Type. it can be either Cconnector.CONNECTOR_TYPE_INPUT or Cconnector.CONNECTOR_TYPE_OUTPUT for input or output connectors. The connector mode. It can be Cconnector.MODE_REQUIRED or Cconnector.MODE_OPTIONAL defining if the connector must be connected to enable to workflow, of if it is an optional input to the node. Properties can also be added with : addProperty (name, defaultValue) the parameters are: The parameter Name The default Value. This parameter is optional. If it is not defined, the attribute is initialized to null. Finally, the init function returns True. meaining the initialization has been done successfully. The function can return False on error. The ready function: isReady(self) def isReady(self): return True This function is used to define if the node is ready for processing (returning True) or not ready (returning False). It can be used to validate the integrity of the inputs and properties, to be sure the node is not processed if relevant information is missing. The Process function: process(self) def process(self): i=self.firstConnectorByName("myInput") o=self.firstConnectorByName("myOutput") print "input: "+i.url() print i.universalPath().files() print "myProperty: "+self.myProperty o.setUrl(i.url()) return True Finally, the process function executes the task In this case, we just print in the console the contents of the property and the input files in order to access the input connector, the function firstConnectorByName is used. This function returns the first input connector found with the given Name. the prints show the url defined in the input connection with print "input:"+i.url() then print the list of all the files in the input sequence with print i.universalPath().files() Note: Dealing with Universal Paths is something we will cover in a different post. then prints the property value with print "myProperty: "+self.myProperty and finally, it sets the output connector with the same sequence found in the input connector with o.setUrl(i.url()) That will send the unaltered sequence to the next node. Returning True to indicate success

Nice to see you around Rob. Your feedback will be very much appreciated! Miguel

Hi all, As promised, we are happy to announce Mistika 8.8.6 Open Beta is now available for all existing customers. During the open Beta, all customers will have access to this new version using your downloads section in your web account: www.sgo.es/my-account/downloads All the new functionality will be available for personal and professional editions. And as usual, at no additional cost. After the final release, this functionality will also be available in the evaluation version. New features: Mass import of media now supported: Whole folders, and recursive folders can now be drag & dropped, and the material will be organized automatically into clips. During mass import, clips incoming split into multiple parts due to the file size limit of the SSD cards will be automatically placed as consecutive stacks for most file organizations. Multipart clips can now be concatenated into a single clip, with the “Merge From Selected” feature, allowing to treat them as one single clip. This is an instantaneous metadata operation, no actual media merge is necessary. Still-image panorama photography support improved with better still image sets import. When importing an apparent numbered image sequence, the user can choose either if the images are a time sequence or if each image is a separate camera view. Maximum camera number was increased from 32 to 64, allowing for larger still image photography sets. Default preset can be predefined to be applied on all newly imported stacks, to further enhance the mass imports. Media Relink. The system will allow us to locate media not found during the load process. Path Translator. Specially thought for sharing projects between different Operating Systems and simplify compatibility amongst Operating Systems. Zoomable visual editor timeline, to allow work on very long clips. Better alignment for coaxial rigs can be achieved by setting coaxial convergence. Applies both VR360 rigs (VRTul2, Vuze and other stereo couple based rigs) and VR180 rigs (zCam K1, iZugar VR180 rigs etc). Coaxial Convergence Distance parameter added. Forward Distance parameter added as an experimental alternative to Convergence, acts only on the horizon yet not on the poles. Playback Cache is displayed in the time bar. Scrubbing along the cached segment can be expected to be much faster than uncached zones. Import of OZO calibration metadata is now supported. Import of Insta360pro calibration metadata is now supported. Import of Facebook Surround json calibration metadata is now sported. nVidia h264/h265 render now supports the QP mode for constant quality, variable bitrate mode. Makes the codecs more suitable as intermediate format, avoiding quality fluctuation in time due to the GOP cycle. Also, avoids drop in quality of complex scenes and scenes with light flashes. Some presets form the preset library have been updated to enable the latest functionalities: GoPro Omni Freedom360 Samsung Round Vuze ZCam S1Pro ReorderKandao Tool integrated into the GUI. This Drag and Drop utility helps renaming and reordering Kandao sequences simplifying the import and management processes. The Visual Editor includes now a maximize icon. The image area can be maximized by double-clicking on it. New Presets: Preset for OZO upgraded to handle better the back seam Preset for iZugar Z4XL added. Preset for ZCam K1Pro added. Preset for iZugar Z6X3D-C added. Preset for DetuF4Plus added. Preset for 2x Panasonic GH5 with Entanyia 250 lens added. Fixes: Local License server has been improved to automatically renew the licenses on subscription renewals. This was creating support issues to customers, especially to people using OSX with a Touch Bar. 1588 PtGui shows an error message when sending images from an unnamed timeline 1312 Removing the first camera rolls the positions of all the following cameras in the image 1585 Hotkeys related to Edge points do not work 1589 Problem with custom layouts 1595 Crash rendering to prores in Osx systems 1616 Applying a preset to Samsung Gear leaves both tracks of audio unmuted ----------------------- Hi all, We are happy to announce that New Release of Mistika 8.8.6 is now available to all existing customers. All customers will have access to this new version using your downloads section in your web account: www.sgo.es/my-account/downloads All the new functionality will be available for personal and professional editions. And as usual, at no additional cost. After the final release, this functionality will also be available in the evaluation version. New Features: 22. Now the VR metadata injected into the rendered movies supports Side-by-side VR3D180 format. Also, the injection is now done while creating the movie, not as a post-process requiring full movie copy. Fixes: 1581 Fixed a crash when placing more than allowed maximum of 64 cameras in a single stack. 1607 Inject VR Metadata now works in the 'Render all shots' mode. 1616 Applying a preset to Samsung Gear left both tracks unmuted. 1623 Crash at reading an .vrenv file just after saving a different one. 1634 Output to “Little Planet” and “Cube map” produced cropped result. 1636 A possible crash when using Full screen mode fixed. 1637 Up/Down hotkeys on parameters were misinterpreted as zoom in/out. 1639 pro.prj Insta360 calibration files now also work when drag & dropped. 1640 Removing cameras through the clip stack could crash the app. 1647 Wrong behavior of the popup window ¨Add video format 1651 Esc key made the render window to disappear with the render keeping on.

hi Susane, the best way is to uninstall 8.8.3 and install 8.8.4 as you suggest. you can also install 8.8.4 on top of 8.8.3 but even if that works, it is not a clean approach and will leave some useless data in the system registry. so we recommend uninstalling and installing please, do not hesitate to contact us if you need any help during the process

Hi all, We are happy to release Mistika VR 8.8.4. thanks to all the customers for the feedback during the beta period. The Release is available for all customers as part of your subscriptions. You can Download it from your downloads page www.sgo.es/my-account/downloads If you need a new license, you can get it in our shop www.sgo.es/vr-plans What is coming in this new version: New Presets GoPro Fusion Vuze IndieCam Yi360VR preset refined, now corrects lens distortion iZugar Z2XL180 iZugar_Z4XL_3840x2160 New Features / Improvements Latest Nvidia Windows Driver Supported. OSX GPU more efficient, improving render speed and interactivity. Nvidia GPU accelerated encoding for Windows Systems. Provides a large performance boost for the h264 codec, as well as new h265 (HEVC) capability. Speeds as high as 45 frames per second for 4k x 2k encoding are now achieved. You will likely enjoy a significant render speed up with these new codecs, specially for systems where codification was the bottle neck. Also, lossless settings are available for both h264 and h265 codecs, making them interesting as intermediate format for your workflow. Important Note: This improvement is not supported in OSX At the moment, as the new Nvidia driver is not supported by Apple. But as soon as they support it, we will upload the same functionality for OSX. Optical Flow stitching is now typically 50% faster, cutting your render times by up to one third. New Timeline context menu to display TC or Frame Number. The Align Horizon Rotation yellow guide line is now automatically removed when any other action is taken. KanDao Calibration metadata support. It can be read from the KanDao media files if available, allowing for reliable and very precise camera alignment. Multicamera files (like Samsung Gear360 and Vuze) now display only the desired camera and not all of them in the following situations: In lens centering mode. In the camera list Icons. When exported to PTGui or Hugin. Color correction applied during the Lens centering mode to help the centering process on very dark shots. Vuze media clip supported: All eight views, including those stored as the second video track, can be selected by applying the Vuze preset on a single Vuze media clip. Performance has been significantly improved when swapping cameras by dragging over the image in the Visual Editor. DNG support has been improved both in quality and performance. Black Magic compressed DNG format is supported too. Stereo edge points now support cameras with unusual right-to-left camera numbering (like zCam V1), and for presets with extra cameras heading up or down. (Jaunt, zCam V1). License expiration and auto renovation message now much more detailed, explaining what it exactly means and linking to solution instructions. Activation window can be enlarged as necessary. When MistikaVR is reopen, last timeline will be automatically loaded. If MistikaVR closed unexpectedly, last autosave will be automatically recovered. KanDao metadata can now be imported also from KanDao .kdproj files. This allows importing the calibration of the KanDao Studio “Calibrate” tool. Bugs Fixed Fix n-917: Latest Nvidia driver crashing Mistka VR. Fix 1435: Drag and drop does not open contextual menu anymore in Storyboard and keyframe slider. Fix 1336: Error loading a .lnk files. Fix 1382: Camera overlay disappearing with Quick View activated when using Match color in time. Fix 1394: Problems with Paths starting with "/" in Windows systems. Fix 1416: Crash rendering to Left/Right S3D mode. Fix 1459: Mistika VR not starting Automatically the first time just after installing a new license. Fix 1498: Export to PTGui of cameras with multiple views per clip (like Samsung gear 360) not working. Fix 1396: Typing number in the frame offset animates the intermediate states bug 1483 fixed: Rendering 'all shots' with Nvidia h264/h265 codecs did not work bug 1468 fixed: On some Mac computers, stereo side-by-side and top-bottom render output had one of the views broken by aliasing artifacts bug 1552 fixed: The source cameras Mute buttons, once used, made all audio muted, with no possibility to unmute them anymore. bug 1512 fixed: R and L hotkeys did not work if the image view area was not in focus bug 1359 fixed: Storyboard icon did not change if feather overlay was switched on/off. bug 1390 fixed: Match Color did produce wrong results if any camera was disabled bug 1440 fixed: On OSX, the path is now correct using the native file manager

Hi All, As we progress with the VR3D beta, we have found several of the additional functionalities we have implemented are reliable enough to be released, so we have decided to release them and keep working on the VR3D beta, which will probably be in the market very soon :) Customers can download it from their downloads page: https://www.sgo.es/my-account/downloads/ If you are not a customer yet, you can get your version in: https://www.sgo.es/vr-plans New Features: Circular fisheye: Circular fisheye support has been implemented and it can now be imported from PTgui. New input camera "compositing mode": a new parameter has been added to allow adding logos or patches created in any external tool. To do that, set this parameter to "Overlay" and it will be composed over the final result using its mask channel. The overlay supports Yaw/Pitch/Roll and focal length adjustments. JPEG Render: It was one of the top requests in our last survey, so here it it. Mistika VR now renders out jpeg sequences. PNG Render: PNG format added to render formats. TIFF Render: TIFF format added to render formats. Color match between in and out points: Now color match is processed in the used section of the clip (between in and out points) speeding up the process. Resolution info in cameras: The camera preview images now show the actual image resolution and clip name info. Audio Match max offset: Audio match has a new parameter to define the maximum offset accepted as a valid offset. This new parameter makes the analysis faster and more accurate avoiding extremely big offsets which are usually incorrect. Variable Edge points feather: Now Edge points have a variable feather. Edge points feather control added: using the ctrl+shift+left mouse button. "Fill Holes" added: new parameter to fill minor holes by extrusion. New Presets: Boxfish360 Dry Boxfish360 Wet Mi Sphere 360 GoPro 360Rize Pro10 v2 GoPro 360Rize Pro7 v2 GoPro 360Rize Abyss GoPro Kolor Abyss KanDao Obsidian S Performance improvements: Audio Match performance has been improved. Bugs Fixed: Fixed 1393: Work and Material Project paths now support spaces. Fixed 1355: Marks are now removed when saving a camera preset. Fixed 1376: Misleading message when spaces are present in the render name has been fixed. Fixed 1358: Loading layouts with detached windows has been fixed. Fixed 1361: Crash when loading presents by drag and drop to Visual Editor. Fixed 1362: Loss of focus in Project Manager after changing any setting. Fixed 1403: Random crash starting color match fixed. Fixed 1410: Audio in render to mp4 fails with some cameras

Hi All, This monday we will have a Release Candidate for the new version Mistika VR 8.8.1. Customers with interest in the RC early access will find this monday the version in: https://www.sgo.es/my-account/downloads/ If you are not a customer yet, you can get your version in: https://www.sgo.es/vr-plans If the version is as stable as we think it is, we will release it during the next few days, so if you prefer to wait for the final release, you will have it soon :) New Features: New Undo: Now the software supports unlimited levels o undo and redo. Sync to TC: A new option to sync using Time Code is available H265 support: for cameras like Samsung Gear, etc. File Sequences are now imported as a single camera and not as a group of different cameras. ".lnk" support: “Add camera” now supports to add Mistika Ultima “.lnk” files Luma and Color sliders: now, for better sensitivity, they slow down 10x when dragging while holding Alt key Alpha channel export: ProRes 444+Alpha now supported as output format New Presets: iZugar_Z3Xc iZugar_Z4XL Yi360VR SamsungGear360 model 2017 Insta360Pro_3200x2400 Insta360Pro_3840x2160 SumoCinematographer GoProX2Entaniya250_4to3ratio ZCamS1Pro_3840X2160 Performance improvements: Dragging around the output camera interactively using the mouse is now app. 8 times faster. Multithread automatic detection: Mistka VR now optimizes the number of threads to number of CPUs available in the system, improving the performance in systems with more than 8 cores. Bugs Fixed: Fixed 1299: Match Color in Time sometimes was breaking the image colors. Fixed 1331: Layout reset was crashing when used multiple times. Fixed 1328: Changing Material Paths was not stored when leaving the software Fixed 1297: crash.env file recovery was failing sometimes producing a new crash. Fixed 1289: Overlays were not working with Mosaic and Single Input enabled Fixed 1301: Render overwrite confirmation was requested even if the file didn’t exist. Fixed 1288: Overview window disappeared during GUI scale. Fixed 1334: Export from Gear 360 footage was generating images with black border for most output resolutions Fixed 1360: 'Show mosaic' option always loaded in the Storyboard starting a session

Hi All, We have enabled the new online activation/deactivation tool on the web. This functionality will allow you to manage your licenses online, helping you to deactivate from one computer and reactivate it in a different one. You can access this new functionality in the My Account section of the web, or directly in this link: https://www.sgo.es/my-account/activation-codes In the page you will find all your activation codes, and its status. We strongly recommend to do the de-activation and re-activation using the SGO Activation Tool, as it is not only faster but easier. But in those cases in which you are not in the system to deactivate, this page will become very handy. How does it work? Deactivation Process: 1.- go to https://www.sgo.es/my-account/activation-codes You will see a page like this: 2.- Press the DEACTIVATE button for the activation code you want to deactivate 3.- A confirmation page will be loaded. Press the CONFIRM DEACTIVATION button. The activation-codes page will be loaded again, and your code will be deactivated. 4.- Now you can go to your new system and activate your activation code on it Note: The old system will stay in semi-deactivated mode. That means, the system needs to confirm the deactivation (see below). If your activation code doesn't have an DEACTIVATE button, it could either be that the related product is not deactivable, or the activation code is still in semi-deactivated mode. Activation Process: If you have internet connection, you can activate again your code with the SGO Activation Tool as usual. but if you do not have internet connection, we have also added to the portal the ability to do offline activations. To do that: 1.- press the ACTIVATE button for the activation code you want to activate. this will send you to the activation-wizard 2.- Select the features to activate and press NEXT. By default, all the features attached to the activation code are enabled, which is the more likely option. 3.- Enter your System ID (LMdata) and press ACTIVATE. The System ID can be found in the SGO Activation Tool and copied to the clipboard with the Copy System ID to Clipboard button You will receive the license by email, and if your system is connected to internet, it will automatically update your license next time to start the system. Confirming the deactivation: Once you disable a code, it will remain in semi-deactivated mode. that means, it will not accept more deactivations until the first one is confirmed. In order to confirm it, you just need to start the SGO License Server in the original system having internet connection. It will automatically confirm the deactivation for you, enabling your code to be deactivated again when needed. Please, feel free to give us feedback about this functionality. Kindly yours,