File sizes growing by magic?!?!?!?!?!?!

I create DVD's for a wedding business. My file sizes are "growing" and i don't know why. This is the first time I've noticed it. I've designed and burned over 100 wedding DVD's using this method. I use a template in DVD studio pro and I drag and drop my assets onto the appropriate button.
The project material is 102 minutes. Some double layered video.
This particular project says that a
DVD best quality 150 min compression (using compressor template) is 3.92G. I put it in the DVD template and it jumps to 4.4G.
The audio size (AIFF 16bit-2200Mhtz) is 68M. I put it in the template and my 4.4G from above jumps to 5.7G. 68M to 1.3G??
I have no idea what is wrong. I've spent four days compressing in various ways using compressor. The description above is the fifth and last attempt.

What you should do is open the project, close the project, then reopen it. The calculator of size is not always accurate and can "jump" when assets change.
Also do not use AIFs, make AC3s and use them instead, saves room and improves performance (prevents issues)
Also note thhat is you are using items in motion menus, that also in creases size each time you extend the length of time (or add audio if there was none)
You should have no isssues with getting 102 minutes of video on a DVD-5 usually (unless very high motion and you need higher encoding rates)
Build to the hard drive to get a better sense of the real size if the above does not help )opening/cclosing/reopening should get you back on track though)

Similar Messages

PDF file size grows each time form is saved (with no data changes). Why?

I have an SAP Adobe form (PDF) and we are seeing a difference in the Save behavior between when it is viewed in Adobe Reader vs. the adobe plug-in(?) for Internet Explorer.
When the form is viewed in Internet Explorer, every time the user saves the form the file size grows (even with no data changes in the form - i.e., open the form, hit save). This is not true if the form is opened in Adobe Reader.
The form in question has multiple pages but the only fields directly bound to the SAP source are a handful of identifiers (e.g., order number) and a dynamic table. It appears from our testing that the more entries in the table when the form is created, the greater the size increase each time the file is saved. The table length is not changed after the form is first generated.
Is there a known difference in the behavior of Adobe Reader vs. the browser plug-in which would account for this difference? Our users have Adobe Reader X installed on their machines.

If this is an XFA form, as opposed to an Acroform, you should ask in the LiveCycle Desiger forum or a more relevant LiveCycle forum.

LPX file size grows every time I save (with almost no changes) - WHY?

Hi all,
I am just now starting to move from Logic 9 to Logic Pro X. I first imported a very simple file from logic nine as a folder project and did not import anything except the file.
- Then, I immediately saved it. took more than 30 secs on core i7 - why so long?
- next I "saved a copy as" file 1a - file size 700k - nice and small.
- that I loaded the first logic X file back in and muted a few things and saved again
- I made some other very minor changes like muting and re-saved three or four times.
Here is what is strange –
Original file = 1 MB
main LX file was 2 megs and each subsequent save gained about 1 MB each time I hit save! So, the final grew to 6 MB after just a few saves!
I checked to see if there was some large edit history file I could purge – but it was empty because all I had done was change some mutes…
Q: what is going on with this large file size growing every time I hit save without any major changes – I would like to know what's going on.

It has to do with undo history, backups, and autosaves. You can see these if you right click on the file and show package contents. Explore in there and you should see these growing in the alternatives folder. I would imagine there is kind of a limit to how many of these there are, but haven't looked to closely at it.

File Size Grows Upon Insert

My image file sizes grow enormously when I insert them. One
jpg (a still) is 9.87 KB but when I insert it in DW the readout
shows it as adding 120K! Another jpg (banner) starts at 20K but
when inserted it's 70K. Is it related to using layers? I'm just
starting on DW so I must be doing something wrong. Any help is
appreciated. Thanks.

Life Savers? You give out crummy Life Savers? Grrr - you get
the trick!
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Ken Binney" <[email protected]> wrote
in message
news:ehltrr$4qm$[email protected]..
> Uh oh, Murray's starting his trick-or-treating early
this year.
>
>
> "Murray *ACE*" <[email protected]>
wrote in message
> news:ehlqlt$19o$[email protected]..
>> They are really only accurate if you hold one eye
closed when reading
>> them....
>>
>> --
>> Murray --- ICQ 71997575
>> Adobe Community Expert
>> (If you *MUST* email me, don't LAUGH when you do
so!)
>> ==================
>>
http://www.dreamweavermx-templates.com
- Template Triage!
>>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>>
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
>> ==================
>>
>>
>> "schreinervideo"
<[email protected]> wrote in message
>> news:ehlqi2$16c$[email protected]..
>>> Thanks for responding. I understand it's just
linking to the image. The
>>> "readout" is the little window in the lower
right corner that displays
>>> size and
>>> connection speed. I know the readings are
accurate because they're
>>> confirmed on
>>> Web Page Analyzer.
>>>
>>
>>
>
>

File Size Growing too much with every Save

I have designed a form that uses Giids with drop-down lists and also some Image Fields. When I am using the form and I save it the file size grows excessively with each save. If I add even one character to a sentence the file size may grow by as much as 500K or more. Saving a few times causes the file to become far to large to send by email. Any ideas what I need to try and fix, or is this just normal?

Nope, I have it unselected and it still grows by leaps and bounds. Any other ideas? Is there anyone I can send a form to who can work on it for a fee?

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.

Huge file size grow when using external editor

Hello,
I want to use an external editor such as Photoshop or Pixelmator. When I set one of the applications to be the external editor everytime I open a file for editing a version is created with a file size of approx. 57 Mb.
Any ideas what is going on here?

Lt, it's also worth seeing if you have the setting for the TIFF so that it best suits you. If you don't require a 16 bit TIFF make sure the it's set to create an 8 bit TIFF instead. The 57 meg size sounds like a 16 bit image. An 8 bit one will be half that
. Before Aperture I used to stay16 bit right up until I passed the image off to whoever it was going to, at which point I'd make them an 8 bit version because that would usually be what they wanted. But now so much of whatever advantage that brought me (exposure and tonal changes, especially in solid areas) is being done in Aperture, even before creating a TIFF, so it can be argued that for many people the advantage of exporting 16 bit to the external editor isn't gaining them that much. If it's going to a consumer printer (that is not 16 bit aware) even more so. 16 bit is better, but if size is an issue and Aperture is doing 90% of the global tweaking, I don't think sending the editor an 8 bit TIFF is a crime : )

Projector and dir file size grow 7X unexpectedly - dcr remains the same.

I’m updating a Shockwave project that is also available
for download (so size matters and I’ve got a dcr and exe of
the same project). Last year the file sizes were as follows: dir =
933kb, dcr = 203kb, exe = 4,857kb … all reasonable. I started
with last year’s file, eliminated numerous redundant scripts
and cast members (including an unused font), combined the
functionality of scripts that were similar, streamlined the
operation of other scripts, updated some internal data, replaced
the one and only bmp with a new one for this year (same size),
saved and compacted … and for all my effort to clean up this
year’s version I get the following: dir = 33.9Mb, dcr =
224kb, exe = 37.5Mb The xtras are an obvious suspect but I went
down the list and they’re the same as last year, the only
outside xtra being POM (which hasn’t changed since 2006) I
recompiled last year’s project and the sizes were still
reasonable, so Director isn’t broke. Anyone know what's up?
PS: I made a dummy copy of this year's movie, elminated
everything (all sprites, all cast members, all xtras), save and
compact, and the dir file is still 33Mb?!?!?
PPS: Well, I copied everything into a fresh document, spent
about an hour making sure scripts not attached to sprites didn't
get left behind, re-attached the required xtras, and now I'm back
down to a 4.4Mb projector but I'm not sure why.

Thanks Mike. The odd thing is the results above were after a
“save and compact” (as a matter of habit I always
compact). Even with everything stripped out of the file I
couldn’t get Director to jettison whatever garbage had gotten
lodged in. On the plus side, moving the cast and score to a fresh
document not only cured the problem but also allowed me to
eliminate some legacy xtras that were no longer being used (this
project has been updated yearly since 2002).
PS: Flash's memory and file size audit report is really nice
for trouble shooting this kind of problem, it would be nice if
Director gets the same feature.

Other file size grow to more then 6GB. Heed help to reduce size.

I have the iphone 3G- 16gb. Recently I noticed that the orange section(Other) has grown to 6gb. I have less then 1gb free space now. How can I reduced this "other" file size and what is this? At first I thought it was the book mark so I got rip all of it but "other remain at 6gb". Any suggestion or help appreciated.

i had the same issue. I had just updated to iTunes 8.2.1. When I synced phone it said phone was synced with another library. IMPOSSIBLE! this is the only computer (iMac) I have ever synced with (or even plugged into.) I went ahead and clicked erase current iphone content and sync. I thought "no problem" as I have everything backed up already.
I got a message saying "Not enough memory for all the music and photos." No new music or photos since last sync a few days ago. Not there is 9 GB of "other" data. How do I erase all the "other data?" Does "restore" really do this? or an app like iStat?
Any thoughts will help.
Thanks
Message was edited by: Swaim
Message was edited by: Swaim

File sizes grow too fast when asset added

When I add a 125 Mb mp4 file to my menu in DVD Studio Pro, the size of the file as indicated by the green guide at the top goes from 3.4 Gb, to 5.4 Gb.
Any idea why a 125 Mb .mp4 file would cause the DVD to get so big so fast?

Yes, the main DVD assets are one .m2v and .ac3 file with chapter markers that make up the 3.4 GB. The file I want to add is a smaller, 1/2 hour separate and related file. This is why I tried to use .mp4 because I was less concerned about the video quality.

File size grows when compressing to h.264

I wonder if any of you can help me here. I created a quicktime movie from iPhoto of a slide show. It runs for 3mins is 1024 x 768 pixels with MPEG Layer 3, Stereo, 44.100 kHz and a data rate of 915.78 kbits/sec. The file is 9.9 MB.
I "compressed" it to h.264 as follows:AAC, Stereo (L R), 44.100 kHz
H.264, 720 x 576, Million and a data rate of 717.84 kbits/sec.
The file GREW to 16.5MB.
Any idea on what I am doing wrong.
Dave

Thanks for the input. Yes I looked at the save as option and the file would swell to 20MB saved that way. I had not realized that the Finder was so "economical" with its information.
The movie size was more abritary than anything else, smaller than the original. I have done slides shows in iDVD before.
The reason for trying to go to h.264 was for use on a PC. Whilst quicktime is available under Windows, a lot of people want to use Windows Media Player and mp4 will play in WMP. I used a PC utility to transcode the movie on the PC but ended up with a 37MB file on that occasion.
Is there an efficient way to turn QT movies to WMP AVI's?
Dave

File Size Grows from a few mb to over a gb

I work for a high school and in our Mac Labs our newspaper students use Indesign. The files that they create are stored on a Windows file server that the students access using SMB.
We've experienced a situation over the last few issues where a student will work on a file and save it. Once saved it is only around 4mb-6mb in size. However, the same student or another student will then try to manipulate the same file only to find that it has grown to over a gigabyte in size causing Indesign to be unresponsive. We'll then have to save the file as a different name and remove the old file. Photos are not large and it's pretty basic usage of Indesign.
My question is this: Does anyone else have this problem? If so, is there a remedy or process that we could follow to alleviate this problem?
Basic info:
Newer iMacs running Snow Leopard
Indesign CS4 Design Standard
Files are stored on Windows Server 2008.
Any help is appreciated.

This may not be the problem, but repeatedly doing a plain save can cause terrific file bloat. All of the od change history is retained, but useless, when the file is closed. Doing a save as periodically forces a complete rewrite and purges that junk.

Growing PDF File Size is Pathetic

Hey all,
I have been using Acrobat for a number of years but ever since my organization updated me to v9, this growing file size is pathetic! If I move a button on a form, the file size grows 100k. If I add a field, the file size grows 100k. I started with a 58k size form (with about 25 fields), and making a few changes and adding a field or two pushed the size over 1meg?!?!
Is there ANYTHING that I can do to stop this? (and yes, I have tried "optomizing" the form using all sort of included options, and on mulitple occasions, optomizing the form ADDED size to the file!?)
And lastly, is Adobe EVER going to fix this??
Thanks for your time.

Hi ~Grafiti.
Thanks for replying.
I thought that as well. I panic when I add a few fields and it grows to over a meg!
On other forums, users who have this problem have said that it's Acrobat adding redundant "XML Junk" to the file. They also say that a way to remove it is to save the form as a "XDP", then "hex edit" all the junk out. Yeah...like I am gonna do all that
Thanks again.

Need help -To Restrict Huge temp file, which grows around 3 GB in OBIEE 11g

Hi Team,
I am working on OBIEE 11.1.1.5 version for a client specific BI application. we have an issue concerning massive space consumption in OBIEE 11g installed linux environment whenever trying to run some detail level drill down reports. While investigating, we found that whenever a user runs the drill down report a temp file named nQS_xxxx_x_xxxxxx.TMP is created and keep's growing in size under the below given folder structure,
*<OBIEE_HOME>/instances/instance1/tmp/OracleBIPresentationServicesComponent/coreapplication_obips1/obis_temp/*
The size of this temp file grows huge as much as around 3 GB and gets erased automatically when the drill down report output is displayed in UI. Hence when multiple users simultaneously try to access these sort of drill down reports the environment runs out of space.
Regarding the drill down reports:
* The drill down report has around 55 columns which is configured to display only 25 rows in the screen and allows the user to download the whole data as Excel output.
* The complete rows being fetched in query ranges from 1000 to even above 100k rows. Based on the rows fetched, the temp file size keeps growing. ie., If the rows being fetched from the query is around 4000 a temp file of around 60 MB is created and gets erased when the report output is generated in screen (Similarly, for around 100k rows, the temp file size grows up to 3 GB before it gets deleted automatically).
* The report output has only one table view along side Title & Filters view. (No Pivot table view, is being used to generate this report.)
* The cache settings for BI Server & BI Presentation services cache are not configured or not enabled.
My doubts or Questions:
* Is there any way to control or configure this temp file generation in OBIEE 11g?
* Why the growing temp file automatically gets deleted immediately after the report output generation in screen. Is there any default server specific settings governing this behaviour?
* As per certain OBIEE article reference for OBIEE 10g, I learnt that for large pivot table based reports the temp file generation is quite normal because of huge in-memory calculations involved . However we have used only Table view in output but still creates huge temp files. Is this behaviour normal in OBIEE 11g. If not, Can any one Please suggest of any specific settings to be considered to avoid generating these huge files or atleast generate a compressed temp file.
* Any other work around solution available for generating a report of this type without the generation of temp files in the environment?
Any help/suggestions/pointers or document reference on this regard will be much appreciated. Please advice
Thanks & Regards,
Guhan
Edited by: 814788 on 11-Aug-2011 13:02

Hello Guhan,
The temp files are used to prepare the final result set for OBI presentation server processing, so as long as long you dataset is big the tmp files will be also big and you can only avoid this by reducing your dataset by for example filtering your report.
You can also control the size of your temp files by reducing the usage of the BI server.I mean by this if you are using any functions like for example sorting that can be handled by your database so just push to the DB.
Once the report finished the BI server removes automatically the tmp files because it's not necessary anymore.you can see it as a file that is used for internal calculations once it's done the server gets rid of it.
Hope this helps
Adil

Index file increase with no corresponding increase in block numbers or Pag file size

Hi All,
Just wondering if anyone else has experienced this issue and/or can help explain why it is happening....
I have a BSO cube fronted by a Hyperion Planning app, in version 11.1.2.1.000
The cube is in it's infancy, but already contains 24M blocks, with a PAG file size of 12GB. We expect this to grow fairly rapidly over the next 12 months or so.
After performing a simple Agg of aggregating sparse dimensions, the Index file sits at 1.6GB.
When I then perform a dense restructure, the index file reduces to 0.6GB. The PAG file remains around 12GB (a minor reduction of 0.4GB occurs). The number of blocks remains exactly the same.
If I then run the Agg script again, the number of blocks again remains exactly the same, the PAG file increases by about 0.4GB, but the index file size leaps back to 1.6GB.
If I then immediately re-run the Agg script, the # blocks still remains the same, the PAG file increases marginally (less than 0.1GB) and the Index remains exactly the same at 1.6GB.
Subsequent passes of the Agg script have the same effect - a slight increase in the PAG file only.
Performing another dense restructure reverts the Index file to 0.6GB (exactly the same number of bytes as before).
I have tried running the Aggs using parallel calcs, and also as in series (ie single thread) and get exactly the same results.
I figured there must be some kind of fragmentation happening on the Index, but can't think of a way to prove it. At all stages of the above test, the Average Clustering Ratio remains at 1.00, but I believe this just relates to the data, rather than the Index.
After a bit of research, it seems older versions of Essbase used to suffer from this Index 'leakage', but that it was fixed way before 11.1.2.1.
I also found the following thread which indicates that the Index tags may be duplicated during a calc to allow a read of the data during the calc;
http://www.network54.com/Forum/58296/thread/1038502076/1038565646/index+file+size+grows+with+same+data+-
However, even if all the Index tags are duplicated, I would expect the maximum growth of the Index file to be 100%, right? But I am getting more than 160% growth (1.6GB / 0.6GB).
And what I haven't mentioned is that I am only aggregating a subset of the database, as my Agg script fixes on only certain members of my non-aggregating sparse dimensions (ie only 1 Scenario & Version)
The Index file growth in itself is not a problem. But the knock-on effect is that calc times increase - if I run back-to-back Aggs as above, the 2nd Agg calc takes 20% longer than the 1st. And with the expected growth of the model, this will likely get much worse.
Anyone have any explanation as to what is occurring, and how to prevent it...?
Happy to add any other details that might help with troubleshooting, but thought I'd see if I get any bites first.
The only other thing I think worth pointing out at this stage is that we have made the cube Direct I/O for performance reasons. I don't have much prior exposure to Direct I/O so don't know whether this could be contributing to the problem.
Thanks for reading.

alan.d wrote:
The only other thing I think worth pointing out at this stage is that we have made the cube Direct I/O for performance reasons. I don't have much prior exposure to Direct I/O so don't know whether this could be contributing to the problem.
Thanks for reading.
I haven't tried Direct I/O for quite a while, but I never got it to work properly. Not exactly the same issue that you have, but it would spawn tons of .pag files in the past. You might try duplicating your cube, changing it to buffered I/O, and run the same processes and see if it does the same thing.
Sabrina

File sizes growing by magic?!?!?!?!?!?!

Similar Messages

Maybe you are looking for