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

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

New Bugs In Media Pro

Paul Silk
Looks like they introduced new bugs in ver 1.4 when fixing ver 1.3!

If you select more than one image to add the same title to you cannot enter it, it just stays there highlighted.

http://www.pbase.com/paulsilkphotography/image/148960319.jpg

Then if you click off them to another image the title you entered is then transfered to that images rating and does so to every image you click on.
http://www.pbase.com/paulsilkphotography/image/148960320.jpg

Once you close the program down and reopen it everything rights itself but it's damn annoying.

Also now when you use the light table and press the escape button to exit it the program crashes every time.

So my question is, who are these beta testers and do they actually use the software like us mortal folks? 🤓
0

コメント

6件のコメント

日付 投票
  • Jim MSP
    [quote="Paul Silk" wrote:
    Looks like they introduced new bugs in ver 1.4 when fixing ver 1.3!

    ........

    Also now when you use the light table and press the escape button to exit it the program crashes every time.

    So my question is, who are these beta testers and do they actually use the software like us mortal folks? 🤓


    Yes, I just verified the esc button error.
    I have tended to just x out the window, as I stick it on my 2nd monitor.
    But hit Esc - and down it goes.
    0
  • ohkitsune
    doesn't crash on my Mac. Paul are you a Windows person? pretty sure Jim MSP is.
    while it still does weird things sometimes, it may be my imagination but 1.4 seems a little faster than 1.3.
    0
  • Jim MSP
    [quote="ohkitsune" wrote:
    doesn't crash on my Mac. Paul are you a Windows person? pretty sure Jim MSP is.
    while it still does weird things sometimes, it may be my imagination but 1.4 seems a little faster than 1.3.


    Yes, I am only on Windows.

    Re faster - I think it is also.
    I tend to load the load the photos initially with rendering using the Windows WIC. That is very fast.
    I then render only the ones I process in CO with the CO engine. And that seems faster than the CO 6 rendering
    0
  • Pascal Costes
    I confirm, no problem on mac.
    0
  • Thomas Günther
    I have to confirm that 1.4 does it's way down from from EM2 with every new "fix" release!
    I use MP as well as COne on Mountain Lion as well as Win7 and 8.

    While the 1.4x version were buggy regarding the use of the 32bit importers and caused my system sometimes crashed before even a catalogue was opened, now the core seem often to run stable, but the rest went down to a level much below zero.

    --- ISO data in the exif were not read/written out in a way that COne was able to process and indicate them
    --- no proper implementation of proper character sets & there is no way to tell MP (and COne) which "proper" and persistent use of any character set ca be established
    --- in contrary to former releases, now they made some new in that way: all vocabularies, metatdata, keywords, etc are gone with the wind. I HIGHLY RECOMMEND ALL USERS TO BACKUP ALL METADATA, SCRIPTS, KEYWORDS ETC THAT ARE USED TO COPY , BECAUSE ALL DATA ARE GONE AFTER THE INSTALLATION OF MP1.4
    --- in contrary to the former releases of MP as well as with EM2 and iView, it now is IMPOSSIBLE to synchronize the metatdata with the files.
    (I DON'T USE SIDECAR-FILES and will hopefully never do so for my workflow). Every bit that is added with MP 1.4 to a pictures is gone, once the picture is opened with another piece of software. This more than a PITA!
    the following filetypes, besides jpg, png, tiff, are affected:
    - Canon RAW
    - Nikon RAW
    - Sony RAW
    - Panasonic RAW
    - Leica DNG
    regarding this MP is becoming at least useless because it mw can only be used as a simple importer, like e.g. Nikon Transfer, but Nikon grants this tool/functionality to its users/customers and does not charge them around 150€ (like POne does for a more or less useless piece of whopped together code-fragmnets).

    While, as mentioned above, especially the importers from MP caused file and system corruption with continuously allocating RAM and NOT freeing it, until every allocatable bit is inactive/used and causes the system to a halt via buffer-overflow, now this behavior is still masked and will be indicated not as inactive/allocated RAM, but will increase the resources allocated to MP - the effect is the same: causes crashes and kernel-panic. Was this stuff coded in Bangladesh or Burkina Faso with high potentials form that places?
    What is MediaImporter and its behavior in MP, is the usage of core picture server in COne. All messy and together unusable!

    The collaboration with COne still does not work as promoted and (hopefully) intended.
    While iView/EM2/MP until 1.3 could be used as a DAM, which follows it's naming,now it seems that all capabilities that are needed and were the reason to go with MP are now stripped from the software, because COne cannot handle theses informations.

    I stopped MP sending the crash reports to POne, because the logs are too huge and arise too often per day (>10 times!)

    As well that MP usually could be used as the primary instance to start the workflow from the camera, now it became a real cul de sac and can reasonably only be used as a BACK-end to COne.

    Has anyone ever tried to use COne to do the metadata work - and afterward process the results in MP? Apparently the development team DID NOT.

    Conclusion:
    I deleted MP 1.4, remain with 1.3.2, and will look forward, which jokes will be implemented with release 1.5!

    saludos redondos -
    tom
    0
  • Paul Silk
    I'm just about done with Phase One, a bug that was fixed previously has now reappeared in the latest update and how many more will I find.

    When you transfer files using the the transfer files action the xmp sidecar files are left behind in the original folder..really you fixed this once Phase One, one step forward and two back!

    Syncing annotations does not always work, it still sometimes hangs onto memory when you shut it down and have to use the task manger to make it stop, plus a lot of more annoying things I have discovered that I just cannot be bothered to list.
    0

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