Thanks for you answers.
Max.

I'm experiencing slow rendering times in MistikaVR, especially when working with high-resolution 360-degree videos. I've checked my system resources, but I'm not sure if there are specific settings or configurations that could further optimize the rendering process.

Could you provide some tips or recommendations on how to improve rendering speed in MistikaVR? Are there any specific GPU settings, CPU configurations, or workflow optimizations that you would suggest?

Thank you for your assistance!

Frame.io has recently released Version 4 of their API, which is incompatible with the version currently used in the Frame.io node within Mistika Workflows. 

This means that if you upgrade to the new version of Frame.io, the existing Frame.io node in Mistika Workflows will cease to function.

Our team is already working on developing an updated, compatible node for Mistika Workflows. If possible, we recommend postponing the update to Frame.io V4 until we can confirm that the new node is available.

If you have any questions or need further assistance, please feel free to reach out. We appreciate your understanding and patience.

Thanks
miguel.

Very unworkable ..., I had to uninstall it.

My system is on MAC VENTURA 13.5.

I had an issue with the installation of my Mistika Workflows license.

I downloaded and installed everything as instructed. But when I try to launch the activation tool, the mac spinning beachball appears and after a while, I need to force quit the activation tool.

Are there any log files that I can send to you to troubleshoot? Or is there something within my system that is blocking the activation tool from launching? This is a corporate mac that I am using so if Mistika workflows needs to release some firewalls or outgoing ports etc, pls let me know.

Strangely I am able to activate my Boutique license on another company machine without much issues.

Thanks

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

The DNxHR/LB will not render to atom format.  (separate video/audio)  And it still gets quarantined.

I would like to ask if it is possible the make use of Mistika Workflow and setup a H.264/265 transcoding farm which means I can make use of multiple workstations to do batch jobs?

Regards,

Curly

If the file gets inspected with info, it shows one audio track, instead of the quantity that the source has.

ex: 

and 

What would I do in mistika?

Thanks for your support.

I have the perfect project that I wanted to use Workflows for but unfortunately there seems to be a few issues that I am unable to resolve that you might be able to help with?

I have files from a camera without proper filenaming or timecode so I need to generate files that are usable within a post production workflow. My plan was to create ProRes master files to use in the online and MXF Avid media for the offline, an easy task for Workflows you would think?

My first issue is that in order to rename the source with a consistent structure my files end in the date so for example: A001_B001_1234_200730.avi - Workflows takes the last numbers of the file, in this case my date string (200730) and strips it from the filename and uses this as the timecode generator. This is fine for a file sequence where you may want the frame numbers removed but that may not be what you want to use as the timecode, also it removes that string from the filename but leaves it intact for the tapename field so I end up with  ProRes and MXF files with the incorrect filename but the correct tapename and wrong timecode! If I ‘ cheat’ the system and add _000000 to the end of the source filename I can get Workflows to generate the correct timecode that I am after (in this case 00:00:00:00) and filename but the _000000 is left in for the tapename! There needs to be an option to force timecode to be a specific value within the parameters of the node, especially when there is no embedded timecode in the source media and the same with tapename. There needs to be an easy way to ensure that the tapename can be generated consistently with the filename.

The second issue is with frame rate. My source files are inconsistent frame rates but I need to bring a consistent value to them. In this case, sources can be 30fps but I need to make everything 25fps. The way Workflows handles this is inconsistent with the way Ultima handles it. I do not need any sort of retime, I just need to tag the newly generated files with the updated frame rate. If I being the source media into Ultima in a 25 FPS project and keep it frame for frame and compare it to what Workflows has generated the duration matches but there is some shift in the actual image timing? It is like Workflows is applying some sort of retime when changing frame rate rather than just tagging the files as the intended frame rate?

Any advice appreciated or if any of those Missing features could make in into a future release I would really appreciate it!

Thanks.

Vote for your favourite feature to be added to Mistika Workflows!

Community’s feedback is essential to make Mistika Technology better every day, so SGO invites all users and industry professionals to let us know which feature they would like to see implemented in future releases of Mistika Workflows.

This Survey contains three questions only and will not take more than two minutes to complete.

GET STARTED

Thank you for your collaboration!

The idea is to generate a checksum for a given file or folder, copy it to a new location and verify the copy.

Here is a screenshot:

If I run the workflow it fails, but the files are copied properly.

If I run a verification of the copied files on a separate workflow there is no error.

Workflows build 20200504, Windows 10

Can I timeline render with Mistika workflow?