Carlos Gessler

Hi Jan Marteen! I´ve already added you feature request to close Mistika by cmd+Q beaing asked if you want to save the project. Thank you very much!

Hi Jan, sorry for the delayed response. 1. Mistika shows a warning message to save anytime that you´ve done changes and click on exit Mistika. This issue that you´ve descrived still happens? It happens everytime that you close Mistika? 2. I´ve already send your request to the Dev team. Anyway, I leave here the link where wspoke about to help other people that are reading this topic: 3. The comas and spaces are allowed in Mistika when importing. I´ve tried to import a file with the name that you´ve provided and I´ve been able to import it. Could you open a ticket sending us a file which Mistika can´t link due the name to test it deeper? 4. Thank you very much. I´ve added this as feature request! As always, thank you very much Jan! Cheers! Carlos

Hi Jan! The thing is in Mistika there are two auto keys. One related to the shape points and asoftness and the other related to position XY. You can modify the shape after doing the track by deactivating the Autokey. But, if you have animated the points or the feather, the only way to modify the shape and keep this new form is adding keyframes, adding a blur or making again the animation. Of course! I already included it in the feature request documentation. Have I nice day! Cheers! Carlos

Hi! Thanks a lot for reaching out! Of course, it may works. You could make a rig with different cameras, but, to be sure, the best way would be to test first the different rigs. Please, create a new ticket in: https://support.sgo.es/support/solutions You could send us a synchronized frame of each camera we could create the preset for that resolution but please try to send a scene that matches with the next. First, try to obtain a suitable scene for the calibration: To create a preset for that rig, please do the following: - Nothing and nobody close to the camera, at least 3 meters - A street with buildings and trees, squares, parking lots - Large halls, like sports venues, with a structured ceiling, with a camera in the open - Public garage with no cars or columns at less than 3 meters If a calibration shot cannot be obtained, choose the shot most fitting the above. Optional, especially convenient for cameras with little overlap: Ask for a static scene, and two shots, second with the rig rotated half its camera spacing: Means if they are 4 cameras at the horizon at 90 degrees, rotate the rig 45 degrees. This provides an apparent doubling of a number of cameras and produces better lens distortion detection. Notice that if a camera allows setting the image ratio at different values, like GoPro that can record both 4:3 and 16:9, settings for both resolutions may be needed. Recording a larger image is always better but some customers used a 16:9 ratio apparently. I look forward to your answer! Cheers! Carlos

Hi Jan! Thank you very much, now I know what you mean. I´m affraid but in this case, this autokey is referring to shape points and softness, so, the feather is part of these keyframes. Tto do a feather you could add a blur to the shape or make again the animation. I hope it´s useful! Cheers! Carlos

Hi Jan Maarten, Thanks a lot for reahing out! I´m not sure about what do you mean "Uber key" but, I thing the tool that you need is the "Shift" or the Scale parameters while you are working in the Keyframe graph. How it works? Please, Go to the Keyframe graph, select the keyframes that you want affect. Use the "Shift" tool to make an offset to the keyframes. Also, you can use the Scale parameters inside the Keyframe Graph. I´ve attached a video to show you how it works. . Please, let me know if this is the tool that you referred. Scale Tool.mp4 Shift Tool.mp4

Hi, Илья Ивановm, The render function "by block" generetes one render per different "block". Mistika will interpretate as blocks the clips between spaces. So, you could have different versions of projects on your timespace and Mistika will render them as different renders. See the media attached. (The clips named as "block" are only a representation for help to understand which clips Mistika undestand as blocks) Please, let us know if you have any doubts! Cheers! Carlos

Hi Thashisho, Sorry for the late reply. Of course, the most quickly workflow that you could create is working with the Watcher folder. Please, to work with the Watcher Folder, follow these steps: - Create a Watcher Folder in Mistika Workflows. - Give a source folder to the Watcher Folder (You could drag and drop the folder into the Watcher folder or you could select it in the file field). This folder will receive the files or folders that you want to transcode. - If you have different extensions on your folders, please, use the Include and exclude fields in the Watcher Folder. - Link a set colorspace node to the watcher folder to select your ammut and Gamma. - Link a ProRes node (or another transcode node). Set your output colorspace and give an output folder. - Add to the queue. - Then, copy your folders and past into your folder linked to your watcher node folder. The workflow starts. Here you have a tutorial in which you can see how the watcher folder works from the minute 8:10: Of course you could select another high 444 12 bits formats as Mistika JS or sequence formats as EXR. Let us know if you have any more doubts. Cheers! Carlos

Hi, Thashisho. Thank you very much for reaching out and thank you for using Mistika Workflows, which is much appreciated. I´m affraid DNG Raw is not supported in Mistika Workflows. But, if you would like to use a Folder node to transcode any other group of sequences into single videos, you can do it in an easy way: Drag and drop the folder that contains your sequences into Mistika Workflows. Drag and drop a task node to transcode your media. If you want to transcode your media into a ProRes files, please, drag and drop the ProRes task node. Select an output directory to your transcoded media. You can do it by drag and dropping your destination folder into your ProRes task node for example. If you have media in your folder that you don´t want to transcode it, you have the "include" and "exclude" options on your Folder input node. If you have in your folder, for example, R3D files and .mxf files and you only want to transcode the R3D files, please, type "*R3D" in the "include" field and "*mxf" in the "exclude" field. Also, if you have Raw files or you need to do a color transform, you can use the SetColorSpace task node. Please, link the Folder input node to the SetColorSpace node and link the SetColorSpace node to the ProRes task node. Open the SetColorSpace properties by clicking on this node. Select our Gammut and your gamma (Gamma REDLog3G10 and Gamut RED Wide Gammut RGB (RED) For example) Add to Queue and click on play. The render starts. I´ve attached 4 screenshots to show the steps. Let us know if you have any more doubts. Cheers! Carlos