Premiere hangs when exporting

Has anyone had any trouble with Premiere freezing/hanging during an export? I have my CC account on a work iMac and a retina MBP 15" and both are experiencing the same exact issue: when I try to export the sequence I created the application hangs indefinitely (spinning pinwheel) as soon as I hit the Export button. It may have something to do with the ExportQuicktime.bundle file, as if I force quit the application it will hang when I try to re-open it unless I restart the machine.
Help, please!

AMD Graphics?

Similar Messages

  • Premiere crashes when exporting to Soundbooth

    I've searched everywhere for an answer but can't find anything.  When I try to export an audio file from Premiere to Soundbooth, Premiere hangs.
    The only change to my system recently was I downloaded some Matrox codecs.  Anyone have any ideas or solutions?  I'm using Win 7.  Thanks

    Thanks, I appreciate the quick response.  I don't have a Matrox card but I was working on a project that the client used a 1920 x 1080 Matrox codec.  It was version 10.  My Premiere is version 5.03.  The audio file is just an HDV file that I was trying to correct audio on.  I thought it might have something to do with Dynamic link but I was able to import AE comps.

  • Serious show-stopping bugs in Premiere Pro when exporting

    OK, so first of all, I get that making a video editor is not an easy task. In fact, it's a nightmarish task. One I would never even attempt. However, Premiere Pro CS6 has been worked on since 1992 or so, by one of the biggest and wealthiest software companies in the world, with well paid experts on this very thing. It's supposed to be professional-grade, but bugs like this makes me wonder if it's some sort of a joke. It simply does not do what you tell it to when exporting. I come back to this problem (and similar ones) again and again. It's not me doing anything wrong. It's not me having misunderstood something. It's serious bugs in this software. There is no other explanation. Please look at these images:
    To the left: the video file as it appears in Premiere Pro.
    To the right: the video file as it appears once exported using the "Match Sequence Settings" option.
    What you cannot see well in the images is that the quality is also significantly lower, and it stutters in an insane fashion.
    It does NOT match the sequence settings. I repeat: it does NOT match.
    I know some people on this board are eager to reply quickly, but I would rather have you think this over before. It gets very tiresome to have people shout out the first (incorrect) thought that pops up in their minds. Thank you for respecting that. Please only respond if you know what is going on for sure.

    The "Match Sequence Settings" settings forces Pr to use rendered preview files as a source, instead of the actual source video.  If no rendered preview files are present, it defaults the export settings to the same settings that are used in the sequence to generate the preview files.  Check your sequence settings - you'll see what export settings Pr is using when MSS is selected.  Most likely, it's not what you want or expect.
    I've been told that the Match Sequence Settings check box is working as designed.  I personally think it's confusing and misleading.
    Jeff

  • Premiere hangs when it cant find cache files

    Hi all,
    My question:
    How do I force premiere to open my projects without searching endlessly for cache files?
    If this cant be done:
    What is the best way to create a network based central cache folder from which multiple users can draw from. (the problem of course is the potential for this file to grow exponentially)
    Background
    9 times out of 10 when I attempt to load my premiere projects off the network, the load bar will reach just about 95% and hang for an eternity. We have identified that our company bandwidth was getting a bit overloaded but I think another issue has reared its ugly head.
    Our company stores all premiere files and related footage on the network to allow for easy access from many users. However, when a user who did not create a certain project attempts to open it on their desktop, the same loading problem comes up. It appears that if I push my cache files to the network, point premiere to that folder, the file loads rather quickyl (indexing aside).
    So can I force premiere to give up on a hopeless search of the local computer for cache files and if not, how can I create an organized  system where many users can pull from the same cache folder. You will notice, if i simply create a central folder the following will take place:
    The folder will grow
    I will have to wipe it
    files will stop loading while premiere desperatly attempts to find non existant cache files.
    Thanks for your help.

    Some reading
    Win Server is NOT supported http://forums.adobe.com/thread/851602?tstart=0
    Not in a Network environment http://forums.adobe.com/thread/771151?tstart=0
    -and not on a "domain" http://forums.adobe.com/thread/858977?tstart=0

  • Latest version of Premiere crashes when exporting media to Queue

    BUG REPORT TO ADOBE
    Select sequence
    Export Media
    Export QUEUE
    Export dialogue appears, but progress frozen
    AME starts up
    Premiere has crashed and required forced restart
    PP 8.2.0 (65)
    AME Build 8.2.0.54
    The above are latest versions as of this morning. When will this be fixed? I cannot rely on this feature

    Thanks for the suggestion - I will give that a try. This is on Mac OS X Yosemite BTW. I am now exporting via PP which always seems reliable but takes PP out of action for several hours while it exports, which is the main motivation to get it working properly with AME.

  • InCopy hangs when exporting to pdf

    Hi there,
    We have a few files that are having this issue in that when the InCopy user tries to export to pdf, the program hangs. The InDesign user can export a pdf without issue. The files do not have a known font issue and it's happened on small as well as larger documents. This doesn't happen with all of our files - just a handful... which some are pretty simple so not sure why it's happening...
    Any ideas?

    Dear Jeff,
    Please go through the settings:
    When using the new Function of 'Exporting to PDF'/'PDF Generation' the following two settings need to be applied/checked:
    1.  Path needs to be defined via 'Administration->System
        Initialisation->General Settings->Path->Attachment Folder
    2.  The Windows User needs to have write/modify permission for the folder  defined under 1.
        (To check if the permission is correct, access the folder and check if a new file could be saved)
    In case this does not work please do let us know, does this happen also when you export to word.
    Moreover, is this user or machine specific?
    Regards,
    Gagan Thareja

  • QuickTime Pro For Mac Hangs When Exporting, Small BlankWindow Appears!

    I am trying to export a movie file with the following settings:
    VIDEO:
    Compression: H.264
    Quality: High
    Key Frame rate: 24
    Bitrate: 4000 kbits/sec
    Frame recording: yes
    Encoding mode: multi-pass
    Dimensions: 480x360
    SOUND:
    Format: AAC
    Sample Rate: 44.100 kHz
    Channels: Mono
    Bit rate: 128 kbps
    When I try to export a file, regardless of setting, it hangs up and I must force quit. I get the "Spinning Beach Ball" and nothing is export also no progress window just a blank small window,I'm using QT version 7.4.5 on "Tiger"ver.10.4.11.
    After staying up all night trying to figure out the problem, I gave up and just used an older version of QuickTime ver. 7.2 which worked just fine.
    Thanks for any help with this issue.

    Yes.

  • ICal hangs when exporting a calendar

    When attempting to export a calendar (as a backup), it causes iCal to hang, and I have to Force Quit. The calendar is ~9.5 Megs in size. I have run Disk Utility.
    I am using iCal version 5.0.3.
    The last backup that was successful was on 9/21/2012 (I back up every week). Because I have added events and reminders since then, I don't want to restore that file but would like to see if there is a way ro "fix" the hangup so that I can get a good calendar export.
    Anybody have any suggestions?
    Thanks.

    through additional experimentation, here is what i learned.
    when i created the calendar, i told iphoto i wanted to display american holidays and a calendar from ical.
    If i unselect the show holidays options, my dates import correctly.  with holiday selected i get some dates from ical, but only to the extent they don't over lap with holidays.
    once i noticed this pattern, i went back and forth and sure enough if you have an event from ical on say chirtmas day, it won't be imported into your calendar.
    I didn't seem to matter which order the events were added to the calendar ... holidays first or ical calendar dates first.
    Finally, i created an ical calendar with the holidays i wanted displayed, then in iphoto told it not to include holidays, but to display both ical calendars.  That had the same issue.  on date where you have events on both calendars, only one set of dates will appear in iphoto.
    so to conclude building a calendar in iphoto you can not include dates from mulitple ical calendars without conflict.
    i stopped short of merging calendars in ical, but i guess that's next.
    Not to be too critical here, but that sounds like bug someone at apple might be able to fix.
    Perhaps some of the developers you have building weekly updates to itunes and put them to work cleaning up this kind of mess.
    Hope this helps others with the same problem.
    regards.

  • Help - Premiere CC2014 When exporting it's not using my whole CPU LONG EXPORTS

    Using my recently built computer with:
    250gb SSD samsung (Software)
    2TB HD 7200 rpm (media, export)
    6 core I7 4930K
    Noctua SSO CPU cooler
    Nvidia Geforce 770 4gb GPU
    32 gb of ram
    750 watt power supply
    Asus mobo
    Pretty decent computer. that shouldnt have problems exporting pretty basic videos.
    I am exporting for the web.   .h264 CBR with 12-16 mbps  or similar
    No Max rendering checked.
    using multiple camera files from Sony, Canon, Gopro.
    When it starts exporting a video that is 20 minutes long will take 4 hours to export. Video that is 3 minutes long (right now) is taking 25 minuts to export. That didn't used to be the case.
    I open my Task manager and look at the processor it is only using 1 core at about 10%
    I do have GPU acceleration on but I have switched it on and off and it hasn't made a difference.
    I believe when I exported from my CS5 version it would use the whole processor and hash it out real quick.
    THE BIG QUESTION: IS THERE ANY SETTINGS I NEED TO CHANGE TO OPTIMIZE MY COMPUTERS HARDWARE TO EXPORT THINGS EFFICIENTLY.
    Anyone have this problem and find a solution for it?
    I am new to usin the adobe community and problem solving on forums so let me know if I didn't give you enough information.

    I too have this problem, and it seems to be relatively new. I'm trying to figure out if there's anything I changed, but I can't place it. I've read a few threads with people having this same issue though, so I don't feel like it's anything I've done.
    The only solution I've come across is to do a restart. After restarting, I open AME and just start my queue. It then utilizes all cores. Tomorrow I'm going to attempt to install a previous version of AME and see if the problem goes away.
    This thread mentions a solution: AME CC2014 Very Slow Encoding
    However, I believe this solution does not work. I did as it says, and it only temporarily fixed it, and I think that was due to the restart. Also, my power settings are set to Performance.

  • Package hangs when exporting data to Access DB when running under SQL agent & proxy - works fine under BIDS

    Hi all - - I have searched every nook & cranny to find a similar issue, but the ones I have found have not solved my problem.
    I have a simple package that exports data from a SQL database (2008R2) to several Access databases (Client needs them to be mdb, not accdb).  The whole thing works fine in BIDS, but even though we have created a proxy for the SQL agent, the job runs
    without throwing an error, updates the time stamp on the databases, but does not do anything to them.  I created a log file with both the BIDS version & SQL agent version, and the logs look very similar, except that the BIDS one is about 3 times longer.
     The SQL agent one shows no obvious errors or issues.
    I do have the Access database engine installed on both the server where the SQL agent is running as well as my development environment.
    The job does have the 32 bit runtime option checked as well.
    The DBAs are working on the proxy & permissions, and I am wondering if they have missed something in that arena, or if there is something else I may have missed in settings on the package?
    We have been beating on this for days now, so any help would be greatly appreciated.
    Thanks,
    John

    Hi John,
    Not sure what "but does not do anything to them" means, but I believe once you start running your job with a domain account based proxy it must work (JET uses Admin behind the scenes to actually manipulates on the db that needs to be impersonated).
    Arthur My Blog

  • Premiere CC 2014 Export

    Hi There
    Have found that Premiere CC 2014 is buggy when it comes to exporting. Premiere hangs when sending sequences to Media Encoder and often Media Encoder 2014 crashes while rendering.
    I have to play a game of trial and error when it comes to exporting. I first try sending to Media Encoder and Premiere crashes so export directly from Premiere and sometimes that crashes. 
    On another note I have found that After Effects 2014 aborts render when you switch to another app to do other work. You hear the render complete chime, and the render queue says it is done, but when you check the rendered movie the render did not complete.
    I'll switch back to the previous versions until I can find a solution.
    cheers
    Specs

    Do you have a utility to check your computer temperatures?
    You MAY have a hardware problem, since video editing puts a LOT of stress on all components... below is not exactly the same, but worth reading
    BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • 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 CC 2014 hangs when sending sequences to Media Encoder CC 2014

      Whenever I try to send a sequence from Premiere Pro CC 2014 to Media Encoder CC 2014, Premiere immediately freezes and becomes unresponsive. AME seems to still be running just fine.
    I've tried the following troubleshooting steps:
    – Clearing the media cache.
    – Clearing and moving the scratch disks.
    – Deleting all render previews and re-building them.
    – Completely re-installing all of Adobe's Creative Cloud suite.
    – Importing the at-question PPCC14 project file into a fresh PPCC14 project and importing only the sequence I need to export.
    – Dragging and dropping the at-question Premiere sequence into AME.
    – Opening only AME and trying to drag the entire Premiere project file from Finder.app into AME's render queue. (This happens to work, as a matter of fact, however something strange happens once the sequence is in the AME queue. It pops up just fine, I can change the render settings and file export location, but when I click the green play button at the top right, nothing happens. AME doesn't hang or freeze up or anything, it's just that nothing happens. No prep, no nothing – very strange.)
    – Uninstalling CUDA completely and tried using only OpenCL and software-only rendering engines.
    – Opening the same at-question project on an entirely different computer.
    – Trying to export from PPCC14 itself.
    – Tried opening up an entirely different PPCC14 project and exporting – worked perfectly. So it must be something with this specific project file.
    I eventually got it working (honestly, I'm not even sure what I did – at that point it felt like I was in a zombie state after four hours of troubleshooting and was just repeating troubleshooting steps because I was trying to hit a deadline with this export.) I was able to export it directly from PPCC14 – I was never able to get it to work with AMECC14, however.
    Other miscellaneous noteworthy things: This project I'm trying to export is massive – it's a feature documentary that's about 2 hours in length. It's very complex in its edits, has a mixture of ProRes 422 files and .MTS files, and the entire project is reading media from three separate USB 3.0 hard drives. I know that's not the ideal workflow, but it's been doing just fine until this last time I tried to render out the latest export for our client.
    Thanks in advance for anyone's help.

    I've tried importing into a new blank project, but that did not seem to work. I then tried selecting the sequence in the bin and exporting that as a "Simplified Project" via the File menu. That still does not work when sending the sequence to AMECC14, but it does work when I render straight from PPCC14.
    I have also found that as long as I give it enough time to load up and all that, I seem to be able to export just fine from PPCC14 itself – I'm still getting the freezing/hanging when trying to send to AMECC14 however.
    Thanks for the help so far Cgunningham – I really appreciate it. I'll keep following up here if I find anything else new out.

  • Premiere Pro CC hanging on export media

    Hello,
    I've a project shot on P2 cards with a couple of MP3 audio tracks. Never been a problem before. Went to export media (Queue to Media Encoder) and as it's processing the request the application stops responding.  (also realized at this time the auto-save wasn't so I lost 2hrs work)
    After recreating and saving - same issue - hang on export media
    Updated to Premiere Pro CC 2014 - managed to get to Media Encoder and then it failed with an unspecified H.264 error (I'm trying to save to the H.264 YouTube 720p 29.97 compression) When I tried again, it hung up on the export process as originally happening.
    Trashed preferences (of both versions of PPCC) - tried again - same results
    Removed MP3s and tried again - same results
    Went back to Premiere Pro CC and opened another project shot with a Canon 7D and was able to export media.
    I've done at least ten projects with my Panasonic Camera's and the P2 workflow in Premiere Pro CC and have not had any problems.
    Any suggestions on how to troubleshoot further would be greatly appreciated.
    Mark
    MacPro

    OK, So to be more specific it's hanging when I send it to Media Encoder Queue. I was just able to just do a direct export.
    I found the article on permissions and that was not the issue.
    I've made no changes to hardware and have done three projects with the same codecs, type footage, duration (1 hour range) with no problems.

  • Premiere CS4 - Crashes when Export is selected

    Seems like every time I turn my attention to things other than video, and then return after a while, Premiere has a
    new problem. Like it's angry at me for neglecting it.
    This time it's the export feature. When I click on Export to create a video, the program just hangs up. Adobe Media Encoder does not start. Media Encoder does come up when I start it myself, but not when called from Premiere.
    When I try to click on any place on Premiere during this period, I get an aggravated "beep."  It's almost as if there is a hidden alert box, but I have tried all I can think of to find it, and can't.
    I hope I am not gonna have to uninstall and reinstall. I do have a life.
    If anyone has any thoughts, I'd sure appreciate seeing them
    Thanks.

    Thanks, guys, for all the input. One of the suggestions had to do with having gone from two monitors to one. That is not the case for me. I have been using two monitors for quite some time without problems, and am still using two monitors.
    As I mentioned in my original post, when the lock-up occurs, it acts like it has thrown up an invisible dialog box, awaiting my response.  It dawned on me over the weekend that if the program is doing that, then hitting either Enter or Esc should make a difference. So I tested that theory this morning, and sure enough, if I hit Enter it continues on with the Media Encoder. If I hit Esc, it unlocks the program.
    So obviously there is a dialog box that is somewhere off the screen. As I also mentioned earlier, I squished all the open windows down in case the dialog box was behind one of them, and I never saw it.
    My only concern is, I don't know what question I am answering when I am hitting Enter to continue with the process. Maybe someone can tell me? If it came up before, I don't remember what it was.
    Ten lashes on me for not thinking of that idea sooner.
    Thanks again!
    Bill

Maybe you are looking for