Al'BenJ

8th January 2004 20:07 UTC

My first presets - please look
In reading through this forum, I have discovered that some consider it wise for newbies to post their presets here before releasing them in a pack. Over the last few weeks, I have played around with AVS alot and I have come up with some pretty cool presets. Please tell me what you think. Any comments/suggestions/tips welcome.:)

Jaak

8th January 2004 21:59 UTC

m8, you got more than potentian... if you keep working on avs you'll be very good very fast :)
for first pack, its FUCKING good, I just love:
The Shapemaker
Crystalline Web

keep up working on avs ;)

[edit]
i must note that use use very interesting varjable names :) but i like it :D

Warrior of the Light

8th January 2004 22:20 UTC

It really shows that you're not afraid of coding, unlike many other starterrs and that really pays off here.
Sure, there are things that could be done different, but for a first start, this is really good. Most first presets aren't much more than Moving Particle+Water+Blitter Feedback called "Hyperspacetunnel"

Try to download packs from others - It will inspire you and you can learn a lot by learning how they do things. At first, this will be frightening, but you'll learn things along the way. Also try if you can gat PiR's tutorial and Atero's Primer. That explains about all there is.

Best one: Fairydust
then: Crystalline Web
The shapemaker needs some work, it runs kinda slow.
The picture for Drunken Amoebic Rainbow was missing though. Be sure to add that when you submit.
Overall score for a first pack: 3.25/5

Deamon

8th January 2004 22:25 UTC

Some very interesting presets indeed. Keep it up, you have more than just potential, you got a feeling for it. Next time, please post in the presets subforum ;).

Welcome to the community :)

UnConeD

9th January 2004 00:05 UTC

Not bad for a first. Some notes:

Shapemaker:
- The first effect list is way too heavy. Move it to the end and figure out how to achieve the same effect with minimal components. Then move it back in.
- There are way too many buffer saves here, I doubt you'll need them all. If I disable the effect list with the 4 buffer saves in it, I don't notice any difference in output.
- The trans/fast brightness + trans/fast brightness + trans/colormap can be optimized to a simple colormap, because the colormap is set to replace. Just remove the brightnesses, and divide the positions of the colors in the map by 4 (use right-click > set position).
- The convolution with only 1 entry and scale 1 is useless.
- Instead of 2 multipliers, consider a colormap. You're only using the brightness anyway, 'cos the colors are added at the end.

Those crazy celtics:
- Your setup with buffer saves is a bit crazy for two reasons: first, you should first copy 1 dot to 2, and then copy those 2 to 4. This way, you save a copy operation. Secondly, instead of all those buffer saves, you can just use a couple of effect lists:
Effectlist (I:Replace/O:Additive) { Trans/Movement: r=r+$pi*.5 }
Effectlist (I:Replace/O:Additive) { Trans/Movement: r=r+$pi }
If you don't mind accuracy loss, you could just do the 2 movements in the main loop, set to blended, and do a x4 multiplier at the end.

The same applies to Fairydust.

Al'BenJ

9th January 2004 04:12 UTC

Thanks UnConeD for the tips. On "Those Crazy Celtics" I saved a very noticeable number of FPS. The other two I also sped up, but I just like them better at 10 FPS than I do at 16-17. Is there any way I can limit the FPS in a given preset? That way I could optimize them and set the FPS to 10 and everybody could see them exactly the way I do.

Deamon

9th January 2004 10:05 UTC

Nope, it's been asked before, but till now, there's no result.

Warrior of the Light

9th January 2004 12:58 UTC

Would that technically be possible?

akx

14th January 2004 17:25 UTC

;-c: Why not, if the AVS API allowed reading of current FPS info? Wishlist this, someone. :)

Yathosho

14th January 2004 17:31 UTC

i like the eye in the sky preset, oldskool!

Shock Value

15th January 2004 00:15 UTC

You can read the current FPS:

Frame:

deltatime = gettime(time);
fr=fr*.9+deltatime*.1;
framerate=1/fr;
time = gettime(0);

Try that and use the value of framerate to adjust your presets accordingly. For example, if you really did want a limited FPS, use a superscope with varying n values to target a specific framerate (increase n values if above target, lower them if above, although this does not have to be done linearly).

Neoavs

16th January 2004 14:33 UTC

Well, as your first pack, it's really cool. My fav was Spastic Elastic, very smooth colors.

Keep experimenting with the effects, and study others' avs', and you'll become a great avs'er in no time.

hungryskull

16th January 2004 23:51 UTC

You have serious potential.:)