Premiere CS6 /Totalcode pluging, bug during export

Hello,
I try the demo version of total code for Premiere 6.0.3
I am very disappointed, because in H264/AVC export ,
preset HDTV 1080i
frame rate changed from 25i to 50p
the value of Reference Frames (Advanced setting panel) is always ignored and set to 3 in output,
Changing this value, or any B-frame setting has no effect, output is always 3 Ref Frames. (Checked via Mediainfo)
This is very annoying as many Multimedia-disks players (Like DVICO S1) does not support well Ref Frames greater than 2 (=> generate lags during video play).
This is a bug in Totalcode, as it was previously working in MainConcept Codec suite 5.1
Any way to bypass this bug will be appreciated, I plan to migrate to Totalcode for Cuda acceleration.
Olivier

That is a question for Main Concept, not Adobe
http://www.mainconcept.com/products/apps-plug-ins/transcoding/totalcode-studio.html?gclid= CNbUrIiG0rQCFYl7QgodgBsABQ

Similar Messages

  • Premiere Pro CS6 on PC freezes during export.

    I have a PC and do video editing for my job. I found that premiere has begun freezing at random and inconsistent intervals whenever I want to export a file. Is this normal? Is there a solution?

    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

  • Premiere CS6 Unknown Error in Rendering & Export

    Hello,
    this is an ongoing problem that persisted on any version of Adobe Premiere Pro I worked with, including CS5,5.5 and the latest 6.
    I am stuck with a feature film on a CS6 Timeline, getting an Unkown Error during rendering and Media Encoder exports. 
    I get the same error if I attampt to create a new trimmed project with Project Manager.
    I am aware that this is one of the most common problems in this forum, and before opening a discussion I tried everithing I could:
    - Replace the media at the point of the error/crash (even though the error seems to happen randomly in dirrerent portions of the timeline)
    - Disable MPE
    - Reset Secutity and permission on files
    - change hard drive
    - Create a new sequence
    - Disable second monitor
    I have to bring an export of my film and a new trimmed project by tomorrow to a color house and I am currently stuck.
    I managed to render the entire timeline before exporting. Redering would stop randomly, generating the same "Unkown Error in Copiling Movie".
    Although I rendered the entire timeline by creating different IN-OUT with the work area selection.
    After a long and tetious rendering process I managed to have the entire timeline "green" and ready to go.
    I figured that this way the exporting process would have been successful. Unfortunatelly not.
    I switched to Premiere Pro for its ability to edit R3D media, but what's the point if we cannot export the project? And neither trimm it to a file that I can give to a colorist?
    Here some details of my workstation and source media:
    - MacPro 12cores 64Gb ram
    - Internal 6Tb raid for source media
    - 4Tb Dulce Scratch drive
    - Editing 4K and 5K R3D Media natively
    If anyone found a solution to this problem, please help.
    Thanks

    Hi Neonhigh,
    If you are going to color correction, why do you need an output? Aren't they color correcting the native files?
    I need an output as reference for the VFX department, I need an output for the sound designer, I need an output for the producer, I need an output for myself and to send to my girlfriend. The question I should ask you is, why shouldn't I need an output?
    What's wrong by exporting my timeline in a format that is not r3d files for reference and production management?
    I was talking about color correction only, as they usually only need the native files. Of course, an output would be necessary for all the other things you mentioned. Nothing wrong with that.
    Neonhigh wrote:
    If you need an output for some reason, why are you rendering at all?
    As I explained I simply rendered because the software was having several random "Unkown" problems in exporting. I though rendering and exporting a file matching the timeline settings would have solved those annoying Unkown Errors, giving me at list an export based on the render sttings.
    Problem is that PPro CS6 fails also to render the timeline, and I needed to break the process in 30-40 segments in order to achieve a complete rendering.
    Rendering in Premiere Pro is primarily for playback, and not necessary for output. In fact, it's a waste of time in most cases. Render files are typically not used for an output unless you explicitly want to do so. Typically they are lower resolution "preview" files that you don't want to use.
    Regardless, you should have no trouble rendering sections of your Timeline. Are you updated to Premiere Pro CS6 (6.0.2)?
    Can you try an export without rendering?
    I wish PPro CS6 was reliable enough to allow me to simply export.
    I still did not solve the problem. Several people from the redusers forum are trying to help me as and they all ran into the same issue.
    Currently this are the issues:
    - PPro does not render the entire timeline
    I'm trying a test project right now and so far it is rendering OK. Can you point me to the reduser forum post where people were giving you assistance?
    - does not output the entire timeline (if not chopping it in 12-15 parts)
    I'll test that, as well. You should not have to segment the sequence in order to get an export.
    - Project Manager does not trim the project to pass it to over post prod facilities.
    Sorry, the Project Manager will not consolidate every media type. It will copy, however. This would be a feature request or bug report: http://www.adobe.com/go/wish
    Beside questioning me with why I want to render or export my project,
    Not questioning your capabilities or talents, I just wanted to know what you wanted to do, and why. Typically, most people don't render as much in Premiere Pro as they do in other NLEs and I was wondering why you needed an export to go to color correction. That's all.
    Many users in this forum (as well as on the entire internet) experienced th same Unkown Problem:
    http://forums.adobe.com/message/4661398
    There could be many different variables which can cause that error. The troubleshooting doc you found addresses many of those. I will add the "Unknown Error" warning to the document.
    There is no "single fix" for this problem, I'm afraid, and these are our opinions and solutions on the matter.
    A legitimate gripe would be that the error is too generic, and I would agree with you there. The error should contain more details about how to remedy your issue. Please make a feature request for more descriptive error dialog boxes: http://www.adobe.com/go/wish
    I will also mention it to the product team.
    I understand that, being an "Unkown Errror" Adobe does not have a iniversal fix, but please don't ask me why I want to output my timeline.
    Again, I was only asking in the context of color correction. Of course, you want an output for various reasons.
    I've written up your bad experience in my case notes and I'll do my best to get you some better answers to your questions. You definitely should not have to jump through hoops to render or export a .R3D sequence.
    Neonhigh wrote:
    Here is a temporary fix for who runs into this problem:
    Yesterday, after trying everything I could think of I simply exported an XML, opened it in Final Cut Pro and exported all the files and formats that I needed. No Unknown Errors.
    Thanks for the workaround. I'll add it to my notes.

  • Premiere CS6 start/stop bug

    Hello Forum,
    Running CS6 on a macbook pro. (Dual 2.9ghz 4gb ram), Premiere will not playback clips.  When I hit spacebar or play, it will go for a second, then stop.
    I have searched the forum and have tried switching audio settings, still no fix.
    I have uninstalled Premiere and re-installed.  No fix.
    Any ideas?
    Thanks!
    - Ryan

    I am on Windows, but have a few saved Mac messages that may help (or, may not... but free to read)
    Mac and Root User http://forums.adobe.com/thread/879931
    -and http://forums.adobe.com/thread/940869?tstart=0
    Mac and Playback loops http://kb2.adobe.com/cps/842/cpsid_84287.html
    Mac Retina Bug http://forums.adobe.com/thread/1159632
    Troubleshooting guide for Mac freeze
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html

  • Premiere and Media Encoder Crashing During Export of Quicktime Files

    Premiere CC and Media Encoder CC crashes when exporting Quicktime H.264 files. Sometimes the export will work, sometimes it crashes the app. After crashing, the app will freeze while loading "ExporterQuictimeHost.bundle" and requires a hard re-boot of the system to startup again.
    I have tried removing some Quicktime codecs from the Quicktime library folder, as suggested in other threads. This has not solved the problem.
    I am editing with Quicktime ProRes 4444 files.
    Any help on this would be greatly appreciated. Here's some system info:
    Mac Pro Mid 2010
    OS X 10.9.4
    2 x 2.66 GHz 6-Core Intel Xeon
    36 GB Memory
    NVIDIA Quadro FX 4800 1536MB
    Blackmagic DeckLink HD Extreme
    Cuda Driver Version 6.5.14
    Creative Cloud CC 2014

    I'm having similar problems. I can't export anything now...either from Premiere or from Media Encoder. My sequence is ProRes HQ, I am exporting using sequence settings.
    It gets about 75% of the way through and bails with this error message:
    Export Error
    Error compiling movie.
    Unknown error.
    That's really helpful. Addtionally, when I tried to export out of Media Encoder, I was greeted by an extremely loud bleating goat noise when it failed. Nice. I had a room full of clients. Thanks Adobe.
    I'm seriously doubting the claim of "Pro" at this point.
    This was not beta tested with a ****.

  • Scale bug during export in CS3!!!

    I have a slideshow which all of the pics are scaled with the option "scale and crop edges". When I preview it in encore it looks perfect. The problem occurs when I export/builds the dvd, flash or whatever. When I playback the slideshow it looks like some of the pictures jumps between the two scaling options "scale and crop edges" and "scale and apply matte". In one frame the picture fills the entire screen and in the next frame it has 1/4 of black matte on each side. The jumps in scaling happens totally random, or at least I can`t find a pattern.
    I appreciate all feedback!
    THANX

    You can't "fix" overscan. Your audience has TV sets that are overscanned to some degree.
    But your audience also has computer monitors that (most likely) don't overscan at all.
    You have to create content that takes overscan into account if your target audience will be viewing that content on a TV set.
    You can safely ignore overscan if your finished DVD will be shown *exclusively* on a computer monitor.
    If we eliminate overscan as a consideration at all, then I have to ask: does the scaling change occur before, during or after a transition between static slides? How about changes between slides with motion effects applied?

  • Premiere Pro 1.5 - crashing during exporting as movie

    Premiere Pro 1.5 - been using successfully for years - same computer winXP - now it crashes (stops exporting) as making .avi.  
    Plus, when loading the program, keep getting prompt about a failed attempt to load ffdshow (not on white or black list?).   PLUS, sometimes program crashes when working with title editor.
    I understand the custome rphone service is not available for the 1.5 version - again, been successfully using PP 1.5 for years - I've have change little on this computer ... other than xp updates.?  
    YES - I tried reinstall.   YES - I tried adobe updates.
    Help!

    I have read other messages saying that ffdshow can cause problems... you might go to the search box back on the main page and enter ffdshow
    I have also read that a corrupt font can cause problems, with the advice to use a font manager to remove/relink fonts to find the bad one

  • Premiere HD sequence keeps crashing during export

    Hi there everyone,
    Today I experienced a problem completely new to me. I tried exporting an HD sequence to a small WMV for use on the web. I used Ctrl-M (export media) to export directly without using the queue. No matter what kind of export settings I entered, the export render fails roughly halfway and Premiere hangs. I also tried an uncompressed Quicktime export, which crashed at about 25% in the same manner.
    The workaround for this issue appeared to be using the queue instead of a direct export... which comes a little strange to me as SD sequences never seem to fail like this. Anyone any ideas?
    Thanx in @vance,
    Tom

    Hi Harm,
    Thanks for taking time to answer. What happens is I get a Windows error message stating 'Premiere has stopped working' and I can choose to end the program straight away or let Windows find a solution and then stop the program; a definitie frozen situation. So I guess it stops responding.
    I have a Matrox MX02 LE graphic system, Windows 7 SP 1, version 5.0.3 of Premiere, HD source material (1440x1080) in the standard Matrox HD codec and I have tried exporting to a 1024 x 576 Quicktime with compression set to NONE for both audio and video. I also tried exporting to WMV 1024 x 576 in the highest variable unconstrained bitrate for A/V available.
    There are no blank spots in the timeline.
    As said, using the queue feature for export, leading to the full start of the Media Encoder appeared to be a workaround.
    Then again, I tested exporting the same thing directly, so without queuing, from an SD project, which worked nicely.
    I therefore suppose it must have something to do with the HD to SD conversion, but it beats me what it could be.

  • Adobe Premiere Elements 7.0 hangs while exporting and during peak file generation.

    I have Adobe Premiere Elements 7.0 (PRE7). I have a project which is using a single clip from a Mini-DV that was captured with Nero 8. Nero 8 was used because it was captured prior to installing PRE7. The file is 12GB and is on a USB disk drive because I don't have the space on my main hard drive (I have about 11GB free). My project doesn't do too much that's fancy. It merely uses about 20 minutes of the 60 minute Mini-DV captured AVI, and it uses simple transitions between each scene. I also have very simple titles at start and end. No themes or anything else.
    I've seen two problems. 1) While editing the project, seemingly (but I'm not positive it's related) while the peek file was being generated, PRE7 would get into a state of using about 40% to 50% CPU, and it would not let me do anything else. The other problem, 2) While using "Share" to export the video to WMA for playback on PC (about 180MB estimated file size according to Adobe), the file is exported to about the last remaining 5 seconds, but then PRE7 goes into that mode of hanging with 40% to 50% CPU usage.
    One time when it had this 50% CPU issue, I let it sit overnight, and the export was finished in the morning. The export that time was to a 90MB FLV for posting to the "web" according to the Share wizard. But when I was doing the above (issue #2), it went into the 50% CPU usage but didn't finish after waiting around 2 hours. Even if I were to let it sit that time, and it were to finish, it seems like something's wrong and that this is unacceptable.
    When this happens, and PRE7 goes into 50% CPU utilization, there is no pacifier or percentage bar advancing. It usually happens near 100% finished. Only one time did it complete successfully after leaving it unattended at 90% complete for an extraordinary amount of time.
    To recap:
    C:\ hard drive ---> PRE7, my project.
    E:\ USB drive ---> 12GB source AVI file and destination for export.
    I saw elsewhere on this forum that someone imported a mini-dv captured AVI into Window Movie Maker and then exported it to Mini-DV from that app. This solved that person's problem with hanging during peak file creation. I had the 50% hang issue during peak file generation but I'm not sure it was related to peak file generation. A peak file was generated in a project which, when exported with share as mentioned above, still did the hang 50% CPU issue. Regardless, I will try the import/export/movemaker thing and report back but I've been trying enough things that I wanted to take a second to ask for assistance.
    Does anyone have this issue, and is there a patch or fix?
    I might be able to provide a user mode dump of the 50% CPU adobe process. There is some call stack information and I'm wondering if developers would want this info if they don't already have a solution/fix to this bug.
    Thanks for any help.

    I have some more info on the hang which I've been experiencing during export/share of a project which uses an AVI as its one main clip. Adobe Premiere Elements 7 (PRE7) appears to be hanging because it's looping endlessly in ImporterAVI.prm. I'm wondering if this info can be passed onto Adobe developers and/or if I can submit this information elsewhere for such processing. I also have a process dump file which might be helpful, not to mention the original project files.
    I used Process Monitor to help analyze this situation, and prior to PRE7 getting into the endless loop, it appears to be reading from the AVI file little by little, and WMEncodingHelper.exe is writing out little by little to the destination file, both of which I would expect. When PRE7 gets to the end of the import/export, Process Monitor appears to show all the aforementioned disk activity ceasing. I see neither process reading or writing. This would be normal if the share/export procedure had completed. But PRE7 is not complete. It is hung and is operating at 50% CPU utilization.
    Far below in this post are technical details which may be helpful to an Adobe developer determine why the importer could get into this endless loop. In those details, there is a jump instruction, "jb ImporterAVI!xImportEntry+0xf32", which will always jump if a particular compare always turns out a certain way. But in my review of the counters being compared, it never will get to a point of exiting. When I modify a flag (the carry flag) to be 0, the loop exits. When I did this, my export/share of my project completed successfully. So it was done, but for some reason, PRE7 was looping and looping in its AVI importor instead of completing the export (aka "Share").
    I cannot say that this certainly indicates a bug with PRE7, but it seems to me that there's enough data for Adobe to be at least investigating this particular issue. I'm not the only person who has seen this as there was at least one other message describing the same problem which the user resolved by effectively re-creating the AVI file via a no-op import/export into and out of MovieMaker. My AVI also goes through MovieMaker, import/export, without a hitch.
    In a sense, I view PRE7's "share" as essentially an import, processing of imported information (i.e., effects and transitions), and an export. It's an import of all clips into the project at the right times, a processing of all effects, and finally an export to a destination. I realize this is simplistic, but the point I'm making is I have a simple project with a single AVI, and it appears that the "import" portion of PRE7's Share option is choking on the only clip used by this project. I also don't have much but simple transitions and a beginning/ending title on the project, so I'm not thinking this use of PRE7 is much more than what I'm doing with MovieMaker when importing/exporting this AVI.
    I fully agree that optimum hardware can be either required or critical for certain types of video editing, but PRE7 is a consumer program and I'm not using anything extensive about it and the symptoms are that PRE7 is looping on its import of a file other programs don't have a problem with. I already tried purchasing a 1TB external, which I'm glad I did, but I really think Adobe developers should look at this issue. There may be a problem with handling certain AVI clips used in a project when those clips come from certain sources. If there is an issue, perhaps it could warrant a fix that would make PRE7 more compatible with these other clips.
    Does Adobe have a procedure for people to upload (or mail) projects and files to it so that they can troubleshoot why the importer gets into this state? I also mentioned earlier that I have a full user-mode dump of the process which may be of value to a dev. Can I submit this information anywhere?
    Here are textual technical details:
    Plug-in which loops: C:\Program Files\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US\ImporterAVI.prm
    The following are the instructions at the "bottom" of the loop which never ends. Below, I put "***" at the jump instruction I mentioned earler. If I force the carry flag to be 0 at that point, and the jump is skipped, the export completed successfully. Additionally, notice that [esp-0x1c] is 0x2000, and that both eax and edi are 0. When I see it loop, eax stays at 0 and never reaches 0x2000. I wonder if something about the AVI is causing values used by this importer to be such that it causes this endless loop, and if that's the case, and if such values are valid/good, I'm wondering if the importer can be fixed by being able to detect such values so as to not choke (if in fact it's an importer issue).
    1239dda2 50 push eax
    1239dda3 ffd1 call ecx
    1239dda5 8b442424 mov eax,dword ptr [esp+24h]
    1239dda9 015c2428 add dword ptr [esp+28h],ebx
    1239ddad 03c7 add eax,edi
    1239ddaf 83c410 add esp,10h
    1239ddb2 3b44241c cmp eax,dword ptr [esp+1Ch]
    1239ddb6 89442414 mov dword ptr [esp+14h],eax
    ; *** This is where it loops around and around.
    1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2)
    ImporterAVI!xImportEntry+0x1040:
    1239ddc0 8b542420 mov edx,dword ptr [esp+20h]
    1239ddc4 52 push edx
    1239ddc5 e810d40000 call ImporterAVI!xImportEntry+0xe45a (123ab1da)
    1239ddca 83c404 add esp,4
    ImporterAVI!xImportEntry+0x104d:
    1239ddcd 5f pop edi
    1239ddce 5e pop esi
    1239ddcf 5d pop ebp
    1239ddd0 33c0 xor eax,eax
    1239ddd2 5b pop ebx
    1239ddd3 83c428 add esp,28h
    1239ddd6 c3 ret
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    3195d9b8 12387545 10590f9c 27c53e00 06b35ff6 ImporterAVI!xImportEntry+0x103a
    3195d9ec 1239ea10 06b35ff6 00000000 27ad8a60 ImporterAVI+0x7545
    3195da1c 1238aa31 06b3554b 00000000 7fdf0000 ImporterAVI!xImportEntry+0x1c90
    00000000 00000000 00000000 00000000 00000000 ImporterAVI+0xaa31
    [esp-1Ch]: 3195d9a0 00002000
    eax=00000000 ebx=00000000 ecx=3195dbcc edx=00000000 esi=27ad8a60 edi=00000000
    eip=1239ddba esp=3195d984 ebp=3c7ba50b iopl=0 nv up ei ng nz na pe cy
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000287
    ImporterAVI!xImportEntry+0x103a:
    1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2) [br=1]

  • Premiere CS6 not exporting to ME6 Queue

    I've had nothing but success with Premiere Pro CS6, but the ability to Queue up videos to Media Encoder CS6 suddenly stopped functioning (nothing happened that I'm aware of). I'm able to Export just fine from Premiere and can add manually to ME, but cannot export to the queue list.
    This happens after reboot, with different video files, and when the renderings are deleted or not. MECS6 will open, but just sit there. Any ideas of what would be going on?
    System Specs:
    Mac Pro 1.1 on OSX 10.6.8
    Dual 2.66GHz Intel Xeon
    GeForce 7300GT
    4GB ram

    To import a sequence into AME with PPRO closed, open an OS file browser and go to the path where your pproj is saved. Drag and drop that file into AME (either onto a preset in the Preset Browser or directly into the Queue). You can also select "Add Premiere Pro Sequence" in the File Menu and then browse to your project. Regardless of which path you go down, AME will bring up dialog that shows you all the sequences within the project.
    I expect that importing through one of these workflows will yield the same results as dragging and dropping a sequence from PPRO to AME. All of these methods work directly with the original project file, whereas the normal workflow of exporting from PPRO (File>Export>Media) saves a temporary copy of the sequence at the instance you export.
    Note that in our experience, all of these export workflows add the job to AME in a matter of a few seconds, so we did see a need for a progress dialog. Clearly in your case something is significantly bogging down the process. Perhaps project size or complexity, effects & color grading, some I/O bottleneck.... The fact that drag-and-drop is, what, five times faster makes me suspect that an I/O problem (something like a badly fragmented disc where the snapshot of the sequence is being saved) is at least part of the equation, but that doesn't explain why drag-and-drop still takes over a minute.
    Can you check RAM and CPU usage before and during export to see if either resource is getting pegged?
    Also, what drives do you have your project on and are you encoding to? Are you using a solid state drive? An external drive? Working across a network? Do you have antivirus software running?
    Another possible culprit is conforming audio. I'm not sure what the best way is to check if that's happening other than watching your media cache folder to see if new files are being written.

  • Export Premiere CS6 (h.264) - Audio out of sync with several players...

    I've had this problem before, but unfortunately it happened again.
    I exported an mp4 with h.264 compression. The file plays perfectly with VLC player and everything is in sync. Of course, in Premiere (CS6) everything is in sync as well.
    It is also synced correctly with Windows Media Player, as long as you don't 'scroll' or skip parts in the video. If you do that, the audio gets out of the sync...
    With QuickTime it is completely out of sync. Vimeo plays it back perfectly, with YouTube it is out of sync...
    How is this possible? What is causing this?
    I thought that it could have had something to do with the video and audio tracks not being of the same length. I have already mastered the audio tracks into 1 track (wav) and made the same length as the video tracks, before I exported... On previous projects I have have not done that, and the audio was slightly out of sync there as well on Youtube.
    What did I do wrong? Any settings I could have done wrong? Is this a bug of Premiere? What can I do to prevent this?

    Yea, that sounds plausible but from the other hand, this happens only with (my) exported clips from Premiere...
    When I download or watch clips from the internet that are mp4 files with h.264 compression, there is no problem. I just skip through a file of 4GB and it plays back fine. Also the clips from my camera (which are h.264 files) play back fine with everything in sync.
    Also, I almost never see sync problems on YouTube.
    There is something else going on here... It must be.

  • Why wont premiere CS6 export .mp4's?

    why wont premiere CS6 export .mp4's?  Everytime i try to export h264 mp4's the final export is an unrecognizable .m4v file.
    I read about this 'bug' in a thread started over 8 months ago,  and read that the 'work around' is to export with audio on. (my videos have no audio channels, so why would i want to save them and make them larger, by encoding them with audio?)
    I am preparing to switch from Final Cut 7, to Premiere Pro, but i'm concerned to do so as this bug apparnetly was never fixed by adobe, almost a year later.  There seems to be no way to encode an .mp4 without audio using Premiere Pro CS6 or Media Encoder CS6.  Is there any kind of patch or another way to export .mp4's?
    thanks.

    That is exactly my point!  Why should I have to export an audio channel and increase the file size to work around a known bug of the software...
    We export about 100 videos a day and it will add up.  These are files that will be online, and size is an issue.
    I'm just not sure that we'll want to invest in software with a known bug that hasn't been addressed after months. 
    I was hoping that maybe there was a patch or update that I haven't found yet.  Thanks all.

  • Mac Pro restarts with kernel panic error during Adobe Premiere CS6 or Adobe Media Encoder CS6 render/encode.

    Multiple times this week, my Mac Pro at work has been restarting during renders in Adobe Media Encoder CS6 and Adobe Premiere CS6. This seems to be specific on this computer only. Identical computers don't have this problem. Here is the system report after it reboots to OS X:
    Interval Since Last Panic Report:  252068 sec
    Panics Since Last Report:          2
    Anonymous UUID:                    7DF9A04B-0693-5FC4-60CF-4BC6ABDB3C1E
    Fri May 17 15:37:07 2013
    panic(cpu 0 caller 0xffffff8009ab7e95): Kernel trap at 0xffffff8009e1b814, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x00000000000000b8, CR3: 0x000000000c3d3000, CR4: 0x00000000000206e0
    RAX: 0x0000000000000001, RBX: 0xffffff8039ebfb98, RCX: 0xffffff800a08eb00, RDX: 0xffffff82413abde8
    RSP: 0xffffff82413abde8, RBP: 0xffffff82413abe20, RSI: 0x00000000000000b8, RDI: 0x0000000000000001
    R8:  0x0000000000000000, R9:  0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
    R12: 0x000000000000004a, R13: 0x0000000000000371, R14: 0xffffff8040611cb0, R15: 0xffffff80404ec008
    RFL: 0x0000000000010206, RIP: 0xffffff8009e1b814, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x00000000000000b8, Error code: 0x0000000000000002, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff82413aba80 : 0xffffff8009a1d626
    0xffffff82413abaf0 : 0xffffff8009ab7e95
    0xffffff82413abcc0 : 0xffffff8009acd4dd
    0xffffff82413abce0 : 0xffffff8009e1b814
    0xffffff82413abe20 : 0xffffff7f8bcf4d54
    0xffffff82413abe60 : 0xffffff7f8bcf72f1
    0xffffff82413abf20 : 0xffffff8009d86e2b
    0xffffff82413abf60 : 0xffffff8009a3dcfe
    0xffffff82413abfb0 : 0xffffff8009ab2977
          Kernel Extensions in backtrace:
             com.apple.nke.asp_tcp(7.0)[78FAA01C-ABC4-3AD3-8D9A-6187F7911E1A]@0xffffff7f8bce f000->0xffffff7f8bcfbfff
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    12D78
    Kernel version:
    Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
    Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
    Kernel slide:     0x0000000009800000
    Kernel text base: 0xffffff8009a00000
    System model name: MacPro5,1 (Mac-F221BEC8)
    System uptime in nanoseconds: 76945023460235
    Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 20 GB, SMC 1.39f11
    Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
    Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
    Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
    Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
    Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
    Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
    Serial ATA Device: HL-DT-ST DVD-RW GH41N
    Serial ATA Device: WDC WD1001FALS-41Y6A1, 1 TB
    USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd300000 / 2
    USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd320000 / 3
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x5a100000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x5a110000 / 3
    FireWire Device: built-in_hub, 800mbit_speed

    That doesn't look like a complete panic report. Is there any more to it? Regardless, I suggest you run the extended form of the Apple Hardware Test. If it fails to identify a fault, remove the RAM upgrade and test with the original RAM.

  • Error exporting Premiere CS6 sequence to edit in Audition CS6

    Hi there!
    I've been trying to export a sequence from Premiere CS6 to edit in Audition CS6 through "edit>edit in Adobe Audition>sequence". However, I keep receiving the following error message:
    Premiere Pro has encountered an error.
    [../../Src/Sequence/TrackItem.cpp-171]
    When I hit continue the rendering doesn't move forward and I have to cancel the process.
    Does anyone has a clue what could be wrong???
    Thanks a lot!

    This is a link to something similar
    right click dynamic link to audition broken (premiere cc 2014)

  • Premiere Pro CS6 crashing when trying to export

    Trying to export a video in PP CS6 and keep getting this error:
    "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project."
    This happens no matter if I try to export AppleProRes or H264 or whatever)
    I'm working  on a new MacBook Pro   running OS X  10.9.5
    Processor- 2.5 GHz Intel Core i7
    Memory- 16GB 1600 MHz DDR3
    I've tried everything you normally do like:    restart - reinstall software - creating new project - trying different material - ....
    AND: I also checked Video Rendering and Playback (Mercury Playback Engine) : It's set to "Software Only" and greyed out.
    Any help is greatly appreciated! I have to finish that #### movie until tomorrow :-(
    THANK YOU!

    Sorry - forgot some details:
    Premiere Pro Version: 6.0.5
    Software is installed on a brand new computer. On the old one it ran without problems, on the new one I can work with Premiere without problems but I cannot export anything.

Maybe you are looking for