Monday, March 5, 2012

Re: [Avid-L2] shorthand for compositing subtitles vs data track?

 

This can go in / out Avid, (using the Subcap effect), render way better
titles than Avid does with Subcap,
export for DVD (in 4 colored bitmaps with anti-alias between text and
outline), export for Flash / JWplayer / SAMI / Youtube and a couple of other
formats,
it is a way faster subtitle editor than any NLE and it comes with great
support. (by me :-)
http://www.videotoolshed.com/?page=products&pID=12

Bouke

VideoToolShed
van Oldenbarneveltstraat 33
6512 AS NIJMEGEN
The Netherlands
+31 24 3553311
www.videotoolshed.com
For large files:
http://dropbox.yousendit.com/BoukeVahl998172

----- Original Message -----
From: "Paul Dougherty" <lists@postlit.com>
To: <Avid-L2@yahoogroups.com>
Sent: Tuesday, March 06, 2012 2:08 AM
Subject: [Avid-L2] shorthand for compositing subtitles vs data track?

> As I research a possible (5min) subtitling assignment I'm trying to
> see is there is a shorthand for simply adding (marrying) translation
> subtitles to a video vs a job that is best suited to having a text
> data track created. For example for dvd or new media delivery, one
> would want to avoid actually compositing subtitles with video. In my
> project I think it's just fine to composite them. In doing my
> research I probably want to sidestep the fine points of title
> metadata track issues and just look for solid subtitle
> conventions/guidelines advise and workflow best practices. That is
> treat it as an ordinary titling assignment and try to follow say the
> "BBC Subtitling Editorial Guidelines"
>
> At a glance how does one tell one approach vs another, again is there
> a shorthand or moniker for the different approaches?
>
> I suspect my client will need this on a regular basis, so I might as
> well take the plunge and try to master the process.
>
> Thanks in advance for any advise.
>
> Paul Dougherty
>

__._,_.___
Recent Activity:
Search the official Complete Avid-L archives at:   http://archives.bengrosser.com/avid/
.

__,_._,___

No comments:

Post a Comment