MarkBrodhuber saidNow this is weird… I have to say “Thanks” and “You’re welcome” in the same sentence
urbazon saidWill do, thanks for the suggestion!
Hi Mark, can you please get devs to add “gb” in validation list for the “File Size” field of the upload form? It only accepts “mb” and “kb” and everything else throws error.
Not a problem . The change to allow “gb” has been deployed.
We’re very happy to announce that we’ve recently increased the existing file size cap for VideoHive submissions. The previous limit was set to 1GB per submission. We always allowed larger files, but if you wanted to submit a file that was larger than 1GB, you had to write into support to request permission before submitting your item.
The individual file size cap is now going to be 3GB. And while not much else is changing, I did want to make you all aware of some key points. Although we’re allowing files to be up to 3GB, we ask that you still focus on keeping your file sizes down whenever possible. We’d like all authors to use smart compression for all footage and videos. When you’re including assets within a project file, we ask that you focus on achieving the lowest file size you can reach before it starts negatively affecting quality. Authors have done a pretty great job working within 1GB so far, so I’m expecting most submissions will still be lower than 1GB.
Please also be mindful of buyers when you decide to submit large files in general. VideoHive buyers are located all over the world, and there’s no way to know download speeds and bandwidth availability for everyone.
- Submissions 1GB or smaller will be treated as business as usual.
- Submissions 1GB – 3GB will be reviewed as normal, but we reserve the right to reject any file that we feel could have been compressed or provided differently. So for example, if you upload a Motion Graphics submission that’s 3GB and we feel that it would be very easy to reduce the file size down without any significant quality loss, we will soft-reject and ask you to try reducing the overall size.
- Submissions over 3GB require approval from Envato Staff before it can be reviewed or accepted. If you want to upload a file that needs to be provided as one submission but the file size is larger than 3GB, you can create a new support ticket requesting permission. Please send through a preview video or any other examples, along with your reasoning for needing to exceed the cap. Once approved you’ll be allowed to submit your larger file for review.
My latest item was rejected for this exact reason: I uploaded it to the Motion Graphics category but was told that I was focusing too much on the AE preview. It is actually a Motion Graphics pack containing 150 video clips. I had to re-upload the entire thing to the After Effects Project category and it took around 17 days in total for the file to finally be approved.
Now it is basically encouraged to actually make a preview for your Motion Graphics.So what is the difference? Where do you draw the line?
I could be wrong, but it sounds like the issue with your file was that you were actually including AE project files within your Motion Graphics submission. If that is the case, we generally want the focus of the preview video to be on the rendered Motion Graphics, not the AE project. Since you cannot advertise a file to include additional freebies or bonuses.
In the event that your file was including an AE project, the focus needed to be on the Motion Graphics aspect of the file. That rule still applies today. What’s changing with this new policy is when you submit a Motion Graphics file that is made up of elements like transitions, you could cut together a preview video which shows those elements in use. So in the example of transitions, you could make a faux slideshow of photos, with your transition elements driving the actual transitions between each photo.
It’s not really something that was previously forbidden. We’ve allowed them to come in when they made sense, but we were always making exceptions as the general rule was that preview videos needed to be a certain way. Now we’re actually encouraging these kinds of presentation-style preview videos .
We’ve recently begun accepting what we call presentation-style preview videos for applicable Motion Graphics submissions. We feel that buyers tend to appeal to these kinds of preview videos since they portray real-world use scenarios.You can read the official policy and all of its details in the help center: https://help.market.envato.com/hc/en-us/articles/204063054-Presentation-style-Preview-Videos-for-Motion-Graphics
Hey guys, I thought I’d pop in here to try and explain the situation with the new plugin fields.
A little history
As many of you probably remember, we used to explain plugin usage within Projects using a single attribute titled “Requires Plugins” and the value was either Yes or No. Over the years I received many requests from both authors and buyers to expand this field to actually list out the specific plugins because up until very recently the only way to explain plugins used was through the item description.
Listing out required plugins in the description was always mandatory and it was setup that way for a reason. If you submit a project that requires Trapcode Particular, but neglect to list it in your description, buyers might find themselves unable to use the project if they do not own a Particular license. Requiring it in the description was a solution, but it was never very effective. Mainly because all we required was that the plugins were listed somewhere in the description. Each and every author has their own description style. Some would list required plugins at the top, others would bury this info below everything else. Some may include the information in a neat ordered or unordered list, and others might just type out each plugin required in sentence/paragraph form.
This inconsistency creates a very confusing experience for buyers. If it’s not easy to see which plugins are required, it could lead to a large number of refund requests and some very upset buyers.
Why we went with the new solutionWe racked our brains for quite a while about the ideal solution to this problem. There’s many possible ways we can present this attribute but we felt that this method best achieved the desired results.
- Allows authors to easily explain which plugins are utilized and can be edited if the buyer owns the plugin.
- Allows authors to easily explain which plugins are actually required.
- Will help people locate your item in the future, when these could potentially be searchable facets
- Will improve consistency and buyer confusion, removing the need to list all plugins in the item’s description (unless you select “Other”). Buyers now know all of the plugin related information is available in the item page sidebar. More importantly, it’s always going to be presented exactly the same way, for each and every item.
Regarding the concerns raised..
They way I understood it is if you provide two versions, one with prerenders, one with the plugins, you list those plugins in the “plugins used”. And if only a plugin version is included you list it in the required plugins list.
That is correct.
This is the tricky part: If you used a plugin in the creation of your item but do not provide a plugin version, only a prerendered, I think you list in in no list at all. But if buyers search for a specific look instead of a plugin to use, they might be filtering out those with only prerenders for no reason.
In the event that you used a plugin to create something, like a particle animation using Particular, but did not include the version of the project file that actually uses the plugin, you’d simply select “No Plugins” for both fields.
This is the way the rule has always been and hasn’t changed at all. If you went outside and shot a texture and included that texture image in your project, or rendered a 3D asset from another software program, or included any other footage or media assets, you wouldn’t reference plugins at all. So any media that’s included (rendered or otherwise) does not need to be referenced back to the plugin, unless of course the editable plugin version of the project has actually been included.
Keep in mind that if you use a plugin with a project file and want to provide a prerendered version, it’s in your best interest to also include the editable version for buyers who do have access to that plugin. Providing only the prerendered version here only serves to limit the appeal and usefulness of your item, so this scenario is really more of an edge case and is not recommended.
Very confusing. Why should the buyer need to know what plugins or 3D software I used to make a template? What’s the use of that option? If you ask me, we should open a thread and give suggestions, vote and that would be the best way of implementing important things in item description, and making search for buyers more efficient.
Buyers do not need to know what plugins or 3D software were generally used to create assets for the project, and we’re not asking you to provide that information. You’re only selecting plugins in either of these lists if you’ve included a project file that actually utilizes/requires these plugins. Again, we’re only asking you to provide information that’s valuable to buyers and requiring you to provide information that buyers would absolutely need to know before purchasing.
Take this scenario for example. Lets say I submit a new project that makes use of Element 3D, Optical Flares, and Particular. To make my project available to the largest audience possible, I prerender out the Optical Flares and Particular animations, and create a second prerendered project that uses the rendered videos rather than referencing the two plugins. When I go to submit, my attributes would look like this:
- Element 3D
- Optical Flares
- Element 3D
These attributes basically tell the buyer that my project makes use of all 3 plugins, so if they own the plugins, they have complete control and can customize every aspect of the project. But if they do not own OF and Particlar, they can still use the prerendered version to achieve the desired result. Aside from some basic adjustments, they will not be able to edit the results from the 2 plugins. It also tells them that regardless of the prerenders, Element 3D is required for them to use the project.
What’s nice here is that if/when this gets tied into search, buyers will have the ability to search for projects that they can use, while hiding anything they can’t, creating a better user experience. If I do not have Particular, I really wouldn’t want to see any projects that require me to own Particular. Projects that use particular, but do not require it would also show up in these results since buyers without Particular can still make use of them.
I hope that helps clear things up a bit.
It looks like your file was hard-rejected a few hours ago. You might want to check your email’s spam folder to make sure the notification email didn’t get held up there. If you cannot locate the email and need further clarification, please create a new support ticket. Our support staff will be happy to assist you and provide more information.