Vault size issues

I have 2 vaults on seperate external HDDs, after a nice smooth upgrade to A3 i decided to update them, they were both 116gb, after A3 update, one is 37gb the other is 26gb, shome mishtake shurely?
have any of you experienced similar effects on your vaults? or have any ideas as to :
a) why they have shrunk?
b) why they are different sizes?
on a lighter note, having had a play with some of the new features, adjustment brushes etc i am very happy with a3 so far, not having to do stuff in photoshop will cut down my workflow no end, all i need now is for all my plugins to have 64bit versions released

i seem to have answered this one myself, the simple act of creating a new vault from within A3 appears to have sorted this query out, maybe it will hep others too

Similar Messages

  • Library size differs from Vault size

    I just made a new Aperture Vault. My Aperture Library file is 41.66GB. My Vault file is 35.41GB.
    Why are these different?
    I have consolidated the library as well, so I am sure that the issue is not related to referenced files.
    Thanks,
    ~BC

    Thanks for that. Does my vault size (85% of the library size) seem about right to you?
    I only ask because the whole point of the vault is to be sure nothing is lost ... so I want to be sure I have this set up properly.
    Thanks,
    ~BC

  • Vault size in AP3

    Anybody else seeing Vaults that are as big as their main library ?
    I use a library with referenced masters and the library is around 22GB at the moment (still in the proces, after a whole WEEK, of manually exporting and importing projects from my AP2 library).
    My vault is the exact same size. It seems to copy all the thumbnails as well, they use 20GB out of that 22GB.
    AP2 didn't have huge vaults like that!
    Another issue to add to the list for AP3!

    Firstlaunch, thanks for your reply - sorry for my delayed response; I've been away for a bit.
    Anyway, to respond to yoyur question - it was the error message that appeared which indicated the 14GB size increase. At the time, I couldn't perform the backup as there was not enough space on the drive. Since then, though, I bought a larger external drive and when I ran the Vault on it (having made no changes from the prior situation) the Vault size did not (again, did not) jump in size.
    So, to recap:
    - I use, and always have used, referenced files, and my AP2 vault was 20GB.
    - After I upgraded to AP3, I immediately ran the Vault, whereupon AP3 renamed the original Vault "old" and proceeded to build it's own fresh version - that was 40GB. I.e. - without any alterations to the underlying data set, the Vault doubled in size. In fact, since I only had limited space on the drive I was using, I deleted the old Vault on that external drive (I still had a parallel old vault available just in case) which is what gave me the room to build the AP3 vault.
    - After importing 12GB worth of RAW files, my attempt to update the vault was met with an error message saying I would need an additional 14GB of space. Without enough free drive space, I did not run the vault update.
    - After adding a larger external drive to my system, I ran the Vault from scratch, and it's actual size remains about 40GB.
    So I can only conclude that, as you evidently suspected, the error message was somehow wrong; that I did not in fact require an additional 14GB of space after all.
    Perhaps this falls under the same bug (er, undocumented feature) category as the one where when I attempt to e-mail versions, regardless of what settings I make in preferences, AP3 always generates full-size (i.e. - 14MB apiece) output. When I do a simple export, it works fine; it's only when I try to directly e-mail that it does this - seems to be another case of poor file size handling.
    I am not going to mark this question answered only because the original question remains - why did the error message warn me about a ridiculously large vault size increase when in fact it never happened? I suspect that the Vault warning simply looked blindly at the fact that I imported 12GB worth of images and somehow "assumed" they were managed files, even though they were referenced.

  • Paper Size issues with CreatePDF Desktop Printer

    Are there any known paper size issues with PDFs created using Acrobat.com's CreatePDF Desktop Printer?
    I've performed limited testing with a trial subscription, in preparation for a rollout to several clients.
    Standard paper size in this country is A4, not Letter.  The desktop printer was created manually on a Windows XP system following the instructions in document cpsid_86984.  MS Word was then used to print a Word document to the virtual printer.  Paper Size in Word's Page Setup was correctly set to A4.  However the resultant PDF file was Letter size, causing the top of each page to be truncated.
    I then looked at the Properties of the printer, and found that it was using an "HP Color LaserJet PS" driver (self-chosen by the printer install procedure).  Its Paper Size was also set to A4.  Word does override some printer driver settings, but in this case both the application and the printer were set to A4, so there should have been no issue.
    On a hunch, I then changed the CreatePDF printer driver to a Xerox Phaser, as suggested in the above Adobe document for other versions of Windows.  (Couldn't find the recommended "Xerox Phaser 6120 PS", so chose the 1235 PS model instead.)  After confirming that it too was set for A4, I repeated the test using the same Word document.  This time the result was fine.
    While I seem to have solved the issue on this occasion, I have not been able to do sufficient testing with a 5-PDF trial, and wish to avoid similar problems with the future live users, all of which use Word and A4 paper.  Any information or recommendations would be appreciated.  Also, is there any information available on the service's sensitivity to different printer drivers used with the CreatePDF's printer definition?  And can we assume that the alternative "Upload and Convert" procedure correctly selects output paper size from the settings of an uploaded document?
    PS - The newly-revised doc cpsid_86984 still seems to need further revising.  Vista and Windows 7 instructions have now been split.  I tried the new Vista instructions on a Vista SP2 PC and found that step 6 appears to be out of place - there was no provision to enter Adobe ID and password at this stage.  It appears that, as with XP and Win7, one must configure the printer after it is installed (and not just if changing the ID or password, as stated in the document).

    Thank you, Rebecca.
    The plot thickens a little, given that it was the same unaltered Word document that first created a letter-size PDF, but correctly created an A4-size PDF after the driver was changed from the HP Color Laser PS to a Xerox Phaser.  I thought that the answer may lie in your comment that "it'll get complicated if there is a particular driver selected in the process of manually installing the PDF desktop printer".  But that HP driver was not (consciously) selected - it became part of the printer definition when the manual install instructions were followed.
    However I haven't yet had a chance to try a different XP system, and given that you haven't been able to reproduce the issue (thank you for trying), I will assume for the time being that it might have been a spurious problem that won't recur.  I'll take your point about using the installer, though when the opportunity arises I might try to satisfy my cursed curiosity by experimenting further with the manual install.  If I come up with anything of interest, I'll post again.

  • Vault size smaller than Library

    I have 30k referenced photos (188 gb) with a Library size of 11 gb. The Vault size is only 1.7 gb! This makes me nervous. In the past, both have been about the same size. What is happening?? thank you

    Here is more detail: I started with a 7gb Library, with about 6gb of managed files and limited referenced files. I then brought in all of my old files with Import Folder into Project, which added 28k files. After that, the Library went to 16 gb (seems large!). Next I relocated the managed files out, about 6 gb, and the Library shrunk to 10 gb. I did a new Vault store and the Vault size shrunk from the original 7 gb to 1.7gb. I can also see along side of it the Deleted files, 6gb, of those moved out.
    If I look in the Vault at a given folder (from the Import Folder into Project), its size is 313mb; the same folder in the Library is 2.2 gb. Looking at a given imported project, Library has a folder of 17mb, AP.Minis of 41mb and AP.Thumb of 76mb. The same file in the Vault has a folder of 20 mb and several little 8k things. Clearly thumbnails were generated although Preview was turned off, and tested that I could not drag thumbs out.
    Hope this helps, thanks, gib

  • Smartcardio ResponseAPDU buffer size issue?

    Greetings All,
    I’ve been using the javax.smartcardio API to interface with smart cards for around a year now but I’ve recently come across an issue that may be beyond me. My issue is that I whenever I’m trying to extract a large data object from a smart card, I get a “javax.smartcardio.CardException: Could not obtain response” error.
    The data object I’m trying to extract from the card is around 12KB. I have noticed that if I send a GETRESPONSE APDU after this error occurs I get the last 5 KB of the object but the first 7 KB are gone. I do know that the GETRESPONSE dialogue is supposed to be sent by Java in the background where the responses are concatenated before being sent as a ResponseAPDU.
    At the same time, I am able to extract this data object from the card whenever I use other APDU tools or APIs, where I have oversight of the GETRESPONSE APDU interactions.
    Is it possible that the ResponseAPDU runs into buffer size issues? Is there a known workaround for this? Or am I doing something wrong?
    Any help would be greatly appreciated! Here is some code that will demonstrate this behavior:
    * test program
    import java.io.*;
    import java.util.*;
    import javax.smartcardio.*;
    import java.lang.String;
    public class GetDataTest{
        public void GetDataTest(){}
        public static void main(String[] args){
            try{
                byte[] aid = {(byte)0xA0, 0x00, 0x00, 0x03, 0x08, 0x00, 0x00};
                byte[] biometricDataID1 = {(byte)0x5C, (byte)0x03, (byte)0x5F, (byte)0xC1, (byte)0x08};
                byte[] biometricDataID2 = {(byte)0x5C, (byte)0x03, (byte)0x5F, (byte)0xC1, (byte)0x03};
                //get the first terminal
                TerminalFactory factory = TerminalFactory.getDefault();
                List<CardTerminal> terminals = factory.terminals().list();
                CardTerminal terminal = terminals.get(0);
                //establish a connection with the card
                Card card = terminal.connect("*");
                CardChannel channel = card.getBasicChannel();
                //select the card app
                select(channel, aid);
                //verify pin
                verify(channel);
                 * trouble occurs here
                 * error occurs only when extracting a large data object (~12KB) from card.
                 * works fine when used on other data objects, e.g. works with biometricDataID2
                 * (data object ~1Kb) and not biometricDataID1 (data object ~12Kb in size)
                //send a "GetData" command
                System.out.println("GETDATA Command");
                ResponseAPDU response = channel.transmit(new CommandAPDU(0x00, 0xCB, 0x3F, 0xFF, biometricDataID1));
                System.out.println(response);
                card.disconnect(false);
                return;
            }catch(Exception e){
                System.out.println(e);
            }finally{
                card.disconnect(false)
        }  

    Hello Tapatio,
    i was looking for a solution for my problem and i found your post, first i hope your answer
    so i am a begginer in card developpement, now am using javax.smartcardio, i can select the file i like to use,
    but the problem is : i can't read from it, i don't now exactly how to use hexa code
    i'm working with CCID Smart Card Reader as card reader and PayFlex as smart card,
              try {
                          TerminalFactory factory = TerminalFactory.getDefault();
                      List<CardTerminal> terminals = factory.terminals().list();
                      System.out.println("Terminals: " + terminals);
                      CardTerminal terminal = terminals.get(0);
                      if(terminal.isCardPresent())
                           System.out.println("carte presente");
                      else
                           System.out.println("carte absente");
                      Card card = terminal.connect("*");
                     CardChannel channel = card.getBasicChannel();
                     ResponseAPDU resp;
                     // this part select the DF
                     byte[] b = new byte[]{(byte)0x11, (byte)0x00} ;
                     CommandAPDU com = new CommandAPDU((byte)0x00, (byte)0xA4, (byte)0x00, (byte)0x00, b);
                     resp = channel.transmit(com);
                     System.out.println("Result: " + getHexString(resp.getBytes()));
                        //this part select the Data File
                     b = new byte[]{(byte)0x11, (byte)0x05} ;
                     com = new CommandAPDU((byte)0x00, (byte)0xA4, (byte)0x00, (byte)0x00, b);
                     System.out.println("CommandAPDU: " + getHexString(com.getBytes()));
                     resp = channel.transmit(com);
                     System.out.println("Result: " + getHexString(resp.getBytes()));
                     byte[] b1 = new byte[]{(byte)0x11, (byte)0x05} ;
                     com = new CommandAPDU((byte)0x00, (byte)0xB2, (byte)0x00, (byte)0x04, b1, (byte)0x0E); */
                        // the problem is that i don't now how to built a CommandAPDU to read from the file
                     System.out.println("CommandAPDU: " + getHexString(com.getBytes()));
                     resp = channel.transmit(com);
                     System.out.println("Result: " + getHexString(resp.getBytes()));
                      card.disconnect(false);
              } catch (Exception e) {
                   System.out.println("error " + e.getMessage());
              }read record : 00 A4 ....
    if you know how to do , i'm waiting for your answer

  • Recording File Size issue CS 5.5

    I am using CS 5.5, a Balckmagic Ultra Studio Pro through USB 3.0 being fed by a Roland HD Video switcher. Everything is set for 720P 60fps (59.94) and the Black Magic is using the Motion JPEG compression. I am trying to record our sermons live onto a Windows 7 machine with an Nvidia Ge-Force GTX 570, 16 GB of Ram and a 3TB internal raid array (3 drives). It usually works great but more often now when I push the stop button in the capture window, the video is not proceesed and becomes unusable. Is it a file size issue or what. I get nervous when my recording goes longer than 50 Minutes. Help

    Jim thank you for the response. I have been away and busy but getting
    caught up now.
    I do have all drives formatted as NTFS. My problem is so sporadic that I
    can not get a pattern down. This last Sunday recorded fine so we will see
    how long it last. Thanks again.

  • Swap size issues-Unable to install DB!!

    Unable to install DB. End part i am getting failed due to swap size issue .. FYI...
    [root@usr~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/hda2             5.9G  5.9G     0 100% /
    /dev/hda3             3.0G  848M  2.0G  31% /tmp
    /dev/hda5              34G   12G   21G  37% /refresh
    /dev/hda1              99M   12M   83M  12% /boot
    tmpfs                 3.9G     0  3.9G   0% /dev/shm
    [root@usr~]#
    Please help me...Thanks

    You can increase your swap space.. I have also faced same issue
    Just try: http://www.thegeekstuff.com/2010/08/how-to-add-swap-space/
    ~J

  • Unable to install DB(swap size issues)

    Unable to install DB. End part i am getting failed due to swap size issue .. FYI...
    [root@usr~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/hda2             5.9G  5.9G     0 100% /
    /dev/hda3             3.0G  848M  2.0G  31% /tmp
    /dev/hda5              34G   12G   21G  37% /refresh
    /dev/hda1              99M   12M   83M  12% /boot
    tmpfs                 3.9G     0  3.9G   0% /dev/shm
    [root@usr~]#
    Please help me...Thanks

    I tried with dd if=/dev/hda3 of=/dev/hda5 count=1024 bs=3097152
    Now the o/p is below ...
    [root@user/]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/hda2             5.9G  5.9G     0 100% /
    /dev/hda3              35G   33G  345M  99% /tmp
    /dev/hda5              34G   12G   21G  37% /refresh
    /dev/hda1              99M   12M   83M  12% /boot
    tmpfs                 3.9G     0  3.9G   0% /dev/shm
    [root@user/]# cd /tmp/

  • Vault size

    I have a large, referenced aperture library.  When I do "update all vaults" the file size is very small.  Is there any way for me to make sure that all of my projects are being backed up in the vault

    I'm guessing that the "Aperture Library" is in your Pictures folder and the Vault (default name: "Untitled Vault") is on a backup device. When you "Add" a vault it goes thru a dialog box where you picked its location. Otherwise, you can open the Vault pane at the lower left of the Aperture window and click the triangle to the left and it will show you the Vault's name and location.
    (Your next reply just popped up.)
    The size of the folder containing your original image files doesn't really matter here. (Bigger does mean a bigger Library and Vault but there is no specific formula I can offer.)
    The Aperture Library is databases with keywords, adjustments, etc., and image previews. Part of its size is determined by the Preferences setting (size and resolution) for your Preview images. They can let you organize but not adjust your images without the Masters being online.
    The Vault size will be similar to your Library size. Over time this relation may change.
    If you had a Managed Library, it would be 233GB plus databases plus previews. And the Vault would be a similar size.

  • Backup vault size

    My library seems to be growing larger and more rapidly than I would expect. I have about 28,000 photos. Most D200 jpegs about 5-6 GB, some older and smaller few thousand at 1-2 GB, about half -scanned slides and 35 mm about 8-10 GB. The vault size is 437 GB. Seems that on average I am using about 15 GB per photo. Recently I added 1118 scanned 35 mm avg 7-10 GB. They came on 3 DVDs - 1 about half full - est 11-12 GB of Jpeg data. I loaded them into Aperture and rebacked up vault and it grew by 45 GB - no other changes since last backup. I also back-up to an online archive and it sits on about 75 GB though files somewhat (smaller 3- 8 GB). When it approached my internal 500 GB drive capacity, I got a 750 GB drive added a few thousand images and tried to back up and got warning "insufficient disc space available". I still had about 300 of 698 GB available with vault size of 437 GB. I did determine that if you delete the vault and write a new one it will fit on a 500 or 750 drive. Any Help? Thanks.
    MacPro Qaud   Mac OS X (10.4.10)   4GB RAM, 30 CD

    I figured it out - thought I might share.
    It turns out that the previews generated at the highest quality for the 30" display are Huge Files. They are anywhere from 2-3X larger than the original file. Hard to believe? Original file 5.0 MB creates preview of 17.4 MB. This overall creates a database that is 3-4x larger than the imported images(including other misc control files). This can be fixed easily by reducing the quality of the preview down to 7, which corresponds to a file size of about 850 KB. Then regenerate the previews (control,option together with click, select generate previews). This can be done for batches, or the entire library. The quality changes was not really apparent. Hope this helps others avoid this situation.

  • Windows Update Helps with File Size Issues?

    I'm just wondering if anybody has recently noticed an
    improvement related to the file size issue variously reported
    throughout the forums?
    I ask because our IT folks distributed a Windows update on 2
    days last week and since the application of those updates I have
    not experienced the freakishly large file sizes and the related
    performance issues in Captivate. Unfortunately I don't have any of
    the details of what patch(es) were installed, as it was part of our
    boot script one morning and I didn't even realize it was updating
    until I received the Reboot Now or Later alert.
    Anyway, I was curious because I have experienced significant
    performance improvement since then.
    Rory

    If you are using a remote workflow ... designers are sending off-site editors InCopy Assignment packages (ICAPs) .... then they need to create assignments in order to package them for the remote InCopy user. So there's no need to split up a layout into smaller files or anything.  An assignment is a subset of the INDD file; multiple assignments -- each encompassing different pages or sections -- are created from the same INDD file.
    When the designer creates the assignment, have them turn off "Include original images in packages"; that should keep the file size down.
    Or -- like Bob said -- you can avoid the whole remote workflow/assignment package rigamarole all together by just keeping the file in a project folder in the Dropbox folder on teh designer's local hard drive, and have them share the project folder with the editors. In that workflow, editors open the INDD file on their local computer and check out stories, just as though they were opening them from a networked file server.
    I cover how the InCopy Dropbox workflow works in a tutorial video (within the Remote Workflows chapter) on Lynda.com here:
    http://www.lynda.com/tutorial/62220
    AM

  • Vault Size/contents ZERO

    I created a vault on an external drive, of my 89G Aperture Library.
    After it created the vault...the contents and size equaled that of the actual library.
    Start and restart Aperture and the Vault status icon is yellow, telling me there has been changes in my library, which there hasn't. So i go and check Vault size, and much to my dismay it says Zero bytes on disk and no package contents.
    I click update vault in aperture, does it's comparing for a bit, then finishes with no errors.
    Vault status icon is black (stating everything is up to date) but Vault is still Zero Bytes and no contents.
    Any ideas!?
    Thanks.
    kevin

    The vault should be smaller: no previews or thumbnails are stored in a vault. So that is odd.
    How are you measuring the size of the vault and library?
    How is your external drive formatted? If it is not HFS+ case insensitive then all bets are off. That is also called Mac OS Extended case insensitive.

  • What am I doing wrong - size issue

    Need some advice...as usual!
    I designed a site on my 17" monitor and set the margins to 0
    and table to 100%. However when I look at it on different screens
    it looks rubbish...big gap at the bottom of the page with the
    design cramp at the top. I wonder if someone would mind looking at
    my code and see what's wrong with it. The site was designed using
    various techniques including css for nav bars, tables, and
    fireworks elements. the site can be viewed at:
    www.shelleyhadler.co.uk/nerja.html
    thanks for your help. Shell

    >Re: What ams I doing wrong - size issue.
    Several things...
    First, your 17" monitor has noting to do with web page
    layout. What
    resolution is your monitor set to? it could be 800 pixels
    wide or 1280
    pixels... wouldn't that make a difference? That aside, screen
    resolution and
    size are irrelevant anyway. What counts it eh size that your
    viewers have
    their web browser window set at.
    I have a pretty large monitor, set to a very high resolution,
    so I open
    several windows at once and size them so I can see the
    content in all.
    Sometimes my browser is full screen and sometimes its shrunk
    down to less
    than 600 x 800. Your web site needs to accommodate that.
    Every web viewer
    out there is different and likes the way they have their
    screens set up. So
    you need to be flexible and your site needs to be flexible.
    Next, Don't design in Fireworks and import to Dreamweaver.
    Fireworks is a
    superb web ready graphics and imaging processing program. The
    authors
    (mistakenly) threw in some web authoring stuff that works
    very poorly.
    Design your pages using Dreamweaver. Learn html markup and
    css styling to
    arrange it, then use Fireworks to create graphics to support
    your content.
    Along the way, be aware of the diffferant browsers in use.
    Internet
    Explorer is the most popular (or at least most in use) simply
    by virtue of
    the Microsoft market share, but it is also the least web
    complient (by virue
    of the Microsoft arrogance) so some things that work there,
    (like your green
    bands) won't on other browsers and vice versa.
    That said... graphically, your site looks great. You have a
    good eye for
    composition and simple clean design. You just need to learn
    to use html to
    your best advantage to create some realy nice looking and
    nicely working
    sites.
    "shelleyfish" <[email protected]> wrote in
    message
    news:[email protected]...
    > Need some advice...as usual!
    >
    > I designed a site on my 17" monitor and set the margins
    to 0 and table to
    > 100%. However when I look at it on different screens it
    looks
    > rubbish...big
    > gap at the bottom of the page with the design cramp at
    the top. I wonder
    > if
    > someone would mind looking at my code and see what's
    wrong with it. The
    > site
    > was designed using various techniques including css for
    nav bars, tables,
    > and
    > fireworks elements. the site can be viewed at:
    >
    > www.shelleyhadler.co.uk/nerja.html
    >
    > thanks for your help. Shell
    >

  • VAULT size is smaller than the LIBRARY

    my vault size is smaller than the aperture library.  is it saving everything?  it seems like the two should be the same size or at least close to the same size.  i regularly update my vault so that it is current with the library.  VAULT = 168 GB | LIBRARY = 262 GB

    what is the consequence if i totally turn previews off?
    The major consequence is that you will not be able to share images from your library through the media browser. So if you want to email an image for example or add an image to a document you will need to export the image first rather then be able to get the preview from the library.
    Also if you have referenced originals and the originals go off-line nothing will appear in the library. If you had previews for those images you would still see them and be able to do tasks like rate them.
    Finally some operations might appear slower as you won;t see anything on the scree until the image you are looking at is rendered. With previews while Aperture is rendering the image in the background it will display the preview.
    It is possible to selectively maintain previews for some projects and not for others. This might be a comprise position between having previews for al images and having no previews at all.

Maybe you are looking for