Javier Moreno

Hi Guys, This Google doc contains an introduction to the Mistika Workflows Script Editor Introduction to Mistika Workflows Script Editor It is still a draft document for the beta version. Please provide your feedback in reply to this post...

Hi are you sending the audio trough the Aja board or trough the motherboard? To confirm If it is a codec issue or not , try to get some footage with any other codec (Prores, Avid mxf, ... ) and see if it also happens. Then, if it is an issue of that specific codec issue I would recommend to open a support ticket and send a link to one of those files, so it can be further investigated by Mistila developers

Hi, I'm afraid this is not possible. The render resolution needs to be changed manually.

Hola Manuel, Las carpetas a usar las pregunta durante la instalación, no estás obligado a usar las que vienen predeterminadas. La carpeta de proyectos es donde Mistika crea cada proyecto (cada proyecto se guardará en una subcarpeta de ese sitio). Y si que tiene gestor de proyectos, solo que este está ya dentro de Mistika , no en la herramienta de configuración (por lo que no sale en ese vídeo) . Cada proyecto puede contener muchos timelines diferentes e incluso subcarpetas que vayas creando para organizarlo. Es decir, en Mistika un proyecto no es "un timeline" sino típicamente el nombre genérico de una producción completa que puede contener muchas versiones, pruebas, renders, referencias a la media importada, etc. Por otra parte, la otra carpeta que se pregunta es para la media por defecto. Esto simplemente es para que cuando haces render (o una captura de video) ya te proponga un path por defecto bajo ese sitio, pero siempre lo puedes cambiar sobre la marcha. De hecho el "path builder" (accesible tanto desde la herramienta de configuración como desde las opciones del panel de render ) te permite definir presets con sintaxis a media, para definir donde y como quieres construir los path de directorios destino y nombres de fichero de la media producida en los procesos de render. De esa forma no tienes que definir el path en cada render, solo elegir el preset que quieres.

The latest presets can be download from the presets forum: https://forums.sgo.es/forums/index.php?/forum/46-rig-presets/

It looks like a permissions issue. You may need to login in your account before you can download those links

Hi guys, The VR 360 tutorials for Mistika Boutique are here: VR 360 Workflows in Mistika Ultima & Boutique

test2, this is a test , please ignore..

The key aspect is the GPU, I suppose your rig has 6 cameras and you want stereo at high resolution. The GPU will be critical for this. Then, the PC2 and PC3 sound better, as the 1070 should be faster than the 980. As you want highest resolution I would aslo recommend a bit more RAM, also because it is not a expensive component. 32GB should be fine. Regarding the GPU, a better option would be a gforce 1080 ti, but it depends on your budget, the 1080 ti is faster but logically more expensive. Also please note that if you use a very fast GPU you will also need a CPU that can keep the rythm during the render. A particular case that requires hi spec CPU is rendering to Prores, which is a slow format and the CPU will need to be decoding the camera files and encoding to Prores at the same time. In that particular situation, having a top spec GPU with a slow CPU could transfer the bottleneck from the GPU to the CPU. Meanwhile, if you plan to render with the NVidia encoder then an average CPU model is enough One more detail. If you plan to render to compressed formats (mpeg4, h264/h265, Prores) then that's all you need. But if you need to render to uncompressed formats like DPX then you may want to pay attention to the hard disk, use a fast model or a decent SSD.

They are the coefficients of a third degree polynomial. MistikaVR uses uses same formula as PTGUI for compatibility. Here it is a description: http://www.ptgui.com/ptguihelp/main_lens.htm In few words, each one is related with the distortion in the outer, middle, and center areas of the lense.

The 2.9 fps sounds normal for that specs, but it also depends on the complexity of the scenes. The complexity depends on these aspects, from top to down: - The activation of Optical Flow. This is the most complex process of all. - The number of cameras and their total aggregated resolution - The render resolution and the render codec. In general, those processes need these resources: - Most of the processing in Mistika VR is made by GPU: Geometry adjustments, Color adjustments, Optical Flow (which is typically the bottleneck), etc. Then, the GPU is the most critical component. - The processes that are let to CPUs are only the decoding of camera codecs and encoding of the render codec. With the exception of uncompressed codecs and the NVidia codecs in the particular case of Windows. Then, if you see low CPU usage while rendering it is probably because the GPU is acting as a bottleneck, and a faster GPU would be recommended. But if you see very high usage of CPU while rendering, then the image codecs are the bottleneck. Selecting an easier codec for test renders may help , or if you have an SSD or a fast disk array you could use an uncompressed formats to save CPU resources. In general, most of the render panel options are auto explicative. Except the Add to render queue button, for which there is this document in the knowledge base Regards, Javier

Hola Alfonso. La manera fácil de ejecutar una lista de trabajos de render en Batch es añadir multiples escenas al mismo timeline, y luego al dar a render seleccionar la opción All Shots. ¿Es esto lo que no te funciona? En cambio, si lo que estás intentando usar el botón "Add To Render Queue" (por favor confirma) ese botón no es para gestionar los render con Mistika VR sino para integrar con programas de gestión de render de otros fabricantes. Por ejemplo Smedge ( es gratis para la primera máquina o número de horas, por si lo quieres probar). Su uso se explica en la knowledge base de la sección Tribe->Support , en este artículo: https://support.sgo.es/solution/articles/1000253968-integration-with-external-render-farms-add-to-render-queue- Saludos, Javier