Offer your services to support. You can earn some money working for Envato and make support go quicker.
At the moment, support is just one cobweb covered old lady – Dolores – sitting at a rusty switchboard, slowly working her way through an in-tray that is nearly 400 meters deep.
Hi guys, I wanted to ask this question to make sure I’m within the rules.
Is it allowed to use presets/ scripts in our templates, such as text scripts, etc, including scripts which can be bought from videohive itself.Most templates can do without the presets, but it can save a lot of time to use certain presets, mostly as a starting ground for certain effects, than build upon.
I would say that you can’t use presets in your templates, because the preset can be re-saved off from your project. Scripts are perhaps different, but nonetheless in certain cases it seems that the use of the script in templates could undermine sales of the script.
After Effects didn’t exist when I was 18.
My advice is to keep on going. If making stuff for Videohive acts as an incentive, then why not try it? But don’t let it be a disincentive if your items get rejected or don’t sell.
You’re just staring out and you’re young. This is just the beginning. Main thing is to enjoy what you do.
Oh… and other advice: learn how to spell “thanks”.
In fact, before I began my work in envato I analyzed it and put in video hive a idea of ??origami birds and My impression was that maybe I had more sales , given that, there was not same in the video hive . But it seems, there is not required sales Now what is your opinion? Do envato market be analyzed? Or totally unexpected.
It’s pretty random. Well, it’s very hard to predict what’s going to take off and what isn’t.
I think it’s fair to say that work that has a high quality execution and is original has a better chance of selling well over time than otherwise. One thing to make certain of is that your work has a broad appeal. Think about who will want to buy your work and why, then think up a project that is perfect for this generic market without itself being too generic!
felt_tips saidIt says Expected: ) in line 3
I have a little question felt. I am working on a project. I have 8 to 9 lights randomly moving. I have wiggle expression on their position.
Now the question is, all of them are moving differently, i want them to follow the same path after lets say 5 secs. Means before 5 secs they are all moving randomly and after 5 secs they slowly come together to move on exactly the same pattern.Is there a way to control their wiggle by a single slider control which can offset their movement and direction by increasing the value and once set to zero they move together.
Here’s one way to do it, based on the fact that wiggle is different for each layer, because the layer index is used as part of the input, whereas noise is always the same (given the same input). You use a slider to make a layer move between its independent wiggle and the general one.a = wiggle(2, 40); b = noise(time*2)*40; tControl = effect("A Slider Control")(1).value/100; // % slider 0-100 tControl*b + (1-tControl)*a;
It shouldn’t do. The code won’t give an error. I’ve just checked it in Ae and it works without a problem. I suspect you’ve mis-typed it.
The main point of this thread is for people to learn some stuff, rather than felt-tips doing their work for them. This is a good opportunity to learn a little about debugging and work out why this expression is not working for you!
Since line 3 is just picking up the value of an effect slider and dividing by 100 (something an expression writer will do hundreds of times a day) it shouldn’t be too hard to work out what’s going wrong. Why is After Effects expecting a closing parenthesis? There are only 4 parentheses on this line overall. Do the opening and closing ones match up? Try commenting out the other lines with // in front of them so you can work on this line in isolation. Before you copy and paste my code below, make sure you work out why the expression is not working for you. You will learn from this.
In checking this myself, I did notice however that the result it creates isn’t quite what I wanted. I forgot to add the noise generated wiggle to the original value, which was moving the layers up to the top left of the screen. Also the noise was creating a one dimensional wiggle and we need two… so I’ve updated it to the following….
tFreq = 2; tMag = 100; tNoiseInput = time*tFreq; a = wiggle(tFreq, tMag); b = value + [noise(tNoiseInput), noise(tNoiseInput+1000)]*tMag; tControl = effect("A Slider Control")(1).value/100; // % slider 0-100 tControl*b + (1-tControl)*a;
I’ve also split out frequency and magnitude as separate variables for more control. You could connect these up to sliders too.
It’s tested and it works perfectly, btw.