Skip to main content
Inspiring
March 12, 2007
Question

Strange project sizes

  • March 12, 2007
  • 12 replies
  • 3250 views
Hi guys,

I've seen a lot of forum messages about overlarge project sizes and artifact information causing project file size growth. What I've just discovered, however, has me totally confused on this issue.

In an effort to resolve other problems (my autosize caption issue from a previous message), I ended up creating a series of blank projects (as advised in many of the reduce-project-size solutions) in which to copy and paste the slides from my troubled projects (I first tested with one and not only achieved some success with better resizing of my captions but also got a whopping file size reduction from 9,000KB to 3,000KB).

Before I even got to the copy-and-paste stage, however, I noted really strange behaviour with my blank project sizes. At first, I created a project (Step5, and somewhat later Step5_skin for the blank project with the custom skin) ... then since I had a lot of projects to move over, I thought to simply "Save As" the blank project to several names as a shortcut rather than creating each from scratch. I also wanted to apply our custom skin to the blank projects before copying and pasting but I forgot to do so for the first "Save As" I did. The following summarizes the results for each blank project file, including their sizes:

Step5 = 125KB, new blank project with current skin, one default slide

Step5a = 235KB, simply a Save As of Step5, with no additions, no changes to the project whatsoever
(110KB increase due to Save As)

Step5a_skin = 241KB, Save As of Step5a after having added our custom skin to the project
(6KB increase due to either skin or Save As)

Step5a_2 = 240KB, reopened Step5 and did another Save As (just exactly as when creating Step5a)
(5KB more than doing the Save As from the original creation of Step5)

Step5x_skin = 125KB, reopened Step5a_skin and did a Save As without changing anything in the project
(reduction of 116KB!)

Step5xx_skin = 240KB, reopened Step5x_skin and did a Save As without changing anything in the project
(increase of 115KB)

Step5xxx_skin = 240KB, kept newly created Step5xx_skin open without changes and did a Save As
(same size as source .cp but the Step5xx_skin .cp file reduced size to 235KB as soon as this new file was saved from it! Then tried creating yet another Save As from this file and the new one created at 240KB while this one then reduced to 236.)

Does any of this make any sense to anyone out there? Just why am I getting these madly fluctuating file sizes on exactly the same minimal projects???

Gail

    This topic has been closed for replies.

    12 replies

    ChovanskyAuthor
    Inspiring
    March 13, 2007
    OK guys, sarcasm aside (although I must admit the situation certainly lends itself to it ;o), it would be really, REALLY nice if issues such as this were OFFICIALLY acknowledged and either labelled upfront as "Unfortunately unfixable at the moment so don't waste your time trying until we figure it out." or "Here's a workaround to help keep you sane while we figure it out." A time frame of WHEN such problems might be expected to be resolved would also be a nice bonus to an open approach, but we're adults who can accept an honest "I don't know." if such is the case. Many of us using Captivate work in the software industry and understand that things don't always function the way we hoped or expected they would, particularly software we have inherited from others. It would just be useful to be kept reasonably informed!

    Just knowing that a problem really exists, its exact nature, and that somebody somewhere is trying to fix it is not only a balm to the troubled soul (and an explanation for an irate boss) but a huge time saver because I (and apparently many others) wouldn't have spent a ridiculous amount of time trying to figure out what was going wrong and questioning our sanity / working methods / intelligence.

    So if those with the ear of the powers-that-be at Adobe could drop them a hint, it would be much appreciated. I can understand their not wanting to get into an on-going dialogue with us that drains the time they need to fix these problems, but keeping us in the dark is frustrating, annoying, and a waste of OUR time. Let's all play fair please. The customer is not always right but should HAVE some rights, and the top one of those is valid information about the product we've paid for. It is in everyone's best interest, provider and client, not to work in the dark.

    Gail
    Captiv8r
    Legend
    March 13, 2007
    Hi Gail

    I appreciate your taking the time to post. For you and anyone else reading this thread, I cannot stress deeply enough how important it really and truly is to submit a Bug Report via This Link Right Here.

    I say this because those of us that talk to Adobe on a regular basis can tell them about an issue until we are blue in the face. But until they start hearing about it from the masses, it's not likely to be viewed as a serious issue. After all, if they only hear about it from a few of the Community Experts, it could well be that they think we are simply doing something out of the ordinary and seeing the issue.

    Cheers and happy Tuesday all... Rick
    March 14, 2007
    It is good to be able to submit a bug, but I have lost almost a week of development time pasting a completed project into a new blank project one page at a time in order to have a usable product. I am becomming a very angry captivate user.
    Inspiring
    March 13, 2007
    Gail -
    Listen to me carefully - it's not YOU (LOL)!

    What you're seeing is the same, unofficially unacknowledged imaginary problem everyone else is delusional about.

    (Sorry to bear bad news.)

    Just about everyone is as amazed and frustrated as you are.
    RoboWizard
    Inspiring
    March 13, 2007
    HI rbLearning

    I'm not sure what you mean with your comment:
    What you're seeing is the same, unofficially unacknowledged imaginary problem everyone else is delusional about.

    While Adobe hasn't yet acknowledged this publicly as an issue, I'm not sure where you are gathering that it's any sort of problem that anyone is delusional about and claiming doen't exist.

    Cheers... Rick