Captivate 2017 Video demo Trim and “Offset timing”

Hello! I’m pretty new to Captivate and brand new to Video Demo. I’m using it to create training videos for an iOS app.

Hope the Community can help. Thanks in advance.

Here’s the weirdness: I work on a particular segment of the video: I add the iOS gesture and then I back up a bit to add a callout with instruction such as “Tap X”; then, I might back up a bit more and enter a text caption explaining to the learner what she’s about to do or to mention important screen elements. I do this for a series of steps…and then I move closer to the start of the video to find the next screen change — and more or less repeat the steps. I’ve been working backwards in the video because I have already experienced trimming out a segment of video — only to have all the “later” objects lose their timing on the video stream. And it’s not as simple as removing 30 sec of video — and all the objects are “out” by 30 seconds. It’s so random I can’t figure out the pattern. I’ve also had a scenario where I did the previous, aligning the objects to display when a certain screen appears on the video…and then trimming out earlier video — and then discovering that the objects I just created/added/ timed now don’t have the right screen image behind them — and sometimes that screen image is gone — lost when I trimmed.

If someone would explain how video “Offset timing” works, that too, would be helpful. I’ve taken to locking the video track while working on tracks, but if I’m going to trim I’m pretty certain I need to remove that lock. I don’t know if my timing issues are due to some position offset that I’ve caused inadvertently and not noticed.

Hope you can help. I’ve spent hours on minutes of video…and then had that weird situation where I no longer had the right background image behind my objects…

The post Captivate 2017 Video demo Trim and “Offset timing” appeared first on eLearning.

Responsive eLearning with Captivate 2017 – Part 12: Enabling gestures

In this Part 12 of 14-part blog series, we will talk about enabling gestures for your responsive eLearning courses. So far we’ve learned how to create a responsive project, rescale it, add Fluid Boxes to the slides, add objects to the Fluid Boxes, apply background fill, modify the properties of the Fluid Boxes, use the static and optional properties, best practices for adding text, using Fluid Boxes in master slides, and recording responsive simulations in Adobe Captivate 2017.

One of the things that characterise the mobile experience (versus the desktop/laptop experience) is the touch screen. Owners of mobile devices use their fingers to interact with their devices by performing various gestures like swipes, taps, double-taps, pinches, and so on. The Mobile Palette feature in Captivate gives you the ability to leverage the power of those mobile gestures in your projects.

The Gestures option is not limited to the Responsive Projects only. You can use Gestures in any standard project as well, but they will function only if you publish the project in HTML5 format.

Watch this video to learn how to enable gestures for responsive and HTML5 courses:

In the next part, we will learn how to convert non-responsive projects to responsive in Adobe Captivate 2017.

Happy captivating! 			</div><!-- .entry-content -->
	    
	<footer class=

Responsive eLearning with Captivate 2017 – Part 11: Recording responsive simulation

We are almost at the end of this blog post series. So far we’ve learned how to create a responsive project, rescale it, add Fluid Boxes to the slides, add objects to the Fluid Boxes, apply background fill, modify the properties of the Fluid Boxes, use the static and optional properties, best practices for adding text, and using Fluid Boxes in master slides. Now let’s learn how to record responsive simulations in Adobe Captivate 2017.

The steps to record a responsive simulation are the same as a normal simulation. The only difference is that you cannot start the workflow from creating a simulation directly. You will first need to create a responsive project and then add simulation slides to it.

Watch this video to learn about the steps to record and edit responsive software simulations:

In the next part, we will learn how to enable gestures for responsive and HTML5 courses in Adobe Captivate.

Happy captivating! 			</div><!-- .entry-content -->
	    
	<footer class=

Responsive eLearning with Captivate 2017 – Part 10: Using Fluid Boxes with master slides

In this 14-part blog series, so far we’ve learned how to create a responsive project, rescale it, add Fluid Boxes to the slides, add objects to the Fluid Boxes, apply background fill, modify the properties of the Fluid Boxes, use the static and optional properties, and best practices for adding text in responsive projects. Now let’s learn how to use Fluid Boxes in master slides. Also learn how they are different from Fluid Boxes added to the Filmstrip slides.

When you apply a Master Slide to a slide in the project, it inherits the Fluid Boxes from the master slide.

Fluid Boxes on master slides work almost the same as the Fluid Boxes on filmstrip slides. Here are a few differences:

  • You cannot name the Fluid Boxes on Master Slides.
  • When a slide is associated with a Master Slide, the Fluid Boxes from the Master Slide are inherited by the slide.
  • These inherited Fluid Boxes cannot be deleted, but they can be resized.
  • Along with these inherited Fluid Boxes on the slide, new Fluid Boxes can be added and subsequently deleted on the slide.
  • Question slides in Captivate projects also inherit the Fluid Boxes from the associated master slide. And the same differences will apply to the Fluid Boxes inherited from the Master Slides on the question slides.

Watch this video to learn more about Fluid Boxes in master slides:

In the next part, we will learn how to record responsive simulations in Adobe Captivate 2017.

Happy captivating! 			</div><!-- .entry-content -->
	    
	<footer class=

FREE WEBINAR – Working with Image in Adobe Captivate

DATE: Wed 29th August 2018

TIME: 12.00pm AEST

REGISTER NOW: https://adobe.ly/2MRe4Ji

So we know how to insert an image, but what about all the other fun and time-saving things we can do with images in Adobe Captivate . . ?

What about using animated GIFs? Or working with images in responsive projects? Do images behave differently when designing a responsive project?

Those are great questions and we’re glad you asked!

In this webinar, we’ll examine image behaviours, tips and workarounds. We’ll also look at the inbuilt Adobe Captivate editing functionality.

Not only will we delve into editing images from within Adobe Captivate, but we’ll explore using an outside image editing program, like Photoshop, or even MS Paint (I know there are fans out there..) and importing back into Adobe Captivate.

Don’t know how to insert an image at all? You’ll learn that too!

We hope you can join our webinar @12pm (AEST) Wednesday 29th of August.

REGISTER NOW: https://adobe.ly/2MRe4Ji

The post FREE WEBINAR – Working with Image in Adobe Captivate appeared first on eLearning.

First Impressions: Creating Responsive Content in Adobe Captivate 2017

If you design or develop eLearning content, you’ve likely run into issues displaying content on multiple devices, such as desktop computers, tablets and smartphones. For example, a really nice graphic may display well on a laptop, but look too small or be cut off on a smartphone.

Authoring packages that generate “responsive” content have solved the issue of displaying on different devices by allowing the content to rearrange itself based on the type of device. The advantage is that you create content once and it displays well on all devices.  Adobe Captivate 2017 is one such package, allowing you to create responsive content through Break points and Fluid Boxes.

Break Points

Captivate’s first method of creating responsive content is through the use of Break Points. In short, Break Points are views within the Captivate interface that show how your content will appear on different devices. What’s more, you can adjust the content within each view, such as changing the size or position of text and images. Captivate stores this information for future reference.

When you publish your project, Captivate includes the layout for each of the Break Points. This comes in handy when someone tries to view your content using different devices. Captivate will detect the type of device and present the content according to your Break Point format. For example, the text and graphics will display on the users phone according to your Break Point format for a smartphone.

Fluid Boxes

The second method Captivate uses to create responsive content involves the use of Fluid Boxes. This method differs from Break Points in that instead of formatting your text and graphics for a number of individual views, you enter content into one view that contains “Fluid Boxes”. These Fluid Boxes, in turn, resize and adjust themselves to the screen size of whatever device displays the content in a “fluid” manner.

Fluid Boxes are organized much like a spread sheet where you have a grid of cells, with each cell allowing formatting of its contents, such as the font size. However, with fluid boxes, you can specify how the cells and content react when the screen size of the display device changes. For example, you can set the properties of the Fluid Boxes so they adjust the content size or reorganize it by wrapping.

Comparison

Based on my initial experience, both Break Points and Fluid Boxes produce responsive content that will get the job done. However, each method has its own unique advantages and disadvantages.

Break Points provide a greater deal of control on how your content will display on different devices, allowing you to set specific font sizes, graphic sizes and their relative positions. However, the downside is that your content is optimized for only 5 display sizes. If your are delivering content through a variety of different smartphones and tablets, you could run into some problems.

Fluid Boxes, in contrast, will adjust to any device based on screen size. However, you give up some flexibility in specifying how the content will be displayed. Simple designs, that allowing wrapping of content, seem to work best.

Conclusion

Both Break Points and Fluid Boxes are powerful features that will allow you create responsive content for end users. Which method works best will likely depend on your design style and the number of different display devices your end user have. If you are into control, and can standardize delivery devices, Break Points will likely work better. If you are delivering to a large variety of devices, and don’t mind simplifying your designs, Fluid Boxes will likely work better.

I look forward to exploring the responsive features in Captivate 2017. Good luck with your own eLearning efforts.

The post First Impressions: Creating Responsive Content in Adobe Captivate 2017 appeared first on eLearning.