All Activity

Hi Ken, Thanks a lot for reaching out! Due to the insta360 pro 2 mapping, the best way to keep all your information is by setting the render vertical size as close as possible to your vertical shots size. In this way, if your shots are, for example: 3200x2400 I recommend to set your render as 4800x2400 (because 4800 is twice 2400, and if you keep your vertical as 2400, your horizontal must be 4800 to keep the 2:1 recomended aspect ratio for Latlong images. Talking about the target device, it depends on the device and your purposes. In the case of Oculus, I recommend to export to HEVC codecs, because .mov (as far as I remember, maybe it has changed) are not supported by Oculus, and HEVC will offer you the best results interms of resolution and performance inside the headset. I hope it´s useful! Please, do not hesitate to ask anything if you need further assistance 🙂 Cheers! Carlos

Hi Ken, Thanks a lot for reaching out! You can try to modify the Yaw/Pitch/Roll parameters on the output camera panel. In this way you will be able to modify your front or repositioning your shot. This tutorial may help you: To zoom in/out your camera, you can change the mapping to "planar rectilinear" in your output camera tab, and then, you´ll be able to set your focal lengh (But remember that you´ll lost some parts of the image. Have a nice day! Carlos

Dear I shot my videos with an Insta360 pro 2, in i-log 8k 60fps (pano mode). What would be the optimal export settings if I want to use the videos on a Quest 2 (DEOVR, Unity, ...)? Thanks in advance! Kind regards Ken

Dear I just bought a insta360 and one of my shots is too low (camera on the ground) and the subject of the shot is too close. I understand I cannot change the shot in post, but is there a way in Mystika where I can (1) or zoom the shot out a bit or (2) elevate the POV a little bit? Kind regards Ken

Hi everyone, A new version of Mistika VR is now available adding a new improvement. You can already find this version in the Downloads section of you SGO Online Account. Bug Fix and Feature Enhancement Resolved issue preventing correct connection to Deo VR due to an incorrect streaming URL. Added copy/paste option, allowing users to conveniently copy and paste the streaming URL.

купить лист холоднокатаный

Do I uninstall version 10.6.2 before installing the latest version?

Hi everyone, A new upgrade of Mistika Boutique is now available adding new updates and improvements. You can already find this version in the 'Downloads' section of your SGO Online Account. SDK Updates ARRI Alexa 35 (Windows and Linux only) Sony VENICE 2 Improvements Dead Pixel detection improved in Phantom RAW files. Fixed Bugs: Display Filter menu's functionality now shows multiple filters correctly. Fixed an issue that caused Display Filters to not display properly on the main GUI. Corrected the behavior of the Gamma Curve within DNG files. Note: The gamma curve no longer affects DNG files unless it is explicitly set. Fixed an issue with rendering the TC when changing FPS. Gamma curve is now read correctly in the Phantom RAW files. Resolved an issue with rendering to 32K EXR RAW RGB Half. Fixed memory leak when applying a denoise effect on top of another denoise effect. Up/Down Arrow controls in Timespace will no longer affect the Visual Editor viewer. The cursor no longer transforms to ↔︎ when clicking the temperature. Mistika can now render vertical resolutions correctly. AAF from Media Composer with R3D files can now be conformed correctly. Fixed a memory leak when rendering with Green Screen FX. Audio EDL files can now be generated properly. Fixed a conforming bug in reverse clips with XMLs. Fixed an issue related with left-clicking on an empty area of the Visual Editor. P2 files of type Audio/Video are now imported correctly. The playback cache is no longer automatically invalidated when editing inside a group. Known bugs: ARRI camera-generated MXF files with ProRes encoding cannot be read correctly. The ArriParams Tint does not work correctly.

To continue my learning, I am interested in understand Mistika's notion of stitching preset. 1. If my Gear 360 2017 camera has FOV of 192.8, then how does this relate to a Mistika stitching preset Focal Length of 10.652? 2. How does the lens distortion correction affect the image, is the image warped to correct the image?

Hi there! Create fully automated post-production workflows that will contribute to a better media management with the complete set of features in Mistika Workflows. This template demonstrates how to efficiently filter and organize the contents of a folder based on various criteria. The first step involves filtering the media based on its frame rate (FPS), accepting only 23.98, 24, or 25 FPS. Any media with 30 FPS will be relocated to a separate location, while media with other FPS values will be deleted. Next, an extension filter is applied to the accepted media. Depending on the extension, different debayers are used to ensure accurate color space conversion. The final result is a properly rendered clip in EXR AP0 Linear format. In Mistika Workflows, any folder or multiple folders can be filtered using metadata fields, enabling the creation of customized workflows. This is just an example workflow to streamline media management. You can modify it to fit your needs adding new inputs, tasks and outputs. If you need assistance, please reach out by opening a ticket on SGO Support Portal. Enjoy Mistika Workflows! Media Management.mwf

Hi there! Automate your multi-master deliveries in just a few simple steps. You can have a look at this video to learn how to create this automation in just a few simple steps. The workflow is triggered automatically by the Watcher input node, which starts the process each time a clip is placed in its designated folder. After that, three versions will be created: an EXR in Linear light ready for production, an Apple ProRes review file, and a client version in H264. These versions can be uploaded and sent through various services such as Aspera and Signiant, as well as platforms like Frame.io, Vimeo, and YouTube. You can also set notifications every time a version is uploaded via email or Slack, as shown in the example for the Apple ProRes version. This is just an example workflow for the multi-master deliveries. You can modify it to fit your needs adding new inputs, tasks and outputs. If you need assistance, please reach out by opening a ticket on SGO Support Portal. Enjoy Mistika Workflows! Multimaster.mwf

Hi there! With this template you will start to explore all the different Metadata Management automation options Mistika Worklflows has to offer. Our platform reads all available metadata from source media, whether it is in RAW format or not. You can edit, modify, and export the metadata. The “Edit Metadata” node allows you to add additional information, such as custom comments, keywords, and production details to your media. This metadata can be exported without transcoding to CSV and XMP, both of which are fully compatible with DaVinci Resolve and the Adobe Suite. You can also generate metadata during the transcoding process and use it as dynamic tokens to build the destination folder structure and rendered file names. To add these dynamic tokens, use brackets [ ] to access the list of available tokens. This is just an example workflow for the automated metadata management. You can modify it to fit your needs adding new inputs, tasks and outputs. If you need assistance, please reach out by opening a ticket on SGO Support Portal. Enjoy Mistika Workflows! Metadata_Management.mwf

Hi there! Using this template you will learn how to streamline ACES pipeline with Mistika Workflows. Our platform supports the latest ACES 1.3 version. By default, Mistika Workflows reads the source clip metadata and builds the necessary color space conversions during transcoding to different formats. In this example, we work with two formats: R3D and DNG from DJI drones. To set the R3D media to AP0 Linear, we connect a debayer node for RED files to the folder and configure the color space to ACES. This is possible because RAW formats typically include the IDT in their parameters, so we only need to select ACES for them (note that the required debayer may vary depending on the RAW camera). The DJI files don't have this option embedded, so we need to make the color space conversion during transcoding. To do this, we set the input color space (DJI D-Gamut and DJI D-Log) and then use the EXR and ProRes nodes to convert the color space to AP0 Linear and Rec709, respectively. The output color space in Unicolor uses ACES ODT as default values. If you need custom outputs, set the option to custom and define the output Gamut and Gamma. This is just an example workflow for the automated ACES pipeline. You can modify it to fit your needs adding new inputs, tasks and outputs. If you need assistance, please reach out by opening a ticket on SGO Support Portal. Enjoy Mistika Workflows! ACES_Workflow.mwf

Hi there! This template shows a sample easy-to-build workflow to automate your proxy creation process for editorial in three simple steps. 1) As an Input, we can use Folder or Watcher node, both set to filter the files by extension, reading only ARRI, R3D, Sony and Blackmagic RAW files (simply switch the connection to use one or another or deploy a Serialize node to use them both). 2) To create the proxies we can use ProRes or DNxHD* codecs, depending on the editorial software used in the pipeline. 3) Finally we can send a notification via email or Slack to the editorial team once the proxies are ready. Make sure to set up the nodes correctly before the launch. This is just an example workflow for the automated proxy creation. You can modify it to fit your needs including adding new inputs, tasks and outputs. *Please note that you’ll need a separate license for DNxHD that you can easily purchase in SGO Online Shop. If you need assistance, please reach out by opening a ticket on SGO Support Portal. Enjoy Mistika Workflows! Proxy Creation.mwf

Hello, I realize this should go under the Jobs forum, but I was not able to post there for some reason.. We are looking for people that are well-versed in Boutique to help us make render templates. Basically, we need to try to recreate text moves and FX in Boutique that were first created in After Effects, so that we can have Workflows create unique versions. Some moves are pretty straight forward, others more complicated. We are an ad agency in the US and these would be for TV spots. If anyone is interested, please send me a DM (not sure if you can do that here this is my first post), and I can offer more details. But this would be a freelance gig and would be somewhat regular work each month. Thanks so much.

Hi everyone! We have released a major upgrade of Mistika Workflows, that features new integrations with external applications, incluiding AWS S3, Dropbox, Vimeo and YouTube, as well as additional nodes and advanced features. This version is already available on your Online SGO Account. New Integrations Dropbox - Easily upload and download media to your Dropbox account directly from Mistika Workflows. TUTORIAL AWS S3 - Automatically upload and download media to your Amazon Web Services S3 storage directly from Mistika Workflows. TUTORIAL Vimeo - Upload your media automatically to Vimeo. TUTORIAL YouTube - Upload your media automatically to YouTube. TUTORIAL New Nodes and Features classifyByMetadata node - Filter your input, such as a folder, watch folder, or FTP, based on the metadata associated with it. TUTORIAL jsonCurvesData property added to RndFile - This new option enables you to use RND files created in Mistika Boutique, Ultima, or VR as templates to batch apply the effects or manipulate its parameters directly in Mistika Workflows. changeCurvesData node - New node allowing the modification of the FX parameters of the RND input. classifyByAge node - Filter the input files by its existence time/lifespan. scaleResolution node - This node allows you to modify the size and resolution (by pixel and percentage) of your media when transcoding. addRoot property added to input folders - A new parameter added to the input folders that allows you to preserve the internal folder structure when transcoding media. This makes it easier to automatically create the corresponding folders in the destination. setUPmetadataFrom node - This node enables you to add metadata from one universal path to another, which can be particularly useful when certain processing tasks don't maintain your media's metadata. This is especially helpful for managing RND files. For example, if you have a clip that you are processing and you want to ensure that it retains its metadata, you can set up a separate metadata source using this node. mdataFrom connector added to rndFile - A new connector added to the RND files to add the metadata from the setUpmetadataFrom Node. Comp3D node - This new functionality allows you to easily create simple compositions with a background or foreground directly within Mistika Workflows. WF-I-10 dcp, dcpReel and dcpCompliantFile support mp3 node - Added input/output support for .mp3 files. Python Updates New auxCode property ftp::translateFinalFilePath(self,filePath) exposed to auxCode Cworkflow::isProcessing added to Python MediaFileInfoData exposed to Python UP MediaFileInfoData getter and setter added to Python NameConventionItem exposed to Python NC removeItemAt, insertItemAt,appendItem added Mistika.app.getResolutionNames() added Mistika.app.getResolutionNames(string name) added Connector::setRemovable added to Python Connector::isRemovable added to Python Frames to Fields interpolation type added Fixed bugs The issue causing a creation of undefined additional folder when certain tokens (such as Resolution X/Y) were used for rendering is now fixed. "Production" token no longer interferes with token creation. Custom transcoding resolution is now properly read by X/Y resolution token. The ending "/" for FilePaths is now correctly placed when paths are loaded through the GUI. Fixed an issue caused by the Split node with certain unsupported formats. Move node functionality has been corrected and files are now properly moved instead of deleted. EXR files are now correctly scaled when using the rescale within the transcoding panel. Fixed Export Single frame feature. XAVC TC is now managed correctly. FileName and ClipDirectory are now correctly written by CSV. Fixed XDCAM audio channels management. R3D files can now be correctly managed from Watcher and Folder nodes. Fixed rendering with name conventions for sequential files. Fixed functionality of the properties panel when Mistika Boutique is installed after Mistika Workflows. Resolved the issue that reset the project to null when a project was changed in Mistika Boutique. Checksum node now functions correctly. Fixed an issue with changing file paths in the inputs nodes manually. Fixed a crash that occurred when multiple workflows were running and were stopped. Fixed an issue that prevented conversion to interlaced R3D files when Open CL was set. Classify by metadata feature now works properly with 24, 25 and 50 fps. Mistika will now function correctly on Linux when an RND is rendered by the Mistika render node. ExportSingleFrame and Enable Frame Range features in the task nodes now work properly. Known bugs Vector Paint coming from Mistika Boutique is not rendered correctly by Mistika Workflows. Conversion from RAW media to XAVC may result in an "Invalid Gamut selected. Only rec.709 and rec2020 are supported (Windows only). Rendering from DNG may result in a more contrasted image than the original. MistikaRender may create an incorrect FilePath when the workflow is launched.

Hi Mistika Pro's. I need to do VECTOR PAINTOUT / CLEANUP in 360 VR 3D STEREO. When using the "classical" workflow with a VR View and a Vector Paint, the Vector Paint seems to only work on both eyes in parallel. So what I paint in the Left Eye view, will also be applied to the Right View, and accordingly wrong there. I somehow need to split the Stereo stream and work on each eye separately, then merge it back together. How is that possible in Mistika? I also watched every Tutorial you have and looked through the Manual, but couldn't find anything on this. Thanks!

Hi everyone, A new release of Mistika Boutique is now available adding some improvements. This version is already available in the Downloads section of your SGO Online Account. Improvements: Keyer FXs now work on HDR of 16 bits. Accesing the Shortcut Pack has been changed from Ctrl+< / Ctrl+> to Shift+< and Shift+> New mConfig now supports AJA driver for Centos (7.4 and 7.8). Fixed: Fixed issue related with overwritten files in Name Convention when installing additional Mistika Technology software. “Ctrl +S” shortcut now works correctly when the node graph is opened.

Hi all, A new version of Mistika VR is now available adding new improvements. This version is already available in the Downloads section of your SGO Online Account. Fixed Bugs and Improvements: Projects created in the 10.5 version of Mistika VR are now compatible with the new features introduced in 10.6 - Render Options and CDL Grade. Autocalibrate "Error 6" and "Error 3" now displays clearer messages. Fixed issue related with overwritten files in Name Convention when installing additional Mistika Technology software. Insta360 Pro 2 Audio.mp4 files are now supported with the “Import Stabilization metadata” feature. Fixed issue rendering formats with 4444 Image. The Streaming driver is now stopped when the remote session is disconnected.

After filing a bug report, it appears that 10.6 does not upgrade or migrate the vrenv files to the new file format. all new functions (i.e. auto calibrate or CDL grade) only work on fresh files/projects, and will crash/destroy older projects.

Hi everyone! We have released a new version of Mistika VR introducing a magic autocalibrate tool and immersive stitching in the Meta Quest 2 headset. You can now download this latest update directly from the Downloads section of your SGO Online Account. 🙂 New Features Mistika VR Connect add-on application for Meta Quest 2 headset. With Mistika VR Connect you’re able to stitch 360º VR media directly in Meta Quest 2 headset, using some of the most popular features of Mistika VR. This innovative application allows you to manipulate your stitches to perfection and speeds up feedback cycles by providing (remote) VR output for your clients or team members in real-time. To see how to set up the connection between Mistika VR desktop host application and Mistika VR Connect, see this TUTORIAL. You can get Mistika VR Connect app by clicking GO PLAY. Features included to Mistika VR Connect: Autocalibrate tool Mistika VR essentials: Improve Offsets, Improve Angels, Match Color, Match Color in time Color Management, Edge Points, Camera Yaw, Pitch and Roll parameters Camera temperature exposure and tint controls Check out this TUTORIAL to discover Mistika VR Connect functionality in detail. Autocalibrate Tool. A new feature based on global stitching optimization, capable of calculating lens distortion and focal lengths of individual cameras, in addition of their sensor offsets and heading angles whose calibration was already supported by the "improve offsets/angles" features. The autocalibrate feature is specially beneficial for 3D stitching, as it produces much better vertical alignment of the stereoscopic view. Dynamic tokens and tags support. New tokens system enabling tag autofill in name convention. Select among several different tokens, such as resolution, color space or framerate and they’ll be part of the destination path or render name. These tokens can be added by using square brackets [example]. When you create the first bracket you get a drop-down menu with the different tokens, write or select the one you want and the bracket will close automatically. Custom Render Crop Options (180º x 180º Equirectangular). Output resolution customization depending on where our project will be projected - virtual set, dome, immersive room, etc. Spherical Transform. With the YAW, Pitch and Roll parameters we can now orientate the part of the image that we want to be displayed in the final render. CDL Grade for the Input Cameras - A new menu found in the Camera Controls panel, enabling primary colour grading operations for each of our cameras individually controlling offset, power, slope and saturation. Orientation Metadata Integration. This new feature detects camera position at which the media was recorded, by taking into account the metadata of the camera's gravity sensor and its orientation. Contact Sheet. Enabling the mosaic export from all the cameras we have in our sequence. This new option can be found in the Apply section of the Render options. When the Contact Sheet is activated in the Visual Editor we can only see the Mosaic view. User-defined Timecode/Frame display and processing. This functionality allows us to choose the Output/Render timecode of our Project and lets us work with the needed timecode in the Visual Editor. User adjust Camera Layer Order. New order system between layers. One way to understand this new functionality is considering Mistika VR as a layer system, where all the cameras are placed in the level 0 by default (the stitch level). With this new feature the user can move the cameras up and down as overlays, changing the layer order of each camera. Improvements Gyroscope Metadata Insta360 Pro 2 support in audio.mp4 file Fixed Bugs Switching cameras in the Clip Stack now displays the image appropriately in the interface MP4 NVidia movie frame rate is now working correctly Out/Input Gamma now works properly when using the mouse wheel Fixed Black GUI with AMD

Hi Jay, Thanks a lot for reaching out! We´ve received your message in our support portal so let me paste the reply I sent you via support portal 🙂 "In the case you have a different computer to send files there is a parameter that "force checking". This parameter is located at the Watcher node "Force check". Just set the number of second you want to the Watcher check for changes inside the folder. It should make work your workflow. Please let me know if it worked for you. Cheers! Carlos"

Hi, I have a watch folder on a shared SAN active running a workflow. When I use the machine running mistika workflows to drop a file into the watch folder, the script will run. But if I use a different machine not running Mistika workflows connected to the shared SAN and drop a file in, the script will not run from the host machine. Is there a fix to this? Do I need to run an auto trigger to check the watch folder? I had tried that with little success.

¡Hola++! What about RHEL 9? THX Peter Kovář

Hi everyone! We have released a massive upgrade of Mistika Workflows, adding several new smart features to further optimize content delivery processes and take Metadata Management to a whole new level. This version is already available on your Online SGO Account. New Features Extended render metadata support - Adding metadata export to XMP and CSV formats. To learn how to manage metadata in Mistika Workflows, take a look at this TUTORIAL. Edit Metadata Node - With this node, you are now able to modify and/or add file’s metadata. New tokens system added to Name Conventions - Dynamic tool, enabling tag autofill in name convention. You’re able to select among several different tokens, such as resolution, color space or framerate and they’ll be part of the destination path or render name. These tokens can be added by using square brackets [example]. When you create the first bracket you get a drop-down menu with the different tokens, write or select the one you want and the bracket will close automatically. To learn how to use these dynamic tokens, check this TUTORIAL. Additional tag fields available for Name Conventions Auto-filler for the FilePath items Smart Conform Filtering - To facilitate and speed up the deliveries, Mistika Workflows now allows you to perform the Conform only deploying the files that have been used in the final edit, being able to filter from XML, EDL or AAF files. To learn more about how this feature works, have a look at this TUTORIAL. Crop Node - Crop the image or the RGBA channels separately, or add a soft cut. Rescaling Functionality - Mistika Workflows is now able to automatically apply framing feature to your media, including resolution change, transform, rescale and crop. 3D LUT Node - Apply any look-up-table to your media automatically. The 3D LUT’s can either be generated in Mistika Boutique or in (any) other relevant program. To learn more about how to apply 3D LUT automatically, check out this TUTORIAL. Stitch Refiner - This new functionality enables you to refine your optical flow stitching of the .rnd files, automatically applying match color and geometry. STMaps Node - Applies STMaps to its corresponding cameras. Classify by Extension Node - This new node enables you to automatically filter and manage your files by extensions. The extensions can be added/removed by your preferences. Render farm integration adding Deadline support - Rendering tasks can now be handled directly by the Deadline render farm. To see how to set up the Deadline in Mistika Workflows, check this TUTORIAL. Bypass Functionality added to nodes; Watcher Node cache file - Intelligent system to prevent duplicating the tasks when modifying the workflow. Movistar 8.3 - Mistika Workflows now supports the entire delivery pipeline according to the latest standards of Movistar. winSMBcopy Node (Windows only) - Enabling Move & Copy of the files to the network location. JoinFile Node - Enables automatic merge of selected frame ranges. SplitFile Node - Enables automatic split of selected frame ranges. To learn how to use Join and Split nodes, take a look at this TUTORIAL. rndFile Node - .rnd files are now supported in Mistika Workflows. New Codecs 7thSense DNxHD opAtom FUJI RAF Other Improvements Improved GUI responsiveness when rendering Ipp2 params added to RED Node Upgraded CableLabs Node: Strict property added IsDownloadable and IsStreamable added to non strict CableLabs 1.1 Source added to non strict CableLabs 1.1 FTP Node upgrade: protocol property added Mail node moved to outputs Trash color connected to AreYouSure property Python Improvements: sgoPaths.apps exposed to python Python Modules Offline Installation getAffinity and giveBackAffility functions added to workflow UP getMetadata and readMetadataFromFile exposed to py PYTHON_HOME env variable not used anymore. new MISTIKA_PYTHON added setSupportedTypes implemented in python nodes Enhanced Line Commands Support: Autoload Folder Long parameters support -r param changed to work as in other Mistika products (autoload changed to -A) Check out Mistika Workflows playlist on YouTube to see all the tutorials.