Image Integrity

quote:

---

Originally posted by: Rebecca Knapp
Hi,
Just a little niggle I wondered if anyone had come across or knows how to resolve. When I record a software application, the screens appear to record correctly. During playback, there are a few odd behaviours where the top lines of text boxes are missing, or they almost 'ghost' on other slides (i.e. slide 1 has a grid on, slide 2 should have no grid, but some of the grid lines are displayed on slide 2 anyway).
It's not a major issue, it's just a niggle that if i can resolve it would make my project look better. I'm currently in a project that has substantially more slides than best practices suggest, so I wondered whether this would have anything to do with the issue? I will split my project this week into several small projects, just thought i'd mention this see if the two were linked.
Many thanks
Becky.

---

I've recently encountered a similar problem. Whereby, the files inside captivate look fine, its when it spins out to preview or publish that there are error's in the background images in effect. The way I got around this was to go into the Preferences, and unchecked the "Advanced Compression" Option. That seemed to clear that up, as I'm running an Nvidia Quadro NVS 290 256 MB Graphics card, with an Intel Core 2 Duo E6750 with 3.48 GB of RAM (not sure why the ram shows up as that number), but unchecking that seemed to solve the problem for me, as I only had captivate open when doing these tests.

If you still see no improvement followint the other suggestions, try
updating your graphic card drivers.

Steve


--
Adobe Community Expert: eLearning, Mobile and Devices
My blog - http://stevehoward.blogspot.com/

I apologize for the multiple posts. I got a server time-out and hit F5 a few times too many.

Display issues are sometimes related to the fact that in auto-capture mode, Captivate takes a screenshot as soon as you complete an action, like click a button or hit Enter.

If the application (or possibly just your video card) is slow, Captivate sometimes takes the picture before the application has finished redrawing. I get bits of the old screen mixed with bits of the new. Others have reported the same behavior.

I work primarily in a slow-ish client-server app so I see the issue quite often. I've resigned myself to hitting Print Screen to take a manual capture after every major screen change, then deleting any duplicate slides and library images in Captivate once the capture is complete.

It's a bit of a pain, but I prefer to leave auto capture turned on as a safety net in case I forget to do a manual screenshot. Better to have too many screenshots than too few.

It only takes a few minutes to delete the extra slides, clean out the unused items in the library and do a Save As twice to purge those items from the file. Much preferred to finding that I missed something and have to reset my scenarios and start over again or muck about in Photoshop to recreate missing data.

Thanks for that. I think i was being a bit blinkered and not looking what else was running, and same as your machine, SQL is running at 213,000K and Outlook 210,000K....that may explain things then.
I'll give it a go again with less things running at once.

Many thanks

Becky,
I've noticed that if I have a lot of other programs open when I am creating my Captivate presentations that the quality of the video can be diminished. I don't think that it has to do with Captivate, but rather the graphics card on my machine and how much memory is being used by other applications.

I use Powerpoint as the basis for many of my Captivate projects and if I have a lot of programs running, Powerpoint doesn't display things correctly.

Make sure to check that you don't have memory hogs running in the background. In my case, SQL Server was starting up when I started my machine. There wasn't anything to indicate that it was running, but it was using quite a bit of resource.

If you do an ALT-CTRL-DELETE, look in the task manager under processes and click on the Mem Usage column, you will see what applications are using to most memory, even if they are running in the background.