Drop Initial WAAAY Too Large

We have a spec for a drop initial that is 2 line, 35 pt in a secondary font. When we use either a nested style or a character style in the drop cap dialog, or if we simply hilight the 2 line DI and make it 35pt, InD seems to multiply the 35 by whatever it is doing to make the intial larger when "2" is entered into the "Lines" field of the drop caps dialog.
Am I missing something or is this a bug?
Thanks

Ken K, Edit: I forgot everyone here but me seems to be named Ken :) The previous post was indeed in repsonse to Ken G.
We cross posted there. Consider this, you call InDesign a "professional typesetting package" while I would call it a professional page layout application with very good typesetting features.
I'm not a software engineer, and I don't work for Adobe, but I can surmise that InDesign was introduced both to replace Pagemaker and to compete with Quark Xpress, which it has done quite well. Most users of those applications are not setting long documents, they are working in short documents with a lot of other graphical features, and priorities about what is desired by or will benefit the largest number of users are always part of a development cycle.
InDesign is making improvements to long doc features with each new release, but to expect it to be Ventura is as unrealistic as expecting it to mimic Word. Some decisions are made for convenience, some are made because they have larger implications for other areas of the program.
You happen to like the ability of setting drop cap specifications manually. I think the automation is a better solution and a timesaver 99% of the time. And I've offered you a workaround that seems passable, so at this point I would say stop comparing strengths and weaknesses and start embracing differences and learn to use the tool as it work best. American handsaws cut mostly on the push stroke, Japanese on the pull, and either will eventually get through the board if you use them backward, but both work better when you understand what they are designed to do.
Peter

Similar Messages

Too large frames/Outdiscards errors

Hi !
We have a problem with switch connected to an IBM Chassis (model : WS-CBS3012-IBM-I).
Several links seem to flap from time to time and we have dropped packets (Outdiscards) :
XXX#show interfaces counters errors
Port        Align-Err     FCS-Err    Xmit-Err     Rcv-Err UnderSize OutDiscards
Gi0/7               0           0           0           0          0        43983
XXX#show controllers ethernet-controller gigabitEthernet 0/7
     Transmit GigabitEthernet0/7              Receive
   2584788113 Bytes                        971769475 Bytes
   2128747524 Unicast frames              2142250737 Unicast frames
     10109338 Multicast frames                  7644 Multicast frames
     11694673 Broadcast frames                  1660 Broadcast frames
            0 Too old frames               991831483 Unicast bytes
            0 Deferred frames                 726180 Multicast bytes
            0 MTU exceeded frames             106240 Broadcast bytes
            0 1 collision frames                   0 Alignment errors
            0 2 collision frames                   0 FCS errors
            0 3 collision frames                   0 Oversize frames
            0 4 collision frames                   0 Undersize frames
            0 5 collision frames                   0 Collision fragments
            0 6 collision frames
            0 7 collision frames                   0 Minimum size frames
            0 8 collision frames           208582465 65 to 127 byte frames
            0 9 collision frames           286273443 128 to 255 byte frames
            0 10 collision frames           15408397 256 to 511 byte frames
            0 11 collision frames           12313490 512 to 1023 byte frames
            0 12 collision frames           10599137 1024 to 1518 byte frames
            0 13 collision frames                  0 Overrun frames
            0 14 collision frames                  0 Pause frames
            0 15 collision frames
            0 Excessive collisions                 0 Symbol error frames
            0 Late collisions                      0 Invalid frames, too large
            0 VLAN discard frames         1609083109 Valid frames, too large
            0 Excess defer frames                  0 Invalid frames, too small
       320523 64 byte frames                       0 Valid frames, too small
    396763728 127 byte frames
      6601722 255 byte frames                      0 Too old frames
     28139208 511 byte frames                      0 Valid oversize frames
      4064656 1023 byte frames                     0 System FCS error frames
    285633065 1518 byte frames                     0 RxPortFifoFull drop frame
   1429028633 Too large frames
            0 Good (1 coll) frames
            0 Good (>1 coll) frames
The interface is Full-1000 and is configured :
interface GigabitEthernet0/7
description "SRV-001-PRD-VM1 - VMNic0"
switchport trunk allowed vlan 11,12,99
switchport mode trunk
link state group 1 downstream
end
For the "too large frames", I have already read the post : https://supportforums.cisco.com/discussion/11034901/too-large-frames-what-does-mean-performance, so, I think it's not serious.
But I don't know why some packets are dropped because the configuration seems good ...
Can you help me please ?
Thank you in advance !

87752686 Valid frames, too large
This is nothing. You get this counters if the port(s) is/are configured as Dot1Q Trunking.
There is nothing to be worried about.

Images too large for Drop zone in Template

Is there a way I can resize images I want to use after I drop it in a drop zone? For some reason, all my images are too large for the drop zones - even after making smaller in photoshop.
Thanks!

I'm fairly new to DVD SP too and wondering the same thing.
Shouldn't we be able to edit the image mask?
It's kinda worthless to just accept what DVDSP decides to do with the photo.

Drop down "save" screen too large

I frequently save web pages as PDFs. When I select "save" or "save as" from the file menu, a drop down page opens to allow me to select the location in which to save the data. The bottom of this new page extends beyond the screen so that I am unable to see or select the "Save" button to commit to the location. The original screen is sized correctly , it's only this "save" screen that is too large. How can I resize this drop down page?

Hi
quitting Safari then trashing
Home/Library/Preferences/com.apple.safari.plist
should reset that & anything else customisable... but if you'd rather keep other changes, try the following command in Terminal, after quitting Safari
I'm assuming that you do mean the Save window created when say on this page, you choose File - Save as...
defaults delete com.apple.safari NSNavPanelExpandedSizeForSaveMode
you could also likely click the expand/contract arrow next to the 'export as' name box - which will make the window smaller & thus hopefully usable - but remove some of its features, including the corner drag to alter its size.

Very large file 1.6 GB..sports program for school. lots of photos, template where media spots saved and dropped photos in..trying to get it to printer swho says its too large but when reduces size loses all quality...HELP??

Please help...large file my sons Athletic program. Had noto problem with Quality last year..this new printer said file is too large..too many layers, can I FLATTEN..He reduced size and photos look awful. It is 81 pages. Have to have complete before next friday!! Help anyone??

At that size it sounds like you have inserted lots of photos at too large a size and resolution.
Especially for a year book style project, first determine your image sizes and crop and fix the resolution to 300 dpi, then drag them into the publication. Pages does not use external references to files and rapidly grows to quite large size unless you trim and size your images before placement.
Peter

Target File Size Too Large?

Hello,
We have an interface, that takes a Source File-> Transforms it in the Staging Area ->and outputs a Target File.
The problem is the target file is way too large than what it is supposed to be.
We do have the 'Truncate Option' turned ON, so its not duplicate records..
We think its the Physical and Logical Lengths that are defined for the Target files.
We think the logical length is way too large causing substantial 'spaces' between the data columns thereby increasing the file size.
We initially had the Logical Length for the data columns as 12 and we got the following error:
Arithmetic Overflow error converting numeric to data type numeric.
When we increased the Logical Length from 12 to 20 the interface executed fine without errors. But now the target file size is just way too large 1:5
Any suggestions to prevent these additional spaces in the target columns??
Appreciate your inputs!
Thanks

Since 'File-system' does not have a property 'column length', ODI will automatically set a standard 'column length' according to the datatype of the column. In your case, as both your source and target is File, check the max length of each column in your source ( Ex: if your file is huge then open the file in excel and verify the lengths) and set the same 'Logical length' for your target file datastore.
drop the temporary tables (set the 'delete temp objects' option to 'true' in the KMs) and re-run the Interface. hope this helps.
Thanks,
Parasuram.

I am trying to download my paid for Elements 13 upgrade. When I click on the "download" button, I recieve this message: 413 Header Length too Large

I am trying to download my paid for Elements 13 upgrade. When I click on the "download" button, I receive this message: 413 Header Length too Large. Help?

You can download using direct download link , which I had provided.
Download Photoshop Elements products | 13, 12, 11, 10
During installation , when prompted enter serial number and proceed with the installation .
If you had purchased upgrade serial number.
First enter Photoshop Elements 13 serial number .
Then it will ask for previous qualifying version serial number.
From the drop down list , select Photoshop Elements 12 and then enter Photoshop Elements 12 serial number

TIme Machine backup grows too large during backup process

I have been using Time Machine without a problem for several months, backing up my imac - 500GB drive with 350g used. Recently TM failed because the backups had finally filled the external drive - 500GB USB. Since I did not need the older backups, I reformatted the external drive to start from scratch. Now TM tries to do an initial full backup but the size keeps growing as it is backing up, eventually becoming too large for the external drive and TM fails. It will report, say, 200G to back up, then it reaches that point and the "Backing up XXXGB of XXXGB" just keeps getting larger. I have tried excluding more than 100GB of files to get the backup set very small, but it still grows during the backup process. I have deleted plist and cache files as some discussions have suggested, but the same issue occurs each time. What is going on???

Michael Birtel wrote:
Here is the log for the last failure. As you see it indicates there is enough room 345g needed, 464G available, but then it fails. I can watch the backup progress, it reaches 345G and then keeps growing till it give out of disk space error. I don't know what "Event store UUIDs don't match for volume: Macintosh HD" implies, maybe this is a clue?
No. It's sort of a warning, indicating that TM isn't sure what's changed on your internal HD since the previous backup, usually as a result of an abnormal shutdown. But since you just erased your TM disk, it's perfectly normal.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
2009-07-08 19:37:53.659 FindSystemFiles[254:713] Querying receipt database for system packages
2009-07-08 19:37:55.582 FindSystemFiles[254:713] Using system path cache.
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 309.5 GB excluded items size: 22.3 GB for volume Macintosh HD
No pre-backup thinning needed: 345.01 GB requested (including padding), 464.53 GB available
This is a completely normal start to a backup. Just after that last message is when the actual copying begins. Apparently whatever's happening, no messages are being sent to the log, so this may not be an easy one to figure out.
First, let's use Disk Utility to confirm that the disk really is set up properly.
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the Format must be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac.
If any of this is incorrect, that's likely the source of the problem. See item #5 of the Frequently Asked Questions post at the top of this forum for instructions, then try again.
If it's all correct, perhaps there's something else in your logs.
Use the Console app (in your Applications/Utilities folder).
When it starts, click +Show Log List+ in the toolbar, then navigate in the sidebar that opens up to your system.log and select it. Navigate to the +Starting standard backup+ message that you noted above, then see what follows that might indicate some sort of error, failure, termination, exit, etc. (many of the messages there are info for developers, etc.). If in doubt post (a reasonable amount of) the log here.

ReportExportControl -- File is too large for attachment

Hi all,
Back with a exception again.
Few reports deployed on BOXIR2 SP4 comes with an error as following
com.crystaldecisions.report.web.viewer.ReportExportControl
15bf5ea9377e1c1.rtf File is too large for attachment.
Few reports take date range as input and generates result based on that. When date range is small report is generated without any problem. If is large and has large set of records(approx above 10K records) then comes up with the above error.
Another set of reports whatever be the case throws this error.
But when the parameters are set in CMS console and run in console report is generated without any problem what ever be the date range.
After searching a lot no solutions in hand!!
Please suggest solutions/possible scenarios / checklist to solve this issue.
Thanks & Regards
lnarayanan

It turns out the report was so large it was basically overloading everything (disk space, cache sizes, timeouts, etc.) ... Here's the solution from the case:
1) For page server and cache server
Make sure location of Temp Files/Cache files has enough free space (more than 500 MB)
2) For page server and cache server
Minutes Before an Idle Connection is Closed = 90
3) For page server
Minutes Before an Idle Report Job is Closed = 90
4) For cache server
Maximum Simultaneous Processing Threads = automatic
5) In the command line of page server and cache server, add
"-requestTimeout 5400000" [without " "]
6) Maximum Cache Size Allowed (KBytes) = set it to an appropriate value (for e.g. for 500 Mb, value should be 500*1024 = 512000)
(This setting limits the amount of hard disk space used to store cached pages. If we need to handle large reports, a large cache size is needed. Maximum allowed is 2048 GB)
After all this, an "Error 500 - Java heap space" happened. The amount of memory allocated to a JVM application can be set using the options -Xms (the initial size) and -Xmx (the maximum size).
Regards,
Bryan

HT1229 My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my

My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my iMac (that's my responsibility). I dragged it to Trash and when it started to move I clicked over to the new hard drive to confirm it had indeed been copied. I became nervous when I didn't see among the few files on this otherwise empty new hard drive anything that resembled a 280GB Library so I cancelled the migration to trash.
How can I be sure that my iphoto has been copied and that all my "metadata" survived in tact?

the new backup drive
I thought the new drive would be your data drive to host the iPhoto library. Do you also use it for TimeMachine backups?
I am unable to search either in email as well as Finder. I AM able to search within iPhoto though, thankfully
Spotlight may still be busy rebuildig its index.
You could try to rebuild the Spotlight Index, if you do see no progress:
Spotlight: How to re-index folders or volumes
I hope, other frequent posters will drop in. I have not used iPhoto 8.x in long time.

"This backup is too large for the backup volume" - Info

Hi there. I had a problem with my time machine and got an error stating "This backup is too large for the backup volume". I did noticed after logging in that TM was indexing in the upper right corner [magnifier with a flashing dot(spotlight)] for a few seconds. So then I went on to "back up now" and it was preparing and then I got the Error message described above. So I uninstalled my anti-virus (you must disable auto protection/or exclude timemachine.app and its plist file (location below)from Anti-virus preferences in the case you have a anti-virus app, otherwise it will take forever to back up.) though that was not my issue. I then turn off time machine and deleted this .plist file in Macintosh HD > Library > Preferences > com.apple.TimeMachine.plist....STOP here if this fixed your problem after restarting. Time machine External Drive in Disk Utility **THESE STEPS WILL ERASE YOUR ENTIRE BACKUPS** ( "Erase" and rename or "partition" to make more that one partition on the External Drive if you wish, and Rename) (Disk utility> Partition tab> "option" you must - guid=intel / apple partition map=PowerPC)...sorry alot of newbie out there...by deleting the "com.apple.TimeMachine.plist" = when you plug in you TM it will ask you if you want to use the drive as a TM back up automatically. This did the trick. But to let you guys know I also used Cocktail (app) and used a feature it has to erase my computers spotlight index and rebuild it. Also in Cocktail, when you have your time machine plugged in you can erase its index and disable it all together. I recommend you first disable spotlight (before the first initial TM backup) in system preferences > spotlight> Privacy (tab) and plus to add time machine ...which has to be mounted (plugged in) to add from window under "Devices".

http://www.macfixit.com/article.php?story=20090403093528353

Error: "This backup is too large for the backup volume."

Well TM is acting up. I get an error that reads:
"This backup is too large for the backup volume."
Both the internal boot disk and the external baclup drive are 1TB. The internal one has a two partitions, the OSX one that is 900GBs and a 32GB NTFS one for Boot Camp.
The external drive is a single OSX Extended part. that is 932GBs.
Both the Time Machine disk, and the Boot Camp disk are excluded from the backup along with a "Crap" folder for temporary large files as well as the EyeTV temp folder.
Time Machine says it needs 938GBs to backup only the OSX disk, which has 806GBs in use with the rest free. WTFFF? The TM pane says that "only" 782GBs are going to be backed up. Where did the 938GBs figure come from?
This happened after moving a large folder (128GB in total) from the root of the OSX disk over to my Home Folder.
I have reformated the Time Machine drive and have no backups at all of my data and it refuses to backup!!
Why would it need 938GBs of space to backup if the disk has "only" 806 GBs in use??? Is there anyway to reset Time Machine completely???
Some screenshots:
http://www.xcapepr.com/images/tm2.png
http://www.xcapepr.com/images/tm1.png
http://www.xcapepr.com/images/tm4.png

xcapepr wrote:
Time Machine says it needs 938GBs to backup only the OSX disk, which has 806GBs in use with the rest free. WTFFF? The TM pane says that "only" 782GBs are going to be backed up. Where did the 938GBs figure come from?
Why would it need 938GBs of space to backup if the disk has "only" 806 GBs in use??? Is there anyway to reset Time Machine completely???
TM makes an initial "estimate" of how much space it needs, "including padding", that is often quite high. Why that is, and Just exactly what it means by "padding" are rather mysterious. But it does also need work space on any drive, including your TM drive.
But beyond that, your TM disk really is too small for what you're backing-up. The general "rule of thumb" is it should be 2-3 times the size of what it's backing-up, but it really depends on how you use your Mac. If you frequently update lots of large files, even 3 times may not be enough. If you're a light user, you might get by with 1.5 times. But that's about the lower limit.
Note that although it does skip a few system caches, work files, etc., by default it backs up everything else, and does not do any compression.
All this is because TM is designed to manage it's backups and space for you. Once it's initial, full backup is done, it will by default then back-up any changes hourly. It only keeps those hourly backups for 24 hours, but converts the first of the day to a "daily" backup, which it keeps for a month. After a month, it converts one per week into a "weekly" backup that it will keep for as long as it has room
What you're up against is, room for those 30 dailies and up to 24 hourlies.
You might be able to get it to work, sort of, temporarily, by excluding something large, like your home folder, until that first full backup completes, then remove the exclusion for the next run. But pretty soon, it will begin to fail again, and you'll have to delete backups manually (from the TM interface, not via the Finder).
Longer term, you need a bigger disk; or exclude some large items (back-them up to a portable external or even DVD/RWs first); or a different strategy.
You might want to investigate CarbonCopyCloner, SuperDuper!, and other apps that can be used to make bootable "clones". Their advantage, beyond needing less room, is when your HD fails, you can immediately boot and run from the clone, rather than waiting to restore from TM to your repaired or replaced HD.
Their disadvantages are, you don't have the previous versions of changed or deleted files, and because of the way they work, their "incremental" backups of changed items take much longer and far more CPU.
Many of us use both a "clone" (I use CCC) and TM. On my small (roughly 30 gb) system, the difference is dramatic: I rarely notice TM's hourly backups -- they usually run under 30 seconds; CCC takes at least 15 minutes and most of my CPU.

"Backup is too large for the backup volume" error

I've been backing up with TM for a while now, and finally it seems as though the hard drive is full, since I'm down to 4.2GB available of 114.4GB.
Whenever TM tries to do a backup, it gives me the error "This backup is too large for the backup volume. The backup requires 10.8 GB but only 4.2GB are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I understand that I have those two options, but why can't TM just erase the oldest backup and use that free space to make the new backup? I know a 120GB drive is pretty small, but if I have to just keep accumulating backups infinitely, I'm afraid I'll end up with 10 years of backups and a 890-zettabyte drive taking up my garage. I'm hoping there's a more practical solution.

John,
Please review the following article as it might explain what you are encountering.
*_“This Backup is Too Large for the Backup Volume”_*
First, much depends on the size of your Mac’s internal hard disk, the quantity of data it contains, and the size of the hard disk designated for Time Machine backups. It is recommended that any hard disk designated for Time Machine backups be +at least+ twice as large as the hard disk it is backing up from. You see, the more space it has to grow, the greater the history it can preserve.
*Disk Management*
Time Machine is designed to use the space it is given as economically as possible. When backups reach the limit of expansion, Time Machine will begin to delete old backups to make way for newer data. The less space you provide for backups the sooner older data will be discarded. [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
However, Time Machine will only delete what it considers “expired”. Within the Console Logs this process is referred to as “thinning”. It appears that many of these “expired” backups are deleted when hourly backups are consolidated into daily backups and daily backups are consolidated into weekly backups. This consolidation takes place once hourly backups reach 24 hours old and daily backups reach about 30 days old. Weekly backups will only be deleted, or ‘thinned’, once the backup drive nears full capacity.
One thing seems for sure, though; If a new incremental backup happens to be larger than what Time Machine currently considers “expired” then you will get the message “This backup is too large for the backup volume.” In other words, Time Machine believes it would have to sacrifice to much to accommodate the latest incremental backup. This is probably why Time Machine always overestimates incremental backups by 2 to 10 times the actual size of the data currently being backed up. Within the Console logs this is referred to as “padding”. This is so that backup files never actually reach the physically limits of the backup disk itself.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space. Do NOT, however, delete files from a Time Machine backup disk by manually mounting the disk and dragging files to the trash. You can damage or destroy your original backups by this means.
Additionally, deleting files you no longer wish to keep on your Mac does not immediately remove such files from Time Machine backups. Once data has been removed from your Macs' hard disk it will remain in backups for some time until Time Machine determines that it has "expired". That's one of its’ benefits - it retains data you may have unintentionally deleted. But eventually that data is expunged. If, however, you need to remove backed up files immediately, do this:
Launch Time Machine from the Dock icon.
Initially, you are presented with a window labeled “Today (Now)”. This window represents the state of your Mac as it exists now. +DO NOT+ delete or make changes to files while you see “Today (Now)” at the bottom of the screen. Otherwise, you will be deleting files that exist "today" - not yesterday or last week.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides. If it has been some time since you deleted the file from your Mac, you may need to go farther back in time to see the unwanted file. In that case, use the time scale on the right to choose a date prior to when you actually deleted the file from your Mac.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*Full Backup After Restore*
If you are running out of disk space sooner than expected it may be that Time Machine is ignoring previous backups and is trying to perform another full backup of your system? This will happen if you have reinstalled the System Software (Mac OS), or replaced your computer with a new one, or hard significant repair work done on your exisitng Mac. Time Machine will perform a new full backup. This is normal. [http://support.apple.com/kb/TS1338]
You have several options if Time Machine is unable to perform the new full backup:
A. Delete the old backups, and let Time Machine begin a fresh.
B. Attach another external hard disk and begin backups there, while keeping this current hard disk. After you are satisfied with the new backup set, you can later reformat the old hard disk and use it for other storage.
C. Ctrl-Click the Time Machine Dock icon and select "Browse Other Time Machine disks...". Then select the old backup set. Navigate to files/folders you don't really need backups of and go up to the Action menu ("Gear" icon) and select "Delete all backups of this file." If you delete enough useless stuff, you may be able to free up enough space for the new backup to take place. However, this method is not assured as it may not free up enough "contiguous space" for the new backup to take place.
*Outgrown Your Backup Disk?*
On the other hand, your computers drive contents may very well have outgrown the capacity of the Time Machine backup disk. It may be time to purchase a larger capacity hard drive for Time Machine backups. Alternatively, you can begin using the Time Machine Preferences exclusion list to prevent Time Machine from backing up unneeded files/folders.
Consider as well: Do you really need ALL that data on your primary hard disk? It sounds like you might need to Archive to a different hard disk anything that's is not of immediate importance. You see, Time Machine is not designed for archiving purposes, just as a backup of your local drive(s). In the event of disaster, it can get your system back to its' current state without having to reinstall everything. But if you need LONG TERM storage, then you need another drive that is removed from your normal everyday working environment.
This KB article discusses this scenario with some suggestions including Archiving the old backups and starting fresh [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
Let us know if this clarifies things.
Cheers!

Why is Encore 5.1 AUTO mode building files just a bit too large for DVDs?

I've been doing the same videos for a few years using Encore 1.5 and more recently Encore 5.1 (with Premiere 5.5). The videos are typically football games with short 2-25 secs of motion menus. If I put two games per DVD, the total running time has been up to 2 hours total per game. I've made dozens of these with Premier writing AVI files (standard 720x480 vide) and writing in Encore 1.5 using auto settings. With Premiere CS4 I started using the dynamic link to Encore CS4 and still ran beautiful DVDs on auto transcoding.
Now, when using the same standard video files in Premiers 5.5, and using dynamic link to Encore 5.1, on auto transcode settings, the image files or transcode files (depending on how I order the build) keep coming out 150 - 300 MBs too large for the DVDs (typically Tayo-Yuden or Verbatim burning to Plextor/Pioneer drives). (Windows-7-X64 Intel D975XBX2 MB.)
To see if I was going nuts, I recently saved a job as two AVI files (same length as the sequences sent through dynamic link to Encore CS5.1) and did the same DVD setup in Encore CS4 but importing the AVI files as timelines. The chapter points didn't convert for Encore CS4 so I had to install manually. The end result, though, was a DVD image that worked fine.
So I then went to the Encore CS5 build window and set the DVD size to manual, dropping down from 4.7GBs to 4.25. The result fit, but then left too much free space (though the vids still looked OK).
I know by other discussions that others are having issues with Encore CS5.1 - or maybe it is related to Premiere 5.5 sequences. Recently burned a set with 22 secs motion menu and 1.4 hours of video and had no problems on auto. This leads me to believe either that Encore is underestimating the transcode sizes or there is a problem with writing DVDs at or near two hours in length.
Anybody have answers, suggestions?
Thanks,
Doug A

Thanks, Giorgio.
I do you imgburn quite a bit and even the new version 2.5.6.0 which allows for truncating and overburning wouldn't write to either the Plextor burners or the Pioneer 205 (Blu-Ray in DVD mode).
I just ran another image build setting the disc size (for the burn) at 4.5GBs rather than the automatic 4.7GBs. This helped and gave me a final image size of 4.33GBs - still not large enough to maximize the disc and the compressed code for better quality, but in this case, a tradeoff for just getting the job done.
I hope Adobe updates a fix for this problem, if indeed, it turns out to be a bug. Also, while I'm on the the bandwagon, the motion previews in Encore 5.1 do seem to preview in very low res. I'll need to check to see if there is a setting for this, but I've not experienced it before 5.1.
Regards,
Doug A

File too large for volume format?

I'm trying to copy a 4.6GB .m4v file from my hard disk to an 8GB USB flash drive.
When I drag the movie in the finder, I get a dialogue telling me the file "is too large for the volume's format". That's a new one for me. If the flash drive has 8GB available, and the file is only 4.6GB in size, how is that too large? Does it have to do with the way the flash drive is formatted? It's presently formatted as MS DOS FAT 32. Is that the problem? Do I need to reformat as HFS+? Or is it some other problem?

The flash drive is pre-formatted FAT32 which has a maximum allowable file size of 2 GBs. Change the flash drive format for OS X:
Drive Partition and Format
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.

Drop Initial WAAAY Too Large

Similar Messages

Maybe you are looking for