MicrostockGroup

Agency Based Discussion => iStockPhoto.com => Topic started by: Mancubus on February 28, 2017, 08:47

Title: Vector file problems after DeepMeta3 upload
Post by: Mancubus on February 28, 2017, 08:47
Hi all

I have some issue depending the upload with DeepMeta3 and Vector files.

Generally the upload process itself works fine with DeepMeta3.
I always upload eps+jpeg (high res) files and they always gonna be queued for the getty reviser.

But: After the files are checked and approved, I receive the following messages:
The ESP system says "NEEDS REVISE".

To fix this, I have to login myself into the ESP system and choose the right batch and add the JPEG files manually again to every vector file. The system/reviser message says, that the jpeg files are broken and I have to re-upload them.

This problem concerns _EVERY_ vector upload I make with DeepMeta3.

Is this problem already known?
Any hints?

Maybe I'm doing something wrong. ;-)
Title: Re: Vector file problems after DeepMeta3 upload
Post by: FrankyDM on March 01, 2017, 01:01
Hi all

I have some issue depending the upload with DeepMeta3 and Vector files.

Generally the upload process itself works fine with DeepMeta3.
I always upload eps+jpeg (high res) files and they always gonna be queued for the getty reviser.

But: After the files are checked and approved, I receive the following messages:
The ESP system says "NEEDS REVISE".

To fix this, I have to login myself into the ESP system and choose the right batch and add the JPEG files manually again to every vector file. The system/reviser message says, that the jpeg files are broken and I have to re-upload them.

This problem concerns _EVERY_ vector upload I make with DeepMeta3.

Is this problem already known?
Any hints?

Maybe I'm doing something wrong. ;-)

You're not doing something wrong ;)

There have been issues with Illustration uploads over the past few weeks.

As author of the DeepMeta software, I've reported this to the Getty developer team and got feedback that indeed there were issues with thumbnails last week. These should be solved now.

Still following up on this though. Thanks for reporting.
Title: Re: Vector file problems after DeepMeta3 upload
Post by: Mancubus on March 02, 2017, 02:06
Thanks for your reply.

Still the same error. :-(

Message:
"Notes
Apologies, unfortunately the jpg file has corrupted. This could be a bug in Deep Meta. Please re-upload or try ESP."
Title: Re: Vector file problems after DeepMeta3 upload
Post by: FrankyDM on March 02, 2017, 11:53
Thanks for your reply.

Still the same error. :-(

Message:
"Notes
Apologies, unfortunately the jpg file has corrupted. This could be a bug in Deep Meta. Please re-upload or try ESP."
Thanks for reporting. I've asked Getty development team to help me sort this out.

------

Edited to add: one thing you could try that might be helpful, is to select "US West" as your "upload region" in DeepMeta settings.
I've had a few vector artists who no longer had issues after doing this.
(and make sure you use the latest version of DeepMeta of course).

The idea behind this is that Getty eventually moves all files to the US region, so if you upload directly to that region, nothing can go wrong with the transfer of your files to that region.

Thanks!
Title: [SOLVED] Re: Vector file problems after DeepMeta3 upload
Post by: Mancubus on March 08, 2017, 04:44
Hey Franky

I wanted to give you a short feedback about the given solution:
It really works as you described!

I've changed the upload region to "US West", updated DeepMeta3 to the latest version, and now my vector + illustration files are getting uploaded correctly @ ESP. No further issues now!

Thanks for your support!
Title: Re: [SOLVED] Re: Vector file problems after DeepMeta3 upload
Post by: FrankyDM on March 08, 2017, 15:39
Hey Franky

I wanted to give you a short feedback about the given solution:
It really works as you described!

I've changed the upload region to "US West", updated DeepMeta3 to the latest version, and now my vector + illustration files are getting uploaded correctly @ ESP. No further issues now!

Thanks for your support!

That's interesting. Thanks very much for reporting this!
I'm in touch with a Getty developer working on this, and will pass this info on to him.