Captivate 6 crashes when publishing to mp4

I have published all of these files already in the SWF format and would like to publish them in mp4. Each time I attempt to publish in mp4 Captivate crashes and closes with no remark of what error occured. All of my 9 files to publish react the same way (each published to swf and all crashed to mp4). What can I do?
Also I have experienced another problem with the table of contents and publishing to PDF, the PDF will show up as a white screen with no content but the same file in SWF will publish just fine with the table of contents. Why is the table of contents crashing the PDF?
Thanks for your help

I am experiencing the same problem; however i'm on a MAC OSX 10.9.4 running Captivate v6.0.2.325
Steps to reproduce the crash on my system:
1) open the .cptx
2) File, Publish
3) in the Publish window, click Media
3) Select Type: MP4 Video(*.mp4)
4) I select the folder to publish the mp4
5) Select Preset: Custom
6) Check boxed "Copy Preset values and customize"
7) Profile:  Main
8) Level: 41
9) Bitrate Encoding: VBR, 1 Pass
10) Target Bitrate: 2
11) Max Bitrate: 4
12) Advanced Options: Force republish all the slides and Scalable HTML content - ARE NOT CHECKED
I un-installed Captivate and re-installed but still I am having this crash issue every time I try to publish in mp4 format.
Can you please provide any help or assistance here.
Cheers

Similar Messages

  • Adobe Captivate crashes after publishing to mp4

    I have read several of the discussion threads and tried things but it hasn't helped yet. Sometimes the publishing works but MANY times Captivate crashes. Here is the event viewer information of my last crash. I read in one of the threads that this might help someone to figure it out.
    Message 1 (error message)
    Faulting application name: AdobeCaptivate.exe, version: 5.5.0.257, time stamp: 0x4db56069
    Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
    Exception code: 0xc0000374
    Fault offset: 0x000ce6c3
    Faulting process id: 0x1e44
    Faulting application start time: 0x01cdd893843faab3
    Faulting application path: C:\Program Files (x86)\Adobe\Adobe Captivate 5.5\AdobeCaptivate.exe
    Faulting module path: C:\Windows\SysWOW64\ntdll.dll
    Report Id: d967f783-4486-11e2-8328-d0df9aa57a1a
    Message 2 (information message:
    Fault bucket 2811503758, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: AdobeCaptivate.exe
    P2: 5.5.0.257
    P3: 4db56069
    P4: StackHash_5d2b
    P5: 6.1.7601.17725
    P6: 4ec49b8f
    P7: c0000374
    P8: 000ce6c3
    P9:
    P10:
    Attached files:
    C:\Users\Angela\AppData\Local\Temp\WER70CC.tmp.WERInternalMetadata.xml
    These files may be available here:
    C:\Users\Angela\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_AdobeCaptivate. e_2de121f3449f9ee8f829157b6c0b4d78f48bc16_1a428813
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: d967f783-4486-11e2-8328-d0df9aa57a1a
    Report Status: 0

    I am experiencing the same problem; however i'm on a MAC OSX 10.9.4 running Captivate v6.0.2.325
    Steps to reproduce the crash on my system:
    1) open the .cptx
    2) File, Publish
    3) in the Publish window, click Media
    3) Select Type: MP4 Video(*.mp4)
    4) I select the folder to publish the mp4
    5) Select Preset: Custom
    6) Check boxed "Copy Preset values and customize"
    7) Profile:  Main
    8) Level: 41
    9) Bitrate Encoding: VBR, 1 Pass
    10) Target Bitrate: 2
    11) Max Bitrate: 4
    12) Advanced Options: Force republish all the slides and Scalable HTML content - ARE NOT CHECKED
    I un-installed Captivate and re-installed but still I am having this crash issue every time I try to publish in mp4 format.
    Can you please provide any help or assistance here.
    Cheers

  • Captivate 6 crashes when publishing Media - MP4

    It alwas crashes the firs time I try and I have to restart the progrm.
    On the second or thied try it sometimes works.

    I am also experiencing the problem and have tried four times today to publish a file as an mp4.  Is there a way to prevent this?

  • Captivate crashes on publishing HTML5 output with a widget that uses "requires" tag in oam.xml

    Has anyone else run into this problem?
    I have an HTML5 widget that depends on certain (small) image files.
    When I try to wrap those image files in the oam.xml file via the <requires> tag, the widget places on the Captivate stage just fine, but Captivate crashes on publish.
    Remove the <requires> elements (but leave the empty tag) and it publishes just fine, but the images don't make it into the published folder.
    Here is the oam.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <widget name="PBEAWidget" id="com.iastate.widgets.PBEAWidget"
           spec="0.1b" jsClass='PBEAWidget' sandbox='true' width='180' height='30'
           xmlns="http://openajax.org/metadata">
        <!-- Required tag specifies any external depencies your widget might have such as images, jQuery etc, see http://helpx.adobe.com/captivate/using/create-wdgt-files.html -->
      <requires>
      <require type="folder" src="assets/images"/>
      </requires>
        <!-- Main widget JS file -->
        <javascript src="js/PBEAWidget.js"/>
        <!-- Properties tag currently not supported -->
        <properties />
        <content type='fragment'>
        <![CDATA[
      <div id="ConnectionDiv" style="display: inline-block; padding: 4px; vertical-align: center">
      <img src="images/lights-02.png" id="statusLight" width="16" height="16" alt="Connection Status" style="position: absolute: left: 0; top: 0; margin-bottom: 2px; cursor: pointer"/>
      </div>
      <div id="FeedbackDiv" style="display: inline-block; padding: 2px 6px 0px 6px; height: 28px; border: solid 1px #fff; border-radius: 6px">
      <img src="images/icons_01.png" id="createFeedback" width="24" height="24" alt="Write Feedback" style="cursor: pointer"/>
      <img src="images/icons_02.png" id="finishFeedback" width="24" height="24" alt="Submit Feedback" style="cursor: pointer" />
      </div>
      <div id="PrintDiv" style="display: inline-block; padding: 3px 6px 0px 6px">
      <img src="images/icons_03.png" id="printCourse" width="24" height="24" alt="Print Course" style="cursor: pointer" />
      </div>
      </div>
      ]]>
        </content>
    </widget>

    Hi
    Can you please forward the file, or share it in a shared location, so that we can look into the issue?\
    Thanks,
    Mohana

  • Captivate Crashing when editing video demo

    I have been having a lot of issues with Captivate crashing when I'm editing video demos. When I try to save, the save progress bar will get to 'thumbnails' and then freeze up. I have to close and restart the project and lose all information that has not been saved. I try to save after every thing just to be sure, but this is still very frustrating.
    Does anyone else have issues with this?
    The videos I'm working with are about 6 minutes long. I've trimmed a lot of information out in an attempt to make it a shorter video. It seems that after so many 'trims', Captivate doesn't function very well. I'm assuming a work around would be to just make shorter videos, however, if anyone else has an issue such as this I was wondering what your work around was.
    Thanks

    You left out one important number: how much free space left on your hard drive?

  • Captivate 8 crashes when publish "near CD quality" audio

    When publishing a project using "Near CD quality" in the size/quality settings, Captivate 8 crashes midway through the publishing process.  I can split the project in 2 parts and it will publish successfully.  I am running Captivate as an administrator.  My system:  Intel Core i7-4700MQ CPU @ 2.40GHz, 8 GB DDRS RAM, GeForce GT755M, Samsung SSD 840 EVO 250GB (125GB available)

    It appears, looking through the crash log, that this particular project/file has become corrupted so...
    I would suggest you use the Selective Track Import feature in Logic and see how much of it you can rescue...
    See....
    http://www.apple.com/logicpro/how-to/#logicpro-transfer
    and
    http://documentation.apple.com/en/logicpro/usermanual/index.html#chapter=7%26sec tion=6%26tasks=true
    ...for more info...

  • Flash 8 crashes when publishing (Mac 10.3.9)

    I've searched the forums and haven't found an instance that
    is relevant enough to my situation.
    Pretty basic, really. I have a registered version of Flash
    and I go to publish. Not doing anything crazy with the publish
    settings. The document I'm working on isn't immense or overly
    complex, either.
    It gets about 1/3 or 1/2 through publishing it, then crashes
    (i.e., "The application Flash has unexpectedly quit.").
    This is part of the message that my OS sends to Apple...
    "Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_INVALID_ADDRESS (0x0001) at 0x0e8e8d9e"
    What's all that about?
    From what I've read, Flash is a bit buggy (hit & miss)
    with this whole crashing thing.
    Anybody have any links or idears on how to get this fixed (or
    at least working better/more reliably)?
    I've repaired permissions, run Onyx (i.e., deleted system
    cache, etc. etc.), restarted, updated, repaired permissions,
    restarted. . .
    In a pickle...
    Can some kind soul help me out? I hate pickles...
    Thanks,
    -j

    Well, I talked to Adobe support last night for about an hour
    and this is the scoop. Evidently, I was only having problems with
    one of my documents. I was able to successfully publish a different
    document. I was also able to save it, too. This document, however,
    was much simpler than the one I was having problems with.
    In my troublesome document, I had imported some .swf
    animations that I had exported from ImageReady. I didn't realize
    that Flash creates a .swf library symbol,
    and two library instances of
    each frame (a bitmap and a movieclip symbol).
    I realized that I had many, many duplicates and duplicates of
    duplicates. My document had become ridiculously huge (~227MB). I
    deleted all those instances, re-imported the .swf file and got my
    file size down to about 77MB. I was now able to save my document,
    but I still couldn't publish it.
    So, the support guy told me to go into "Publish Settings",
    click on the "Formats" tab and deselect "HTML". Click the publish
    button at the bottom of the dialogue window and presto! It
    published (albeit without the HTML file).
    That's about where it ended. The support guy couldn't figure
    out why this document was crashing Flash when trying to publish
    both the .swf
    and .html files. He recommended a work-around of creating
    the HTML file in Dreamweaver. I had already been hand-coding the
    html file as a work-around, so that's where we left it.
    So, this is what I learned:
    1. Repair permissions, run Onyx & clear your system cache
    (don't have Onyx for 10.3.x? You can download the
    zip
    file. You need admin access. Be careful with it, you can screw
    up your computer. Be conservative with the settings. Use at your
    own risk).
    if this doesn't solve it, then:
    2. Make sure you're up-to-date on your system software, Flash
    software, and Flash player. Repair permissions again after updating
    any software.
    if this doesn't solve it, then:
    3. Go to Users > username > Library > Application
    Support > Macromedia and rename the Flash 8 folder as "Flash 8
    old". Flash will create a new folder when you load it (it's an app
    preference folder). You may delete "Flash 8 old" if this solution
    doesn't end up really screwing things up (or you can delete it if
    it fixes your problem). If this solution does end up creating
    problems (or if you had certain settings you just can't lose),
    delete the new "Flash 8" folder and rename "Flash 8 old" to "Flash
    8".
    If it still doesn't work, re-evaluate your .fla:
    4. Limit the size and complexity of your .fla (delete
    superfuous library instances)
    5. Library instances can become corrupt, leading to a crash
    (delete suspect ones, re-create them)
    6. Fonts can become corrupt, leading to a crash (validate
    your fonts)
    7. Importing .swf files into your .fla file is iffy, due to
    different compression(?) settings. This could be the culprit in my
    circumstance. I may try doing a loadmovie deal on it at some
    point... when I figure out where/when it could be loaded in the
    background.
    7. Publish your .fla without the .html document.
    If all else fails and your Flash app just ain't workin', here
    are instructions for uninstalling the studio (and it appears,
    individual applications):
    Studio TechNote
    8f101099
    Hope this helps!
    Keywords: Flash crashes when I try to publish crash crashes
    crashing keeps crashing keep crashing Flash crashes on publish
    Flash stalls-out when saving stalled stalling

  • Flash CS6 crashes when publishing fla`s with big libraries

    Hi guys,
    I am currently working with Flash CS6 and i noted that the bigger the libraries in my fla`s get the more likely flash will crash when i try to publish these fla`s. It already has gotten to a point where all the crashes, and then trying again to publish, has taken up a considerable amount of my time. But the thing is the publishing does not alway result in a crash, its more like 80% of the time it crashes. Also what i do once a file has crashed, i open it again and then just open and close some folders in the library, then safe and then try to publish again. After doing this 4 - 5 times publishing suddenly works again, but also just 4 - 5 times until it crashes again and i have to do it all over again.
    So again, this only seems to happen with fla`s with big libraries. Is ther something i can do about this?

    It's been my experience that Flash doesn't much like a few things in particular. One is large vector files with a lot of points; in other words stuff brought in from Illustrator or trace bitmapped from within the program so you might try reducing the amount of points in your art if you'r working with imported art. Flash seems to work best when all art has been created within the program. If you've converted it to vector via the Trace Bitmap or Illustrator's Live Trace it doesn't like that either. It also tends to bog down with high resolution bitmaps, especially with many layers (which greatly add to the file size) so you might try to flatten some of the art to make it more managable. In general, maybe see if you can reduce whatever file sizes you can in your project before you import them. I typically have some pretty big libraries and Flash doesn't crash so much for me so changing your workflow a bit might be useful. IF it's code that's crashing the render, that I can't help you with, but there's some pretty knowledgable people on this board who might be able to help in that regard.

  • Captivate Crashes When Loading Project

    Hi:
    Have ver 1.01 of Captivate and using Windows XP
    History ... My computer crashed and I have the hard drive
    from the crashed computer in a hard drive enclosure and connected
    to my new computer.
    Captivate is on drive g: and so are my cp files ... I can
    open the Captivate sample file but when I try and open the cp files
    I created Captivate closes when I try and load a project.
    Anyone got any ideas .... have read about shortening path
    names and the problems of using a LAN with Captivate. What is
    confusing is that the Captivate Sample cp file opens but my files
    that are in the same directory do not open.
    All worked fine before the crash of my computer and the
    addition of the hard drive enclosure. Thinking my best option would
    be to download Captivate to my new computer and move my cp files
    there.
    Apprecitate any assistance.
    Cheers
    Doug

    Problem solved ... downloaded Captivate ver 1.1 to my new
    computer and all works ... Cheers, d

  • Captivate 6 - When publish, image backgrounds are black and open text entry is neon green

    The files are fine when in Adobe Captivate, and they publish well. However, upon playing back the published file, all the images are black. The text entry field becomes neon green.
    See attached images for "before" (in Captivate) and what it looks like "after" (upon publishing and then playing back that file).
    Thanks for any help you can provide.

    Hi there,
    Can you please confirm the complete version of Captivate (Help > about Adobe Captivate).
    Also please change the quality of slide to optimized or 24 bit, and do this for every slide.
    Go to edit > preferences > SWF size and quality > uncheck Advanced Project Compression and Compress SWF file.
    Then at the time of publishing check 'force re publish all slides'
    Thanks.

  • Captivate Crashes when Changing Existing Projects

    Hi
    I've created 9 Captivate Projects using Captivate 4.  I'm now going back to change some of them.  With 4 of them, every time I duplicate a slide or add new recorded slides, Captivate crashes.  I don't have time to recreate them from scratch.
    The files range in size from 7.5 mb to 9.5 mb.
    I'm using VM Ware to connect from a virtual Wyse terminal to a virtual PC.  Captivate is installed on the virtual PC.
    Any suggestions would be gratefully received.
    Cheers
    Kathy

    That's a pretty complex setup for Captivate, especially considering how dependant it seems to be on local video card support. Your going through a lot of virtualization layers that - I'm surprised CP opens for you at all! ;-)
    Is this the same setup you had when originally authoring?
    There's no way you can try to edit directly on a 'real' PC?
    If not, you could try copying all slides in the CP project file, then pasting them into a new, blank CP file (or, alternatively, create a new, blank CP file and do an import on the current CP file). Sometimes that process helps resolve corruption or other 'bad pointer' issues...
    HTH
    Erik

  • Flash Professional cc 2014 crashing when publishing

    Updated from Flash Pro cc to 2014 version and Flash Pro now crashes when I try to publish to Android format. Worked in previous versions, this does this on all my Macs.

    Hi,
    Can you please send us the crash dump and also verify if it is happening with all the contents or is it specific to some content..If it is specific to publishing of a particular content, can you please provide us the content and exact steps for repro.
    Thanks,
    Sangeeta

  • Error message - Captivate has stopped working - when publishing to MP4

    I get and error message that Captivate has stopped working when I try to publish to an MP4. I am using Captivate 6. How do I solve this problem?

    Hi Shivers,
    What is the Exact version of Captivate you are using (Go to Help > About Adobe Captivate) ?
    Please try to clear the cache of Captivate ( Go to Edit > Prefrences > General Settings)
    See Screenshot
    Please clear cache from computer as well..
       Go to Start>Run>Type %temp% and then click on ok
    Delete all the files from that folder(Some of the files which are in used will not get deleted , Ignore them)
    Then try to Run as Admin and check if this works
    Thanks and Regards
    Himanshu Satija

  • RoboHelp 9 Crashes When Publishing From Framemaker 10

    Hello,
    I am attempting to publish my Framemaker 10 doc in Robohelp 9.  When I click publish, RoboHelp launches, and then quickly crashes while it says it's "loading components".
    Both products are part of the TechComm Suite.
    Anyway, it doesn't matter if I choose HTML Help, Adobe Air, WebHelp, for Flashhelp...this problem surfaces in exactly the same way.
    The installation and output folders are all located on my local machine.
    I can go to my Robohelp project and import my FM Book and get it to generate from there, but the problem with this approach is that it imports all of the xref references with each TOC entry, so this is unusable and impractical to edit by hand.
    Is there an error log saved somewhere, so I can get more details on when exactly the application is crashing?

    Not sure what you mean if you go into RH and import it – that’s basically what publishing is doing in FM. Have you set up a project and saved off the setting in the .isf file first? I believe you need to do that before the publish option really works.

  • Flash CS4 crashes when publishing big SWF that previously were working fine

    Hi all,
    This is driving me crazy, I tried looking into Adobe FAQs and other places inside this site but cant find a good solution to this, in fact I found people asking the same issue. The fact is Im making a game that after being published is 7Mb SWF, this was working great and in fact I havent made any critical change there, only updated a text field with a typo (no code), then when I tried to publish it crashed (other big games I made are making Flash crash too), and crashes the same when hitting CTRL+ENTER or just selecting File>>Publish or File>>Publish settings>>Publish, I reinstalled the whole CS4 6 or 7 times and even got a tool from here to uninstall the player (I thought it uninstalled the player used from IDE but its apparently the browser plugin) asuming the issue could be there but still keeps crashing after I re-install it, oddly small FLA files can be published, I looked into CS5 faqs and I have seen they can set the cache size there but I cant find in CS4, and Im unsure if is due to that but just my guess after all I read about this, could someone help me please? Thanks a lot beforehand, I have been fighting this for 4 days almost sleepless
    Im only using as2 code in these projects I meantioned, and I have Windows Vista on this machine, just if this helps to solve it, again, thanks for any clue
    Edit: Im unsure if this is the right section or not, please receive my apologies if its wrong place as maybe this is intended for only code doubts but I couldnt find the right section to ask it so please move it to the appropiate place when you can and Im sorry for the trouble

    Well my friend, you saved me here =), that final advice you gave was the solution, I followed the steps, deleted the registry keys and deleted the folders with the preferences, then I reinstalled over the damaged Flash Pro version and it worked again!!, I even managed to recover my workspace with the folder I saved before, dont know why I never got a dialog to reset preferences in the middle of this process as you mentioned and as is said in the article, but the important is that it worked, and finally the Flash Pro is able to publish the mentioned as2 projects, takes a bit of time to publish but it was never too fast with bigger projects.
    I owe you one, I would like to include a link to your site in the game as a way to thank you for this, but if you feel its wrong or you prefer any other way to show how much I thank you for this please let me know
    The link I would like to add can be seen here in the game tittle screen and "About" section
    http://mordaza.eu5.org/School%20Memories.swf

Maybe you are looking for