PHP has the string-processing and hash-table power of Perl combined with the clear syntax of C/C++. Very yummy.
I even use it as a shell scripting language. Using some registry hacks and such you can make it so .php files execute directly from the CMD like an exe or bat.
AVS Tutorials
39 posts
Atero-
Your problems with the links on my page is strange. I haven't had any problems with these links on any of the several computers I've accessed the site from. Downloads doesn't work because I haven't made a downloads page yet. Aside from that, all the other links seem to work (I just checked them).
Jahecklesafar and UnConeD-
Sounds like some solid advice. I'll check out PHP this summer...I'll have plenty of free time once school gets out on Friday.
Your problems with the links on my page is strange. I haven't had any problems with these links on any of the several computers I've accessed the site from. Downloads doesn't work because I haven't made a downloads page yet. Aside from that, all the other links seem to work (I just checked them).
Jahecklesafar and UnConeD-
Sounds like some solid advice. I'll check out PHP this summer...I'll have plenty of free time once school gets out on Friday.
my own tutorial
I was going to make a tutorial, but I just dont know enough. I am so confused by AVS math... I know that d=atan(d) pulls the outside of the image towards you... but WHY? I can never figure that out. Why does the arc tangent of the D variable make things distorted like that?
Oh, and UnconeD, you are my god. (ignore the sig though, we arent all a peice of you 😁 )
I was going to make a tutorial, but I just dont know enough. I am so confused by AVS math... I know that d=atan(d) pulls the outside of the image towards you... but WHY? I can never figure that out. Why does the arc tangent of the D variable make things distorted like that?
Oh, and UnconeD, you are my god. (ignore the sig though, we arent all a peice of you 😁 )
you can start now
Start writing your guide now; whenever you figure something out, write it down to put it in your guide. That's the best guide...write down the problem, and make some notes as you figure it out. Then write everything down & explain it right after the light bulb comes on. Do it before the light bulb goes out!
That's the best way to explain how to figure stuff out...figure it out yourself & then write it down.
Start writing your guide now; whenever you figure something out, write it down to put it in your guide. That's the best guide...write down the problem, and make some notes as you figure it out. Then write everything down & explain it right after the light bulb comes on. Do it before the light bulb goes out!
That's the best way to explain how to figure stuff out...figure it out yourself & then write it down.
I've Expermented ...
I been expermenting with the scope and stuff for over a year now hopeing to draw even a line but with no sussess. I don't know when im gunna finaly understand what the hell sin is or what cos and the rest of the confuseing math is i dont even know why none of my stuff appears even starter scopes i end up totaly destroyingi have no clue what make things go up or down or in and out if anyone know what the hell im talking about or has enough time to tell me exactly what the sin and x ext. does to the avs tell me it really been hard createing static images know theres much greater potential for avs.
P.S. For a hint on what i need to know even the basics of this could be helpful cuz like i said before i cant even make anything show up on the screen
I been expermenting with the scope and stuff for over a year now hopeing to draw even a line but with no sussess. I don't know when im gunna finaly understand what the hell sin is or what cos and the rest of the confuseing math is i dont even know why none of my stuff appears even starter scopes i end up totaly destroyingi have no clue what make things go up or down or in and out if anyone know what the hell im talking about or has enough time to tell me exactly what the sin and x ext. does to the avs tell me it really been hard createing static images know theres much greater potential for avs.
P.S. For a hint on what i need to know even the basics of this could be helpful cuz like i said before i cant even make anything show up on the screen
Do not worry, Matt_W74656
We were all here once. I remember me experimenting with the SSC and getting nothing but mess.
To draw a line with the SSC:
In the Point field of the SSC write: x=i. Isn't that a pretty line? Well, it all starts from here...
What you need is to:
1) Search the forums. There is plenty of stuff on this topic there.
2) Read the FAQ.
3) Get loaded with tutorials (try searching for "AVS Primer" and other in the forums)
4) Go to sites like mine (AVS Discussion) or soulcatalyst's (http://soulcatalyst.**********/main.html)
5) Experiment a lot (you'll get the hang of it eventually)
We were all here once. I remember me experimenting with the SSC and getting nothing but mess.
To draw a line with the SSC:
In the Point field of the SSC write: x=i. Isn't that a pretty line? Well, it all starts from here...
What you need is to:
1) Search the forums. There is plenty of stuff on this topic there.
2) Read the FAQ.
3) Get loaded with tutorials (try searching for "AVS Primer" and other in the forums)
4) Go to sites like mine (AVS Discussion) or soulcatalyst's (http://soulcatalyst.**********/main.html)
5) Experiment a lot (you'll get the hang of it eventually)
here's something
I just realized I need a little more of a transition from Algebra I graphing to get to where this part of my guide starts. I'll work on getting basic line graphing a little later, but I hope the Microsoft Word document is a help for now. It's really the same principle in my current guide...it just changes the line (simple equation such as y=.5x+2) based on the sound input
I just realized I need a little more of a transition from Algebra I graphing to get to where this part of my guide starts. I'll work on getting basic line graphing a little later, but I hope the Microsoft Word document is a help for now. It's really the same principle in my current guide...it just changes the line (simple equation such as y=.5x+2) based on the sound input
The Latest
I've finally gone back and started working on SoulCatalyst's Domain again. It's been about a month and a half since the last page update, but i hope to keep future updates closer together.
The main site is now the Tripod one (http://soulcatalyst.**********/), and the Xoasis site will be for experimenting with page design, and thus may not be the most up to date. This also makes it so I only have to update one site instead of two to add something new, which should help to make updates faster.
The links and downloads pages are finally up, and there's now a guestbook for SoulCatalyst's Domain (at the tripod site), and I'll be working on more tutorials for the basics of AVS.
I've finally gone back and started working on SoulCatalyst's Domain again. It's been about a month and a half since the last page update, but i hope to keep future updates closer together.
The main site is now the Tripod one (http://soulcatalyst.**********/), and the Xoasis site will be for experimenting with page design, and thus may not be the most up to date. This also makes it so I only have to update one site instead of two to add something new, which should help to make updates faster.
The links and downloads pages are finally up, and there's now a guestbook for SoulCatalyst's Domain (at the tripod site), and I'll be working on more tutorials for the basics of AVS.
The explanation of d=atan(d) is pretty simple... first of all you need to know how movements work:
The formulas you enter specify the *source* pixel in function of the *target*. When AVS applies the movement, it looks up the source pixels for every target pixel and copies the colour from source to target.
So when you specify d=d*2, you're saying that pixels halfway to the edge (d=0.5) should get the colour that is at the edge (d=0.5*2=1). This means that the image will be zoomed *out*: the area (-1...1) gets squised into (-0.5...0.5).
Now if this makes sense, you'll understand why atan(d) makes a tunnel movement. Open this in a new window:
The red line is the plot of f(x)=x, a 45° angled line. This is 'no movement', every point gets projected onto itself.
The blue curve is an approximation of the plot of f(x)=atan(x). I exaggerated the curving to make it easier to illustrate.
We take a point at a certain distance (the leftmost fat ellipse on the bottom axis) and we're going to apply the movement d=atan(d). We trace its location on the graph upwards (gray line). We need to draw a horizontal line and intersect with the blue curve. This is where this point would end up after one step of movement. Again, this is not how AVS works, but this is how it works intuitively.
We trace down again and find the target distance as the second point from the left on the axis. You can see the point moved ******ds.
Now we keep applying this: trace up, trace horizontal, intersect with blue, trace down to find out where it will end after several frames (and repeated movement). You can see that because the distance between the red line and the blue line increases, the point will move ******ds faster and faster.
What we're doing is actually a kind of source map now. AVS looks at the graph 90° rotated. You can understand that, if the blue curve doesn't cover the entire vertical range, that some points on the red line might not have a target horizontally of them. This is why a source-map can leave holes in the image.
Now what this example doesn't show is that there can be a huge difference is resulting movement from two slightly different curves, because the shape of the movement is the result of repeatedly following the points, rather than just once.
The formulas you enter specify the *source* pixel in function of the *target*. When AVS applies the movement, it looks up the source pixels for every target pixel and copies the colour from source to target.
So when you specify d=d*2, you're saying that pixels halfway to the edge (d=0.5) should get the colour that is at the edge (d=0.5*2=1). This means that the image will be zoomed *out*: the area (-1...1) gets squised into (-0.5...0.5).
Now if this makes sense, you'll understand why atan(d) makes a tunnel movement. Open this in a new window:
The red line is the plot of f(x)=x, a 45° angled line. This is 'no movement', every point gets projected onto itself.
The blue curve is an approximation of the plot of f(x)=atan(x). I exaggerated the curving to make it easier to illustrate.
We take a point at a certain distance (the leftmost fat ellipse on the bottom axis) and we're going to apply the movement d=atan(d). We trace its location on the graph upwards (gray line). We need to draw a horizontal line and intersect with the blue curve. This is where this point would end up after one step of movement. Again, this is not how AVS works, but this is how it works intuitively.
We trace down again and find the target distance as the second point from the left on the axis. You can see the point moved ******ds.
Now we keep applying this: trace up, trace horizontal, intersect with blue, trace down to find out where it will end after several frames (and repeated movement). You can see that because the distance between the red line and the blue line increases, the point will move ******ds faster and faster.
What we're doing is actually a kind of source map now. AVS looks at the graph 90° rotated. You can understand that, if the blue curve doesn't cover the entire vertical range, that some points on the red line might not have a target horizontally of them. This is why a source-map can leave holes in the image.
Now what this example doesn't show is that there can be a huge difference is resulting movement from two slightly different curves, because the shape of the movement is the result of repeatedly following the points, rather than just once.