Workflows using Emotion Systems tools

Although most of our website concentrates on our various tools, a number of customers have contacted us asking how they might use our tools as part of achieving complex workflows. Therefore, here we present a number of workflow examples from our customers, and describe how our tools can meet these needs. For ease of explanation, everything is described using our desktop tools in a manual configuration. Of course anything that can be achieved with our desktop tools can be achieved fully automatically using our eNGINE.

I need to loudness correct multiple languages at once
Our eFF tool has flexible channel layout options, and can correct up to eight stereo tracks in a single pass. Each track is individually corrected.
My MXF contains PCM and Dolby E tracks. Can you help?
Dolby E support is optionally available with all our products. Without a Dolby E option, our software will still process MXF or MOV files containing Dolby, but the Dolby encoded tracks will remain unchanged during processing. With the option, you can ensure Dolby E encoded audio is loudness compliant. PCM and Dolby tracks are all adjusted in a single pass, and each track is adjusted individually.
My incoming files have the language tracks in the wrong place. What should I do?
eRAP can be used to open your MXF or MOV files, and can move and track to a new location.
How can I mute unused/unrequired tracks in my MXF/MOV?
eRAP can be used to mute any chosen audio tracks.
I have been asked to supply HD files in the DPP or AS11 format, but the audio is in the wrong place
eRAP is fully compatible with files in DPP or AS11 format, and can remap audio channels as required.
I need to rework the audio in DPP or AS11 file, but I have heard this is not possible
With eRAP, it is easy to replace either one or more audio tracks with new tracks, or just to replace a short segment.
My files only have PCM, but I need to send Dolby E encoded files to playout
eCODE can be used to take a combination of the PCM audio in a MXF or MOV file, and convert it to a Dolby E encoded wav. Then you would use eRAP to insert the Dolby wav back in to your original MXF/MOV
My files contain Dolby E audio, but I have to supply PCM files to playout
eCODE can be used to create a PCM wav from the Dolby E within your MXF/MOV, then eRAP would be used to place that wav into your original MXF/MOV file at the correct location.
I do a lot of Audio (Video) descriptor work, and need access to the M&E in the MXF/MOV
eRAP can easily extract the entire M&E track, or just a short segment.
I do a lot of Audio (Video) descriptor work, and need to insert my new audio into the MXF/MOV
This can be done easily with eRAP. It can either take your newly mixed audio and replace an entire existing track, or can just replace a short segment of the existing audio
I have a separate Audio (Video) descriptor track, but I need it included in the Dolby E track in my MXF/MOV
I have run out of channels in my playout server, yet need to add Audio (Video) descriptor, so I will be going to Dolby E. How can I achieve this?
This is a common requirement. We would start with using eCODE to Dolby E encode either the PCM in your original MXF/MOV, or you WAV file as needed. Then eRAP would place the encoded audio into the correct locations, shuffling the existing tracks around as needed. Finally you could use eFF to loudness correct all of the PCM and Dolby channels.
I like your flexible manual workflow tools but I don't understand how they can be automated?
Our eNGINE tool uses a REST API, and can control arbitary numbers of parallel processing paths, which can be split over multiple hardware units, or run in large virtual machines. We let you make workflows using our tools in various combinations, and your own tools pass jobs and profiles to eNGINE
Some vendors charge a lot for creating new workflows. Do you?
A key advantage of our solutions compared with some vendors is that ongoing costs are slashed. Rather than providing software that is so complex to operate that only we can create new workflows, we instead provide you with an easy to use graphical tool. As you need new workflows, you create them yourself. Of course we will always help as required, but in most instances you will find you can easily achieve everything you need without contacting us.
Your tools are not integrated into my MAM. What is involved in achieving this?
A major advantage of our approach is that eNGINE can be configured to carry out a whole sequence of operations, and we distill this down to a single ‘workflow’. Hence the MAM sends a single MXF/MOV file, and chooses a single workflow when a file is processed. The MAM does not need to know whether our software is carrying out a single operation or ten.
How much MAM integration rework is required when I need to change my workflows?
As we use a single “workflow” to represent a whole series of operations, and you can edit the workflows yourself with our easy to use UI tools, then there is no MAM re-programming required just because you now need to add Dolby E encoding into your process, for example. The MAM continues to call a single workflow, but the workflow now does a more complex set of operations. This provides huge savings in MAM maintenance, which reduces your overall costs.

By continuing to use the site, you agree to the use of cookies. To change your mind please go to our Cookie Policy Page. Cookie Policy

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.