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. ⚠️

MediaPro In Perfect Environment, Still Fails

Comments

8 comments

  • Bob6
    All of our computers, and all of our catalogs, working local or over the network, all experience the exact same issues. We are not able to work for any length of time reliably. This is even with a NEW Catalog, it can crash or behave strangely within minutes of creating it.

    As stated, I ran my most recent tests on two Mac Mini's, and 2 external drives. Specs Below:

    Creating New JPG Only Catalogs (JPGs created with CaptureOne v6.x, no compression)

    2013 MacMini, Osx 10.8.4, 8gb RAM
    MediaPro v1.4.1
    Purchased 1 month ago, ran through Drive Genius Burn In, and hours of reliable network copying of image files.

    2011 MacMini, Osx 10.8.4, 16gb RAM
    MediaPro v1.4.1
    Very reliable workhorse. OS Reinstalled about 2-3 months ago.

    LaCie 500gb Rugged Firewire 800 drive
    OWC 1TB Rugged Firewire 800 drive
    Both drives tested with Drive Genius 3, no bad blocks found. All images otherwise catalog and open properly.


    I mixed and matched drives, databases, and had the external drives local and networked. We need to work off external drives, due to the large amount of JPGs we use. Also, we need to take them on the road for Photoshoots.

    PLEASE NOTE: We have had all these problems and more, over the past 2 years on all of our systems. Most often used locally with a 2012 MacBookPro, OSX 10.7.x 8GB Ram.

    I tried to create NEW Catalogs. I simply wanted to isolate my problems, and make this work. I either needed to work in very small groups of 1,000-2,000 or MediaPro would crash if I tried to use larger batches. We have a high volume studio, and this becomes impractical.

    Out in the field, the Photographer uses .CR2 Raw Files from Canon Cameras EOS-1D x and EOS- 1D Mark IV with the same mixed results.
    0
  • rmoorlag
    I can not help you on this and i'm affraid Phase One will not either...
    So, good luck!
    0
  • NNN634263157773796913
    I read your posts with great disappointment. I am in no way at the level you are with Media Pro but as a long time user of iView I am constantly disappointed in Phase One's Media Pro. It is so frustrating that the program very often freezes just trying to open the app directly or a catalog. I find myself constantly going back to iView (I'm using Snow Leopard).

    I am very fearful of using it's tools for fear that all will be lost. I hope that there is someone in that company that will take the responsibility of answering our questions and fixing these problems.
    0
  • H. Cremers
    I am not overly sure why you are so disappointed. Sure, the fact that it doesn't work for you is disappointing.

    But i am getting the feeling that the OP is running the library off of a network drive. Media Pro is not meant for that. Also, he states he runs (or works in) a high volume studio, Media Pro is not meant for that.

    While i would like all these things as well and then some, Media Pro was not designed to do that. it is a desktop DAM for personal use, whether professional or amateur.

    When you need high volume (read enterprise level), networked (read enterprise level) DAM, then you'd better look elsewhere.

    If the OP's studio is not employing too many people, perhaps Daminion may help, otherwise it's one of the paid for DAMs like Extensis etc., or one of the open source DAMs like Nuxeo, Razuna, etc.

    These are indeed intended for and designed to be used across (large) networks and accessed (simultaneously) by many users. Of course, then you won't have any integration with your CO7 edits anymore.
    0
  • NN634848743872730260UL
    Thanks for this. I gather from this reply that Media Pro is not meant for networked, enteprise-level DAM. We're having lots of issues with Media Pro. Thumbnails disappearing, wierd duplicates appearing out of nowhere, new files being generated on the network that were not generated by the user (so they say), crashing. I'm surprised Media Pro doesn't officially state this software is not for this purpose. I have to call to get the official scoop so we can consider other alternatives such as what you mentioned.

    Thanks. Al
    [quote="HCS" wrote:
    I am not overly sure why you are so disappointed. Sure, the fact that it doesn't work for you is disappointing.

    But i am getting the feeling that the OP is running the library off of a network drive. Media Pro is not meant for that. Also, he states he runs (or works in) a high volume studio, Media Pro is not meant for that.

    While i would like all these things as well and then some, Media Pro was not designed to do that. it is a desktop DAM for personal use, whether professional or amateur.

    When you need high volume (read enterprise level), networked (read enterprise level) DAM, then you'd better look elsewhere.

    If the OP's studio is not employing too many people, perhaps Daminion may help, otherwise it's one of the paid for DAMs like Extensis etc., or one of the open source DAMs like Nuxeo, Razuna, etc.

    These are indeed intended for and designed to be used across (large) networks and accessed (simultaneously) by many users. Of course, then you won't have any integration with your CO7 edits anymore.
    0
  • H. Cremers
    [quote="NN634848743872730260UL" wrote:
    Thanks for this. I gather from this reply that Media Pro is not meant for networked, enteprise-level DAM. We're having lots of issues with Media Pro. Thumbnails disappearing, wierd duplicates appearing out of nowhere, new files being generated on the network that were not generated by the user (so they say), crashing. I'm surprised Media Pro doesn't officially state this software is not for this purpose. I have to call to get the official scoop so we can consider other alternatives such as what you mentioned.

    Thanks. Al


    This, to me, seems like concurrency problems. If more than one person has the catalog open and makes updates, which typically happens in a network situation, the database will seem to be updated "out of the blue". This is exactly one of those enterprise functions for which Media Pro (nor any of its earlier incarnations) had been designed for.

    Why some of the other stuff happens to your catalog, i don't know (i saw your other post), we'd need more info and also other people to chime in.
    0
  • Nick
    Interesting thread. Wish the product documentation was upfront about not running over a network. Seems reasonable to want to access a catalog from more than one machine. Can't bring the desktop on the road.

    I have a small 444MB catalog with 3500 images and found a workaround. There is probably a MAC equivalent to the Windows workaround (I wouldn't know though). For desktop machines, I use Windows' offline files with auto sync for the catalog file and then break the network connection just before opening the file. That speeds things up considerably and allows server storage.

    There are still bugs working locally on my small catalog file. The primary bug I encounter is frequent intermittent freezes lasting ~ 12 seconds. That seems OS specific since it does not occur on the old XP machine. Windows 7 x64 (2 machines) has a huge problem with that. XP also handles reading a networked file much better, as when I forget to break the connection. Just a nervous 45 sec save due to file size. Yes a corrupt db is probably in my future 😊
    0
  • NNN634550888500443360
    I too am a long-time user of iView, since the very first version. I've used nearly every version since then, including when it was Expression Media.

    Sadly, I find myself waiting for the product to return to what it once was.

    I've finally given up on Media Pro. It is far too unstable to use for real work. Most of the things I attempt to do result in crashes. I find myself tip-toeing around sensitive areas and saving constantly (which can be very slow on a large catalog with many previews).

    I really wish it could be like it was in the iView days. I have lots of custom Applescripts that I wrote over the years to accelerate my workflow. iView was even the reason I learned Applescript! But the current state of the software is unusable. Given how few updates there have been since 1.4.1 was released (what was it, June of last year?), I have regretfully lost hope. This was money wasted, I'm sad to say.

    John
    0

Post is closed for comments.