Author Topic: PM suddenly not working properly after using new CF reader  (Read 4384 times)

Offline photobear

  • Newcomer
  • *
  • Posts: 25
    • View Profile
PM suddenly not working properly after using new CF reader
« on: August 10, 2016, 07:49:05 AM »
I am running Photo Mechanic Version 5.0, build 17671 (4483a36) with a 2015 Macbook Pro, with El Capitan 10.11.6. When I used a no-name CF reader for the first time, The Mac "Photo" app opened. I finally got it go back to launching PM, and resumed using my regular lexar card reader. The problem is, now all of a sudden PM is not giving the "beep" upon ingest completion, it isn't automatically unmounting the source disk after ingest, and it is no longer creating a dated folder on my desktop.

Any suggestions on how to fix this?
« Last Edit: August 10, 2016, 08:04:24 AM by photobear »

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: PM suddenly not working properly after using new CF reader
« Reply #1 on: August 10, 2016, 09:12:45 AM »
Are there any error messages in the Ingest Progress window?

I'd like to see your Photo Mechanic log.  In Photo Mechanic go to the Help menu and choose "Reveal Support Data..." and moments later a Finder window will come forward with the zipped log file selected.  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your zipped PM log file.

Thanks,

-Kirk

Offline photobear

  • Newcomer
  • *
  • Posts: 25
    • View Profile
Re: PM suddenly not working properly after using new CF reader
« Reply #2 on: August 10, 2016, 09:33:23 AM »
No error messages. Log attached.

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: PM suddenly not working properly after using new CF reader
« Reply #3 on: August 10, 2016, 01:35:27 PM »
No error messages. Log attached.

I have been informed by our support staff that this problem has been solved, is that correct?

Thanks,

-Kirk