メインコンテンツへスキップ

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

>128,000 file catalogs not working out

NN231363UL
I've been playing with the new release and despite the advertised ability of being able to create catalogs with more than 128,000 files I'm finding that catalogs right up to 128,000 files work just fine, but adding any more files than that will cause strange behavior - the extra files won't have thumbnails generated and the file size and pixel size info in the list view will either be absent or have completely bogus data reported. Also the catalog and media size reported in the status bar will start to change wildly and either scale down to 0 or even into negative values. Sometimes when adding the extra images, MP1 will simply crash, with no data available in the crash reporter. This is a new installation on a machine that has never had Expression Media 2 installed so I know it's not a matter of old prefs interfering.

The expanded catalog size was one of the specific features I was looking for so I hope that can get fixed soon. I'd be happy to provide any additional info although as I say, the crash reporter doesn't seem to be picking up any telemetry from the crashes.

Thx, Mike
0

コメント

14件のコメント

日付 投票
  • rmoorlag
    Hello Mike,

    Did you logged a support call for this?
    Peter Krogh tested this and he was succesfull: .
    You can see his screenshot of 124.000 images in a 3Gb catalog, so it should work.

    Roelof
    0
  • NN231363UL
    As I said, 128,000 files seems to be the cap. I'd like to see how Peter fares if he adds another 4001 files to his catalog. FYI, I'm interested in tracking and comparing on the order of 1-4 million files if possible.

    Thanks, Mike
    0
  • rmoorlag
    I should have to make test images to reproduce this becouse i have only 70.000 images (1,5 Gb catalog).
    Despite of how interesting such a test would be, i do not have the time right now.
    Someone else maybe with enough images on the shelf?
    Roelof
    0
  • imaginatian
    Everything that follows has the proviso that it didn't work for me, running Media Pro on a slow and old Windows XP (SP3) desktop.

    OK, I have enough images to test this. Started with an empty catalogue and then "Imported from File" my yearly based catalogues. However this wouldn't work for .ivc files so each year catalogue was opened and re-saved in the new format. These catalogues are of JPGs only and contain only medium quality thumbails that are 320px in size i.e. no previews of any sort - the actual images are on the same computer so no point in having them. I have equivalent catalogues of DNG files, which may or may not be online, but the JPG's are more for my laptop.

    The first couple of imports were fairly "quick", maybe 25 images or so per second. However once the new catalogue got up to around the 50,000 image mark the import speed had halved. I couldn't tell you the final speed as it was beer o'clock when I did this late last night! I got as far as the final import before going to bed and woke up to find it had been the straw that broke the camels back! There was a "Please tell Microsoft..." pop-up window.

    The good news was that the auto-save feature had left me with a viable catalogue only a few hundred images short of breaking point. I managed to manually add images until I got to 127,999 and saved this catalogue. This file is 3.09GB in size and not the 3.9GB shown on screen. I then added another image. This was "accepted" but it wasn't rendered.

    http://imaginatian.com/xMedia_images/MediaPro128000.PNG

    I then added the 128,001st image. It was just a wafer thin image but, like for Mr Creosote, it was too much - although fortunately a lot less messy!

    http://imaginatian.com/xMedia_images/MediaPro128001.PNG

    So for me large catalogues don't work in MediaPro. However personally it doesn't really matter. I've had this problem with iView since mid 2010 and had plenty of time to prepare for it so had moved to year based catalogues. This was better anyway for performance reasons and with my images I don't have to do much cross-catalogue searching. Would I use it if it did work? Probably not. I don't change my older catalogues that much so my incremental backup scripts run faster as they have less to do. My current 2011 catalogue is almost 400MB and much more manageable than a 4GB file would be. Aside from the physical file size the performance would have to be a lot better than it currently is, i.e. speed wise MediaPro is a lot worse than iView MediaPro on my hardware, especially as the catalogue size increases.

    Hope this helps.

    Ian
    0
  • NNN634272722125339672
    ^^^ Good thing you blocked out her FACE! 😁
    0
  • NN231363UL
    As far as performance, backups, and more importantly, delivering on an advertised feature 😊, perhaps it's not too late to introduce a bundle format for the database files?
    0
  • Jim MSP
    [quote="NN231363UL" wrote:
    As far as performance, backups, and more importantly, delivering on an advertised feature 😊, perhaps it's not too late to introduce a bundle format for the database files?

    In order of importance for me:
    Performance (esp speed of rendering RAW media)
    Reliability (for what the final feature set and allowed sizes are)
    DB size (I'll live with multiple catalogs IF this is the only limitation)
    0
  • Wade Mattson
    I must say that though a large catalog size would be nice, I would have to say I'd probably end up making specific catalogs for the various types of photography I do, as well as yearly catalogs with all subjects together.. Though as a searchable data base then its most logical to have all images together.. Maybe a search funtion that can work over several catalogs would be the answer.. The search could return the found items to the active catalog..

    Brent
    0
  • NN231363UL
    That would also be acceptable, as long as the image comparison function (Find->Show Similar...) worked across catalogs in addition to the other EXIF search functions. From a logical standpoint though, simply providing the framework to index a (virtually) unlimited amount of objects shouldn't be that hard - pro database systems and filesystems do it all the time, some better than others of course. The only other obstacle would then be the actual size of the database itself, which as I mentioned could be overcome by using a bundle format.
    0
  • rmoorlag
    Maybe a search funtion that can work over several catalogs would be the answer

    Searching within all Open catalogs is standard functionality of EM2 and MP1...
    http://dl.dropbox.com/u/25580003/FindScreen.png
    Roelof
    0
  • NN231363UL
    That's good - though I still want to be able to compare many images across several different locations so if this functionality could be introduced for the Show Similar command, that would be a viable solution.
    0
  • Sausalito
    [quote="imaginatian" wrote:
    Everything that follows has the proviso that it didn't work for me, running Media Pro on a slow and old Windows XP (SP3) desktop.



    The good news was that the auto-save feature had left me with a viable catalogue only a few hundred images short of breaking point. I managed to manually add images until I got to 127,999 and saved this catalogue. This file is 3.09GB in size and not the 3.9GB shown on screen. I then added another image. This was "accepted" but it wasn't rendered.


    Hope this helps.

    Ian



    Ian -

    I'm using a mac if that makes any difference, but I have nearly 125, 000 files and the whole db is only 1.3gb. Why would yours be so much larger? and is that part of the problem???

    tom
    0
  • rmoorlag
    I'm using a mac if that makes any difference, but I have nearly 125, 000 files and the whole db is only 1.3gb. Why would yours be so much larger? and is that part of the problem???


    The number of images is not the only thing that had impact on the size of the database. The 'Thumbnails & Preview' settings do have a bigger impact than the number of images i.e.

    Roelof
    0
  • rmoorlag
    I found the same boundary on 128.000 files in a catalog on Win 7 32 bit.
    MP1 does show strange behaviour when you cross that number. You can see it on this video:

    At the beginning you can see under 'catalog folders' that the number is counting 128.011 but at 1 min 41 sec the number is suddenly 127.900. The only thing i did was rebuilding the last imported set (5) images. However, the thumbnail is not building up and the images can not be opened.

    I will post a supportcall for this. Phase One promised this would be one of the improvements compared to EM2...

    Roelof
    0

投稿コメントは受け付けていません。