I had the identical problem earlier today and it was solved by a really fine support rep: it's not a bug, it's a safety feature (somewhat misguided, I think, but done "for our own good"). Activating those shortcuts and saving the .kys file (custom keyboard layout) inside an empty project is the answer; it will then be useful in any project. Only problem: that shortcut doesn't show up on the visual keyboard. THAT is a bug, if anything is here. I'm not quite sure I buy the "feature" and "safety" aspect, but that's what I was told. ... View more

If anyone at Adobe wants to know what a captioning module should look like, I have found the best around. It's a free, collaborative environment known as Amara, or amara.org. I am building my subtitles in this program. It has a fully interactive timeline and even the ability to add unsynchronized text in the correct order to add as captions later. Error checking (yes, it tests for 32-character length too). Most importantly, one can run the timeline and press up-arrow/down-arrow keys to drop in and stop the next title. All-around marvelous experience. Adobe, here's the challenge: meet or beat this thing and I'll be back editing captions/subtitles in Premiere in a heartbeat. ... View more

I suspect Premiere enforces the 32-character limit because of required backward-compatibility with CEA-608 where that's a strict requirement. Other software does not have this limitation; after all, we have 16x9 screens which can accommodate more characters than that; the important limitation is what the reader can handle given the display time. An excellent resource for determining errors in line length etc. is Subtitle Edit, a free utility that checks each line for errors (too short or long duration, too long lines, etc.) and will attempt to fix the errors line-by-line. It allows for slightly longer than 32 characters, but checks and notifies on limits for subtitles rather than closed-captions. I think the answer for me is to work entirely outside of Premiere on the captions. Clearly, between Media Player Classic, VisualSubSync, Subtitle Edit and Handbrake I have a more robust caption solution than Premiere can now offer. I REALLY hope they clean up their act. I should not have to use free products that do better what I pay monthly rent to Adobe for Premiere to do...at least, after all of this, I know how to get my project done!!! ... View more

I just found another solution - try this file (just uploaded to Dropbox): this one will load into Premiere with all the characters intact! Dropbox - Act 1T-Ben ent.srt Here's the difference (talk about counter-intuitive...): I found an obscure checkbox in VisualSubSync that is above the name of the SRT file and says "Save as UTF-8". Checked the box, resaved the file and this is the result. Appears to work perfectly. This must be why the small file works too. So many undocumented issues. So little warning or error messages...now if I could figure how to get Premiere to burn the text in without looking like a spindly horror show I'd be there. ... View more

Remove the ellipsis that starts Caption 82 and replace with three periods. That should do it. Change the curly quotes in 84, 85 and 86 to inch marks ("). Note how indescribably UGLY this makes the subtitles. The change to ellipsis is fine. The quotes and apostrophes aren't. Do you ever sleep? 🙂 I hope monstremoi sees the work you and I put in on this and chimes in on this when he comes in to work. ... View more

Just to try and be helpful - those quotes are known as curly quotes, publisher's quotes or "sixes and nines" (the one on the left is shaped like tiny sixes, the one on the right like tiny nines). Members of the upper ASCII set and UTF-16, they are not in UTF-8 and obviously Premiere is forcing UTF-8 standards on the imported file...but NOT on the natively created one! ... View more

Apparently there's a way with some software to specify an SRT file with a higher level of Unicode than UTF-8 (i.e. UTF-16 which incorporates the problem characters). I have yet to get it to work in Handbrake, however. I believe it is that specification that allows the files to work in YouTube and VLC. ... View more

And there you go. The battle is between a nice, pretty display on screen and being able to actually load subtitles, say on a DVD. Those characters work fine in YouTube and if you load the sidecar file with VLC Media Player but the two apps I have that will burn nice captions into the MP4 either ignore the characters - making the captions unacceptable unless you want Caption 88 to read "And soI played for three long days!" (that's a capital I not a lower-case L) and Let's to read Lets  - or in the case of Wondershare throw an access violation on receiving the SRT file. It's not a lot of fun. By the way, the three closely spaced dots are a single character, …, reproducible by holding Alt and typing 0133 on the keypad (not the top row numbers). It's called "Ellipsis" and is in the upper-ASCII set as are the other problem characters here. ... View more

Now you're beginning to understand my conundrum. It's VERY frustrating. As I've discovered with the rest of Premiere's captioning approach, it is one of the worst parts of what is otherwise a marvelous editing program. You should see what it looks like when you use the export function to burn the titles in. Just as spindly and disgusting as they look in the program monitor as you write or edit them. That's totally unnecessary. This level of inconsistency is also a royal pain. Thanks, again, for looking at that; I'm glad I'm not the only one coming to the conclusion that the program is hopelessly inconsistent with regard to these captions. I hope they fix it. We deserve better. ... View more

OOPS sorry I wasn't referring to the display (which should go more than 35 characters on an HD picture; it does in Handbrake where I now am ultimately using it...) the main reason for putting that in is to show that the "illegal" characters (which I think are NOT illegal in CEA-708, by the way) WORK here. They won't display in my other (imported) SRT. My immediate action when I saw what you were talking about (in my 720p video track it actually displayed up to "col", dropping of the "d.") I put a line break before "damp" in the Caption Editor. Then it displays correctly. I just wish this was not so difficult. I can't charge my client what it's going to be worth to finish this. VERY annoying. I do very much appreciate everyone's attention to it. I hope Premiere cleans up its act with a more robust way of doing captions and subtitles (and a nice bonus would be to include an export to Encore for subtitles). Thanks... ... View more

Let's take this one as an example: 78 00:07:41,213 --> 00:07:43,463 - Be gone!  Let’s prepare the table. Premiere only imports the caption to the word "Let". That apostrophe after "Let" to make "Let's" appears to be illegal. The version in the sentence before this one wouldn't be. 82 00:07:52,054 --> 00:07:56,508 …"When do we start?" The ellipsis at the beginning of this line seems to make Premiere stop in its tracks. This caption: 84 00:08:02,072 --> 00:08:05,649 “When do we start the lesson?” won't read in Premiere at all, apparently because of the curly quotes. My understanding is that there is an "extended" SRT that would incorporate that character (in the upper ASCII chart but apparently NOT in UTF-8). If I download a professionally created SRT file it seems not to contain these characters. BUT if I create a CEA-708 file in Premiere and then EXPORT it as SRT those characters come in just fine. Look at my very small second example, (reproduced in its entirety below) with double-quotes around "Red Sea" and a single-character ellipsis in the second caption. From that file (actually the complete text of the file): 1 00:01:17,143 --> 00:01:20,647 This “Red Sea” makes me feel damp and cold. 2 00:01:20,680 --> 00:01:21,381 …idly sitting on its rear like royalty! THIS WORKS. It was written in Premiere's caption editor set to CEA-708, and exported as SRT. Note the same characters PPro rejects in an imported SRT from foreign source. It's a simple text file! No secret handshake here...what makes the difference!!!??? What's sad is that those characters look much better on screen (the curly quotes and apostrophe) than the alternative " and ' marks. As I've said, YouTube and VLC will display them fine. Handbrake will ignore them if I use it to burn them in (but makes lovely subtitles, white with a black drop shadow); Wondershare will declare an access violation if I try to load an SRT with those characters. I think I'm going to have to use Premiere to check the validity of the SRT, Handbrake to burn them in permanently on an MP4, then Premiere to export that MP4 (using MPEG2-DVD preset as my base format) to Encore to make the DVD the client (JUST THIS MORNING told me he) actually wants. Premiere does a TERRIBLE job of burning in the captions as subtitles. They are spindly and ugly, pretty close to what the Program Monitor shows, no apparent choices to get better appearance. Handbrake makes the best burn-in titles. Titles will be burned in, not to be turned on and off. There is no easy way I've found to get an SRT file to Encore to use for subtitles for DVD, the two formats apparently are completely inimical. What a pain. ... View more

You're right, for different reasons: there should not be three substantial lines in a subtitle! I split it differently across the line. It does work better; thanks. But that doesn't approach the issues of these "illegal" characters (none of which are in that selection!) -Jay ... View more

OK but check the text file and then see how much actually imported into Premiere, and see if there are captions missing text and whole lines missing from the end of the file. That's what I'm experiencing. And it has to do with apostrophes, quote marks and ellipses. ... View more

I've sent it to you privately and if you'll look at the message dated Feb 5, 2016 12:23 PM, it's right there in the public forum. What am I doing wrong not to get it to you? Thanks... Jay ... View more

I wonder if you're having the same issue I am. I believe that the inclusion of characters meant to enhance videos but in fact not in the UTF-8 character set might be causing your problems as well. As I indicated to monstremoi, players (YouTube in particular) will deal fine with these characters. It's really nice to see curly quotes and a curly apostrophe instead of inch and foot marks, respectively. But they apparently do not occur in the UTF-8 character set. I use a copy-and-paste model from a “transcript” of my video converted from PowerPoint to RTF. Even though I attempted to save it as UTF-8, the non UTF characters appear and do not get converted (another problematic one is the single-character ellipsis instead of three discrete periods: … instead of ... will give Premiere a problem. Note also that in the quoted word "transcript" this time I typed the " character but the first time I used it I copied/pasted curly quotes). Those are forbidden under UTF-8 rules, but appear in VLC and YouTube no problem. I did note that when I used Handbrake to burn the titles to the video, it worked fine BUT it ignored all those characters, leaving no space where the character occurred. At least that option gives me the ability to review the work and make the necessary changes! Premiere just stops in its tracks, inconsistently. Some characters will cause a caption to display incompletely (stops as soon as the offending character appears). Some will apparently cause the import to stop at the moment of the illegal character. It's very frustrating and unfriendly. If there's an error, there should be a trap for it and notice so it can be fixed, not sitting down in the middle of the road like a stubborn mule and refusing to go on. Here's another anomaly. If I use the Caption Editor in Premiere to create a CEA-708 file, and then export it as an SRT, it exports and imports with HTML-like tags. I tried it with two captions each of which had "illegal" characters, and each one read just fine from the imported SRT. I stripped the HTML tags and it still read fine! A sample is available here: This example is the 2 lines I tested with illegal characters (that works fine, writen in CEA-708 Caption Editor, exported to SRT and the HTML code stripped, contains curly quotes in the first text entry and a single-character ellipsis in the second, neither work in the second file, both do here): https://www.dropbox.com/s/ilowst448wjlrew/Act%201T_Sub_02.mp4.srt?dl=0 This one is up to where I am in the project, from VisualSubSync: https://www.dropbox.com/s/nqkdthqghc84shy/to%20Constitution2.srt?dl=0 Why does #1 work and #2 fail, and on the same controversial characters? If anyone is interested, the text is from Act 1 of the opera LA BOHEME of Puccini, in an English translation. ... View more

Hi, everyone. I'm adding to this thread because I have a .srt problem and it looks like the specialists are all here! I do opera videos. I have been requested to caption one of my videos, and was given a PowerPoint presentation of the "surtitles" for the show. In modern opera houses, the audience will often be given a translation of an opera done in original language. It appears on a screen above the stage (in some very rich houses like the Met Opera in New York City, the translation appears on the backs of the individual SEATS in multiple languages or not based on the wishes of the patron!) In any case, with the tremendous limitations of the PPro caption editor I am creating the .srt in a software called VisualSubSync, which will take a text file and marry it to a section of the soundtrack. The problem is that the original text from the PowerPoint (via RTF export), even converted to UTF-8, contains certain characters (think curly quotes, curly apostrophe, ellipsis in a single character rather than three periods) that other software (YouTube, VLC Media Player, Handbrake) pass on and use, stop the SRT import feature in PPro in its tracks. The track appears to import without error, but when placed on the timeline it stops before whatever the offending character is, leaving a tiny white mark in the upper right corner of the "clip". I've tried everything I can think of to remove all offending characters. Better would be if PPro would fix the importer to be more tolerant. If other software can display it, PPro should be able to work with it as well. Thoughts? ... View more

I have the same issue. I have NO plug-ins or add-ons. What I notice is that whatever loads the stuff under "Libraries" takes a while to happen, flashes white in that window to the left and bottom for a second and then loads in the thing that says "Your content. Anywhere" and "Learn How to Use Libraries". During that process, it is not possible to use the menus, etc. I suspect that the one has something to do with the other. Closing the Libraries window leaves it off permanently, I think...and seems to help. ... View more

Oh...unlike John (above) I use MPEG2 - DVD as my export, and the file does NOT have to re-transcode in Encore. You just have to make sure to set the size right. I use H264 - Blu-Ray for Blu-Rays since the underlying file structure of the Blu-Ray that results is a huge .M2TS file (i.e. AVCHD). I love working in the new XAVC-S format that the FDR-AX100 uses. Just makes one great big MP4 file that loads easy as anything, no stitching together multiple MTS files anymore. ... View more

I just went here: https://creative.adobe.com/products/premiere and note that there's a drop-down menu - located under the text " "In this version" - where you can choose to download CS6. You download the entire suite, then discard (uninstall) everything except Encore. It should work. I agree that it's annoying. Let's say there becomes a 4K version of Blu-Ray...how are we going to write them? Adobe owes us to acquire a new source of this capability. I know the problem is a licensing one with Encore - the company that developed Scenarist (on which Encore is based) sold it to a company called Rovi that has no intention of further developing it or licensing it to Adobe. That's not Adobe's fault. However, I understand Sony has a product that continues support; perhaps Adobe needs a new partner in this? For the moment, I believe you'll get Encore downloaded and working. I've found that the lack of dynamic link works in my favor. Encore used to make its own choices regarding transcoding and they didn't always look good. I use the export settings in PPro and fine-tune the results so that they just fit the disc. Right now I'm editing and transcoding performances of MIKADO and MADAMA BUTTERFLY for Amore Opera here in New York City (took the videos in 4K with my new FDR-AX100 camcorder and edited in pans, zooms, cuts and dissolves...from the ONE camera, to output in HD!)...BUTTERFLY is 2 hours 15 minutes and it's a challenge but I found settings that work very well indeed. Switching audio from PCM to AC3, then adjusting the target bitrate until the file size is JUST under the max (the offered file size estimate is just that, an estimate, often on the small side so I sometimes have to transcode more than once. I also use "Wide Progressive" exclusively, and Encore with the Dynamic Link wouldn't make a file that way that I could use. The look is FAR superior to the interlaced DVDs of yore). The singers and orchestra not being automatons, the show is slightly different lengths on different nights. A full transcode on my system takes about an hour. Making the actual disc takes about 3 minutes. Amazing to watch. You are DEFINITELY entitled to a copy of Encore CS6; you just have to fight for it. Let me know how you make out! Hint: Call corporate if the folks from India can't help you get it. They REALLY don't want to hear from us but they WILL help, in a pinch. ... View more

Unhappy: Not sure what just happened! Did Adobe remove access to CS6? I thought the deal was they'd leave it up indefinitely for just this reason. Have you contacted Tech Support? Hopefully someone from Adobe will see this...but I suggest not using so much ersatz profanity. I can't imagine they won't find a way to provide support for this. ... View more

Jeff, I in fact did ultimately go to Customer Support. It took a long time with a tech in my machine and several reboots (with the use of software called Unlocker, which itself didn't see the lock but offered to open the file for use after reboot). It seems to be limited to that one directory. Somehow, no matter what we did the files and the directory were impervious to renaming or modifying. However, I didn't create that directory, Adobe did. I never touched it, but Adobe did (after being given elevated permission to do so, I believe, back when the CC was installed). So how does that ONE directory suddenly have such high security that an explicitly entered Administrator command prompt can't modify it (access denied)? From my reading around in the forums and other sources, I don't think I'm alone in that. The ultimate solution was that the tech found and uploaded to my machine a fully updated folder. After renaming the original folder (and a reboot because the folder itself was locked at a level higher than Administrator) I replaced it with his and the programs no longer required an update. Any light that can be shed on how such a thing can happen would be useful. A virus or some kind of intrusion? Hardly likely that your average hacker would find that one little obscure directory (C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4). Rather, there must have been some issue in the install process (completely controlled, of course, by Adobe's software) that led to this problem. Eager for thoughts (and don't ever need to have an afternoon like I did). Thanks for listening and hopefully understanding...and possibly positing a cause for this. HOW do files and folders permissions become "compromised"? ... View more

This might (or might NOT) be fun. Opened log, converted to .csv, filtered errors using Excel. Went into WordPad to correct errors in the errors. Here's the result: 01/03/14 02:51:14:039 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\IMSLib.dll""" |  Patcher tool returned error: 32769(Seq 3) | 01/03/14 02:51:14:176 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\libcurl.dll""" |  Patcher tool returned error: 32769(Seq 7) | 01/03/14 02:51:14:325 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\libeay32.dll""" |  Patcher tool returned error: 32769(Seq 9) | 01/03/14 02:51:14:471 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\CEPServiceManager.exe""" |  Patcher tool returned error: 32769(Seq 11) | 01/03/14 02:51:14:554 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\VulcanControl.dll""" |  Patcher tool returned error: 32769(Seq 13) | 01/03/14 02:51:14:691 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\ssleay32.dll""" |  Patcher tool returned error: 32769(Seq 17) | 01/03/14 02:51:14:851 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\zlib1.dll""" |  Patcher tool returned error: 32769(Seq 21) | 01/03/14 02:51:14:868 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " DF037: Unable to delete directory ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\Adobe\AdobePatchFiles"". Error 145 The directory is not empty.. Check and correct folder & parent directory permissions and then try again.(Seq 25)" | 01/03/14 02:51:14:869 |  [ERROR] |   |  OOBE |  DE |  | 13028 | " DF037: Unable to delete directory ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\Adobe"". Error 145 The directory is not empty.. Check and correct folder & parent directory permissions and then try again.(Seq 26)" | 01/03/14 02:51:20:298 |  [ERROR] |   |  OOBE |  DE |  | 12960 | " DF045: File corruption detected. Re-install the product & then apply the patch again. (Can not repair file ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\zlib1.dll"")(Seq 4)" | 01/03/14 02:51:43:747 |  [ERROR] |   |  OOBE |  DE |  | 7416 |  01/03/14 02:51:43:747 |  [ERROR] |   |  OOBE |  DE |  | 7416 |  01/03/14 02:51:43:744 |  [ERROR] |   |  OOBE |  DE |  | 7140 |  Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{45C5DE59-4DB4-4A96-84E1-93C59BD5C4AE}.data. Error 0 01/03/14 02:51:43:748 |  [ERROR] |   |  OOBE |  DE |  | 7416 |   | 01/03/14 02:51:43:748 |  [ERROR] |   |  OOBE |  DE |  | 7416 |  System check returned with error : -4 | 01/03/14 02:51:59:355 |  [ERROR] |   |  OOBE |  DE |  | 8444 |  01/03/14 02:51:59:355 |  [ERROR] |   |  OOBE |  DE |  | 8444 |  01/03/14 02:51:59:352 |  [ERROR] |   |  OOBE |  DE |  | 8268 |  Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{45C5DE59-4DB4-4A96-84E1-93C59BD5C4AE}.data. Error 0 01/03/14 02:51:59:355 |  [ERROR] |   |  OOBE |  DE |  | 8444 |   | 01/03/14 02:51:59:355 |  [ERROR] |   |  OOBE |  DE |  | 8444 |  System check returned with error : -4 | 01/03/14 02:52:15:220 |  [ERROR] |   |  OOBE |  DE |  | 8508 |  01/03/14 02:52:15:220 |  [ERROR] |   |  OOBE |  DE |  | 8508 |  01/03/14 02:52:15:216 |  [ERROR] |   |  OOBE |  DE |  | 12312|  Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{45C5DE59-4DB4-4A96-84E1-93C59BD5C4AE}.data. Error 0 01/03/14 02:52:15:220 |  [ERROR] |   |  OOBE |  DE |  | 8508 |   | 01/03/14 02:52:15:220 |  [ERROR] |   |  OOBE |  DE |  | 8508 |  System check returned with error : -4 | 01/03/14 02:52:30:879 |  [ERROR] |   |  OOBE |  DE |  | 12784|  01/03/14 02:52:30:879 |  [ERROR] |   |  OOBE |  DE |  | 12784|  01/03/14 02:52:30:875 |  [ERROR] |   |  OOBE |  DE |  | 9980 |  Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{45C5DE59-4DB4-4A96-84E1-93C59BD5C4AE}.data. Error 0 01/03/14 02:52:30:879 |  [ERROR] |   |  OOBE |  DE |  | 12784|   | 01/03/14 02:52:30:879 |  [ERROR] |   |  OOBE |  DE |  | 12784|  System check returned with error : -4 | 01/03/14 03:25:06:243 |  [ERROR] |   |  OOBE |  DE |  | 6252 |  DF044: Check and correct file/folder & parent directory permissions of C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\zlib1.dll and then try again. (Failed to restore ACL of file |  Error : 5)(Seq 4) | 01/03/14 03:25:06:243 |  [ERROR] |   |  OOBE |  DE |  | 6252 | " Failed to apply patch to file at ""C:\Program Files (x86)\Common Files\Adobe\CEPServiceManager4\zlib1.dll""" |  Patcher tool returned error: 32769(Seq 4) | 01/03/14 11:38:15:839 |  [ERROR] |   |  OOBE |  DE |  | 7772 |  01/03/14 11:38:15:839 |  [ERROR] |   |  OOBE |  DE |  | 7772 |  01/03/14 11:38:15:836 |  [ERROR] |   |  OOBE |  DE |  | 1484 |  Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{45C5DE59-4DB4-4A96-84E1-93C59BD5C4AE}.data. Error 0 01/03/14 11:38:15:839 |  [ERROR] |   |  OOBE |  DE |  | 7772 |   | 01/03/14 11:38:15:839 |  [ERROR] |   |  OOBE |  DE |  | 7772 |  System check returned with error : -4 | Jeff, I understand you're just trying to help and please understand that my POISONOUS ANGER is in no way directed at you but at someone in the company you work for who caused this problem for me. Thus, from here on out the pronoun "you" refers interchangeably to "Adobe" or "The incompetent engineer (and I use the term loosely) that allowed this dog dirt to be released into my computer"  The problem is clearly NOT with any of my apps but with the infrastructure that you place on my computer to have it all run (thus "common files"). So the advice to uninstall and reinstall is despicable. Rather, YOU fix the garbage in these programs that clearly don't benefit US the users but YOU the company, probably in keeping tabs on my license and right to use CC, which I pay for. I do NOT pay to have that underlying software break and then have to do YOUR work to fix it. Thanks for your ear. ... View more

There's actually only ONE update. It's to CSXS infrastructure, and the attempt to update has destroyed my ability to work in my Premiere project in which I have a deadline. Thanks for nothing to the incompetent engineers who allowed this update past QC. So the link you sent gave a lovely solution: JUST UNINSTALL YOUR APPS. THEN REINSTALL. THEN MAYBE IT WILL WORK. This stinks. HOW DARE Adobe break my PERFECTLY RUNNING apps because of a "bug fix" to an unrelated component that then BREAKS my apps and then wants to force me to un/reinstall my suite? This is misrepresented as a "bug fix" to Illustrator, Prelude, Premiere and Photoshop. In fact it's to some internal component, CEP Service Manager, that now interrupts me every 10 seconds telling me that my application was "unable to start correctly". FYI the app is running just fine except for the disgusting box that interrupts my efforts to edit, every 10 seconds. How would Adobe like to pay my $75 per hour edit rate for the time to uninstall, reinstall and HOPE that it works next time around? I'm furious. HOW DARE THEY DO THIS!!!!????? ... View more

Allynn Wilkinson wrote: Or wait until June 17th.  Real subtitling is a new part of Premiere CC Allynn: Is this something I am missing, or was it wishful thinking? I searched the PPro documentation and found ONE mention of subtitles, nothing about how to do them. It'd be nice if you were right, now that Encore is no longer part of updates to PPro, and that was the way to do subtitles. Jay ... View more