Frequently asked questions

The most efficient way is to create a support ticket at: moovit.jitbit.com/helpdesk. Alternatively, just send an email to support@moovit.jitbit.com or call 0221-30 200 240.

Yes, absolutely. The four components can be used in combination, but this is not essential. The license model is structured to allow the product range to be activated step by step, starting with HelmutFX.

Support costs will be 20% of the sum paid for all purchaised licenses.

A running support contract includes the product support as well as the quarterly released software updates.

Certainly! Watch the video to see our product manager, David, show you just how easily it works.

Yes. To find out more, read our case study on how ORF uses Swat.io and Helmut4 for integration. Link to press release.

Yes, Helmut4 is based on Docker and can be run in a Docker swarm custer. Therefore you will need a minimum of 3 server instances.

The Helmut4 client is compatible with Windows, MacOS, and Linux, while the server specifically requires either Ubuntu 20.04 LTS or Ubuntu 22.04 LTS.

Helmut4 actually supports Adobe Premiere Pro CC, Adobe After Effects CC and Adobe Audition CC.

No, Helmut4's architecture allows a potential of more than 1000 users working within one system without causing a significant system load.

Yes, with Helmut4 your are able to create as many free definable metadata fields as you like. You can do this via the web interface or via the API.

No, with Helmut4 you are able to build as many workflows (streams) as you like, no matter how complex they might be.

No. All exisiting user licenses can be used cross-product. For the system, a rendernode is just the same as an logged-in user with the task to render.

Yes, the Active Directory integration allows you to synchronize groups within Helmut4, and thereby define the rights of for these synchronized users. User can be added, actualized or deleted - as you wish.

Yes, HelmutIO will distribute the jobs by user names. That allows you to define, whether a job should be processed on the local workstation, on a certain workstation or over a pool of available workstations. As a result all ressources will be perfectly used without any bottlenecks in the process.

Yes, because all information about a project is mapped in Helmut4 in its own database (Cosmo) and can be accessed and distributed via streams. Information about the assets used in a project as well as their metadata and usage on a timeline can be called up and distributed. In this way, Helmut4 closes a major gap in the interaction between the NLE and the existing production environment (MAM / PAM).

For Helmut, an asset is the sum of all metadata information that belongs to this asset. Where is it stored, what name does it have, what metadata does it have and is / was it used in a project. This information can be transferred to the system directly via Premiere (Helmut4 Panel), as well as via watch folders, your own web upload, or the open REST API. Once the information has been passed, it can be used in any workflow (stream). This allows the system to load a Premiere project directly via a web upload or, for example, the API without having to open it. The synchronization with the database takes place automatically after the project has been opened.

Yes, all information about assets is stored in Cosmo. This also includes the fact that an asset was used in several projects. Within a housekeeper stream it is possible to call up this information and then filter whether an asset is unique in the project, i.e. only used in this project, or in other projects. You can also query whether the corresponding assets on the timeline have been cut or not. This information can be used later in the workflow.

Yes, this is one of Helmut4's easiest jobs. The streamdesigner therfore offers an action node, which can be used to create numerous files and subfiles. The structure can be dynamically adapted through the use of metadata and thus be exactly the same or completely individual for each project.

Yes, a node is available for this in the stream designer, which can be used in an "Open Project" stream, for example. This converts the project to be opened into the desired version.

In the 'stream designer', the output of each action node can be connected to an output node to output the information of this single action, or the information of all actions of a workflow. It is possible to send email, write files like text files, send notifications to the web interface or to the panel or send a telegram message to a group.

No. The Adobe Media Encoder is used to export sequences and compositions. Within the Stream Designer there is also the possibility to use FFMPG or Adobe Premiere.

Yes, Helmut4 allows you to analyse each file during the ingest process (Mediainfo/FFPROBE), and use the number of audio channels and/or streams as a basis for deciding which proxy to create.

Absolutely. Every production environment has its own requirements for workflows. These can be mapped and implemented via the Stream Designer. This option is available to every customer and enables maximum flexibility and agility.

Helmut4 provides a Javascript Action Node that can be used at any point in any workflow to exchange information between systems. You know Javascript? Now you also master the integrations in your production environment.

Absolutely. Due to Helmut's micro services architecture and the absolutely user-friendly way of creating workflows, the effort of an integration, provided that the system to be connected offers a good API, is a task of a few days. Talk to us.

Yes. The dynamic structure of the Stream Designer to link nodes as needed in the order they are needed also continues in the definition of the parameters of each Action Node. For example, project names can be automatically composed of all available information, such as: day, month, year, time, user name, project name, metadata, etc. The same is true for asset and each time a node is defined, it can be linked to another node. The same applies to assets and it is possible to use only parts of the information at any time.

All information about the sequence is stored during each export as a JSON file next to the sequence to be exported (on the storage). These parameters can be read out via the stream designer with the help of the JSON Extract Action Node and used as a condition for the further course of the stream (workflows). This makes it possible to precisely check whether the sequence is compliant.

Yes, and as much as you want!

Under certain conditions (timeline is correctly created and labelled), Helmut4 can remove individual video tracks during an export to create a clean feed. To do this, Helmut4 communicates via the Helmut4 Premiere Panel and executes the corresponding task, just as if the operator were doing it himself.