Premiere Pro CC no longer reading embedded captions

Premiere Pro CC no longer recognizes captions embedded into a Quicktime file using the XDCAM HD 422 50Mbit codec.
We created several hundred files using the new Premiere CC - all by attaching .scc data to a Quicktime file using the XDCAM HD 422 50Mbit format.  We had another department that would then open those files, trim as needed for different deliveries, and then re-export - maintaining the captions throughout the process.
However, as of yesterday - Premiere CC is no longer reading the embedded caption information when we re-open the file in CC.  If I open the file in Quicktime, I can display the captions.  Also, our Vantage system and Baton file analyzer BOTH see the captions - so they are still there.  However, Premiere CC no longer recognizes them.  This appears to only be a problem with the XDCAM codec as I found a file encoded to ProRes 422 with embedded captions and it opens up into Premiere CC and properly locates and separates out the captions onto V2 as expected.
I'm really stumped on this one.  I've tested 5 different Premiere systems here (all Mac based) and it's happening across all of them.  It was working fine previously.  To my knowledge - we didn't do any updates to these Premiere system since this started happening. 
I tried some of the usual stuff - restart, trash preferences, update (it did download and install the most recent Dynamic Link update but didn't find anything else).  Still stuck.
Any suggestions would be REALLY appreciated.
Sincerely,
Don Hertz
System specs:
Mac OS 10.8.3
Premiere CC 7.0.1 (501)
16-32Gb of RAM (depending on system)
iMac 27" Workstations with 2Gb Video Card (Dec 2012 release)

Well - that's consistent with the additional testing I've done.  Any MPEG based codecs do not work - while ProRes, DVCPro and others work fine upon re-import.  I could have sworn we had it working previously as we've been doing the export - reimport workflow since CCs release but I'll have to go back and look at the exact file formats they were using for the last few weeks.  Perhaps someone goofed on our encoder settings and they were somehow going out to some non-MPEG format for a few weeks.
Hopefully getting the importMPEG function to work in a future update is high on the priority list.
Thank you for the response.
Sincerely,
Don Hertz

Similar Messages

  • Premiere Pro CC won't read media source timecode?

    We recently switched over some of our editing systems to Premiere Pro CC, but for some reason Premiere Pro CC isn't reading the timecode from our source footage.  It works fine in CS6 and CS5, but on each of the CC systems, even though the timecode preference is set to "Use Media Source" the timecode that is displayed in the project window, the source window and even in the timeline with a timecode window effect added and set to media, the time code that is displayed starts from 0 as though it's set for "generate" or in preferences, "Start From 00:00:00:00." 
    All of our source footage is recorded on XDCam or DVCPro 100 and we've been using Premiere since CS5 without issue.  Any help or suggestions would be greatly appreciated.
    Thanks

    Can you upload a short clip somewhere for us to take a look at?
    BTW, exactly which version of CC are you on?

  • Adobe Premiere Pro CC no longer works

    In (the) student (version) of Premiere Pro CC via the (Creative Cloud) app. on (It) installed, but every time (I try to launch) the program, to Adobe Premiere Pro CC no longer works. Other apps do work.
    Message was edited by: Kevin Monahan Reason: translation to English

    thanks the problem is solved,
    greetings wolfturtle
    2014-01-21 Kevin Monahan <[email protected]>
        Re: Adobe Premiere Pro CC no longer works  created by Kevin Monahan<http://forums.adobe.com/people/Kevin-Monahan>in *Premiere
    Pro* - View the full discussion<http://forums.adobe.com/message/6034160#6034160

  • Premiere Pro CC does not embed 708 captions in QT

    Despite the fact that all of the online videos make it seem like exporting embedded closed captions is a breeze, it is not. After much experimentation I have found out there is no way to export 708 captions embedded into a QT file. I have been working with closed captions for a long time, and I am very familiar with the different pitfalls of closed captions. Why Adobe would chose to embed 608 captions only in an HD file is beyond me. To be excepted by broadcasters the captions must be 708 VANC Captions with the 608 alternative. Every time I get a file out of MACCaption this is what is included. I have tried to import those files into premiere pro CC and it does not see the captions.
    I have tried creating the Sidecar file as a .mcc file, and it seems to be correct. Unfortunately there is no way to embed this into a QT file.
    Kevin

    You are correct that 708 captions cannot be embedded in QuickTime files; they can be embedded in MXF OP1a outputs or written to sidecars. This is covered, albeit indirectly, at the bottom of this help page.
    Support for closed captions is a work-in-progress. CC7.0 provided support for CEA-608 and Teletext; support for CEA-708 was added in either 7.0.1 or 7.1. Of course, "support" is a loose concept, and work remains to be done on particular aspects of what exactly can be imported, how captions can be exported, and workflows for editing captions in a project. You can help us set priorities by submitting feature requests on what you think are the greatest needs.

  • Premiere Pro CS5 No Longer Saves Project

    I am working on a Mac OS X Version 10.6.8 with 2 x 2.8 GHz Quad-Core Intel Xeon Processors and 12 GB 800 MHz DDR2 FB-DIMM Memory. I am running Premiere Pro CS5 on this machine.
    I work for a company who produces 50-100 short, education-based videos for clients across the country to post on YouTube. The model we use is not complicated, but geared toward getting these videos edited with graphics and music quickly so they can be released slowly over time. So, needless to say, I'm accessing their project files quite often, until all of their videos are edited. For some reason, however, after a certain amount of times opening & quitting the program, the project no longer saves. This has happened to TWO projects so far (one using AVCHD footage, and the other Canon MXF files).
    Here's what happens:
    The project starts to take longer to save, then, one day I go to save or Auto-Save kicks in and the dialog box comes up but the progress bar never changes.
    It will stay this way as long as I let it, but as soon as I click "Cancel" Premiere freezes up and I have to resort to "Force Quit".
    It is at this point that I become aware of the insanely large file size of the project....in this particular case, 380.2MB.
    I have tried:
    - "Save As"
    - Duplicating the project in Finder and opening the copy
    - Opening Auto-Save Files
    - Creating a new project completely and importing the old project
    - Trashing Preferences
    - And even resetting the workspace to the default "Editing" workspace (a suggestion when Googling the problem).
    None of the above has helped.
    Luckily, at my company, we have another machine (Mac OS X ver. 10.6.8, 2 x 2.4 GHz Quad-Core Intel Xeon Processors, 12 GB 1066 MHz DDR3 Memory) which runs CS5.5. As a workaround, I've been able to take these projects over there and just continue to work on them in CS5.5. But, obviously this is not a solution. I'd like to know what the problem may be behind all this, especially since this is a problem that could theoretically happen in CS5.5 down the line.
    Any insight is appreciated, and please let me know if you need more info on my part!!

    Maybe it was a 32 bit plug-in?

  • Latest Update of Premiere Pro CC no longer supports FLV

    Why? Where's the wisdom in having an editing program that no longer supports FLV and SWF? I was editing on a project for a client using a FLV video file and had invested over 20 hours. I did an update and when I returned to the timeline I was unable to use my video file. It was no longer supported. Now, I was on a very tight deadline and was only half way through the job, and to find out I could not continue the job was very very frustrating. It took me over 3 hours, of valuable time I could have been editing, to deal with Adobe Tech to resolve this. It was very stressful. The only solution was that my FLV file needed to be put through After Effects, which would have rendered the work I had done, over 20 hours, useless, then would have added more time to my job to re-re-render and re-edit. With only a limited time remaining before I needed to submit the completed edit to my client, this was not a solution. So, my question is, why? Perhaps it is time to jump ship and move over to Final Cut. I can not trust Adobe. This is my job, I rely on my camera and my computer/editing platform in order to perform my job and if I can not count on either of these, then I need to find something more reliable. How was this resolved? I had to allow an Adobe Tech remote access to my computer, where they un-installed Premiere and went back to the Adobe site and re-loaded my previous version of Premiere Pro. I am thankful it was resolved, but concerned about the future reliability of Adobe.

    Adobe - in their infinite wisdom - decided earlier that DVD and Blu-Ray are dead. There are no clients asking for DVD or BRD anymore, at least as far as Adobe can discern. Maybe they also decided FLV is dead, but forgot to send out an obituary.
    The only solution is to go back to a previous version where it is still supported, like CS6, where you also have Encore.

  • Why are the latest updates of AME and Premiere Pro CC 2014 only reading 4gb of ram?

    I am running Windows 7 64 bit ultimate with 8gb of ram. The previous versions ripped through rendering, but I don't want to go back to revert back as i have been working with the new version now and the old one won't open the projects made by the new one. I also really like the new interface.
    In task manager all adobe processes come up with *32.
    How do I install the new versions as 64 bit?

    Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration.  Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
    You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions.  The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline.

  • Trying to export into MP4 but premiere pro takes to long.

    I am trying out premiere pro for the first time. I need to be able to export video into MP4. the video does eventually export but takes way too long. almost 15 minutes to export a 13 minute video. every export starts out fine until the file gets to 100% then it just sits there for a long time before finally finishing the export. is this because of my computer? In using a windows 7 with a intel core i5-3350 cpu @ 3.10ghz, 8.g ram 64 bit operating system. and a nividia graphics card

    How many and what size/speed are your hard drives?
    What effects have you applied to your edit, and what are you editing?
    More information needed for someone to help... please click below and provide the requested information
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    CS5-thru-CC PPro/Encore tutorial list http://forums.adobe.com/thread/1448923 may help

  • If Premiere Pro CS5 No Longer Starts ........

    Just about everything has been running great with CS5 on my Mac system until this afternoon. When I started the application, it would begin loading all of its resources and then just quit and give up. I had just installed a plug-in before the flakiness, so by simply removing the plug-in, everything went back to normal. Here is what happened in case you encounter the same problem:
    AE CS5 comes with a new plug-in, Digital Effects Free Form. If you register with Digital Effects, you get a free plug-in, Falloff Lighting. I installed the plug-in in the Adobe/Common/Mediacore folder. It seems Premiere Pro tried to load it, was not at all happy about it, and called it a day.

    Maybe it was a 32 bit plug-in?

  • My MacBook Pro can no longer read/play/do anything with DVDs. I tried re-installing OS and Leopard but discs are rejected almost as soon as I put them in. For some reason my computer is rejecting any and all DVDs.

    A few weeks ago I noticed my MacBook Pro was unable to open or read, etc... DVDs. This included DVDs with jpeg photos on them and DVD videos. I thought I might have deleted something necessary to DVD use. So I tried to re-install OS software. This included Snow Leopard and the original two Mac OS X discs. None would open or play or install. All were spit out of computer soon after I stuck them in.
    So now what can I do? Thank you.

    Do you recommend the canned air
    It works just as well as the regular cleaning discs works.  The only disadvantage is that you will need to keep purchasing canned air once it runs out.  Cleaning discs last forever or until the tiny bristles on the disc wears out.  Whichever comes first.
    Any store that sells cds & dvds will also sell disc cleaners.  Prices vary but they all do the same thing - clean your slot drive.

  • Premiere Pro CC 2014.1 - Enable Closed Captioning

    I would like to enable closed captioning in my video, but the top right menu button that every forum points to isn't there.  Any help?

    Ah!  I found it!  In the video panel at the top right, click on the wrench icon. (highlighted in yellow)
    This brings up the menu for closed captioning:

  • Premiere Pro CS6, Extremely Long Export Times - ProRes

    All,
    Trying to figureout what I'm doing wrong. My sequence is 1920x1080, 29.97 and ProRes 422. The entire thing has already been rendered. I've checked "Use Previews"
    See below:
    Any suggestions? It's a 5:30 sequence.
    Thanks!

    All video movies on Mac are Quicktime, even uncompressed, which can be achieved with Quicktime None or Animation 100%.  Both of those are 8-bit, though, which would defeat "Use Maximum Render Quality," if so desired.
    IINM, image sequences may not require QT.  But, then you migh have issues if the next app in the transcode process don't accept image sequences.  And they're not available as a Preview File Format on Mac.
    However, ProRes is a perfectly fine preview file format.  It's just that Pr doesn't always use the Previews on export, the way it should.
    I usually master to ProRes, and when doing so, Pr usually will use the Previews, and they are fast.
    In any event, I don't normally experience the overly long exports from Pr.  Looking back at the OP, a 2 hour export for a 5:30 sequence is outragous, and I believe is a sign of something else amiss, other than typical Pr behavior.

  • Why does Premiere Pro CS3 no longer import .psd files?

    Over in the German forum, BjoernG has already asked this question as of this past June.  He's gotten no answer, so let's try it here.  Like Bjoern I use PPro CS3.  Mine is on WinXP with all updates.  I import PSD files as keying masks.  I've never had a problem until this evening (27 Aug 2014).  I tried to import a mask I've used many times before.  And it has always worked before.  Tonight PPro refused to recognize .psd as a supported file type, so it didn't show in the import folder file list.  When I told PPro to show "all files *.*", it showed the file.  When I selected it, PPro even showed the "import file" window, then displayed the "File Import Failure" window with Error Message:  File format not supported.  See the picture.
    This is a file I've imported into many previous projects with no problem whatever.  In fact, I started with a project file from last year which showed the mask file in the project assets but offline!  Even though the file had not been moved.
    If PPro CS3 is as obsolete as Adobe claims it is, then who's been messing with it?  And how can we get it "unmessed"?

    I couldn't imagine what any of those steps would do for my problem – but I didn't have a better idea so I tried them:
    > If Premiere is acting weird, restart computer.
    It's a laptop, so it was off all night.  I turned it on this morning.
    > Hold down shift+alt while opening Premiere.
    If I hold down shift-alt before clicking the desktop icon, all it does is select all icons from top left to the Premiere icon.  It does not start Premiere.
    If I press and hold shift-alt immediately after clicking the icon, Premiere displays every tiny module it loads rather than summarizing.  I held shift-alt until Premiere was fully up and idle.
    > Then empty all media cache.
    I did that.  As I write, Premiere is busy reconstituting all of that.
    Then finally, the acid test:  Try to import a .psd file.  Bzz-z-zt!  Still claims it's an unknown file type.
    > jpegs do not have transparency. You can save as png instead.
    I'm using it as a track matte key, so white is equivalent to transparent.  I do have to select "matte luma" instead of "matte alpha" in the effect.  I'll save your advice in case I ever do need transparency.
    Follow-up:  I checked my other licensed copy.  It accepts .psds just fine.  I checked Help About for both; they're identical:  3.2.0 (374).  So the problem must be in an internal setting, an external influence, or a defective module.  And remember, it's not just me, Björn in Germany reported the identical problem in June.

  • AVCHD? Can Premiere Pro handle the longer clips?

    I'm thinking of purchasing the Sony NX5E but have been hearing terrible things about NLE system not being able to handle the AVCHD codec, thus playback being really choppy.
    Is this still the case or have adobe addressed the issue.
    Think im gonnna put the order for the NX5 on hold for a bit!!
    Thanks in advance!
    H

    Hey Harm,
    It was this forum that brought this to my attention. Some of the MVP's and staff have commetted by saying adobe premiere does have known issues with 'Spanned' clips.
    I do have a Mac Pro, Quad 2.6 with 16gig RAM, so would I be ok?
    Greg Baber,Nov 11, 2012 5:24 PM   in reply to MickeyfilmReport
    The known issue with AVCHD is playing back spanned clips - those that are over a certain length so the camera splits them into separate files.  This is not the same thing as saying that Premiere just plays back slow.  For a performance issue, don't assume that it is the bug - look into other possibilities. Also, if you are having a hard time working in AVCHD footage, for whatever reason, a step that can help is to transcode your footage.  Prelude does a good job, and the problem footage that I've worked with was transcoded without issue.  Go into a good intermediary codec, like DNxHD for Mac, and it that could resolve your issue.
    Just sounds like quite an issue?
    Thanks,
    H

  • Premiere Pro is no longer reconnecting certain FLV files

    I have a clip that premiere is reporting as "disconnected media".  It is right where it started, and the directory has not changed.
    When I try to reconnect the media (which is the exact same file name still), the file is greyed out in finder, so I am unable to reconnect it.  I'm also unable to import the clip new.
    Why is premiere preventing me from dealing with this FLV file?  It plays perfectly find on VLC, and it is not a corrupt file. 

    Internal or external drive, and if so, what connection?
    Neil

Maybe you are looking for

  • Distortion in Save For Web interface

    I am still having problems with my Save For Web interface. Attached is a screen where you can see that with just the Optimized view showing (in this case 72%), the picture looks as expected. But if I go to 2-up or 4-up views, the 2nd image (which was

  • Photoshop CS5 doesn't launch - CoolType error msg

    Know this has been an issue others have experienced in some way.  We have brand new iMacs running 10.6.8.  All machines created using same image.  Some of them can't run Photoshop CS 5 (or Flash) even as local admin account, yet others work just fine

  • Use of truncating table

    Hi, I'm using some temporary load tables which are populated with bulk data daily & data is deleted after processing. During processing, I found that suddenly select statements became very slow inspite of very small data. Then I ran truncate command

  • Database Access via WLS Datasource

    I need to access a database resource by JNDI Datasource lookup and not by JDBC Direct Connection. This is needed because the underlying database is an Oracle RAC with several machines and my intention is to use WLS MultiDatasource Feature to round-ro

  • IWDConfiguration service in Web Dynpros

    Hi, I created a .properties file in my web dynpro application, then I am trying to read this .properties file using IWDConfiguration service. Following is my piece of code which I am using, but I am getting error while running the application. IWDDep