MicrostockGroup

Microstock Photography Forum - General => Microstock Services => MicrostockSubmitter => Topic started by: nicksimages on May 26, 2018, 11:27

Title: bug report
Post by: nicksimages on May 26, 2018, 11:27
I am not sure where to report bugs, so I am trying here.

There is an ugly bug with how stock submitter handles model releases. I have noticed it at iStock but it could also relate to other agencies.

When I uploaded to images to iStock, Stock submitter associated images with older model releases of the same model (and not the actual model release that shows in the stock submitter interface) which resulted in Date conflict rejections - now I have to correct everything manually.

The problem seems to be how Stock submitter saves releases at iStock - by using only model name and not the shoot date.
Title: Re: bug report
Post by: Niakris on May 26, 2018, 21:28
I am not sure where to report bugs, so I am trying here.

There is an ugly bug with how stock submitter handles model releases. I have noticed it at iStock but it could also relate to other agencies.

When I uploaded to images to iStock, Stock submitter associated images with older model releases of the same model (and not the actual model release that shows in the stock submitter interface) which resulted in Date conflict rejections - now I have to correct everything manually.

The problem seems to be how Stock submitter saves releases at iStock - by using only model name and not the shoot date.

It's not really a bug.
The program checks for the existence of the releases on the agency website by their names (First + Last name) because those are the only fields visible at all of the agencies and there is no other way.
So if you have multiple releases with the same name and one (or more) of them are already at the agency website the program will use them instead of uploading a new one (otherwise it would upload tons of duplicates of the same release).
If you want a new release to be uploaded you can give it a different name in the program (First or Last name).
Title: Re: bug report
Post by: nicksimages on June 11, 2018, 07:45
Yes, this is a bug and it is solvable. During release upload you can specify the name of the release.My releases added before paying for stocksubmitter do have a shoot date in the name, adding the shoot date to the release name in stocksubmitter and than search for this name in future submissions would solve this.

I would even prefer uploading new release with every picture, because currently the stocksubmitter is unusable for me for images with a release. Or another, less effective solution - the stocksubmitter must know there are already other releases from previous submissions with the same name, a warning is possible as well.

Please let me know the following:
Is this a problem only with istock/getty or also with other agencies?
Title: Re: bug report
Post by: Desintegrator on June 11, 2018, 09:13
I am not sure where to report bugs, so I am trying here.

There is an ugly bug with how stock submitter handles model releases. I have noticed it at iStock but it could also relate to other agencies.

When I uploaded to images to iStock, Stock submitter associated images with older model releases of the same model (and not the actual model release that shows in the stock submitter interface) which resulted in Date conflict rejections - now I have to correct everything manually.

The problem seems to be how Stock submitter saves releases at iStock - by using only model name and not the shoot date.

It's not really a bug.
The program checks for the existence of the releases on the agency website by their names (First + Last name) because those are the only fields visible at all of the agencies and there is no other way.
So if you have multiple releases with the same name and one (or more) of them are already at the agency website the program will use them instead of uploading a new one (otherwise it would upload tons of duplicates of the same release).
If you want a new release to be uploaded you can give it a different name in the program (First or Last name).

I have to look into this. If it really works like you've said, than it's a huge issue.
No for months i'm make newer and newer releases, because they get rejected on Shutterstock.. I'm have written countless e-mails to support claiming that now my release complies with all their criteria. And they keep getting rejected. It's going on for half a year. Could it be that the photos are submitted with the old release?
Never thought about checking that, as it seemed to be obvious that different releases with the same name have to be handled somehow.
Title: Re: bug report
Post by: Desintegrator on June 11, 2018, 09:46
So it's really happening on Shutterstock too.
The newer releases that I've made to adress the rejections of the old ones are not even uploaded to the site.

If the only way to distinguish between different releases is the name field than Stocksubmitter shouldn't allow us to save releases with the exact same name.
Title: Re: bug report
Post by: Niakris on June 11, 2018, 12:16
This is actually a feature requested by some users.
You can create releases with the same name because some users are having multiple releases for multiple agencies and they're controlling which releases will go to which agencies using the "Upload to" setting.

As of issues you're experiencing you can just add something to the release name (e.g. shooting date) so the program will upload the new release instead of an old one.
Title: Re: bug report
Post by: Desintegrator on June 11, 2018, 13:33
This is actually a feature requested by some users.
You can create releases with the same name because some users are having multiple releases for multiple agencies and they're controlling which releases will go to which agencies using the "Upload to" setting.

As of issues you're experiencing you can just add something to the release name (e.g. shooting date) so the program will upload the new release instead of an old one.

Yes, I'm starting to do that. I hope no site will have issue with the fact that what i write in the name field doesn't match exactly with the model's name.
Title: Re: bug report
Post by: Niakris on June 12, 2018, 03:48
This is actually a feature requested by some users.
You can create releases with the same name because some users are having multiple releases for multiple agencies and they're controlling which releases will go to which agencies using the "Upload to" setting.

As of issues you're experiencing you can just add something to the release name (e.g. shooting date) so the program will upload the new release instead of an old one.

Yes, I'm starting to do that. I hope no site will have issue with the fact that what i write in the name field doesn't match exactly with the model's name.

As far as I know none of the agencies have issues with that.
Title: Re: bug report
Post by: nicksimages on June 12, 2018, 07:01
This is actually a feature requested by some users.
You can create releases with the same name because some users are having multiple releases for multiple agencies and they're controlling which releases will go to which agencies using the "Upload to" setting.

As of issues you're experiencing you can just add something to the release name (e.g. shooting date) so the program will upload the new release instead of an old one.

Okay I unserstand. I will start adding shoot date to the release name too. That is a working work around though I still think software should do this automatically as they obviously are two different releases
Title: Re: bug report
Post by: Desintegrator on June 18, 2018, 13:54
BTW,
There is the "Shooting Date" field for releases registered in Stocksubmitter.. does this info get submitted to any of the sites?
Title: Re: bug report
Post by: Niakris on June 19, 2018, 02:05
BTW,
There is the "Shooting Date" field for releases registered in Stocksubmitter.. does this info get submitted to any of the sites?

As far as I remember, no.
Title: Re: bug report
Post by: StockStudio on July 26, 2018, 02:34
Well, I feel this might had to do with what i'm having lately...
i upload only videos, so no need for a seperate release for each shoot (yet...)
But in the last couple of batches my releases were not even attached to the footage (I double checked a few times they are attached in SS before uploading)
Happned in SS, Pond5, Fotolia, VB.

Anyone having the same issue?
Title: Re: bug report
Post by: Niakris on July 27, 2018, 01:55
Well, I feel this might had to do with what i'm having lately...
i upload only videos, so no need for a seperate release for each shoot (yet...)
But in the last couple of batches my releases were not even attached to the footage (I double checked a few times they are attached in SS before uploading)
Happned in SS, Pond5, Fotolia, VB.

Anyone having the same issue?

Did you check if they're still attached in the program when you've noticed the issue?
Title: Re: bug report
Post by: PZF on August 02, 2018, 01:28
OK, I don't follow everything being said on this thread, but I do know that with PHOTOS the MR I attach works for all sites except SS.
The release I attach now has the same name as the one already on SS and it still won't take it.
Oh well.
Title: Re: bug report
Post by: Niakris on August 02, 2018, 06:43
OK, I don't follow everything being said on this thread, but I do know that with PHOTOS the MR I attach works for all sites except SS.
The release I attach now has the same name as the one already on SS and it still won't take it.
Oh well.

It happens with SS sometimes, they have issues with that.
You can just try re-uploading files in case you get release-grounded rejections.
Title: Re: bug report - keywords missing
Post by: Uncle Pete on March 11, 2019, 08:54
I don't know if this is a bug or standard, but after I upload images, I get the notice that image data has changed. Fine, but then I go back and look at my images and all the keywords are gone. Does Stock Submitter strip out the keywords for some reason? What if I want to upload later, not using StS?

Or is this something on my system that's wrong?
Title: Re: bug report
Post by: steheap on March 11, 2019, 09:15
This never happens on my system. Yes, you do get the notice that the images have changed and do you want to save the changes, but that is because the status of the images has changed - ie they are now uploaded, submitted etc. I've never had the keywords removed or changed without me doing that directly.

Steve
Title: Re: bug report
Post by: Uncle Pete on March 11, 2019, 09:18
This never happens on my system. Yes, you do get the notice that the images have changed and do you want to save the changes, but that is because the status of the images has changed - ie they are now uploaded, submitted etc. I've never had the keywords removed or changed without me doing that directly.

Steve

So I can start to think it's a local issue.  ;D

First time, I thought maybe I only entered the words on StS.

New yesterday I made sure they were in the images, I uploaded, went back, the copyright change from Copyrighted to Unknown, Title stayed, Description stayed, all the keywords were gone.
Title: Re: bug report
Post by: steheap on March 11, 2019, 09:30
As an experiment, can you put some keywords, descriptions and the like into a JPEG and then modify the keywords in StS? When I look at one of my files that has been changed there (I alter the order of keywords when I get them into StS), and right click the file to look at properties and then details, I see all the information still in the JPEG itself. You can see the title and description are there  with the tags. I assume that the long set of characters in the comments field are what the StS system writes into the file to identify what has happened to that file in the application - ie has it been uploaded, submitted etc. Certainly I didn't put all those comment characters in there. I assume that each time you do something in the App, that information gets updated and that is why you are asked if you want to save changes.

Steve
Title: Re: bug report
Post by: Uncle Pete on March 11, 2019, 09:36
Might be that I'm using legacy keywording software that uses XMP for data. I'll have to look at things in Lightroom or PS. I noticed that editing images, then saving, the Copyright changes back to unknown. More reason to think it's on my computer, not the software.

What is that screen from you attached? I'll go look. I still use Elements to edit photos and scans.

Title: Re: bug report
Post by: steheap on March 11, 2019, 09:54
This is a windows screen. If you right click on any file in your file explorer and click "properties", you will see something like this. With JPEG files, the details tab of this shows what information is being stored in the file itself  - the keywords etc.

Steve
Title: Re: bug report
Post by: Niakris on March 11, 2019, 13:19
@Uncle Pete

Could you send me an example of a JPEG file that lost metadata to [email protected] ?
Also, did you receive any error messages when you've tried to save metadata in those files?
And did you save them manually or saw the program saving them?
Title: Re: bug report
Post by: Uncle Pete on March 11, 2019, 14:13
@Uncle Pete

Could you send me an example of a JPEG file that lost metadata to [email protected] ?
Also, did you receive any error messages when you've tried to save metadata in those files?
And did you save them manually or saw the program saving them?

I'll do that, but I replaced the missing data. Should I upload a file and look for one that lost data, is that what you need?

Files already had metadata, I did use the save data on StS. I believe it happens after the message "metadata has changed"

Thanks for the always caring response and I'll describe in the email, if I can replicate.

This is a windows screen. If you right click on any file in your file explorer and click "properties", you will see something like this. With JPEG files, the details tab of this shows what information is being stored in the file itself  - the keywords etc.

Steve

That's easy, will look. OK many more, but easy way to see them.

Might be the keywording software that I use, not detecting changes. For nearly everyone it will never be a StS issue. When I look with explorer properties they are still there. Sending one of each in anyway.