Skip to main content
Known Participant
April 17, 2009
Question

Bloated files - found - a painful improvised solution

  • April 17, 2009
  • 1 reply
  • 1310 views

Having followed several items in the forum concerning project files sizes bloating (within Captivate 4) I've tried a few experiments and the results may be helpful to others.

Test 1): A file of one slide (yes, one) that had magically grown from a few kilobytes to 55Mb - the slide was the review slide that is automatically built in by Captivate if you select the review option in a quiz. The only change I had made to the (native) slide was to put a small white rectangle onto the slide. So why 55Mb? My only clue was that I had extracted it from a slide set of 200 slides (yes, big) that had an all up size of 175Mb.

So I created a one slide set (blank slide) of the same screen resolution and imported the review page.

I saved the project under a new name.

Rushed to the file directory and the new file size? 377Kb. A cool reduction of 54.5Mb!

Test 2😞 A file of 20 slides containing video and audio. Carefully purged of unused library items. File size 82Mb.

Repeated the process as per test 1.

New file size? 3.5Mb - and this is reasonable considering that it has an audio stream.

Captivate 4 clearly has a problem that needs urgent attention, this is the worst case of bloating I have ever come across. It's as if the entire history of the project is being added into the project (library?) on every single project change thus topsy gets bigger and bigger.

Remedy whilst Adobe gets its act together and fixes the product, tentatively, seems to be:

Divide up the bloated project into 20 slide sets (assuming a large project) - I've learnt the hard way that it has problems importing slides/objects from anything bigger (crashes routinely where slide set is more than 25 slides).

Then create a one slide project (same dimensions etc.) and import the 20 slide sections into the one slide project a few slides at a time, I bring in the first five, then the second, then the third etc. until all the 20 are imported.

Next save the new project under a new name. Call this S1

Repeat until all the twenty slide sets have been imported into their new projects. S1, S2, S3 ...

Now create a final new one slide project. Call this P1.

Import the sets S1, S2, S3 ... etc into P1 - they will now import (because their size has shrunk).

Finally save P1 under a new name say, P1Complete.

Completed project has shrunk about 80% in size and is manageable even though it has many slides.

Huge apologies if this has been covered before but I couldn't quickly find an answer to Captivate 4 bloating across the threads, and it was impacting a very important project here.

Regards,

Henry

This topic has been closed for replies.

1 reply

KerryWilson
Inspiring
April 21, 2009

I suppose you could also just daisy chain your 20 slide projects (S1, S2, S3 etc) instead of making one big project (P1).

Just in case you need to do some further manipulations and the dreaded file bloat happens again.

And here I was thinking that Cap 4 was supposed to fix the file bloat problem.

I might stick with Cap 3 a while longer... at least I know how to make it do everything I want.

mindgroveAuthor
Known Participant
April 21, 2009

Hi Kerry,

We would normally daisy chain projects because many of our projects have a natural structure like Chapters within Books. But unfortunately our multi-slide productions are typically software capture and two or three minutes of capture of a screen can easily generate 50-60 slides.

I like Captivate 4, potentially, because we use a lot of Adobe CS4 products and they integrate nicely. But I have to say that Cap 4 is very buggy.

We've had bloated files (today we reduced one one-slide production from 75Mb (yes!) to 340Kb. I think the resources library eats up anything and never discards it - I'm highly suspicious of the garbage clearance routines. In fact when clearing out unused items the file size rarely shrinks.

The program isn't very object-oriented and links don't get updated unless you exit a slide then come back again. The classic example of this would be to choose an image for a button, then edit the image, then call up the button again from the resource library. Guess what? Yup, old button still showing.

The audio editing via the timeline is woefully buggy and if you mess with the timeline play-head you get rewarded with a white out.

You can't import slides from other Cap 4 projects if they are over about 20Mb (the project not the slide) because cap 4 crashes.

And you need a hell of a lot of horsepower to do anything in real time.

I hope it gets better, it has a lot of potential but I haven't come across anything quite so stressful in recent times.

Best regards,

Henry

KerryWilson
Inspiring
April 21, 2009

Unless you have already done so, you should copy and paste your reply into the Adobe wishlist/bug report form.

Press here for the link

The more of us that give the Captivate dev team feedback, the more likely they will fix up Captivate and give us the powerful tool we really want.