There are shocking problems with the new Titles & Text plug-in. Whoever wrote the spec for this thing has some explaining to do.
1. There's no proper Unicode compliance. Need Greek or Cyrillic characters? Need anything not in the ANSI character set? Forget it. To put this into context, there's no problem using such characters in the ancient (Legacy) Text generator.
2. CFF OpenType fonts don't appear in the Font Family list. The vast majority of commercially available fonts cannot be used. There used to be an arbitrary restriction in the (Legacy) Text generator but this was removed in Vegas 4.0b.
3. There are problems with the following characters (they're not rendered in the Video Preview):
• – —
149 150 151
Bullet, En Dash, Em Dash
[No-Break Space]
160
173
Soft Hyphen
The first three are needed all the time and this needs to be put right straightaway. It's a moot point whether or not the last should be visible or not (see http://www.cs.tut.fi/~jkorpela/shy.html) but I thought I'd mention it anyway.
Incidentally, ANSI characters 145 to 151 are still not rendered in the Video Preview when using the (Legacy) Text generator so using that instead is not an option. Perhaps they could both be fixed at the same time.
4. There are no OpenType glyph substitution capabilities. Since these are available in the ProType Titler (and are made straightforward by Windows Presentation Foundation), why could they not be in Titles & Text? Why was ProType Titler not developed or adapted? Anyone who knows anything about typography and design is going to want these nowadays (the technology's even in Microsoft Word 2010).
First impressions of NewBlue Title Pro aren't good (first impressions are all I can get so far since it crashes Vegas all the time – bundling this with Vegas Pro 11 might not have been a very good marketing move in the medium term). Anybody who doesn't know the difference between kerning and tracking has no business writing a typographic plug-in. Not supporting kerning is about as amateur as you can get.
1. There's no proper Unicode compliance. Need Greek or Cyrillic characters? Need anything not in the ANSI character set? Forget it. To put this into context, there's no problem using such characters in the ancient (Legacy) Text generator.
2. CFF OpenType fonts don't appear in the Font Family list. The vast majority of commercially available fonts cannot be used. There used to be an arbitrary restriction in the (Legacy) Text generator but this was removed in Vegas 4.0b.
3. There are problems with the following characters (they're not rendered in the Video Preview):
• – —
149 150 151
Bullet, En Dash, Em Dash
[No-Break Space]
160
173
Soft Hyphen
The first three are needed all the time and this needs to be put right straightaway. It's a moot point whether or not the last should be visible or not (see http://www.cs.tut.fi/~jkorpela/shy.html) but I thought I'd mention it anyway.
Incidentally, ANSI characters 145 to 151 are still not rendered in the Video Preview when using the (Legacy) Text generator so using that instead is not an option. Perhaps they could both be fixed at the same time.
4. There are no OpenType glyph substitution capabilities. Since these are available in the ProType Titler (and are made straightforward by Windows Presentation Foundation), why could they not be in Titles & Text? Why was ProType Titler not developed or adapted? Anyone who knows anything about typography and design is going to want these nowadays (the technology's even in Microsoft Word 2010).
First impressions of NewBlue Title Pro aren't good (first impressions are all I can get so far since it crashes Vegas all the time – bundling this with Vegas Pro 11 might not have been a very good marketing move in the medium term). Anybody who doesn't know the difference between kerning and tracking has no business writing a typographic plug-in. Not supporting kerning is about as amateur as you can get.