Bugs & Feature Requests

Hello, After tinkering a bit with workflows, there is a feature i believe it is necessary: "on the fly" option for tasks that involve any kind of transcoding. At the moment, when trying to convert to a file a new location from "X" to "Y" format we are forced to choose between the following 2 ways: Case 01) - read from storage 01 -> convert on storage 01 -> move to storage 02 Case 02) - read from storage 01 -> copy from storage 01 to 02 -> convert on storage 02 -> delete copy on storage 02 It might seem pretty simple, but both scenarios create their own issues that could very easi…

Hi, I'd like to elaborate on three notes, about the workflows nodes, that have drawn my attention in the last few days. First: There is no way to "disable" nodes in the script. I know that must not seem prioritary, but when an extensive script populated with many nodes becomes buggy, disabling nodes for testing is the way to go. All node-based systems offer this possibility to the user. Second: It seems that the nodes don't rearrange well when a intermediate node gets deleted or cut. The default behaviour is to break the stream erasing the connection between the incoming and the dependant nodes on the graph, when, by default, the majority of node…

Hi, It'd be pretty interesting to include a simple node that modifies the resolution on the metadata thru the stream so we can setup "proxy" levels. This way, it would make visually easier, for the workflows operator, to identify/build structures on the graph in cases like the following: The graph above shows the following scenario: If we wanted to use workflows a a system to receive renders from a department, and create all the proper full/low-res exr/movs versions for the studio to use,, at the moment, the output resolution has to be set in each of the "output" nodes, which makes the graph difficul…

Hi!, I'd like to propose a future development that i think i would improve speed and usability on the workflows graph. Like in Unreal engine node editor, i'd like to suggest the creation of a contextual menu, pretty much like the one that exists now when using the right clic on the grpah, but limited to "Tasks and outputs" nodes only. The way it would work is the following: On the output of any node, the user clic+drag to create the line, but when releasing it on a blank area, instead of "loosing" the connection, a dialog box appears showing all the possible/compatible nodes that can be connected to the one we just drag the line from. I hope that t…

Hello, I believe that it is necessary to include a list of recent workflows scripts used in the "File" menu. Mainly for the sake of simplicity+Speed of operation. Thanks Miguel.

For clarity sake, Workflows should include functional backdrops on its graph. Backdrops not only are useful to group nodes, but also to make easier to read/rearrange/debug any node-graph. The difference is pretty evident on any graph: Without Backdrops:

Hi All Maybe a silly question!! But a small job I am doing, and will be onlining soon in Mistika, requires sparkles (don't ask!) like you get in the fun app KiraKira. Can such sparkles be added in online/DI using Mistika? All help gratefully received. Best Phil

It would be a good addition to the software a "node/extra input" that interrupts the flow of an stream until a signal is given to it. The following example paints it clearly: On the image I'm setting up an scenario were a piece of data has to be converted to a .tif format and then copied to another storage elsewhere. After the copy is successful, the .tif conversion requires to be deleted. According to the Overview, the thrash node will be executed before the copy one has a chance to be performed. This can very easily become a hazard and a serious threat to the integrity of the data/storage. A very quick way to solve th…

Perhaps it already exists and I'm not seeing it, but it would be awesome to have and edl conform input node to automate vfx pulls. Some nice features of an edl import node would be: Conform choices similar to other mistika products Get Clip Name from edl and assign to Base Name field Designate Handle length BMVL308_VFX_SCANS_004_20190205_3k_MUS_12.edl

I have a shoot coming up this weekend, with a small budget, which means that we probably will not have a DIT... so I'm thinking that it would be nice to set up a workflow to help with this. What I'm hoping to do with the workflow is as follows. It doesn't have to be triggered automatically, and that might actually be a bit awkward to do with a watch folder due to the windows driver letter business anyway, which is outside your control. Hence the awkward part. So my ideal would be: Plug in the Red minimag reader and the SD card reader Copy the audio + video to two drives Load the video, sync the audio by time code Embed the scene + take from t…

Hello, I launched Workflows for the first time today attempting to convert a ProRes to H.264 and upload to Frame.io. But whenever I would start the queue, the render would fail with a "Media Write Error." Screen grab attached. I got the same error with the H.265 encoder and the NVidia H.264 Encoder nodes. I checked to make sure I had free hard drive space, and even tried putting the base ProResHQ file in a few different places on my computer to make sure it was not a permissions issue. Sometimes when I checked the H.264 node, it was showing fps of 0.00. When I did "reload metadata," the fields would populate, but it would show up as a weird (and different f…

Hi, how fast are you capable to implement a new digital camera support? When a new camera or a new codec or a color science enters the market, how fast are you able to react to it with Workflows? It looks like a great tool, but for example right now I dont see any Sony cameras or Blackmagic etc. I'm curious, because if Workflows is a main trancoding hub in a vfx facilily for example, it has to be able to work with any kind of inputs, right? Thanks a lot, great stuff! Martin

I just upgraded to the latest release of Mistika Workflow. I was keen to try out the H.264 transcoding, since my most common workflow outside of the main app is building the delivery files from the master renders. Still issues. I took a ProRes input with my ProRes 444 master and I took a 'file' input for my audio WAV master connected them to a H.264 output, with default settings. Ran the queue, errors out halfway with 'H.264: Media Write Error', no further details. It created a file that is playable, but is only the first 30s of a 5min video. I ends abruptly at 30s. The H.264 settings are very terse and difficult to read. For example Bitrate just says 10. I gues…

Hi, I downloaded the beta of Mistika Workflows Linux version. I'm on an unsupported distro (Ubuntu 19.04) but I have a problem that I think it's a bug in the installer (and not related to using an unsupported distro). When I launch the .run installer it starts ok and asks for my system password. I type it in and it returns an error saying that the password is not correct but the password I type is correct. My password includes the special character ' which I think is the cause of the problem (maybe the installer doesn't recognized the character ' or maybe it expects it mapped on another key). I would rather not change my system password at this point so I was wondering …

In the open beta under the tasks there is a NVidia H264 node. But it seems to be tied to system with NVidia GPUs. On the current MacPro with AMD GPUs that leaves Mistika without any H.264 encoding task? That codec is required for any content destined for the web.

EXRClip input does not populate "Frames" variable although it shows the frame range properly in url. It would be logical if frame count is updated to reflect the url. None of the other values besides resolution, aspect, fps and format are filled either.