Premiere Pro CC 7.1 Update Kills Bluray (H264) Exports...help!

Yes, there's another thread in the Encore forum about this but since it hit a dead end, maybe someone here in this forum can help since it's actually Premiere/AME causing the issue...
The problem is simple and it's cross-platform:
When you export a H264 Bluray file using the new Premiere 7.1 update (using AME Queue or Direct Export from Premiere) and drop that file into Encore CS6, it shows up as "Untranscoded" and Encore forces you to re-transcode it all over again a second time in order to burn it (you cannot manually switch it to "Don't Transcode"). Export the same exact project using the same exact settings through Premiere 7.0.1 and the resulting files show up in Encore as "Don't Transcode" so they don't get re-transcoded a second time.
Try it. It sucks. Any ideas?

For those interested, the Encore thread is here:
http://forums.adobe.com/message/5821842#5821842
Please file bug reports so Adobe can officially sort this out:
Anyone demonstrating this for themselves should file bug reports: Bug report form.

Similar Messages

  • Premiere Pro random crashing since update to 2014.2

    Been working on the SAME big project over 18 months, in Pr Pro CC, 2014, working on the SAME PC:
    Win 7 SP1 pro 64bit, i7-3770K, 32GB fast memory (25.7 available for Pr), Intel HD 4000 graphics on Asus motherboard with 30" NEC Multisync screen at 2560 x 1600 (same as for years)
    42GB free on my SSD drive C: and 54GB free on my SSD drive S: for preview files, 24GB free on my SSD drive T: for caching files.  Project files etc stored on a normal hard drive F: (for Files!) 1.25TB free.
    NOW last update to 2014.2 and I get constant RANDOM crashes (Windows encountered a fault and had to close this program) despite updating graphics driver and trying different settings in preferences, use mercury etc.  No particular action causes it  - sometimes I am just watching it play a sequence and it just stops. Though of course it may be rendering the last edit at the time.
    Sometimes it runs for all of 15 mins and I think the problem has sorted then it goes again and I have to restart the project, find where I was and re-do my last edits.  If I remember to press Ctrl-S very frequently (every few seconds) it seems to run for a while then I forget for 5 mins and it crashes.
    Grrrr what did you do to the latest version, Adobe??  I need to get this project finally finished in a hurry.... I wish I had not updated the program!  Of course I cannot go back as it says the saved copy is now incompatible with earlier Pr Pro versions.
    I then tried running a previous version at the same time, as simonray suggested in his post - it worked!  So I am able to continue as normal provided I do this stupid bodge fix.
    So it really is down to Adobe as it is the same project, same PC, just different version update.  You did something to a great, stable, program that made it unstable, Adobe...
    To ANSWER RAMEEZ from previous thread:
    A variety of issues can cause PPRO to crash:
    a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin. >>  DIDN'T CHANGE ANYTHING since 1½ years running previous PrPro versions on SAME PROJECT on SAME PC
    the graphics driver  Checked for latest version - didn't stop the crashing
    third-party plug-ins - don't have any
    a problem with the cache files. I am using the same 2 x SSD I have been using for years for autosave and caching. 54GB free space / 24GB free space (current cache in place)
    a problem with the project file (if you're loading a project...)  Doesn't apply
    the Preferences files be set to read-only  How would that happen? Never happened before on any other update and I can change it.
    the user not having administrator rights  Only one user on PC since installation, full rights
    a conflict/incompatibility with some OS setting  Haven't changed anything
    a problem on the licensing/authentication side.  I'm signed up to full Adobe CC. Everything else works, Ps, Lr, Id ...
    A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.
    >>>>>>>>>>>>>>
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: VideoFilterHost.dll, version: 8.2.0.65, time stamp: 0x5486bf85
    Exception code: 0xc0000005
    Fault offset: 0x000000000006d692
    Faulting process id: 0x19d0
    Faulting application start time: 0x01d022d29c3e2d43
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\VideoFilterHost.dll
    Report Id: 1097ced4-8ec8-11e4-aaaf-08606e6e6383
    <<<<<<<<<<<<<<<
    Thanks,
    Rameez

    Problem Solved! (with a small catch)
    While searching crashing issues I came across this thread,"Premiere Pro random crashing since update to 2014.2"
    Marc_Lec  Answered (and I paraphrase here)"...I had the same problem and this is what I did. In 'Preferences Memory'  I increased the memory reserved for other application to at least half the installed and changed the optimize render from 'performance' to 'memory."
    Thank You Marc_Lec for what has been a game changer for me since my last computer and the beginning of PremiereCC problems.
    I changed my Memory reserved for Other Applications from the default 7gigs to 1/2 of my approx.31 available Gigs = 16Gigs. Viola!
    No more crashing what-so-ever!
    I still have to purchase an older  GTX 980 graphics card to take advantage of Adobe's approved code to utilize X=Cuda Cores and GPU, but I think I'll hang onto my new TitanX, in hopes that Adobe will write code and approve it someday in the near future.
    Now why doesn't Adobe say this officially about Memory Settings? (I don't know maybe they do and I missed I somewhere)
    Mine and probably many peoples computers problems here on this board may be attributed to a simple Memory adjustment, because the computer needs more than 7Gigs to run itself, not to mention Premiere.

  • Premiere Pro CS3.0.1 Update

    Found this on another sire. Any ideas?
    Premiere Pro CS3.0.1 Update
    Just got notified that an update is available for Premiere Pro CS3. The update is 3.0.1. Went to Adobe's site to see what the update was, but couldn't find anything on it. Anyone know?

    You get what you give.
    Cheers
    Eddie
    Forum FAQ
    Premiere Pro Wiki
    - Over 250 frequently answered questions
    - Over 100 free tutorials
    - Maintained by editors like
    you

  • PreludeCC and PRemiere Pro CC will not update  error: " log Transport 2"

    PreludeCC and PRemiere Pro CC will not update . update gets to 62% and then quits with the following error code "Log Transport 2"
    System
    OS 10.9
    MacPro 3,1
    All other apps do update.

    HI Steve & Perry,
    Have you tried restarting the machine and applying the updates again ? If yes, are you still getting the same error message ? If yes , could you please share a screen shot of the error that you get ?
    Cheers,
    Kartikay Sharma

  • Premiere Pro CC stopped working? How do I get help from Adobe to get it going again?

    Premiere Pro CC stopped working? How do I get help from Adobe to get it going again?

    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
    •What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    •What is your exact graphics adapter driver version?
    •Have you gone to the vendor web site to check for a newer driver?
    •For Windows, do NOT rely on Windows Update to have current driver information
    •-you need to go direct to the vendor web site and check updates for yourself
    •nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    •ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    -and a fix for at least "some" ATI crashes https://forums.adobe.com/thread/1553342

  • Is it possible to use markers in a Premiere Pro sequence such as Chapter / Comment / Segmentation and export the XMP metadata for a database so that when the video is used as a Video On-Demand resource, a viewer can do a keyword search and jump to a relat

    Is it possible to use markers in a Premiere Pro sequence such as Chapter / Comment / Segmentation and export the XMP metadata for a database so that when the video is used as a Video On-Demand resource, a viewer can do a keyword search and jump to a related point in the video?

    take have to take turns
    and you have to disable one and enable the other manually

  • Premiere pro cc 2014 new update terribly slow, previous versions available?

    recently updated to the newest version of premiere pro in the middle of a project. ( silly, i know) been experiencing so many problems. specifically lag in the program and rendering previews. ive searched all over threads and google for what could be causing the problem to no avail. also have tried uninstalling, cleaner tool, reinstalling. tried changing permissions. at this point i just want to revert back to CC or at least 8.01 but i cannot find any links or a way to return to a previous version of premiere. any help?
    Im using a mac book pro with osx Yosemite
    dual core 2.2 250gb ssd boot and 750gb 7200 rpm internal
    not the beefiest system by any means but it was workable, up until recently.
    im at my wits end with this. 

    Install a previous version of any Creative Cloud application

  • Will not install Premiere Pro CS6; will only "update"

    I downloaded the Creative Cloud and tried to install Premiere Pro CS6 -- but it only gave me the option to "update" it (even though I do not have any verison of Premiere Pro in my Applications. Help!

    Hi rachelrashley,
    Please rename caps Folder from this location and then Relaunch AAM.
    Windows:
    C:\Program Files (x86)\Common Files\Adobe\
    Mac:
    Library/Application Support/Adobe/
    Once done Premiere pro CS6 should show up in the AAM.
    Regards,
    Abhijit

  • Premiere Pro CC Bug Fix Update (7.2.2)

    Hi,
    Today a bug fix update was released for Premeire Pro CC. Check out this link for full details: http://blogs.adobe.com/premierepro/2014/04/premiere-pro-cc-7-2-2.html?scid=social21455164
    Thanks,
    Kevin

    Hi Richard,
    rnaphoto wrote:
    Hi Kevin-
    I see on another thread that lots of folks are having this issue. Since a Plural Eyes workflow if very common, I would expect that your testers would check that out pretty thouroughly.
    We have beta testers and QE engineering constantly testing out common workflows, including with third party applications like PluralEyes.
    Regarding this issue: we tried to test those problems with PluralEyes in house after we heard about them, but have not been able to reproduce the problem. That's why we're collecting media and project files from users.
    rnaphoto wrote:
    In the meantime, is there any way that folks can go back to 7.2.1? I think it would be good if Adobe would give us the option to go back when things go wrong.
    Sure, I wrote a blog post about that: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pr o-cc-or-any-creative-cloud-application/
    Hope that helps you.
    rnaphoto wrote:
    One really gets tired of dealing with these issues since they seem to be happening much more now that the CC allows fairly constant updates. Although constant updates may seem like a good idea to some, for many of us it seems like a lot of risk for not much gain since we are usually under the gun to get stuff done...
    Sorry you feel that way, and not sure what other problems you were having, but most folks are enjoying the updates and not experiencing issues like that. FWIW, you never have to update if you don't want to.
    rnaphoto wrote:
    But I can't emphasize enough that part of the updating MUST include extensive testing using common workflows. I could have told you you had a problem within 15 minutes of installing this update...
    I'm sorry, Richard. Unfortunately, it's not that easy. We could not even reproduce the issue in-house. So, there must be something different with your system, media, workflow, that we have not found yet. We are investigating the issue thoroughly, and hope to have a fix as soon as we can.
    Thanks for understanding,
    Kevin

  • Premiere Pro 3.1.0 update for Intel SSE4.1

    The Premiere Pro team posted yesterday in Adobe Labs an update that offers optimized support for the Intel SSE 4.1 instruction set, as found in the Penryn family of processors. Apparently, this instruction set can provide clear performance advantages for video processing.
    "This update is completely optional and is meant to be a preview of the optimization work that is currently under development for the next release of Premiere Pro."
    http://labs.adobe.com/wiki/index.php/Adobe_Premiere_Pro_Update_for_Intel_SSE4.1

    It's good to see Adobe responding so quickly to new technology.

  • Premiere Pro CC Won't Update

    I have been trying to update my version of Premiere Pro CC to v7.1 since the update came out last month. The update gets to 50% but then it fails every single time after that. When I try to find out why, I get this message:
    I know that it is not something wrong with my firewall settings or anything else because all of my other programs in CC update just fine. What should I do? Am I really going to have to uninstall Premiere and then re-install it?
    Thanks,
    Zack Jacobs

    Hi,
    Below is the link for how to resolve the error
    http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html
    regards
    Karandeep singh

  • Premiere Pro CC 2014 recent update...

    Hi, since this morming when i updated the entire Suite and Premiere... I couldn´t import AVCHD 60fps files in any project... It says that the archive couldn´t be opened... Could it be? Thanks!!!!!

    Please see this thread: How can I get AVCHD clips working after latest Premiere Pro Update (cc 2014)

  • Premiere Pro 7.2.2 Update

    Hi,
    I'm currently running Premiere Pro CC 7.2.1 on my iMac with 10.9.2. I have yet to get the update for 7.2.2 via Adobe CC, and trying to force the update via Premiere Pro Help -> Updates has yielded no updates as well.
    Is there any resolution or direct download to circumvent this?
    Thanks!

    So, I downloaded the update. Thanks for that!
    Now this has happened.

  • Premiere Pro CC 7.2 Update

    Facebook just announced another update to the video tools!
    Here is the link for SpeedGrade.
    To bad I won't get to use any of it.  No renting for me I just wanted to let people know.
    http://blogs.adobe.com/movingcolors/2013/12/12/speedgrade-cc-7-2-update/

    And here's the list of bugs that were fixed in 7.2:
    Import/Export
    Import
    AVCI-200 files have banding artifacts.
    Premiere hangs on importing longer XAVC files
    Some 2k RAW files show no video; instead, Media Pending graphic is displayed
    h.264 movies that were FFMPEG-generated and have uncompressed audio take an excessively long time to load
    XAVC SLOG2 clips now decode to 10 bit range with the proper color space clamping.
    Some AVC-Intra100 clips display artifacts
    Label colors are not preserved when a sequence from another project is imported.
    AAF import files path is missing backslashes
    Some metadata fields are missing or wrong when importing DNxHD assets via AAF from certain third party NLEs
    Merged clips from xml come into Premiere out of sync.
    Import of FCP XML sequence fails (“Generic Error”) if it contains a slug
    After pausing and resuming playback of a growing file in Source Monitor, playback stutters and audio sometimes cuts out.
    AVC-Intra files cause intermittent freezes in the Source and Program monitors
    When a sequence from another project is imported via Media Browser, the organization of constituent clips in bins is lost
    Importing XML from certain third-party color correction apps crashes Premiere Pro
    Media Browser does not remember the path it was last opened to. (Paths are saved to each project file, not application-wide.)
    Export
    Clip timecode is not written correctly in AAF encodes; Start timecode of the output is 0;00;00;00
    If a Premiere sequence containing a Universal Counting Leader is exported to AME, encoding sometimes hangs at Reading XMP (Mac only)
    When exporting to QuickTime, the Channel Layout setting is valid only with Audio Track Layout set to Single Track, but the Channel Layout control remains available with ATL set to N Mono Tracks or N Stereo Pairs
    Sequences exported to FCP XML do not include the elements “logginginfo” and “comment”
    In FCP XML exports, the start times for audio clips do not match in Premiere Pro CC and some third-party NLEs
    If a sequence contains a nested sequence that was synced in a third party app, then exports to FCP XML contain an incorrect <ntsc> element
    Playback
    Playback stutters with a nested multitrack audio sequence
    when Playback Resolution is 1/4 (one-quarter) and Mercury Playback is set to Software Only, HD sources that use ImporterFastMPEG appear square
    The video preview does not update correctly upon trimming the Out point when the direct manipulation control is active.
    When the direct manipulation control is active, moving a clip in the sequence causes the Program Monitor to display all black.
    Overlay displays multicam sequence audio as audio time units.
    Garbage matte effects are incorrectly rendered via Open CL with source content that has non-standard dimensions.
    Decoding errors with specific files manifest as red frames
    Poor performance rendering AVCI-100
    With certain hardware, SDI Transmit has audio issues
    Artifacting in Program Monitor when scrubbing with Transmit enabled [OSX10.9 only]
    Poor performance (dropped frames) when Transmit is used for playback to external monitor or export to tape; limited to certain hardware & drivers
    Editing
    Timeline
    Duplicate frame indicators impair performance with large projects
    Audio sequence clip name does not change when renamed
    Adjusting height of all tracks by scroll wheel with Shift key pressed works in the opposite direction vs. scrolling without Shift pressed (Mac only)
    In the Timeline, thumbnails are black for track items that have speed change to greater than real-time
    Sync by Audio
    Sync by audio fails if selected track items include multiple instances from the same master clip.
    Synchronize by Audio does not work with trimmed clips in some cases
    Synchronize by audio is not available if there’s no clip on either A1 or V1
    Sync by audio does not work correctly if the clip on Track 1 (or Camera 1 for multicam sequences) starts later than the other cameras.
    Merged Clips
    Importing sequences containing merged clips adds duplicate media files to the project.
    Importing a sequence containing a merged clip does not add the merged clip to the Project, but it adds the merged constituent source clips and renames the project items to match the merged clip.
    Subclips of merged clips uses the incorrect range of frames and do not respect the “Restrict Trims to Subclip Boundaries” option.
    If the audio in a merged clip starts before the video, that offset is not accounted for with subclips.
    Matching frame for a subclip of a merged clip does not go to the correct frame
    Multicam
    Occasional crash (TrackItem.cpp-205) upon right-clicking a multicam source sequence in the Project Panel
    After scrubbing a multicam sequence, playback sometimes causes the playhead to jump to the prior position.
    Reveal in Project from Timeline fails with some multicam clips
    Switching the Program Monitor from multicam mode to trim mode via keyboard shortcut puts monitor into undefined state
    If the camera order has been edited, the Program Monitor’s multicam view sometimes displays the wrong camera.
    Selecting a camera in the Source Monitor’s multicam view does not affect what is displayed on an external monitor via Transmit
    With some multicam sequences, loading into the Source Monitor via Match Frame does not draw the In/Out points.
    Nesting
    Mono source tracks don't show waveforms in a nested sequence (even when routed correctly, so as to not do any mixing).
    Rendering audio doesn't work on nested sequences (which means there is no way to force creation of audio waveforms)
    Recording:
    Audio Recording fails if an out-point is set and another clip is on the same track
    Effects and Transitions
    With GPU acceleration enabled, a transition's start and end times are sometimes not honored
    With certain graphics cards, Premiere Pro crashes on scrubbing a clip with Video Limiter Preset applied and GPU acceleration enabled.
    With some third-party transitions, layer parameters cannot be enabled after being disabled.
    With some third-party transitions, layer parameters do not initialize properly.
    When clips with transitions applied are copied & pasted from one project to another, the transitions are lost.
    Keyframe control icons in the Effects Control Panel do not appear after clicking stopwatch
    Markers
    Crash on tabbing from a comment marker to any type of marker other than a comment marker (e.g., a chapter marker)
    In the Source Monitor, the Edit Marker dialog does not open upon second "Add Marker" command.
    Selecting a clip in the Timeline does load the master clip’s markers in the Markers panel.
    Markers panel goes blank when a marker or In/Out Point is added/moved/cleared from a Multicam sequence loaded in Source Monitor
    Closed Captions
    The presence of captions in an XDCAM sequence prevents smart rendering and stitching.
    The app stops displaying many 708 blocks one frame earlier than programmed, which results in no captions being displayed in caption panel thumbnails or in the Source Monitor when you use the CC panel to jump to a block
    Some CEA-708 roll-up captions are decoded as a single paint-on caption block.
    Metadata: Metadata not editable on network files on windows
    Project/Sequence
    Project
    Relatively poor performance opening projects and relinking assets over some networks with Windows workstations versus Mac.
    Crash on loading a project with a preview file stored on network drive that’s not available
    Loading some projects takes a very long time, caused by proliferation of Link Index lines in the project file. (Afflicted project should be fixed by opening in 7.2 )
    With an image sequence selected, "Source Settings..." is disabled
    Relink
    Crash on relinking to valid media
    Opening certain projects invokes the link media dialog even though all content is present and linked.
    Relinking a clip with the “Preserve interpret footage settings” enabled can result in incorrect audio duration
    Relinking to a different master clip with longer duration sometimes fails to sync correctly
    Relinking fails on Windows if the project was created on Mac and content is stored on certain file server systems
    Sequence Settings:
    When Sequence Editing Mode is set to one of the AVC-Intra, XDCAM HD, or XDCAM HD422 options, the Preview File Format is locked on “I-Frame Only MPEG”; the PFF now has options optimized for these editing modes.
    Misc.
    Auto Save can interrupt multi-camera editing
    New Sequence from Clip adds one History entry for creating the sequence and one for each asset added.
    Source monitor misrepresents Audition subclips
    Crash on sending a sequence containing a track item that is entirely danger striped to Audition.
    Edits to keyboard shortcuts are saved despite exiting the dialog via Cancel.
    When an audio-only clip is loaded in the Source Monitor, scrolling by mouse wheel scrubs in the opposite direction of video clips (Mac only)
    With QuickTime Reference Files, Premiere uses the wrong timecode
    With UI Brightness at the lightest setting, track selection highlight and In/Out points are not visible

  • Premiere Pro Crashes after last update

    Premiere Pro WILL NOT RUN since running the update last week. I'm in the middle of a big project and I cannot get the program to boot completely.
    Computer: Dell Precision Mobile m6700, Win 7, 32GB RAM, nVidia K4000 card. Win 7 is up to date.
    The error message is [..\..\src\TickTime.cpp-121]
    Here is the error reporting from the dialog:
    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    Adobe Premiere Pro.exe
      Application Version:    7.1.0.141
      Application Timestamp:    526b4b24
      Fault Module Name:    MSVCR100.dll
      Fault Module Version:    10.0.30319.1
      Fault Module Timestamp:    4ba220dc
      Exception Code:    40000015
      Exception Offset:    00000000000760d9
      OS Version:    6.1.7601.2.1.0.256.48
      Locale ID:    1033
      Additional Information 1:    77b0
      Additional Information 2:    77b047d66f861c9bf4b14af605bb110d
      Additional Information 3:    5076
      Additional Information 4:    507694edd22aca9ddcf76452c7ddcef0
    Also noted; When the application quits (right at the beginning), and I can finally get it to really quit on the screen, it's still showing as running in the Task Manager.
    I have reinstalled Windows and have tried about everything I can think of to isolate the problem, but it will not go away.

    "The 0x40000015 error may be caused by windows system files damage. There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware attack or by an improper shutdown of the computer. All the above activities may result in the deletion or corruption of the entries in the windows system files. This corrupted system file will lead to the missing and wrongly linked information and files needed for the proper working of the application."
    http://www.sevenforums.com/general-discussion/268188-unknown-software-exception-0x40000015 .html

Maybe you are looking for