Filesize [again]

Question

I am posting this again. Besides the fact that it took me
bloody ages to write the first time, I thought it would concern
more than a few users. Maybe there's just not enough people using
it yet?
It is in response to David's article at
http://www.adobe.com/devnet/captivate/articles/filesize.html.
I'm just after a little more information than what he gave. If
anyone think I should, or want to themselves point David to this
post, please let me know. Truth is he probably doesn;t have time,
but it would make quite a comprehensive list of answers for us
beginners:
1. Minimize file size by reducing the recording area in
Captivate:
Sure, but what is the relationship between recording area and
file size? I know there's a relationship between total number of
pixels x bytes per pixel, but there must be more to it than that.
2. Reduce the amount of background noise;
OK - easily done.
3. Reduce the color gradients in your recording area:
How much does this really affect the final size? Is it closer
to .05% reduction or 50% reduction? I can see how this may be
appropriate for simple slideshows, but what if the animations are
graphically intensive, do the color gradients really matter then?
Is this point outdated with the increasing complexity of
animations?
4. When recording in "Full Motion" format, Captivate converts
the recording from AVI format to static screen shots. This
increases the overall file size more than a traditional
recording:
Again, in producing a thoroughly enthralling animation, with
3D graphics and voiceovers, etc, full motion is a necessity. If the
Full Motion Recording options (which is only briefly mentioned in
the demonstration) are altered, is there a proven relationship
between all the settings (Smoother Movie/Video Quality/Video Color
Mode) and the final size of that recording?
5. Remove any extra slides that do not add any value to the
presentation:
Sounds like a sensible idea. Is there anywhere where we can
see the size of an actual slide?
6. If you insert large images, expect your Captivate file size
to grow more than if you insert small images:
Like point 1, what's the magic formula? Even a ballpark
figure would help. David mentions SWF files and the file size
should increase only by about the same amount as the inserted SWF
file. That's good stuff - a tangible amount.
7. On the Start and End tab:
Okay, but I'm definitely going to need those. Again is there
anywhere where we can find out how big they are?
8. Advanced movie compression: Select this option to compress
slide data shared between slides, thereby reducing overall file
size:
Sweet, consider it done. How much did it just save me?
9. Compress compiled SWF file: Do not deselect this option.
I won't. In fact I am not sure why it's even an option!
10. Include Breeze metadata: This option, which is selected by
default, increases the size of the project. If you are not going to
use the project with Macromedia Breeze, deselect the option to
decrease the size of the finished project file (SWF). However, if
there is the possibility that the output file (SWF) may be used in
Breeze, it is best to select this option.
Bit of a crap shoot at this stage. If I knew just how much I
was saving in the file size, I would be better informed to know
whether to include it or not.
11. 508 compliance: Publishing 508-compliant output increases
your file size. If audience analysis concludes that are no learners
with disabilities that need to access your content—or if you
are not otherwise required to comply with Section 508 government
regulations—you can safely turn off 508 support.
C'mon sevens! Again if only I knew the real impact on my
filesize, I would know whether to just leave it checked, just in
case it will one day be needed.
12. Frames per second: The default setting is 30 Flash frames
per second (fps) and this is appropriate in most cases. Note:
Decreasing the number of frames per second does not significantly
decrease the size of your Captivate project and therefore is not
recommended. For example, decreasing the fps rate by half does not
halve the file size. Also, reducing the fame rate of Captivate is
not the same as reducing the frame rate of an AVI. Lowering the
frame rate of an AVI removes static images from the file, which
reduces its size. Removing a single frame from a Captivate project
where no change takes place does not reduce the file size.
Mine defaults to 10 fps, is that bad? Now I'm confused! So
what is the best frame rate, and just how much does it reduce the
file size when changed?
13. Movie background color: Depending upon the type of slide and
how you took screen shots, the background color might not appear on
all slides. Double-click the color box to open the color picker,
and select a new color. Remember that using a bright background
color will increase the file size.
Does this ~really~ matter if I have 3D Virtual models and
constant audio? Or is it like worrying about if the temperature in
Antarctica is 70 below or 71 below?
14. JPEG image quality: Adjust this setting depending upon the
images used in your movie. Lowering your image quality to as low as
50% (from the default 75%) is often not noticeable to the naked
eye. Higher percentage values allow for very high quality images.
Of course, this also increases file size.
Okay, but numbers would be good again.
15. Play tap audio for recorded typing when movie is generated:
This option plays tapping sounds in the final movie whenever keys
are pressed during recording. Including this option adds a small
audio file to your project and does increase the file size, but
only by a small amount.
No sure how much they'll hear the taps with me talking over
them the whole way through it, but I can turn them off. I think a
lot of people finding them slightly annoying anyway, but how much
did I just gain with that happy move?
16. Including a playback control bar increases the file size by
a small amount. If your users do not need a playback
control—as is often the case with simulations and
quizzes—select None from the menu.
Well they are going to need to play these things back
somehow, but I may have that created separately. What's the average
size of a playback control bar anyway? And how does You Tube get
away with all this stuff?
I am not trying to be cynical, I'm really not, but I am
surprised that this has been raised and addressed by
Macromedia/Adobe already. I would assume that as users develop more
engaging and interactive content, these will become more important.
Is there any hope or support for someone like myself, who wants to
know every shortcut there is in order to deliver the best possible
animations?
As always, any help from any of the experts here, would be
gratefully received!
Thanks and I look forward to your replies.
Cheers,
spritc.

Answer 1

Hi spritc
Maybe there's just not enough people using it yet?
I seriously doubt this is the case. There are more and more
folks using Captivate each day. Just based on the forum activity
alone, we are seeing what I feel is a pretty significant and
growing user base. I say this because I conduct Captivate classes.
During each class I mention the Adobe support forums. And I'm
totally shocked at the fact that almost nobody so far has
found/used them! This tells me that even though I'm seeing an
increase in new users here, there are a vast amount that haven't
yet discovered this area.
...If anyone think I should, or want to themselves point David
to this post...
Pointing David to this post won't do anything. Fact is, he
has moved on and now works for the company that has Articulate.
1. Minimize file size by reducing the recording area in
Captivate:
Sure, but what is the relationship between recording area and
file size? I know there's a relationship between total number of
pixels x bytes per pixel, but there must be more to it than
that.
Think about it this way. If I create a simple bitmap image
using Microsoft Paint, and I size that image to be 640 pixels wide
by 480 pixels tall, I've created something that uses 307,200
pixels. If I did the same thing at 1024 pixels wide by 768 pixels
tall, that number increases to 786,432. That's a significant
difference. I just created a stark white image at each of those
resolutions and saw the 640x480 resulted in a file sized at 901 kb.
The same file at 1024x768 resulted in 2,305 kb. So hopefully this
can better illustrate why this bit is important. Probably the
single most important factor to consider.
5. Remove any extra slides that do not add any value to the
presentation:
Sounds like a sensible idea. Is there anywhere where we can
see the size of an actual slide?
Indeed there is. If you click View > Bandwidth Analysis...
you should see a dialog labeled Bandwidth Monitor. This dialog has
three tabs. One tab (normally the one presented as the default tab)
is labeled Slide Summary. I believe this tab has the information
you are seeking.
6. If you insert large images, expect your Captivate file size
to grow more than if you insert small images:
Like point 1, what's the magic formula? Even a ballpark
figure would help. David mentions SWF files and the file size
should increase only by about the same amount as the inserted SWF
file. That's good stuff - a tangible amount.
I'm unaware of any "magic formula" here. But consider what I
offered in the first bit where I advised of the
pixel/resolution/end resulting size.
7. On the Start and End tab:
Okay, but I'm definitely going to need those. Again is there
anywhere where we can find out how big they are?
This one looks like something got lost during copy/paste. I'm
not sure what you are looking for here.
8. Advanced movie compression: Select this option to compress
slide data shared between slides, thereby reducing overall file
size:
Sweet, consider it done. How much did it just save me?
Well, I'm guessing the savings would vary from project to
project. For example, if your entire movie consisted of recording
mostly the same application and not much is changing from screen to
screen save mouse movement and captions, the savings could be
significant. But if the movie is constantly changing, the savings
may be negligible at best. In other words, your mileage may vary.
However, your question of exactly how much does it save me strikes
me as odd. I would think the fact you are reading the article is an
indication that you apparently have some concerns with regards to
file sizes. So I'm confused as to why you want to know the exact
amount it will save you. Even if it's a small amount, it's better
than nothing.
9. Compress compiled SWF file: Do not deselect this option.
I won't. In fact I am not sure why it's even an option!
I've seen posts where projects refuse to compile.
DE-selecting these options can help in these cases because
something about the mix of elements in those projects is causing
Captivate to gag.
10. Include Breeze metadata: This option, which is selected by
default, increases the size of the project. If you are not going to
use the project with Macromedia Breeze, deselect the option to
decrease the size of the finished project file (SWF). However, if
there is the possibility that the output file (SWF) may be used in
Breeze, it is best to select this option.
Bit of a crap shoot at this stage. If I knew just how much I
was saving in the file size, I would be better informed to know
whether to include it or not.
I think the larger question with this one is to ask:
Are you using Breeze? If no, then turn it off. If yes, leave
it selected.
11. 508 compliance: Publishing 508-compliant output increases
your file size. If audience analysis concludes that are no learners
with disabilities that need to access your content—or if you
are not otherwise required to comply with Section 508 government
regulations—you can safely turn off 508 support.
C'mon sevens! Again if only I knew the real impact on my
filesize, I would know whether to just leave it checked, just in
case it will one day be needed.
Again, the larger question here is
Are you creating output that needs to be 508 compliant? If
not, turn it off. If so, leave it selected. However, making a
project 508 compliant involves much much more than simply selecting
this check box and calling it good.
12. Frames per second: The default setting is 30 Flash frames
per second (fps) and this is appropriate in most cases. Note:
Decreasing the number of frames per second does not significantly
decrease the size of your Captivate project and therefore is not
recommended. For example, decreasing the fps rate by half does not
halve the file size. Also, reducing the fame rate of Captivate is
not the same as reducing the frame rate of an AVI. Lowering the
frame rate of an AVI removes static images from the file, which
reduces its size. Removing a single frame from a Captivate project
where no change takes place does not reduce the file size.
Mine defaults to 10 fps, is that bad? Now I'm confused! So
what is the best frame rate, and just how much does it reduce the
file size when changed?
The default frame rate for Captivate is 30 Frames per second.
The fact yours is 10 indicates that at some point you elected to
change it. Not necessarily bad, but could result in a jerkier
movie. As Captivate defaults to 30, I'm going to crawl out here on
this shaky limb and suggest that it's probably what the developers
feel is the "best".
13. Movie background color: Depending upon the type of slide and
how you took screen shots, the background color might not appear on
all slides. Double-click the color box to open the color picker,
and select a new color. Remember that using a bright background
color will increase the file size.
Does this ~really~ matter if I have 3D Virtual models and
constant audio? Or is it like worrying about if the temperature in
Antarctica is 70 below or 71 below?
Most of the time it's like your Antarctica analogy. This is
because most of the time we are recording applications that consume
the entire recording area. I think what David means here is that if
you have perhaps a blank movie, if you have a different color used
on each slide, the size will increase as a result.
I'm skipping the rest of this to get to something you later
say:
I am not trying to be cynical, I'm really not, but I am
surprised that this has been raised and addressed by
Macromedia/Adobe already. I would assume that as users develop more
engaging and interactive content, these will become more important.
Is there any hope or support for someone like myself, who wants to
know every shortcut there is in order to deliver the best possible
animations?
Sorry, but the tenor of your responses certainly exude a
cynical view. Keep in mind that the only player here is now Adobe.
They swallowed Macromedia, so it is no more.
I think David's document was intended to be used in order to
know which areas you should look at or consider when you are
concerned about file size. It's intended to be a list of places to
possibly make tweaks.
The bottom line is that making all or some of the changes
recommended may help dramatically for one type of project and maybe
not at all for other types. As Captivate is an application that can
be used to create almost anything, it's a bit like asking Kodak
just why their digital cameras include the leaves on the trees when
you take the picture. After all, almost everyone is taking pictures
these days and not everyone wants leaves in their pictures.
Sincerely... Rick