Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

size limit on 1.3???

Comments

14 comments

  • rmoorlag
    There is nothing in the releasenotes about the limits so i think the 128.000 file limit is still there.
    Also there is a database limit of 4 Gb (was before 1.8 Gb in Expression Media), also not resolved...
    You can find the releasenotes in the download section under the green download 'button'.
    Roelof
    0
  • Sausalito
    Thanks, I read the release notes and could only find the reference to large file fixes.

    I'm hoping someone from phase one or a beta tester can chime in and tell us what the large file fixes did - hopefully allowing more than 128k

    Cheers,

    Tom
    0
  • Jim MSP
    The release notes read "Many optimizations and improvements to handling of large catalogs."

    I just asked service support if this means I can put my catalogs back together and exceed the 4Gb limit I hit recently. I had previously filed a support case on this.
    0
  • Eldor
    Buried in the online help file (hard to find unless you know the exact search term) is the statement that a catalog file is limited in size to 1.8gb. That's with the latest 1.3 version of Media Pro.

    I found it by accident (you'd think there would be some page in the help where the limits of the program are specified) and now I figure that limit is the cause of the problems and frustrations I've been having with the program. My catalog is now 3gb in size and the spinning gear in the bottom right of the status bar just spins and spins and spins and nothing happens even if I leave it for hours.

    As much as I want to like this program, I feel it's really not ready for prime time yet. SIGH
    0
  • Sausalito
    Eldor-

    You CAN solve that problem by breaking up your catalog. I resisted it and resisted it, but finally did it and now no spinning gear etc. The draw back is that you have to open more than one catalog to search your whole data base...not something I really needed every time since many searches you know in advance to be more limited, but I still need that often enough that the limit is confining and irritating.

    Tom
    0
  • Jim MSP
    [quote="Eldor" wrote:
    Buried in the online help file (hard to find unless you know the exact search term) is the statement that a catalog file is limited in size to 1.8gb. That's with the latest 1.3 version of Media Pro.
    .... My catalog is now 3gb in size and the spinning gear in the bottom right of the status bar just spins and spins and spins and nothing happens even if I leave it for hours.
    As much as I want to like this program, I feel it's really not ready for prime time yet. SIGH


    I guess I don't believe that the "spinning ball " is an issue -- at least on the Windows side of the world. I have two catalogs now, one that is 2.8Gb and the other that is 3.6. Both seem to run well now. I have learned to ignore the spinning ball. I just expand the action window by hitting the lower right + icon. When that shows activity (rebuilds, saves, etc) I know not to do much else or I could hang up the program.

    So, unless I hear something back from service within the next day, I may try combining my catalogs and see if the 4Gb limit is gone.
    0
  • Jim MSP
    I heard nothing from Phase One support as of this am, so I went ahead and tried it.

    The catalog size limit of 4 Gb appears to have been solved/changed.

    I just successfully merged my previously split catalogs back into one, which is now 4.7Gb (smaller than the sum of the parts). The long file names as seen in the Catalog Folders now all appear just fine.

    There were a few start up problems - I had a couple of crashes after merging and saving, resulting in a locked catalog. However, after a couple of go arounds, including adding some new key words, and rebuilding a few photos, followed by a resave - everything seems to be ok.

    This says nothing about a single file size. My large Tiffs and PSDs (120-130M) all seem to be fine, though I have not looked at them systematically.
    0
  • Eldor
    Thanks for the update, Jim. Funny though that the latest help file for 1.3 says there is a 1.8gb limit on catalog size.

    The action window doesn't usually (in my case) show anything going on. I'll check (maybe, if I'm not too frustrated with MP) tonight when I get to my main computer and database. I'm unable to get any kind of preview for my TIFF files though (these are TIFF files from the original Canon 1D, which is what that model called their RAW files) and get a message that rendering for these files is disabled. But I can't for the life of me find any place where I can ENable that.

    Also I have a bunch of Canon CR2 raw files (from various Canon models) and on some of them I also cannot get more than a small thumbnail preview. No matter how many times I try to update or rebuild the preview.

    Gee, I just thought of something regarding those CR2 files... I'll check it tonight but it's possible that this problem is only with the CR2 files from the relatively new Canon 5D Mark III. And that files from earlier models are fine. I'll confirm tonight.

    And is it possible that those original Canon 1D files (TIFF) are simply not supported by MP? (iMatch and Lightroom AND C1Pro all support them just fine.)

    Cheers!
    0
  • Sausalito
    That sounds good as to size, Eldor...thanks.

    BTW, how MANY files are in your 4.7gb?

    My reunited catalog would be under the 4gb limit but would be a bit over (and growing) the 128,000 limit.

    thanks,

    Tom
    0
  • Jim MSP
    [quote="Sausalito" wrote:
    ..

    BTW, how MANY files are in your 4.7gb?

    My reunited catalog would be under the 4gb limit but would be a bit over (and growing) the 128,000 limit.
    ....


    I have 57,300 files in my catalog that is 4.7Gb in size.
    More than 1/2 of them are Canon raw files.

    Jim
    0
  • Sausalito
    Thanks, I'm still worried about the 128,000 limit.

    Half my files are Nikon nef files, so you must be storing larger thumbnails than I am.

    My two catalogs combined are only 1.2 gb

    Tom
    0
  • Jim MSP
    [quote="Sausalito" wrote:
    Thanks, I'm still worried about the 128,000 limit.

    Half my files are Nikon nef files, so you must be storing larger thumbnails than I am.

    My two catalogs combined are only 1.2 gb

    Tom


    I probably am. My thumbnail preferences are 640 with high quality
    My media preview are 1024 with Medium quality.

    Jim
    0
  • imaginatian
    Hi,

    Using the "Import Items from Catalog File..." option I have just imported my year by year catalogs into a single new file.

    The images are jpgs, and are actually all off-line. The thumbnail size is 640, medium quality. There is no preview.

    I now have 183405 images in this catalog. At the bottom left MediaPro reports that the size of this catalog is 7GB. However the actual file size in Explorer is 5.26GB. This is a fraction bigger than the individual year based files, which according to Explorer come in at 5.25GB.

    Note that at the moment I won't be keeping this catalog and working with it from now on. There are a couple of reasons for this. The first is that the performance of the catalog is slowler. It's still usable, just not as quick to respond to filters and searches. This shouldn't be a surprise as my previous largest year catalog had just 36445 images in it. The second reason is the file size. I use SyncBack Pro and have set up profiles to backup changed files to external hard drives. If I work on a single catalog then at the most I have to backup around 1GB of "changed" data. This is a lot quicker than backing up 5.25GB! As I usually backup before shutting down my computer I don't really want to add a couple more minutes to this process.


    One thing I have spotted which is "new", or at least I haven't seen in Phase One's so called documentation, is that when these images were being imported the Catalog Sets associated with the images were converted in to Hierarchical Keywords. The Catalog Sets are still there, so there's duplication of data. This would explain some of the slower performance. Now I don't really want this to happen as I consider Keywords to be "public" and Catalog Sets to be "private" data. I can easily strip this information out but it's an extra step. Also this information doesn't appear to be stored in the keywords, at least when I export to XML. In fact is is sort of duplicated under a new Catalog Set called @Keywords. Hopefully this won't mess up all my scripts that make use of an XML export.

    I'm running on a laptop with Windows 7 (64 bit) with 4GB of memory.

    Ian
    0
  • Sausalito
    That's good news...thanks for sharing it.

    I don't know anything about sync back pro, but you might look into DropBox - it is very fast as they have some technology that looks at you files and only changes the parts of them that have changed. My 1gb catalog is much smaller than yours, but changes to it might not be and it is nearly instant most of the time.

    Tom
    0

Post is closed for comments.