Captivate Save File size

After removing several larger images (3300k) from Captivate
and inserting smaller images (109k), I see that the file size is
now larger than before. Does anyone know what this is
happening?

Hi there
tedpulse wrote:
It appears that the "bloating" problem has not been fixed in Captivate 4...
In that case I would definitely suggest you (and others) take a moment and report this to Adobe as a potential Captivate 4 bug.
Click here to visit the Wish Form/Bug Reporting Form
Cheers... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

Similar Messages

Photoshop Save /File size estimate

Hi
I have a very silly issue that I am sure Ive either unset or has a simple solution. I am using Windows 64 bit photoshop cs5
When I go to file save as and specify JPEG as the file format. The file size estimate does not show anything. I can leave it for ages and it will not display the file size estimate.
Is this a setting that needs to be re-enabled? If so, could a kind soul point me the right direction please
many thanks, all the best
Neil

Zeno has explained it and provided a workaround, but the simple fact that the dialog does not provide an estimate where it should be is really a bug. I reported it a long time ago.
-Noel

Have Tips On reducing .EXE File Size?

Hello,
Captivate exe file sizes are huge compared to comparable exe files produced by competitor software. I set my slide quality to Low, set swf conversion to 16 bit instead of 32 bit, set swf Size And Quality to 50%, and the .exe files are still huge. In fact, changing these settings made no difference to the file size.
Anyone have any tips on reducing the file size of the Captivate Exes, or do you know of any utility that can make .exe files smaller?
Thanks,
Mike

OK somewhere I got mixed up here.
So far as I know, this blig post from the Adobe Captivate Blog explains what is meant to work
http://blogs.adobe.com/captivate/2009/01/adding_rightclick_in_captivate.html
Check the list at the bottom of the page:-
1. Security Setting:   Ensure that the SWF you
published is in Flash Player's trusted path. If you are publishing to
default folder (%My Document%\My Adobe Captivate Project) then you do
not need worry about security settings as captivate automatically adds
that path into trusted path of flash player.
                               2. Disable accessibility: In order to make Right-click work you will need to disable Accessibility from
                               Adobe Captivate 4-> Preferences->Project->Publish settings->Enable Accessibility
                               3. Right-Click will not work in stand-alone SWF file.
                               4. PDF and AVI publish: Right-Click doesn’t work in PDF and AVI publish.
                               5. EXE publish: Right-Click work for AS2 EXE publish but not for AS3 EXE publish
                               6. Preview (F4/F8/F10): Right-Click work for AS2 movies but not for AS3 movies
                               7. Preview (F12, in Web Browser): Right-Click works for both AS2 & AS3.
                               8. SWF Publish (the standard one) : Works for both AS2 and AS3.
                               9. Flash Player Version: Right Click Doesn’t work for movie published Flash Player versions
                           earlier than 8.0
If you are complying with the suggestions here (AS 2 EXE?) then right-click is supposed to work. But I have a feeling I've missed something in what you've said ... or you said it in another post which I've not read.
Steve

Aperture Exporting JPEG's from RAW: file size and quality questions?

Hey Everyone,
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
Is he right, are my pics of lesser quality due to being a smaller file size? I've always been told that the quality of a picture is not in the mbs, but the pixel density.
I've bee told that Aperture has a better compression engine and that the resulting files are of the exact same quality because the PPI and image size are the same. Is that what explains the much smaller file sizes in Aperture?
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs.
Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
Thanks in advance for your help.

mscriv wrote:
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
JPEG is a "lossy" file compression algorithm. Whether Aperture or PS, *every time a JPEG is saved some loss occurs*, albeit minimal at the 11 or 12 level of save, huge losses at low save levels. Some images (sky, straight diagonal lines, etc.) are more vulnerable to showing visible jpeg artifacts.
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
*Both of you are losing image data when you save to jpeg.* IMO the differences between the apps is probably just how the apps work rather than actually losing significantly more data. The real image data loss is in using JPEG at all!
Is he right, are my pics of lesser quality due to being a smaller file size?
I doubt it.
I've always been told that the quality of a picture is not in the mbs, but the pixel density.
The issue here is not how many pixels (because you are not varying that) but how much data each pixel contains. In this case once you avoid lossy JPEG the quality mostly has to do with different RAW conversion algorithms. Apple and Adobe both guess what Nikon is up to with the proprietary RAW NEF files and the results are different from ACR to Apple to Nikon. For my D2x pix I like Nikon's conversions the best (but Nikon software is hard to use), Aperture second and Adobe ACR (what Photoshop/Bridge uses) third. I 98% use Aperture.
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs. Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
JPEG is a useful format but lossy. Only use it as a _last step_ when you must save files size for some reason and are willing to accept the by-definition loss of image data to obtain smaller files (such as for web work or other on-screen viewing). Otherwise (especially for printing) save as TIFF or PSD which are non-lossy file types, but larger.
As to the Aperture vs. ACR argument, RAW-convert the same original both ways, save as TIFF and see if your eyes/brain significantly prefer one over the other. Nikon, Canon etc. keep proprietary original image capture data algorithms secret and each individual camera's RAW conversion is different.
HTH
-Allen

About the file size of Default.png

Hallo forum members,
Is there a 2 MB restriction on [email protected] as there is on normal JPEG pictures?
When I save the [email protected] for a widget the filesize goes up to more than 2 MB, as I save the png with 24 Bit.
Using 8 bit depth to save file size the images show artefacts and color banding.
Ulrike

Book Cover Art
● The book’s cover art that appears on the iBooks Store (also known as the marketing image) is the image
delivered alongside the book asset and does not refer to the cover image included in the book asset. The
pixel limit for the interior cover, as with all interior book images, has been increased to 3.2 million pixels.
● The book’s cover art must use RGB color mode and should be at least 1400 pixels along the shorter axis.
For best results, a good rule of thumb is to use an image that is a minimum of 300 dpi.
● The book’s cover art file must be a high-quality JPEG with .jpg or .jpeg extension or PNG with .png
extension.
● The 3.2 million pixel limit on interior book images does not apply to the external cover/marketing image
that is sent alongside the book asset.
● It is important that you do not increase the size of a smaller image to meet the minimum image size
dimension standard. Excessively blurry or pixelated images will be rejected.
Screenshots
You can provide up to five screenshots per book.
● Full-sized iPad 1/2 images (1024 x 768 or 768 x 1024) in PNG (.png) or JPEG (.jpg) format.
● Full-sized new iPad images (2048 x 1536 or 1536 x 2048) in PNG (.png) or JPEG (.jpg) format.
● For a cleaner look, you can optionally remove the status bar (making the images 1004 x 768 or 748 x 1024
for iPad 1/2, or 2028 x 1536 or 1536 x 2028 for the new iPad).
Perhaps the engineers should take time to read the Assett guide. As yet I have not found any engineers posts advising other than the assett guuide.. do you have a link for any?
Its always better to have higher resolution images than not, and as long as the end product comes with the 3.2 meg limit for all except the cover, its good for those not over familar with image ediiting.
The iPad retina screen resolution is 2048 x 1536 @164 DPI/PPI

Save Captivate 5.5 (.cptx) files in Captivate 7 (.cptx) with huge file size results.

I have been opening and saving Captivate 5.5 (.cptx) files in Captivate 7 (.cptx). The problem is that after saving a file in Captivate 7, the file size increases substantially from the original Captivate 5.5 file size. Can this be avoided or corrected? Thanks!

You're a star. I'd already done the switching off the page thumbnails and reducing page performance. I hadn't thought about cross-references! That's certainly a possibility.
I've just done the "Save As" twice - and that first file is down to 1,100 KB - which is a huge reduction from it's previous size! It's still growing already though - just updating the numbers in the book has taken it from 800 KB up to the new 1,100 without me doing anything else (not even opening it myself). Track Changes is (I believe) switched off ... in Edit > Preferences, unless there's somewhere else...
Shoudl have thought of the Save As as well - used to have to do that with Word docs a few versions ago (not so much now).
Thanks again.
Alison

Huge captivate file sizes

I have been using Captivate to imbed an audio recording of a
presentation into the slides for said presentation. The audio is in
the form of one large mp3 file. When adding the audio, I select the
option to distribute over many files, and line up all the slides to
the correct part of the audio. If i need to edit the slide times or
audio (this happens frequently because captivate seems to be rather
buggy when splitting up the single audio track into one for each
slide) the resulting Captivate Project file rockets in file size. I
believe this is because it is keeping a copy of all audio used in
Captivate, ie an old and new copy of the whole mp3 stream, before
and after editting.
If this happens a few times the file size grows accordingly,
and for a 50min presentation i'm looking at project files of 1.3GB.
These are clearly pushing my (powerfull dual core, 2GB RAM) desktop
to the limit. I have tried removing all unsed items from the
library but this makes no difference to the size of the projects.
To illustrate the problem to a friend I deleted EVERYTHING
from the library, added 1 new blank slide and deleted all the other
slides. The resulting project looked akin to a brand new blank one.
Upon saving (as a new cp file) the project was infact 1.16GB in
size. Eh?
Is there some way of deleting files from captivate projects
other than the library?

If file size is the biggest concern, once you've cleared out
all items
you don't need any longer, try:
1. Doing a Save As, then a Save As again. Often, for whatever
reason,
this finally gets rid of old, unused objects.
2. Create a new project and import the existing project's
slides. This
can have the same effect.
In my experience, the first is better for reducing file sizes
and the
second is better for getting rid of any playback anomalies.
Otherwise, a better approach for what you're doing, again in
my
experience, would be to cut up the audio outside of Captivate
into one
file per slide (using a tool like Audacity), import them all
into the
library, then add each individually. That's our standard
process and
we've yet to experience these huge, bloated CP files (knock,
knock).
Erik
luke@nesc wrote:
> I have been using Captivate to imbed an audio recording
of a presentation into
> the slides for said presentation. The audio is in the
form of one large mp3
> file. When adding the audio, I select the option to
distribute over many files,
> and line up all the slides to the correct part of the
audio. If i need to edit
> the slide times or audio (this happens frequently
because captivate seems to be
> rather buggy when splitting up the single audio track
into one for each slide)
> the resulting Captivate Project file rockets in file
size. ....
Erik Lord
http://www.capemedia.net
Adobe Community Expert - Authorware
http://www.adobe.com/communities/experts/
http://www.awaretips.net -
samples, tips, products, faqs, and links!
*Search the A'ware newsgroup archives*
http://groups.google.com/group/macromedia.authorware

Project file size bloats (Captivate 3)

Does anyone know what causes a project file to become disproportionately bloated? I was working on a file that was approx 200 MB, then imported some objects onto one slide from another project, and suddenly it jumped to over 300 MB (I even deleted all items in the library that weren't being used elsewhere).
I've noticed this phenomenon on more than one occassion. It seems to occur most frequently when importing objects or slides from one project to another.

Hi there
The only way that I've ever seen a file size reduction in Captivate 3 was by performing the following steps:
Open a second instance of Captivate.
Create a new blank project sized identically to the other instance.
Switching between instances, copy slides from the bloated one and paste into the fresh one.
Save the new one and the file size is reduced.
Discard the old one.
Note that you will likely need to re-establish any links you had.
Just a special note here about one of the things you tried. You said you exported to XML. I don't believe you are able to export to XML, then import from XML back into a new project. I believe the XML export works in a very similar manner to the Microsoft Word export. Only the project that exported it will be able to successfully re-import it. As I understand it, the XML export is especially designed for Captivate developers that need to localize (translate) their projects.
Cheers... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

When downloading a file from google drive and save in my phones document directory,the file size is compressed. Why?

I have downloaded files from "Dropbox" and save in phones document directory,After downloading in document directory,the size of the download file is same as the actual size in dropbox. I can also open it from document directory.Everything is ok. But when I follow the same process for google drive files, the file size is compressed(if actual size of file is 1.2Mb the download file size is 61Kb). So I can not open it from document directory.So, How can i download the actual size of the file in document directory? I am using google api objectivec client for google drive.
Thanks in advance.

If an iphone were to try to download a full size document ot photo, it woul overload its own ram, and crash, resulting in a laggy iphone. Therefore it is compresses

I publish a 41mb newsletter monthly into interactive pdf. It always becomes a file size of 4mb, 10% of original, when I save to pdf. This month my newsletter is 41mb and it drops to 11mb, 25% of original. I have re-sized all pictures, deleted pages separa

I publish a 41mb InDesign newsletter monthly into interactive pdf. It always becomes a file size of 4mb, 10% of original, when I save to pdf. This month my newsletter is 41mb and it drops to 11mb, 25% of original. I have re-sized all pictures, deleted pages separately, have gotten the file size down to 16mb and it drops to 7mb, 45% of original.
I have gone back and saved Feb and March and it saves to 10% of original, as it did before, and I use the same mechanism to save now.
I have gone to Acrobat Pro and optimized down to 8.8mb, but the quality is not acceptable.
What other variable is there that I haven't discovered?

My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

I imported an hour of video into iMovie HD and cut it down to a 33 sec clip, and emptied the trash. When I save the project, the file size is 20Gb. How can I save just the 33 sec clip?

I imported an hour of video into iMovie HD and cut it down to a 33 sec clip, and emptied the trash. When I save the project, the file size is 20Gb. How can I save just the 33 sec clip?

Non-destructive editing is an important feature of iMovie HD 6.
iMovie preserves the entire copy of every clip you place into your movie in case you change your mind at a later stage.
So, if you have cut out one minute from a 45 minute clip, iMovie will have stored two complete copies of that clip. This is why is helps to set import as 3-5 minute clips rather than one huge chunk. As DV runs at 13GB per hour your project files can get very big.
One workaround is to complete the editing of a section of the movie, then export that to Quicktime: highlight the clip/s, choose Share-Quicktime, turn on Share selected clips only, and choose Full Quality from the pop-ip menu.
Once you have saved the stand-alone clip to your hard drive, you can re-import it into your project using the File/Import command, and delete the original long clip/s from the project.

In iphoto, how do i save a photo after editing, in the same or higher file size, it's saves in a lower size

in iphoto, how do i save a photo after editing, in the same or higher file size, it's saves in a lower size

It's rather more complicated that this.
iPhoto is a lossless editor. You don't lose any quality on your shot in iPhoto.
The file size you see reported is the size of your iPhoto Preview: this is what gets used if you access the data via a media browser. It's a "good-enough-for-most-uses" version of the shot. Email it, upload to websites, use it in Presentation, Word processing file etc
If you want to set the quality yourself then Export the photo using the File -> Export command.
You can choose to export to Jpeg, Tiff or png. Tiff is lossless but the file sizes are up to 10 times larger. Jpeg allows you to choose different qualities: High, Medium or low. The difference is the amount of compression involved. High quality means very little compression. It's not unusual for photos exported at this setting to have a larger file size than the original.
Which setting you choose depends on the use you intend. Further editing, printing then high is important. Sending to Facebook? Well low will do just fine there as they're going to trash the file anyway.
But the key point: the file size only becomes an issue when you export.
Regards
TD

PDF file size grows with each save if .access property set on a field

We are seeing an odd form behavior and have isolated the apparent trigger to something we are doing in the form script. I'm hoping someone can confirm they see the same problem, details follow:
We have a form generated in LiveCycle. It contains a text field. In the docReady event for that field we have javascript which sets the field to be readOnly (TextField1.access = "readOnly"). We reader extend the form so we can save it from reader and/or the plug-in/control which is used by a browser when reading PDFs.
With that simple form, open the form via the browser (we've tested with both IE and Chrome) and without doing anything else, just save the form (with a new name). When we do that, the saved copy of the form is significantly bigger than the copy we started with. If we then repeat the process using the newly saved file, the third copy is bigger than the second.
This file growth does not happen if you open the file in Adobe Reader (instead of in the browser).
When we look at the file contents via a text editor, what we have found is that each save via the browser is tacking on a chunk of data to the end of the file AFTER the %%EOF mark. This new section appears to be one or more object definitions and ends with another %%EOF. The first portion of the file (prior to the first %%EOF) is identical in all versions of the file.
If you take a copy of the file that has these extra section added, then open and save it in Adobe Reader, it eliminates those extra sections and you get a 'clean', small version of the file again. So those extra sections are clearly erroneous and unnecessary.
Another thing worth noting, we took the script for setting the field access property out of the docReady event and put it as the click event on a button added to the form. If you then open the form, press the button and save it you see the file growth (but not if you don't press the button.) So it doesn't appear related to the docReady event, or timing of when we set the access property of the field.
On the small test form described above the growth of the file is around 13KBytes. But in testing with our real forms we've found that the amount of growth seems to be tied to the size/complexity of the form and the form data. In our most complex form with multiple pages with hundreds of fields and a large amount of XML data (form size is 2+MB), we are getting a file size increase of 700KBytes on each save. This is a therefore, a significant issue for us, particularly since the process in which the form is used requires the users to save it a couple of times a day over the period of a month or more.

I would start by exporting the XML data from the form before and after it grows to see if it is the underlying data that is growing and where. Did you define a schema and bind your form fields to a data connection created from the schema? That is always my first step when creating a form. It makes for a smaller saved file not including multiple levels of sub forms in the data structure.

What is an idea of maximum file size for a film in Captivate?

Hi there,
I'm creating an elearning course in Captivate 7, and it is being published as HTML5. This means the films I've imported are being converted to MP4s, and they are around 10-20mb in size once they've converted. They seem very slow to load on some computers - do you think the file size is too big? Or could it be another issue? Does anyone have a recommendation for maximum file size for films? They are 572 x 322px and around 1-2 mins in length.
Thanks in advance

Probably better guidelines that dictates 'size' of a vi are:
typically no more than 1 video screen in size
is it legible
and is it's function and operation clear.
I have seen examples of '1 vi does it all' that were many screens wide and tall, totally a flustercuck, and nearly 1 MB in size.
Globals and local variables (except for LV2 style) are typcially shunned for they can create a host of problems (race conditions, indeterminant data).
Use connector pane to wire controls and indicators to. Then use wires between vi's to transfer data. I tend to use clusters to hold shared data.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

How do you reduce file size of a PDF if Save As doesnt work?

I have been trying to reduce the size of a PDF, using the Save As > Optimized PDF method.
I have also tried Save As > Reduced Size PDF.
This is on a file made up of 20 pages of full page Jpegs. (These were generated by the script in Photoshop that generates Jpeg files from Layer Comps within the document.)
If I use Reduced Size PDF, I get a greatly reduced file size but the image quality suffers greatly. (Lots of artifacts and blurryness)
There are no options to choose the level of compression I want.
If I use Optimized PDF method, I cant seem to reduce the file size no matter what I set the Jpeg compression to.
Is there some way to cut the size of the file down but not lose so much image quality?
Any suggestions?

Part of the problem here is that the files that are produced when I run the script to output files from layer comps are very big.
If I "save for web" for each layer comp, I wind up with way smaller Jpegs. Thus a much smaller PDF.
So the question is: Can you make the script, Layer Comps to Files, create smaller more optimized Jpegs? (Like you get when you save for web)

Captivate Save File size

Similar Messages

Maybe you are looking for