Hmmmm, I'm honestly surprised that the Captivate plays at all. This is because your screen shot is what I might expect to see if you are adding Word content, not Captivate. You will notice that if you click the Insert tab, that is where you see the Captivate icon. So you normally begin by clicking that icon. Then you point to the index.htm file for Captivate.
What is your RoboHelp output type? WebHelp? Responsive HTML 5? Something else? Whether this will work properly kind of depends on your RoboHelp output type.
Thanks for your response, Rick.
I tried your suggestion, and it didn't work. I think the method of importing Captivate you described is for Captivate demos (see screen shot). However, my Captivate project was created as a responsive project, not a demo. My output for the Robohelp project is responsive HTML5. I think using Document > Adobe Captivate Project is the right way to import the entire project--which, again, plays in the responsive HTML5 output just fine, except for the MP4 video that I inserted in one of the slides.
After some more googling, I found the following article (Crazy about Captivate: Lessons Learned: Video and Resolution in Adobe Captivate) about reducing the resolution for videos that are inserted into Captivate projects. I saved a copy of my video out at the recommeded resolution: 854 x 480 (which is too blurry to be of any use, anyway, because of the size of objects in the video), and discovered that the problem is that the video is buffering (still buffering even at the reduced resolution). I didn't see that it was buffering before, because the play time of the slide on which the video was inserted was only 3 seconds. I increased the slide play time to longer than the video play time, and then I could see that the video is indeed buffering. When I insert the MP4 file into a Robohelp topic, it plays just fine. So I think i'm going to wait until our IT guy can push the latest responsive HTML5 help file output to the server and grab the link to that topic and insert it into the captivate project. Clunky!
Anyway, hope this helps anyone else with the same issue.
Hmmm, sounds like you may have sorted it.
I'm pleased with this post as it taught this ole dog yet one new trick.
Prior to this thread, I was blissfully unaware that RoboHelp offered this ability via the Document Import function. At first, I thought perhaps it was something introduced with RoboHelp 2017 Release. But I just checked and see that it existed in the 2015 Release as well. I presently don't have access to RoboHelp 11, but I plan on seeing if it existed there as well.
So here's the deal on that. It seems that regardless of whether you use the Document Import function or the method I outlined earlier, the end result is that RoboHelp adds files to the project. For the SWF version, you just see the SWF added and for the HTML 5 version you end up with a file in baggage named identical to what you named it during that process but it's all compressed together into a single file bearing a .CPZ file extension. Additionally, a topic is created that is named identical to what you supplied on the dialog.
Sooo, in Captivate, I know that when an external video is added into the mix, it always exists as a separate file that is loaded when needed. Hence your seeing the buffering as the wait progresses for the video to load up.
My initial thought on why you weren't seeing the video was that perhaps you were unaware the video was always a separate object and perhaps the answer would involve adding it to RoboHelp's baggage files area. But it appears perhaps this isn't the case.
So apologies that I was unaware of this ability to import, but I personally learned from this experience, so thanks for that!
Now you did mention something about the slide in Captivate where the video is supposed to play being timed for only three seconds. And in Captivate, when you add a video, there is actually an option where the slide is supposed to remain paused until the video has completed playing. So if you are the Captivate author, were you aware of that option?
Assuming you were and the option is enabled, I'd then have to say there is an issue with Captivate. But if not, perhaps this option is the answer to the issue?
Annnnd after posting that I see you have used a bit of a different import than what I was thinking. Instead of pointing at a Captivate output, you have pointed at a Captivate Project.
Sorry about that. I do believe it still ends up working in a similar fashion to what I explained earlier.
@Rick - RH11 - File > Import > Adobe Captivate Demo & Adobe Captivate Project - yup, both there ;>)
Thanks Jeff! Wondering how I managed to miss that?
No worries! Always appreciate your help. I always know I can count on you and Peter to answer these posts when I'm in a bind. Have a great day!