Transcoding is the step in Projector that converts a finished video from one codec to another, so the file you deliver is in the codec you chose. It is optional, and the clearest way to decide whether you need it is to know what the step does and what each setting changes.
This article is for the producer or developer who has a batch of personalized videos coming out of After Effects and has to decide what happens between “rendered” and “delivered.” We will go through where transcoding sits in a Projector payload, what each transcode setting does, a worked example with two payloads built from one composition, and the cases where you should leave the whole thing switched off.
Where transcoding sits in a Projector payload
Projector organizes work as payloads and missions. A payload is a collection of one or more missions, and a mission is one job inside it. Per Dataclay’s terms page, a mission can consist of any or all of five tasks: exporting data-merged Autografs to digital files, transcoding the versioned output, deploying the transcoded files to a storage and streaming platform, logging metadata from those platforms back to the connected data source, and cleaning up the scratch assets the other tasks created.
Mission task order
Five tasks run in this order inside a mission
-
ExportExporting data-merged Autografs to digital files.
-
TranscodeTranscoding the versioned output.
-
DeployDeploying the transcoded files to a storage and streaming platform.
-
LogLogging metadata from those platforms back to the connected data source.
-
Clean upCleaning up the scratch assets the other tasks created.
Transcoding is the second of those tasks. Dataclay’s own documentation defines it as converting an audio or video file from one codec to another. A codec is the compression and decompression method a video file uses. Raw, uncompressed video is very large, which makes it hard to store and stream cost-effectively, so files are compressed before storage or delivery and decompressed when played. Different file formats, such as MP4, AVI or WMV, support different codecs. The file format is the wrapper and the codec is what is inside it. The two are not the same thing, and mixing them up is the fastest way to get confused by the settings screen.
The documentation gives one plain reason to transcode. If you send video directly to people who might have bandwidth limits, you can pick a codec that produces a smaller file. That is the whole pitch. Projector has a built-in transcoder so you can make that conversion part of an automated distribution workflow, instead of a separate manual pass after the render finishes.
The same documentation is equally plain about the other side. Not all videos require transcoding. If the file coming out of your render is already what you want to deliver, you can leave the step off, and Projector does nothing to it.
The step also appears as a state in the stream-status lifecycle for Projector and Que: “transcoding,” a file being transcoded for delivery, listed between “staged” and “deploying.” Our article on Projector stream status walks through the full sequence of states.
Two scope points are worth fixing in your head before you touch any settings. First, transcoding settings apply to all the missions within your payload. There is no per-mission override inside a payload. If some videos need different settings from others, you split them into separate payloads, and we will do exactly that in the example below. Second, Projector must run on the same computer where Templater is installed and where its output files are stored. If you are new to how the pieces connect, what Projector is covers the ground, and Que versus Projector explains which product handles which job.
The settings, one at a time, and what each one costs you
The transcode settings live in the Transcode section of the Projector interface. You start with the Enable transcode checkbox. Everything else follows from that choice. Below it are four checkboxes about what to do with the files, and then a Setup panel for the encoding itself. We will take the encoding settings first, because they decide what the viewer receives.
Video codec. Projector currently supports a limited number of codecs, and Dataclay says more will be added based on customer requests. The codec you select decides the file type of the finished video. Dataclay’s documentation points to H.264, the codec the MP4 format uses, and describes it as optimized for streaming with good quality even on older or less powerful devices. Its FAQ adds that you may want something different if you are creating very high-definition videos. One interaction matters here. If you do not enable export, Projector uses the file type from your transcode settings for every video in the payload, even if your Google Sheets data source has an output-ext column asking for something else. The output-ext column only takes effect when export is enabled, and only with Google Sheets as the data source.
Video bitrate. Bitrate is tied to frame rate and video definition, and Dataclay’s guidance for 30 FPS web video on a computer monitor is that it should generally fall between 3,500 and 6,000 Kbps. Higher bitrate means better quality and a larger file. Lower bitrate means a smaller file and lower quality. The documentation is candid that if you are new to streaming, you may need to experiment within the recommended range. That is honest advice. No setting on a screen can tell you whether the compression artifacts in your particular template are acceptable. Your eyes can, on a sample.
Video pixel format. Dataclay recommends yuv420p unless your videos will be viewed on something other than a standard computer screen or a mobile device. We have nothing to add to that, and we would not change it without a specific reason to.
Audio codec and audio bitrate. If you deploy to a streaming service, Dataclay says to always select AAC, because most streamers require audio in that format. The recommended audio bitrate is 128, which the documentation calls a nice average for AAC audio. The FAQ also notes that for video files the audio codec must be compatible with the video codec, which is one more reason to stay on the recommended pairing unless you know why you are leaving it.
Transcode settings
Recommended starting values for each encode setting
| Setting | Recommended value | What you trade |
|---|---|---|
| Video codec | H.264 | Optimized for streaming; sets the output file type |
| Video bitrate | 3,500 to 6,000 Kbps at 30 FPS | Higher = better quality, larger file |
| Video pixel format | yuv420p | Change only for non-standard screens |
| Audio codec | AAC | Required by most streaming services |
| Audio bitrate | 128 | A nice average for AAC audio |
Output location. You enter the folder path where Projector should save transcoded videos, or you browse to it, or you check the box to use the asset directory as the output directory. This is a small setting with a real consequence. It decides where the file you will deploy or archive actually lives, so set it deliberately and keep it somewhere you will remember when you go looking for a single file later.
Output width or height. You pick one or the other. Projector adjusts the other dimension to maintain the aspect ratio. Dataclay’s guidance is to size the video for how your users watch, if you know. If you are not sure, or your audience watches on a variety of devices, the documentation says you might opt not to specify sizing at all. The reason is cost. Larger dimensions mean larger files, and larger files mean higher upload, delivery and bandwidth costs.
Two of these settings, video bitrate and output size, trade quality or reach against file size, and Dataclay ties file size to upload, delivery and bandwidth costs. Dataclay’s guidance is to stay inside its recommended ranges and, if you are new to streaming, experiment within them on a sample.
One note on the order of work. Transcoding runs on videos that already exist. In a full Projector workflow, Templater creates a replicate of your After Effects project for each row of data, Projector’s export step renders those replicates into finished videos, and then the transcoder converts the results. Dataclay’s FAQ is explicit that export and render are separate steps in Projector, so the two words are not interchangeable. Projector can also take a finished video you already have, such as a MOV or AVI, and transcode it into a new format without any rendering at all. In that case you leave AEP rendering off, and the transcoder starts from the file you point it at. Our article on Templater covers how the replicates get made in the first place.
A release note is worth knowing about if you run long batches. Dataclay’s release notes say workers now report transcode progress more precisely in Mission Control, which gives a clearer picture of how far along the work actually is. A worker, in Projector’s vocabulary, is one processor core assigned to process missions. By default Projector uses half of the cores on the machine, and a slider at the bottom of Mission Control lets you change that. If you see slowness or heavy memory use, the documentation says you may want to lower the number of workers.
One composition, two payloads: a worked example
Dataclay’s FAQ includes a scenario that shows how the settings come together, and it is a better teacher than any list of checkboxes, so we will use it here with the producer’s name from the documentation. Maya renders 500 short promotional videos from the same composition. She personalizes 499 of them, and she will send those to individual customers as part of an email campaign. She also plans to stream one non-personalized version on her Vimeo channel and promote that link in a social media campaign.
Because transcode settings apply to everything in a payload, Maya cannot run all 500 through one set of settings and get both outcomes. So she splits the work into two payloads. From her data source she chooses which videos go in each one.
The first payload holds the 499 personalized videos. Maya knows her customers are most likely to view videos on a mobile device, so she transcodes with that in mind. She also wants a GIF clip for the campaign, and she will use a personalized video frame as the poster to increase engagement. The second payload holds the single non-personalized video. It gets transcoded for optimized streaming on Vimeo. It does not need a GIF clip, and it gets a different frame as its poster.
Look at what is happening there. The two payloads share a composition and differ in nearly every delivery decision. Because the two groups go to different places and are watched in different ways, they are two payloads.
Two payloads, one composition
Personalized email vs. Vimeo stream need separate payloads
- How viewers watch
- 499 personalized videos, email campaignMost likely on a mobile device
- 1 non-personalized video, Vimeo channelStreamed on Vimeo
- GIF preview
- 499 personalized videos, email campaignYes, for the campaign
- 1 non-personalized video, Vimeo channelNo, streaming services don’t use GIFs
- Poster image
- 499 personalized videos, email campaignPersonalized video frame to increase engagement
- 1 non-personalized video, Vimeo channelDifferent frame as its poster
Because the two groups go to different places and are watched in different ways, they are two payloads.
Now the four checkboxes that sit above the encoder settings, because Maya’s choices touch each one.
Delete original after transcode. The documentation says to select this if you will not need the original again. In practice that means the pre-transcode file is removed once the transcoded one exists. Once it is gone, you cannot re-transcode from it, so if you might want to try different settings later, leave the box cleared. That follows from what the checkbox does and is not a separate Dataclay recommendation.
Create GIF preview. The documentation asks the question for you: should I create a GIF preview? If you only plan to stream the video on a streaming service, probably not. The more videos you produce, the more time it takes to create a GIF for each one, and there can be storage implications too. A GIF preview is a good tool when you plan to promote videos on social media, embed them on a website, or deliver the customized video as part of a direct email or messaging campaign. That describes Maya’s first payload and does not describe her second. So the first payload creates GIFs and the second leaves the box cleared. Dataclay’s terms page defines a GIF clip as a short excerpt of the video saved in the bandwidth-friendly GIF format, and says you can configure when the clip starts and how long it lasts.
Archive poster image and Archive GIF preview. These tell Projector to save the poster and the GIF to your storage location. The documentation says streaming services do not use GIF previews, so if you create one you should always archive it as well. There is a hard dependency here. The storage documentation warns that you must enable and set up archiving if you configured the payload to archive posters, GIF clips or both. If you do not, Projector skips archiving completely and those settings are ignored. Archiving currently means an S3 bucket in a storage account that you provide.
The poster deserves its own sentence. A poster, sometimes called a thumbnail, is the still image used to promote the video. Dataclay’s FAQ says it takes time for Projector to extract a still and convert the image format for each mission, so if you are producing hundreds of videos, lower image quality can save time. The same answer says that might not give the viewer the experience you want, and suggests you configure the best image quality you can while still controlling production time. For a batch of 499, that is a real decision and not a footnote. Test a handful at your chosen quality, look at them next to each other, and then commit.
One more setting from the streaming side connects back to posters. In Streaming Globals, a Poster Time value tells the streaming service which moment of the video to use as the thumbnail. Dataclay strongly recommends creating a poster image in Projector instead, since the frame at a fixed time may not be personalized or attention-grabbing. If you do enter a time, the documentation warns you to know how long your customized videos are. Its example is a three-second video with a poster time of 3.5 seconds, where the streaming service falls back to the first frame. It adds that if your videos differ in length, a single value will land on the intended frame for only some of them.
Finally, Maya’s privacy choice. Streaming Globals offers three privacy levels. Dataclay recommends keeping the video visible to the owner only as the default, because it lets you play through and check everything and stage videos before a campaign, and you change the setting on the streaming service when you are ready. The documentation says public and platform-members-only options are not recommended for personalized videos, since you may not want everyone to see every video. That is not a transcoding setting, but like transcoding it is set at the payload level.
When to skip transcoding, and the bottom line
Dataclay’s documentation says it directly: not all videos require transcoding. So when should you leave it off? The honest answer from the saved documentation is narrow. If the files coming out of your render are already in the format and size you want to deliver, the transcoder has nothing to fix. We do not have a published measurement of how much time the step adds to a batch, and we will not invent one. If time matters to you, run ten videos with the step on and ten with it off, and read the difference from your own machine.
There are three limits you should know before you plan around the transcoder.
First, the codec list is short. Dataclay says Projector currently supports a limited number of codecs and that more will be added based on customer requests. If your delivery requirement needs a codec the menu does not offer, you will need to handle that step outside Projector, or talk to Dataclay about it. The Learn section has related guides.
Second, settings are per payload, not per mission. We showed the fix, which is to split payloads. The cost of that fix is bookkeeping. You need a clear way in your data source to say which rows belong to which payload, and Maya’s scenario assumes she has one. If your data is messy, sort that out first.
Third, the transcoder converts files that already exist. It starts from the video your render or your finished video produced. Our guide to After Effects templates for batch rendering covers the template side, and our piece on on-screen quality for small streaming outfits is a related read for the broadcast side.
Here is the bottom line. Turn transcoding on when the file you render is not the file you want your audience to receive, because of size or compatibility. Start from Dataclay’s recommended settings: H.264 for the video codec, a bitrate in the 3,500 to 6,000 Kbps range for 30 FPS computer-monitor video, yuv420p for pixel format, AAC at 128 for audio. Leave sizing alone if you do not know how people watch. Split your payloads when delivery differs. Leave Delete original cleared until you are sure of the result. And test on a small sample before you commit a whole batch, because the transcoder will apply your settings to every video in the payload exactly as written.
Before you run a batch
Do these before committing a full batch to transcode
- Turn transcoding on only when the rendered file is not the file you want your audience to receive
- Start from Dataclay’s recommended settings: H.264, 3,500 to 6,000 Kbps, yuv420p, AAC at 128
- Leave sizing unspecified if you do not know how people watch
- Split your payloads when delivery differs
- Leave Delete original cleared until you are sure of the result
- Test on a small sample before you commit a whole batch
We covered the settings and one full example above. Here are the questions that come next when someone is about to switch the step on.
Frequently Asked Questions
What does Projector’s transcoder actually do?
It converts a finished audio or video file from one codec to another. Dataclay’s documentation gives the example of sending video to people with bandwidth limits, where you pick a codec that produces a smaller file. The codec you choose also sets the file type of the finished video. The step is optional, and Projector does nothing to files in a payload where transcoding is switched off.
Can I use different transcode settings for different videos in one payload?
No. Transcoding settings apply to all the missions within a payload. If some videos need different settings, split them into separate payloads and choose from your data source which videos go in each. Dataclay’s own example does this with one composition: a personalized email campaign in one payload and a single non-personalized video for a Vimeo channel in the other.
Which settings does Dataclay recommend as a starting point?
The documentation recommends H.264 for the video codec, a video bitrate between 3,500 and 6,000 Kbps for 30 FPS web video on a computer monitor, yuv420p for the pixel format, AAC for the audio codec when deploying to a streaming service, and an audio bitrate of 128. If you are new to streaming, it says you may need to experiment within those ranges. Test a small sample before a full batch.
Should I set an output width or height?
Only if you know how your audience watches. You pick one, and Projector adjusts the other to keep the aspect ratio. If you are not sure, or viewers use a variety of devices, the documentation says you might leave sizing unspecified. Larger dimensions mean larger files, and larger files raise upload, delivery and bandwidth costs.
Do I need a GIF preview for every video?
No. If you only plan to stream the video on a streaming service, the documentation says you probably do not need one. Each GIF takes time to create, and there can be storage implications across many videos. A GIF is useful for social media, website embeds, or direct email and messaging campaigns. Streaming services do not use GIF previews, so if you create them you should archive them too.
What happens if I choose to archive posters or GIFs but never set up storage?
Projector skips archiving completely and ignores those settings. You must enable and set up archiving if the payload is configured to archive posters, GIF clips, or both. Archiving currently goes to an S3 bucket in a storage account that you provide, and each mission is archived separately.
Does an output-ext column in my Google Sheet override the transcode file type?
Only when export is enabled. Dataclay’s release notes say that with export on, you can change the file type of exported videos dynamically with the output-ext column, which currently works only with Google Sheets as the data source. If you do not enable export, Projector uses the file type set up in Transcode for all videos, even when other values appear in your data.
Should I delete the original file after transcoding?
Do it only if you will not need the original again, which is the guidance on the checkbox itself. If you may want to re-transcode with different settings later, leave it cleared.
