HTML5 Encoder issue with publishing - URGENT

I am running Captivate 8 on a Mac. I have created a course with many .flv files. (These were converted from other formats, then uploaded - I did not try to add then let the Encoder convert them upon upload.)
The course publishes fine to .swf.
When I try to publish HTML5 with scalable content, I get hung opening the Media Encoder.
The message reads "Launching Adobe Media Encoder. Generating MP4."
This screen gets stuck. I have Media Encoder open currently.
I need to get this published for a client ASAP. Anyone have any ideas? Thanks for your help!

In case anyone else has this issue, this type of an error is an indicator that the files have not been properly encoded for Captivate. You will need to open Adobe Media Encoder (even if your file is already an .mp4) and encode it.

Similar Messages

  • Encoding issue with " " Less than sign

    Hello Experts,
       I am working on Receiver Webservice scenario where I am facing issue with "<" less than sign. SAP XI system automatically replace it with "&#60;" sign. I can see the changed value in Audit log of communication channel.
    Web service is not able to accept the data and I can see error message in audit log
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAPEXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 573). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type._
    When I check the payload in audit log I can see the XML structure properly but as I open it in Notepad I can see character code "&#60;" instead of  u201Cless than <u201D symbol.
    Audit log XML file is as given below
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns1:TurnaroundDetail xmlns:ns1="http://isotrak.com/webservices">
      <ns1:sessionid>3f2f2592-39d5-456e-8cf2-5d7ee81402c8</ns1:sessionid>
      <ns1:data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-01T12:01:23.00" To="2011-03-01T12:07:10.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></ns1:data>
      </ns1:TurnaroundDetail>
    When I open it in notepad I can see converted value
    <?xml version='1.0' encoding='utf-8'?>
    <TurnaroundDetail xmlns='http://isotrak.com/webservices'><sessionid>dcc4adcd-ce8f-403d-a1cf-01fcc5aab066</sessionid><data>&#60;Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">&#60;TurnaroundDetail>&#60;PlannedJobDepartureDatesFrom="2011-03-02T08:28:29.00" To="2011-03-02T08:38:09.00"/>&#60;DepotReference DepotReference="EASTLEIGH"/>&#60;DepotReference DepotReference="CHANDLERS"/>&#60;/TurnaroundDetail>&#60;/Request></data></TurnaroundDetail>
    I hope this is not caused due to AnonymizerBean configured in receiver SOAP comm channel.
    anonymizer.acceptNamespaces   http://isotrak.com/webservices ''
    anonymizer.encoding  ISO-8859-1 (also tried utf-8)
    anonymizer.quote  ''
    Could you please suggest if I can get rid of "&#60;" character and get < less than sign? Or it is obvious behaviour by SAP XI system w.r.t Encoding and Receiver end needs to decode this character?
    Note: As per Web service requirement whole XML data to be processed by webservice is populated in single Data field. As here we are populating whole XML data file in one field named data
    Thanks in advance.
    Vinit.

    Simply typing "Test <test> test" into a frame and exporting that yields
    <ParaStyle:Body>Test \<test\> test
    and reading it back into ID gives the expected result.

  • H264 encoding issue with FlashPlayer 11

    Hi,
    When encoding live in h264 with the FP 11  then playing it live on another client (through FMS r) the video sometimes (1/3 of times) has major skips or jerks. It's almost as if the video goes back to some older keyframes and then returns to live. Same experience with non-h264 produces smooth video.
    If the server (FMS ) records the video, the replay looks smooth, which is strange because I would have assumed the FP was not encoding well with H264.
    Has anyone had this issue? please reply
    Thank you.

    Hi,
    When encoding live in H264 with the FP 11  then playing it live on another client (through FMS r) the video sometimes (1/3 of times) has major skips or jerks. It's almost as if the video goes back to some older keyframes and then returns to live. Same experience with non-h264 produces smooth video.
    If the server (FMS ) records the video, the replay looks smooth, which is strange because I would have assumed the FP was not encoding well with H264.
    Has anyone had this issue? please reply
    Thank you.

  • Red Blue issue with published DeskI Report in InfoView

    Hi everyone,
    i'm expieriencing a strange behaviour with my published DeskI Reports.
    I'm using logos in my report and they work just fine... in my full client. As soon as I publish them to InfoView and open them up in the browser, then somehow the color red and blue interchange. Red becomes blue and vice versa...
    My System consists of:
    BOE R 3.1 SP2
    Win Server 2008
    DeskI and WebI
    Has anyone expirienced the same issues?
    Thanks and kr,
    Nils

    Hi Stratos,
    so far everything is just fine. Hope you are doing great too.
    my IE version is: 7.0.5730.13
    Tomcat version: 5.5.20
    If I click on the logos in InfoView, nothing happens.
    I tested 3 different ways to implement them:
    1) via link; pictures shows up, but again with the red blue issue
    2) as an object; pictures shows up; also w/ the red blue issue
    3) inserted a cell, and pasted the picture in it, pictures shows up; also w/ the red blue issue
    The strange thing is, that this issue only appears in the browser.
    Thanks,
    Nils

  • Issue with publishing an application that has been updated (application with multiple versions)

    We are using App-V 5.0 SP1.
    I have a package that will need to get patched whenever new security updates are released.  The first version of the application always works fine, but when I update the application and re-publish it, a normal user is unable to pull down the new version. 
    When this occurs I am able to get everything going by logging into the server with an admin account and performing  a sync (Get-AppvPublishingServer | Sync-AppvPublishingServer; Get-AppvClientApplication").  What is it about applications that
    have been updated that would cause this behavior?
    The issue is similar to what the hotfix below addresses, but since we are on 5.0 SP1 I am unsure if this applies still.
    http://support.microsoft.com/kb/2799153?wa=wsignin1.0
    You publish a Version 1 package of an application on a server
    You log on to the client by using a user account
    You confirm that the Version 1 package of Application Virtualization 5.0 is synched, and then you log off the client.
    You publish a Version 2 package of an application, and then you remove the Version 1 application
    You log on to the client by using a user account.
    The application is not published to the user

    Hello,
    Have you verified the event-logs if the attempt to publish the package is visible there (successful or failed)?
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • Encoding issue with Chinese and Japanese characters but not for Korean

    Hi All,
    I am dealing with the problem below and have tried a lot of options to correct this. Could anyone help me resolve the issue?
    Some japanese text is returned to my jsp from SAP, the text looks like ‚P‚T“ú’÷“–ŒŽ––Œ»‹à .
    When I manually set the encoding of my browser to Shift-JIS, the problem is resolved and the text is seen as &#65297;&#65301;&#26085;&#32224;&#24403;&#26376;&#26411;&#29694;&#37329;
    However, I set my response.setContentType as Shift-JIS, the browser automatically selects the encoding as Shift-JIS, but my characters get displayed as ??????
    I had a similar problem with Korean characters, and I used,
    decodedString = new String(strToBeDecoded.getBytes("iso-8859-1"),"EUC-KR");
    It worked and I did not have to use the setContentType method of servlet response. This code however does not work for either Japanese or Chinese characters.
    Please let me know, if there is anyway of getting the characters right on the screen.
    I am using Sun Java Application Server 8.1.
    Thanks,
    Priya

    Get rid of legacy character encodings and just use UTF-8 all the way.
    Read this to learn more: [http://balusc.blogspot.com/2009/05/unicode-how-to-get-characters-right.html].

  • HTML5 Canvas issue with iOS Safari

    I am trying to build a painting application in HTML5.
    I have an HTML5 Canvas in a div. This div is masked with an SVG file using -webkit-mask.
    On iOS Safari and in iBooks Fixed Layout: When you zoom the page by gesture, the mask suddenly stops working revealing the entire canvas and the contents of the div.
    1. There is no problem if the contents of the div is an image. Problem is only with Canvas inside.
    2. The problem seemed to happen when the zoom crosses a mark - possibly 50%. I.e, if you have already zoomed over 50% and refresh the page, there is no problem until you zoom out below 50% and vice-versa.
    Any help would be greatly appreciated.

    Hello Corey,
    I have been trying to work on this issue, but I haven't made much progress
    Breaking up the project into several small chunks seemed to help for the iPad, but it's not ideal.
    I'm seriously struggling with Android tablets though.  Android doesn't support flash anymore, as HTML5 is the "future". Google Chrome on Android tablets has problems with synchronizing animations and sounds cutting out (works fine on a desktop or notebook).  FireFox on Android didn't have the sync or sound issues, but it crashes at random times. I think the root cause behind all this is HTML5 and the browser.  I couldn't figure out the difference between chrome on desktops and notebooks -vs- tablets.  I went to html5test.com and compared the two browsers, and there is definitely a difference between the two browsers.
    When you look at authoring alternatives to Captivate, it seems like their customers are having similar issues.
    I'm still looking for a workaround.  I'll let you know if I find anything

  • Issue with publish settings: html and swf files

    In Flash CS5.5 when selecting, Publish Settings: html and swf, the html file does not display the swf from the URL after ftp. The swf file, however, does display from the URL without the html file. My work around has been to hand code the html. Is this a known issue or is there something else that might be causing this to occur?

    Here are two examples created by two different students in the same lab using the same software configurations:
    http://www.miszxbrii.byethost13.com/howellanimatic.html
    The first frame of this one displays only.
    http://vaivadesigns.byethost3.com/YoungMidterm/YoungMidterm.html
    Here it is again with a new html page:
    http://vaivadesigns.byethost3.com/YoungMidterm/midterm.html
    The swf path was the documents folder and another folder on the HD.

  • H.264 encoding issues with Premiere Pro CC 2014

    After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
    Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
    Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
    Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
    CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
    CC v7 render: Premiere Pro CC.mp4 - Google Drive
    [Version numbers corrected.]
    Message was edited by: Jim Simon

    Mark Mapes wrote:
    This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
    Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
    Sorry, but thats not completely true and by far not the correct answer:
    The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder. 
    Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
    BTW
    Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
    ... but we can track masks in premiere now ... wow!

  • Latest Update of Adobe Media Encoder Issue with C4D Source

    Updated Media Encoder to Build 8.0.0.173 this AM when the Adobe notification came through and it now refuses to encode any project with C4D source.   The issue is codec agnostic.   Tried with both C4D R15 and R16.  No joy.  Any clue?  Would like to roll back to the previous version but not sure that option is available within the uber-slick CC Adobe world.

    I'm confused. You say that you updated ths morning, but then you give the version number for the previous version (8.0), rather than the current version for AME (8.1).
    I just tried rendering and exporting an After Effects composition containing a .c4d scene file through AME 8.1, and it works fine for me on Windows and Mac OS.

  • Encoding issue with pages serving from Linux Apache to Firefox

    Hi,
    I had a problem last year where my help files displayed as a blank page with a question mark when they were served from a Linux Apache Server to Firefox. All other browsers displayed the content perfectly fine.
    I discovered that the issue had something to do with encoding. From what I understood at the time: RH 8 outputs in UTF-8 but Apache prefers UTF-16 so it tries to modify the page. Net result: Firefox can't interpret the page. I apologise if my description is terrible I never fully got my head around the issue.
    To cut a long story short: I was able to fix this by chaging the encoding information at the top of each page from <?xml version="1.0" encoding="utf-8" ?> to <?xml version="1.0" encoding="utf-16" ?>
    My client has produced a new version of their software this year and for some reason my Help doesn't work again, even with modified encoding information. I am assured that the Apache web server has not changed.
    Does anybody have any suggestion?
    Many thanks,
    Alex

    I think this is what I posted last year.
    This is what I was
    advised by the company hosting my site.
    "I would therefore
    conclude that the solution to this problem (on Linux systems running Apache) is
    to add the AddDefaultCharset utf-8 directive to either the Apache config or the
    site .htaccess file. The advantage of the latter is that it only affects individual
    sites. The default Apache character set is taken from the locale file on Linux
    and defaults to iso-8859-1. It is the conflict between the Apache header with
    iso-8859-1 and the page character set of utf-8 that obviously causes Firefox a
    problem."
    In a forum post
    Chrissy_Tissy added
    My machine is
    Windows, but this fix still worked  -
    some notes about making the fix visible:
    1. Do the fix itself
    (httpd.conf: AddDefaultCharset utf-8).
    2. Restart the box
    to apply the fix.
    3. Once the box is
    restarted, clear your cache in FireFox to make sure you don't continue to see
    the cached file.
    Once all this is
    done you will see the output content as expected.
    There is a tool to change the encoding but that does nothing more than you have already done. Maybe showing your client the above will persuade them to change things at their end.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Adobe Media Encoder - Issue with exporting file

    When I send a file to Adobe Media Encoder and I hit queue I get an error, "could not read from source file, please check if it has been moved or deleted".
    The source file location that the AME is trying to use is C:\Users\User Name\AppData\local\temp\file name.prproj
    Is this file location correct?
    Why is not using my scratch disk file?
    How do I change the file that AME is trying to use?
    I have not been able to export a video since I have purchased Premiere CS4.
    Any help with this would be greatly appreciated.

    If you want a quick work-around do not try exporting from Premiere, just save and exit the project after you are through editing.  Open AME and under File, select Add Premiere Pro Sequence, browse for your project file and click on it once--have patience Adobe's feedback here is lousy--your sequence will finally appear in the Sequence window, click on it and then click on OK.  Select your Format,.Preset and Output location.  If you want to tweak your settings just click on the Settings button.  Then hit Start Queue.
    Do you have the project on an external removable drive?

  • Issues with publishing my iWeb site to .MAC - Progress bar freezes at 100%

    Well, as topic says, i'm having troubles publishing my iWeb site to .MAC now since upgrading to '08. The progress bar reaches full circle, but then nothing. Left it uploading to .Mac for well over 2 hours one time while out of the house...nada. Sometimes i get an error message, sometimes not and have to close iWeb while it's still publishing.
    Any feedback regarding this?
    Thanks in advance.
    /Rich

    Update: After 36 hours, I have successfully managed to upload my entire website via the "Publish All to .Mac" option. I now have blue indicators on the left side of my iWeb program in place of those pesky red ones. How did I do it? Well, I'm not sure. But on my last attempt I looked at the problem from a different perspective, so I took an alternate approach. I had a feeling that I was experiencing a network timeout issue caused by a 3rd party software, so I created a Whitelist entry on my website filtering software that allows unlimited access to "idisk.mac.com";; and "web.mac.com";; domains. I've got two kids at home, so I'm running the free OpenDNS Dashboard service on my network which provides content filtering (blocks adult site, phishing site, etc..). I started using this service two weeks ago. My last website update was a week before that. I figured I had nothing to loose by trying. To my surprise, it worked. Now, it took almost two hours to publish, of which the pie indicator was in the  "filled" position for a nerve racking hour. To reconfirm,  I then made a minor change to one of the pages on my website and re-published. This time using the "Publish to .Mac" option in place of the ALL option and once again it worked. It took less than 5 minutes. Now, I'm not sure if this is a coincidence, maybe Apple fixed the problem, or maybe my website filtering service was causing some type of time out issue all along??  Don't know.. But at least for now, I'm a happy camper since I have my site up.

  • Able to solve Mail encoding issue with a stationery?

    To my knowledge there is no final work around to be sure to send multipart messages (consisting of formated text and attachement) in an encoding which will present the message on an outlook client the way you created it in mail.
    In my special case the attachement is a company logo so that could be integrated in the stationery.
    I tried to overcome the encoding problem by using a stationery manualy created.
    The first time I was able to create a stationery with arial formated text including the company logo. When I sent that stationery with some added text and special characters it was the first time it was displayed correctly on the outlook client.
    As the company font is verdana (not my decision) I made the exact same (so I thought) stationery just with verdana formated text and the same image attachemend embedded in the staionery. This resulted in the Message displayed wrong again on the outlook client the text was shown in Times New Roman. From there on I was not even able to reproduce the Arial Stationery which seemed to work. Any Ideas on what is going on with the encoding?
    Stationery might not be a final solution overall as I will not be able to send addtional attachements not embedded in the stationery but still knowing that it would work might be a step in the right direction.
    Robert

    If I send an email with attachement to an outlook client there is shown the wron font which changes if the encoding used to view is manualy changed on the outlook client after the message is received. Any hints on that?
    I don't know of any way an encoding switch could change the display font. But if you would like to send me an example I'll have a look. You have to go to your Sent folder and find a message where this happened, then do Message > Send Again and put my address (tom at bluesky dot org) in place of the original addressee.

  • Encoding issue with Servets

    I am facing a strange issue to display non-english characters in a servlet. I have an helper class produces non-english characters as below
    public String getContent()
    String content = "કેન્દ્ર સરકારે ચૂંટણી નજીક આવતાં સામાન્ય જનતાને ";
    char[] newch = content.toCharArray();
      byte[] bytes = Charset.forName("UTF-8").encode(CharBuffer.wrap(newch)).array();
      String text1 = new String(bytes);
    System.out.println("Non-english content :"+text1);
    return text1;
    I can see non-english text on console when run standalone but when called from servlet it shows some garbage e.g.
    ArticleLocalProcessor localProcessor = new ArticleLocalProcessor();
      String jsonString = localProcessor.parseNeko();
      resp.setHeader("Content-Type", "text/plain; charset=ISO-8859-1");
      resp.setCharacterEncoding("ISO-8859-1");
      PrintWriter out = resp.getWriter();
    out.println(jsonString);
    Output: કેન્દ્ર સરકારે ચૂંટણી
    Any help

    So perhaps if your characters turn into garbage, you're using the wrong character set then.
    I think the only "problem" here is that you labelled this is strange, don't ever do that because it is a flight response. You need to fight - find the mistake you're making.

Maybe you are looking for