Hi Kirk, and again thanks for your reply.
About the IPTC binary failure; No, there are always fields applied.
Having used PM since the beginning, the possibility of having most to all of what is needed for the IPTC section preloaded was one of the biggest draws to PM... And of course the blazing speed ;-} and in my world speed has become the overriding factor.
So there is really isn't any ingest that doesn't have multiple fields filled in.
About the upload issues; Unfortunately this is happening over multiple connections/locations all solid... Some even darn good sooo.
Not my first rodeo, and while I'm not an engineer I did recognize a number of the responses. I have tried to pass this along to the powers that be, but...
Unfortunately one of the recent cutbacks was a full-time data guru that could live troubleshoot such things. I would be interested to know if you think there was one(or more of the responses) that seemed more likely to be directly related. The more precise I can be with any suggestions, the better.
The fact that some files get sent, and then full stop, makes it way to easy to make the the nut behind the wheel the scapegoat, and ignore the problem, which only happens with files that throw the IPTC binary failure fault and in PM.
I have been forced to drop PM for the time being
and use Bridge & Filezilla... Which while it works, just doesn't cut it. At all. Or use Shuttersnitch on the Ipad which has been a bit finicky with swapping connections(an Ipad issue, not Snitch) ...and hope that Fujifilm get the FTP from camera bit sorted. Soon.
Really need to get PM back to normal, but I'm beginning to fear this might be another bizarre issue with Win 10 and some server-side update. Help!
Also PM has never generated debug.log files in this way before. Something new, or symptomatic of these other issues?
Thanks,
Ned
