www.filterforge.com - Scripting

Error Diffusion Dithering

AussieDecalf — Thu, 14 Aug 2025 22:05:53 -0400

AussieDecalf, Fri, 08 Aug 2025 17:36:12 -0400
Hey I'd love to see if anyone can figure out this with me. I'm looking to make a filter that will convert an image to a pixel dithered output. Something like this:

Or like this with multiple colors:

I am specifically looking to make error diffusion or false error diffusion like Floyd-Steinberg, and not ordered diffusion. Ordered diffusion basically inputs a small grayscale bitmap as the diffusion pattern, or a diffusion matrix in code that does the same thing.

I'm already trying to get AI to program this for me, with some minor success. It turns out the fact that Filter Forge uses a sample based architecture means it fundamentally misses the required functionality to render an error diffusion.

But, I'm sure there's some novel ideas out there. I don't know how to code any of this myself, and I am only about as useful with LUA as it comes to catching easy bugs or fixing simple structural issues. I did have the idea of having the script build a pseudo grid that will act as pixels, and then have the formulas interact with that grid, but it might be a pipe dream.

I'd love to see what you all can come up with. There's a web app out there that does this BTW!
Dither Me This

Rachel Duim, Thu, 14 Aug 2025 22:05:53 -0400
My take on this: pixel by pixel manipulation is not a strong suit in FF. You can do a lot with LUA (fractals for instance), but the limitations on LUA make it slow. FF only uses one core when running LUA (not thread safe). And being procedural, the LUA function you create gets called for each block rendered. I also find it is not the easiest to debug and crashes occasionally when in the filter editor. My 2 cents, 3 with tariffs.

Can be made LUA scripting with AI using CHATGTP or any other AI?

SpaceRay — Thu, 17 Oct 2024 14:32:34 -0400

SpaceRay, Thu, 17 Oct 2024 14:32:34 -0400
If you are already a expert script coding creator, maybe ChatGPT can save you time to make it faster, but if you are like me that have zero LUA knowledge it can help maybe too

I have been seeing some tutorials on internet about ChatGPT and it seems that it can create scripts in any programming language that you may need

Then I have seen this confirmation that it can do it

So I thought that maybe it could be useful and interesting for making scripts in LUA to be used in filter forge

THE ANSWER IS YES, YOU CAN DO LUA SCRIPTS FOR FILTER FORGER EASILY

I have already tested it and if you write the correct prompt and you ask that it makes the required input editors they will be created

If there is an error in the script when tested in the map script of FF, you just simply tell the error to ChatGPT and it will be fixed

Although I have to say that when I said YES, I am still testing it, and I am still getting some errors and although it fixes it is still not working as I have zero Lua knowledge to fix it myself

But if you are an expert you can surely benefit from this as you already how to make it right

ABOUT MY EXPERIENCE WITH LUA

I have been trying to learn LUA but I am sorry that can't do it and so have no any experience

I really admire much and congratulate all of you that can be able to make such creative and useful scripts

Thanks very much for any possible help

Title: Script Projects - Debugging Assistance Thread

David Roberson — Sun, 08 Sep 2024 17:47:20 -0400

David Roberson, Sun, 05 Mar 2023 21:13:12 -0500
Greetings fellow script authors!

As we all know, writing a script can be a daunting task. Whether you're an experienced programmer or a novice, there are always hurdles to overcome. Sometimes you may get stuck on a particular section of code, or maybe you're having trouble getting your script to work the way you want it to. Fear not, for this forum thread is dedicated to providing assistance with completing your work-in-progress scripts.

Here's how it works:

Post your script project in the comments section. Be sure to provide as much detail as possible, including what the script is supposed to do, what language it's written in (if, for example, you are trying to convert some python into lua), and what specific issues you're having trouble with.

Other members of the community will read your post and offer their assistance. They may provide suggestions on how to fix the issue, offer code snippets that can help, or even offer to collaborate with you on the project.

If you're feeling generous, take a look at other people's projects and offer your own expertise. You never know when you might be able to help someone else out.

A few ground rules:

Be respectful of others. This is a space for constructive criticism and collaboration, not negativity.

Do not post any malicious code or attempt to exploit vulnerabilities in others' code.

Keep the discussion focused on script debugging and development.

Now, I know the FF Forum are pretty lightly trafficked these days, but I'd like to encourage a bit more interest in and activity on them. I am in the process of expanding my Lua scripting knowledge, recently with the help of ChatGPT. I've found it a good source of information that is difficult to find just searching online. It's a bit of work to get what you're looking for there, as well, so I plan to collect what insights I can and compile them in a more accessible form to share here. So, I'll be posting whatever I can as I go. I hope to lure in a few more with an interest in or more experience with scripting.

With that said, I invite you all to start posting your script projects and let's get to work!

David Roberson, Sun, 05 Mar 2023 21:29:31 -0500
I'll get the ball rolling with this: I converted Simplex noise written in java to lua and found myself caught on a potential out of bounds error being reported as an attempt to index a `nil` value. I've commented out most of the code and focused in on one point, where I could no longer adequately test the problem. I've put a couple day into this, so it's time to put it out there for someone else to look at it. It could be obvious to a more experienced author what I'm missing. If you give it a look, you have my gratitude!

[CODE]
--
-- simplex noise proto.lua
-- v.0.0.1 revision and testing
-- generates simplex noise in 2d, 3d and 4d
-- source: https://weber.itn.liu.se/~stegu/simple...Noise.java
-- used in filter forge map script component

--[[
Simplex noise is a type of gradient noise that is used for generating natural-looking textures, terrain,
and other procedural content.
A speed-improved simplex noise algorithm for 2D, 3D and 4D in Lua.

Based on example code by Stefan Gustavson (stegu@itn.liu.se).
Optimisations by Peter Eastman (peastman@drizzle.stanford.edu).
Lua conversion by David Bryan Roberson (https://github.com/eyeofparadox) in 2023
Better rank ordering method for 4D by Stefan Gustavson in 2012.

This could be speeded up even further, but it's useful as it is.

Version 2012-03-09-2023

This code was placed in the public domain by its original author,
Stefan Gustavson. You may use it as you see fit, but attribution is appreciated.
--]]

function prepare()
-- inputs and precalculation.
noiseScale = 50
noiseOctaves = 4
noiseLacunarity = 2.0
noisePersistence = 0.5

grad3 = {
{1,1,0},{-1,1,0},{1,-1,0},{-1,-1,0},
{1,0,1},{-1,0,1},{1,0,-1},{-1,0,-1},
{0,1,1},{0,-1,1},{0,1,-1},{0,-1,-1}
}

grad4 = {
{0, 1, 1, 1}, {0, 1, 1, -1}, {0, 1, -1, 1}, {0, 1, -1, -1},
{0, -1, 1, 1}, {0, -1, 1, -1}, {0, -1, -1, 1}, {0, -1, -1, -1},
{1, 0, 1, 1}, {1, 0, 1, -1}, {1, 0, -1, 1}, {1, 0, -1, -1},
{-1, 0, 1, 1}, {-1, 0, 1, -1}, {-1, 0, -1, 1}, {-1, 0, -1, -1},
{1, 1, 0, 1}, {1, 1, 0, -1}, {1, -1, 0, 1}, {1, -1, 0, -1},
{-1, 1, 0, 1}, {-1, 1, 0, -1}, {-1, -1, 0, 1}, {-1, -1, 0, -1},
{1, 1, 1, 0}, {1, 1, -1, 0}, {1, -1, 1, 0}, {1, -1, -1, 0},
{-1, 1, 1, 0}, {-1, 1, -1, 0}, {-1, -1, 1, 0}, {-1, -1, -1, 0}
}

p = {
151,160,137,91,90,15,
131,13,201,95,96,53,194,233,7,225,140,36,103,30,69,142,8,99,37,240,21,10,23,
190,6,148,247,120,234,75,0,26,197,62,94,252,219,203,117,35,11,32,57,177,33,
88,237,149,56,87,174,20,125,136,171,168,68,175,74,165,71,134,139,48,27,166,
77,146,158,231,83,111,229,122,60,211,133,230,220,105,92,41,55,46,245,40,244,
102,143,54,65,25,63,161,1,216,80,73,209,76,132,187,208,89,18,169,200,196,
135,130,116,188,159,86,164,100,109,198,173,186,3,64,52,217,226,250,124,123,
5,202,38,147,118,126,255,82,85,212,207,206,59,227,47,16,58,17,182,189,28,42,
223,183,170,213,119,248,152,2,44,154,163,70,221,153,101,155,167,43,172,9,
129,22,39,253,19,98,108,110,79,113,224,232,178,185,112,104,218,246,97,228,
251,34,242,193,238,210,144,12,191,179,162,241,81,51,145,235,249,14,239,107,
49,192,214,31,181,199,106,157,184,84,204,176,115,121,50,45,127,4,150,254,
138,236,205,93,222,114,67,29,24,72,243,141,128,195,78,66,215,61,156,180
}

n = #p

perm = {}
-- initialize permutation table with random values
for i=1,256 do
perm[i] = math.random(0,255)
end

-- extend the permutation table to avoid overflow
for i=257,512 do
perm[i] = perm[i - 256]
end

permMod12 = {}
-- initialize permMod12 table with 0 values
for i = 1, 512 do
permMod12[i] = 0
end

for i=1,512 do
permMod12[i] = perm[i] % 12
end

-- update grad3 and grad4 with the new permutation table
-- for i=1,256 do
-- grad3[i+1] = {grad3[perm[i+1] % 12 + 1][1], grad3[perm[i+1] % 12 + 1][2], grad3[perm[i+1] % 12 + 1][3]}
-- grad4[i+1] = {grad4[perm[i+1] % 32 + 1][1], grad4[perm[i+1] % 32 + 1][2], grad4[perm[i+1] % 32 + 1][3], grad4[perm[i+1] % 32 + 1][4]}
-- end

F2 = 0.5*(math.sqrt(3.0)-1.0)
G2 = (3.0-math.sqrt(3.0))/6.0
F3 = 1.0/3.0
G3 = 1.0/6.0
F4 = (math.sqrt(5.0)-1.0)/4.0
G4 = (5.0-math.sqrt(5.0))/20.0
end;

function get_sample(x, y)
if x < 0 or x > 1 or y < 0 or y > 1 then
return 0.5, 0.5, 0.5, 1
end
local xin, yin = x/noiseScale, y/noiseScale
local noise2D = get_2d_noise(xin, yin, noiseOctaves, noiseLacunarity, noisePersistence)
-- local noise3D = 0 -- get_3d_noise(xin, yin, 0, noiseOctaves, noiseLacunarity, noisePersistence)
-- local noise4D = 0 -- get_4d_noise(xin, yin, 0, 0, noiseOctaves, noiseLacunarity, noisePersistence)

local r = noise2D
-- local g = noise3D
-- local b = noise4D
local a = 1

-- return r, g, b, a
return r, 0, 0, a
-- return 0, g, 0, a
-- return 0, 0, b, a
end

function test_variables(r, g, b, a)
local variables = {r, g, b, a}
local nil_values = false

for i=1, 4 do
if variables[i] == nil then
variables[i] = 0
nil_values = true
elseif variables[i] ~= nil then
variables[i] = variables[i]
else
variables[i] = 1
nil_values = true
end
end

if nil_values then
return unpack(variables)
end
end

--[[
function grad3(...)
local args = {...}
for i, x in ipairs(args) do
args[i] = x % n
end
local a = args[1] + args[2] + args[3]
local gi = permMod12[a % n]
-- for i in `grad3`
if grad3[i] == nil then
return 1, 0, 1, 1
end
return dot({grad3[gi][1], grad3[gi][2], grad3[gi][3]}, args[1] - grad3[a % 12 + 1][1], args[2] - grad3[a % 12 + 1][2], args[3] - grad3[a % 12 + 1][3])
end

function grad4(...)
local args = {...}
for i, x in ipairs(args) do
args[i] = x % n
end
local a = args[1] + args[2] + args[3] + args[4]
local gi = permMod12[a % n]
-- for i in `grad4`
if grad4[i] == nil then
return 1, 0, 1, 1
end
return dot({grad4[gi][1], grad4[gi][2], grad4[gi][3], grad4[gi][4]}, args[1] - grad4[a % 32 + 1][1], args[2] - grad4[a % 32 + 1][2], args[3] - grad4[a % 32 + 1][3], args[4] - grad4[a % 32 + 1][4])
end
]]--

function fastfloor(x)
local xi = math.floor(x)
return (x < xi) and (xi-1) or xi
end

function dot(grd, x, y)
return (grd.x*x) + (grd.y*y) -- debug "Script error (line 141) : attempt to index a nil value (local 'grd')" >>> called from: lines 215,222,229
end

-- function dot(grd, x, y, z)
-- return (grd.x*x) + (grd.y*y) + (grd.z*z)
-- end

-- function dot(grd, x, y, z, w)
-- return (grd.x*x) + (grd.y*y) + (grd.z*z) + (grd.w*w)
-- end

function get_2d_noise(xin, yin)
local n0, n1, n2

local s = (xin+yin)*F2
local i = fastfloor(xin+s)
local j = fastfloor(yin+s)
local t = (i+j)*G2
local x0 = i-t
local y0 = j-t
local x0 = xin-x0
local y0 = yin-y0

local i1, j1
if x0>y0 then
i1 = 1
j1 = 0
else
i1 = 0
j1 = 1
end

local x1 = x0 - i1 + G2
local y1 = y0 - j1 + G2
local x2 = x0 - 1.0 + 2.0 * G2
local y2 = y0 - 1.0 + 2.0 * G2

local ii = (i + 1) & 255
local jj = (j + 1) & 255
test_variables(ii,jj)

local gi0 = permMod12[ii+perm[jj]]
local gi1 = permMod12[ii+i1+perm[jj+j1]]
local gi2 = permMod12[ii+1+perm[jj+1]]
test_variables(gi0,gi1,gi2)

local t0 = 0.5 - x0*x0-y0*y0
if t0<0 then
n0 = 0.0
else
t0 = t0 * t0
n0 = t0 * t0 * dot(grad3[gi0], x0, y0) -- <<< grad3[gi0],grad3[gi1],grad3[gi2] may be `nil`: points at lines 206-208 again
end
local t1 = 0.5 - x1*x1-y1*y1
if t1<0 then
n1 = 0.0
else
t1 = t1 * t1
n1 = t1 * t1 * dot(grad3[gi1], x1, y1)
end
local t2 = 0.5 - x2*x2-y2*y2
if t2<0 then
n2 = 0.0
else
t2 = t2 * t2
n2 = t2 * t2 * dot(grad3[gi2], x2, y2)
end

return (n0 + n1 + n2)
-- return 70.0 * (n0 + n1 + n2)
end

--[[
function get_3d_noise(xin, yin, zin)
local n0, n1, n2, n3
local s = (xin+yin+zin)*F3
local i = math.floor(xin+s)
local j = math.floor(yin+s)
local k = math.floor(zin+s)
local t = (i+j+k)*G3
local x0 = i-t
local y0 = j-t
local z0 = k-t
local x0 = xin-x0
local y0 = yin-y0
local z0 = zin-z0
local i1, j1, k1
local i2, j2, k2
if x0>=y0 then
if y0>=z0 then
i1=1; j1=0; k1=0; i2=1; j2=1; k2=0
elseif x0>=z0 then
i1=1; j1=0; k1=0; i2=1; j2=0; k2=1
else
i1=0; j1=0; k1=1; i2=1; j2=0; k2=1
end
else -- x0<y0
if y0<z0 then
i1=0; j1=0; k1=1; i2=0; j2=1; k2=1
elseif x0<z0 then
i1=0; j1=1; k1=0; i2=0; j2=1; k2=1
else
i1=0; j1=1; k1=0; i2=1; j2=1; k2=0
end
end
local x1 = x0 - i1 + G3
local y1 = y0 - j1 + G3
local z1 = z0 - k1 + G3
local x2 = x0 - i2 + 2.0*G3
local y2 = y0 - j2 + 2.0*G3
local z2 = z0 - k2 + 2.0*G3
local x3 = x0 - 1.0 + 3.0*G3
local y3 = y0 - 1.0 + 3.0*G3
local z3 = z0 - 1.0 + 3.0*G3
local ii = (i + 1) & 255
local jj = (j + 1) & 255
local kk = (k + 1) & 255
-- in `get_3d_noise`
if not ii or jj or kk then
return 0, 1, 0, 1
end
-- local gi0 = permMod12[ii+perm[jj+perm[kk+1] ]
local gi1 = permMod12[ii+i1+perm[jj+j1+perm[kk+k1+1] ]
local gi2 = permMod12[ii+i2+perm[jj+j2+perm[kk+k2+1] ]
local gi3 = permMod12[ii+1+perm[jj+1+perm[kk+1+1] ]
local t0 = 0.6 - x0*x0 - y0*y0 - z0*z0
if t0<0 then n0 = 0.0 else
t0 = t0 * t0
n0 = t0 * t0 * dot(grad3[gi0], x0, y0, z0)
end
local t1 = 0.6 - x1*x1 - y1*y1 - z1*z1
if t1<0 then n1 = 0.0 else
t1 = t1 * t1
n1 = t1 * t1 * dot(grad3[gi1], x1, y1, z1)
end
local t2 = 0.6 - x2*x2 - y2*y2 - z2*z2
if t2<0 then n2 = 0.0 else
t2 = t2 * t2
n2 = t2 * t2 * dot(grad3[gi2], x2, y2, z2)
end
local t3 = 0.6 - x3*x3 - y3*y3 - z3*z3
if t3<0 then n3 = 0.0 else
t3 = t3 * t3
n3 = t3 * t3 * dot(grad3[gi3], x3, y3, z3)
end
return 32.0*(n0 + n1 + n2 + n3)
end

function get_4d_noise(x, y, z, w)
local n0, n1, n2, n3, n4
local s = (x + y + z + w) * F4
local i = math.floor(x + s)
local j = math.floor(y + s)
local k = math.floor(z + s)
local l = math.floor(w + s)
local t = (i + j + k + l) * G4
local x0 = i - t -- unskew the cell origin back to (x,y,z,w) space
local y0 = j - t
local z0 = k - t
local w0 = l - t
local x0 = x - x0
local y0 = y - y0
local z0 = z - z0
local w0 = w - w0
local rankx = 0
local ranky = 0
local rankz = 0
local rankw = 0
if x0 > y0 then
rankx = rankx + 1
else
ranky = ranky + 1
end
if x0 > z0 then
rankx = rankx + 1
else
rankz = rankz + 1
end
if x0 > w0 then
rankx = rankx + 1
else
rankw = rankw + 1
end
if y0 > z0 then
ranky = ranky + 1
else
rankz = rankz + 1
end
if y0 > w0 then
ranky = ranky + 1
else
rankw = rankw + 1
end
if z0 > w0 then
rankz = rankz + 1
else
rankw = rankw + 1
end
local i1, j1, k1, l1
local i2, j2, k2, l2
local i3, j3, k3, l3
i1 = (rankx >= 3) and 1 or 0
j1 = (ranky >= 3) and 1 or 0
k1 = (rankz >= 3) and 1 or 0
l1 = (rankw >= 3) and 1 or 0
i2 = (rankx >= 2) and 1 or 0
j2 = (ranky >= 2) and 1 or 0
k2 = (rankz >= 2) and 1 or 0
l2 = (rankw >= 2) and 1 or 0
i3 = (rankx >= 1) and 1 or 0
j3 = (ranky >= 1) and 1 or 0
k3 = (rankz >= 1) and 1 or 0
l3 = (rankw >= 1) and 1 or 0
local x1 = x0 - i1 + G4
local y1 = y0 - j1 + G4
local z1 = z0 - k1 + G4
local w1 = w0 - l1 + G4
local x2 = x0 - i2 + 2.0*G4
local y2 = y0 - j2 + 2.0*G4
local z2 = z0 - k2 + 2.0*G4
local w2 = w0 - l2 + 2.0*G4
local x3 = x0 - i3 + 3.0*G4
local y3 = y0 - j3 + 3.0*G4
local z3 = z0 - k3 + 3.0*G4
local w3 = w0 - l3 + 3.0*G4
local x4 = x0 - 1.0 + 4.0*G4
local y4 = y0 - 1.0 + 4.0*G4
local z4 = z0 - 1.0 + 4.0*G4
local w4 = w0 - 1.0 + 4.0*G4
local ii = (i + 1) & 255
local jj = (j + 1) & 255
local kk = (k + 1) & 255
local ll = (l + 1) & 255
-- in `get_4d_noise`
if not ii or jj or kk or ll then
return 0, 0, 1, 1
end
local gi0 = perm[ii+perm[jj+perm[kk+perm[ll] ] ] ] & 31
local gi1 = perm[ii+i1+perm[jj+j1+perm[kk+k1+perm[ll+l1] ] ] ] & 31
local gi2 = perm[ii+i2+perm[jj+j2+perm[kk+k2+perm[ll+l2] ] ] ] & 31
local gi3 = perm[ii+i3+perm[jj+j3+perm[kk+k3+perm[ll+l3] ] ] ] & 31
local gi4 = perm[ii+1+perm[jj+1+perm[kk+1+perm[ll+1] ] ] ] & 31
local t0 = 0.6 - x0*x0 - y0*y0 - z0*z0 - w0*w0
if t0 < 0 then
n0 = 0.0
else
t0 = t0 * t0
n0 = t0 * t0 * dot(grad4[gi0], x0, y0, z0, w0);
-- n0 = t0 * t0 * (x0 * grad4[gi0].x + y0 * grad4[gi0].y + z0 * grad4[gi0].z + w0 * grad4[gi0].w)
end
local t1 = 0.6 - x1*x1 - y1*y1 - z1*z1 - w1*w1
if t1 < 0 then
n1 = 0.0
else
t1 = t1 * t1
n1 = t1 * t1 * dot(grad4[gi1], x1, y1, z1, w1);
-- n1 = t1 * t1 * (x1 * grad4[gi1].x + y1 * grad4[gi1].y + z1 * grad4[gi1].z + w1 * grad4[gi1].w)
end
local t2 = 0.6 - x2*x2 - y2*y2 - z2*z2 - w2*w2
if t2 < 0 then
n2 = 0.0
else
t2 = t2 * t2
n2 = t2 * t2 * dot(grad4[gi2], x2, y2, z2, w2);
-- n2 = t2 * t2 * (x2 * grad4[gi2].x + y2 * grad4[gi2].y + z2 * grad4[gi2].z + w2 * grad4[gi2].w)
end
local t3 = 0.6 - x3*x3 - y3*y3 - z3*z3 - w3*w3
if t3 < 0 then
n3 = 0.0
else
t3 = t3 * t3
n3 = t3 * t3 * dot(grad4[gi3], x3, y3, z3, w3);
-- n3 = t3 * t3 * (x3 * grad4[gi3].x + y3 * grad4[gi3].y + z3 * grad4[gi3].z + w3 * grad4[gi3].w)
end
local t4 = 0.6 - x4*x4 - y4*y4 - z4*z4 - w4*w4
if t4 < 0 then
n4 = 0.0
else
t4 = t4 * t4
n4 = t4 * t4 * dot(grad4[gi4], x4, y4, z4, w4);
-- n4 = t4 * t4 * (x4 * grad4[gi4].x + y4 * grad4[gi4].y + z4 * grad4[gi4].z + w4 * grad4[gi4].w)
end
return 27.0 * (n0 + n1 + n2 + n3 + n4)
end
]]--

local grad = {
x = 0, y = 0, z = 0, w = 0
}

function grad:new(x, y, z)
local obj = {
x = x, y = y, z = z
}
setmetatable(obj, self)
self.__index = self
return obj
end

function grad:new(x, y, z, w)
local obj = {
x = x, y = y, z = z, w = w
}
setmetatable(obj, self)
self.__index = self
return obj
end
[/CODE]

David Roberson, Wed, 08 Mar 2023 17:20:17 -0500
I had a thought, but it escaped me, Oh, well...

David Roberson, Wed, 08 Mar 2023 18:16:15 -0500
Hmm. I have a long post written up with formatting tags, but it doesn't show up when I post it here. I tried to post it again, but nothing shows. Let's see if breaking it up a bit helps...

Nope. No luck.

David Roberson, Wed, 08 Mar 2023 18:50:10 -0500
Since I've been having problems with proper indexing and `nil` values in my 2-4D Simplex and Perlin noise scripts, I took a day off to do a breakdown of the `perlin` noise function I'm using in my spherical Perlin noise, describing what each part does:

`perlin`: This section of the `perlin:noise` function initializes the empty `perlin` table and its empty `p` field using the syntax `perlin = {}`, `perlin.p = {}`., the latter of which is used to store 512 pseudorandom gradient values. In `perlin.p = {}`, `p` is a field (also called a key or a member) of the `perlin` table, which is being assigned a new empty table `{}` as its value. So `p` is a field that consists of a table. If you have a table `perlin` containing three tables `p1`, `p2`, `p3`, the fields should be accessed as `perlin.p1`, `perlin.p2`, `perlin.p3`.
[CODE]
perlin = {}
perlin.p = {}
.[/CODE]
Next, an arbitrary seed value is obtained using the `get_intslider_input()` function of the Filter Forge Scripting API. This value is used to seed the random number generator using `math.randomseed()`.
[CODE]
math.randomseed(get_intslider_input(SEED))
.[/CODE]
A `for` loop is then used to fill the `perlin.p` table with 256 randomly generated values between 0 and 255. These values are generated using the `math.random()` function.
[CODE]
for i = 0, 255 do
perlin.p[i] = math.random(255)
perlin.p[256 + i] = perlin.p[i]
end
.[/CODE]
`function perlin:noise(x, y, z)`: The main function that returns the noise value for a given point (x,y,z). This section of the `perlin:noise` function takes in 3 input values: `x`, `y`, and `z`. It calculates the noise value at the given coordinate in 3D space. Here are the breakdowns of the operations:

The `y` and `z` values are set to 0 if they are not provided as input.
[CODE]
y = y or 0; z = z or 0 -- if y or z are not provided, set them to 0.
.[/CODE]
The function calculates the "unit cube" that the point will be located in by using the `math.floor` function to round down the input coordinates to integers and then performing a bitwise AND operation with 255 (which is equivalent to taking the modulo 256). This is done for each coordinate (x, y, and z) to obtain the indices of the cube vertices surrounding the input point.
[CODE]
local xi = bit32.band(math.floor(x), 255);
local yi = bit32.band(math.floor(y), 255);
local zi = bit32.band(math.floor(z), 255)
.[/CODE]
After calculating the unit cube that the point will be located in, the function calculates the relative positions of the input point within the unit cube by subtracting the floored values fr om the input values. This gives `x`, `y`, and `z` values in the range [0, 1] that represent the position of the input point within the unit cube.
[CODE]
local xf = x - math.floor(x);
local yf = y - math.floor(y);
local zf = z - math.floor(z)
.[/CODE]
The fractional part of the coordinates of the point within the unit cube are calculated by subtracting the floored (integer part) coordinates fr om the original coordinates.
[CODE]
x = x - math.floor(x);
y = y - math.floor(y);
z = z - math.floor(z)
.[/CODE]
The `fade` function is applied to each of `x`, `y`, and `z` to smooth the result. The `fade` function is a 6th-degree polynomial that interpolates smoothly between 0 and 1.
[CODE]
local u = self.fade(x); local v = self.fade(y); local w = self.fade(z)
.[/CODE]
The function then declares several variables that will be used later: `u`, `v`, and `w` are the smoothed `x`, `y`, and `z` values, respectively. `p` is a lookup table that stores the permutation of 256 integers used in the calculation of the `noise` function. The remaining variables (`A`, `AA`, `AB`, etc.) will hold the pseudorandom gradient vectors corresponding to the 8 unit cube vertices surrounding the input point.

Note that the function has not yet calculated the gradient vectors or the noise value itself. These will be calculated in the following steps of the function.

We can now calculate the dot product of each corner vector and the distance vector from the point to that corner. We can also use the fade curve to blend the contributions of each corner vector together.

In this section of the `perlin:noise` function, the eight corner points of the unit cube surrounding the input point are identified using a hash function. The operations involved are:

Retrieve the permutation table from the `self` table.
[CODE]
local p = self.p:
.[/CODE]
Declare 14 local variables to store the values of the corner points.
[CODE]
local A, AA, AB, AAA, ABA, AAB, ABB, B, BA, BB, BAA, BBA, BAB, BBB:

A = p[xi] + yi
-- retrieve the value of the permutation table at the position [xi],
-- and add yi to it.
-- Store the result in A.
AA = p[A] + zi
-- retrieve the value of the permutation table at the position [A],
-- and add zi to it.
-- Store the result in AA.
AB = p[A + 1] + zi
-- retrieve the value of the permutation table at the position [A+1],
-- and add zi to it.
-- Store the result in AB.
AAA = p[AA]
-- retrieve the value of the permutation table at the position [AA].
-- Store the result in AAA.
ABA = p[AB]
-- retrieve the value of the permutation table at the position [AB].
-- Store the result in ABA.
AAB = p[AA + 1]
-- retrieve the value of the permutation table at the position [AA+1].
-- Store the result in AAB.
ABB = p[AB + 1]
-- retrieve the value of the permutation table at the position [AB+1].
-- Store the result in ABB.

B = p[xi + 1] + yi
-- retrieve the value of the permutation table at the position [xi+1],
-- and add yi to it.
-- Store the result in B.
BA = p + zi
-- retrieve the value of the permutation table at the position [B],
-- and add zi to it.
-- Store the result in BA.
BB = p[B + 1] + zi
-- retrieve the value of the permutation table at the position [B+1],
-- and add zi to it.
-- Store the result in BB.
BAA = p[BA]
-- retrieve the value of the permutation table at the position [BA].
-- Store the result in BAA.
BBA = p[BB]
-- retrieve the value of the permutation table at the position [BB].
-- Store the result in BBA.
BAB = p[BA + 1]
-- retrieve the value of the permutation table at the position [BA+1].
-- Store the result in BAB.
BBB = p[BB + 1]
-- retrieve the value of the permutation table at the position [BB+1].
-- Store the result in BBB.
.[/CODE]
Overall, these operations perform a series of table lookups to retrieve the values of the corner points of the unit cube surrounding the input point. These corner points are used in the subsequent interpolation steps to calculate the final [B]`perlin:noise` value.

This section of the `perlin:noise` function performs the final step of calculating the noise value for the input coordinates by taking the weighted average between all 8 unit cube coordinates surrounding the input coordinate.

`self.lerp`: The function is used for linear interpolation. It takes two values `a` and `b`, and a weight `w` and returns the linearly interpolated value between `a` and `b` based on the weight `w`. The nested `self.lerp` functions are used to calculate the weighted average between all 8 unit cube coordinates. The inputs to these functions are the 8 unit cube coordinates and the input coordinate. These 8 unit cube coordinates are labeled with different variable names that correspond to their position in the unit cube, such as `AAA`, `AAB`, `ABA`, etc. Inside each `self.lerp` function, there are two more nested `self.lerp` functions, which are used to interpolate the gradient vectors at each of the 4 corners of the unit cube. The gradient vectors are calculated using the `self:grad` function, which takes a hash value and the input coordinates, and returns a gradient vector.
[CODE]
return
self.lerp(w,
self.lerp(v,
self.lerp(u,
self:grad(AAA, x, y, z),
self:grad(BAA, x - 1, y, z)
),
self.lerp(u,
self:grad(ABA, x, y - 1, z),
self:grad(BBA, x - 1, y - 1, z)
)
),
self.lerp(v,
self.lerp(u,
self:grad(AAB, x, y, z - 1),
self:grad(BAB, x - 1, y, z - 1)
),
self.lerp(u,
self:grad(ABB, x, y - 1, z - 1),
self:grad(BBB, x - 1, y - 1, z - 1)
)
)
)
.[/CODE]
Overall, the final output of this section is a weighted average of the gradient vectors at the 8 corners of the unit cube, which is the `perlin:noise` value for the input coordinates.

This section of the `perlin:noise` function defines a lookup table for the `dot_product` function and a gradient function that finds the dot product between a pseudorandom gradient vector and the vector from an input coordinate to a unit cube vertex.

`perlin.dot_product`: This table contains 16 entries, each corresponding to one of the 16 possible bit patterns that can be formed by three bits. Each entry is a function that takes three arguments `x`, `y`, and `z`, which represent the coordinates of a point, and returns the dot product between the pseudorandom gradient vector and the vector from the input point to a unit cube vertex in a particular direction. The directions are determined by the bit pattern associated with the function in the table.
[CODE]
perlin.dot_product = {
[0x0] = function(x, y, z) return x + y end,
[0x1] = function(x, y, z) return -x + y end,
[0x2] = function(x, y, z) return x - y end,
[0x3] = function(x, y, z) return -x - y end,
[0x4] = function(x, y, z) return x + z end,
[0x5] = function(x, y, z) return -x + z end,
[0x6] = function(x, y, z) return x - z end,
[0x7] = function(x, y, z) return -x - z end,
[0x8] = function(x, y, z) return y + z end,
[0x9] = function(x, y, z) return -y + z end,
[0xA] = function(x, y, z) return y - z end,
[0xB] = function(x, y, z) return -y - z end,
[0xC] = function(x, y, z) return y + x end,
[0xD] = function(x, y, z) return -y + z end,
[0xE] = function(x, y, z) return y - x end,
[0xF] = function(x, y, z) return -y - z end
}
.[/CODE]
`perlin:grad(hash, x, y, z)`: This method takes four arguments: `hash`, an integer value between 0 and 255; and `x`, `y`, and `z`, which represent the coordinates of a point. The method computes the dot product between the pseudorandom gradient vector associated with the given `hash` value and the vector from the input point to a unit cube vertex. The `hash` value determines which gradient vector to use, and the direction of the vector is determined by the dot product function corresponding to the last three bits of the hash value. The method returns the computed dot product.
[CODE]
function perlin:grad(hash, x, y, z)
return self.dot_product[bit32.band(hash, 0xF)](x, y, z)
end
.[/CODE]
`perlin.fade(t)`: The `fade` function is used to smooth the final output of the `perlin:noise` function. It takes a single parameter `t`, which represents the input value to be smoothed. The function uses a quintic (degree-5) polynomial to gradually transition from 0 to 1 as `t` increases from 0 to 1. This helps to reduce the appearance of sharp edges and discontinuities in the output of the `perlin:noise` function.
[CODE]
function perlin.fade(t)
return t * t * t * (t * (t * 6 - 15) + 10)
end
.[/CODE]
`perlin.lerp(t, a, b)`: The `lerp` function is a linear interpolation function that is used to combine the weighted average of the dot products of gradient vectors and the input coordinate. It takes three parameters: `t`, `a`, and `b`. The function returns the linear interpolation of `a` and `b` at the ratio of `t`, wh ere `t` ranges from 0 to 1. The resulting value is a weighted average of `a` and `b` wh ere `t` determines the weighting of the two values.
[CODE]
function perlin.lerp(t, a, b)
return a + t * (b - a)
end
.[/CODE]
`noise`, `dot_product`, `grad`, `fade` and `lerp` are all functions defined within the `perlin` table using the colon syntax (`[/B]perlin:function()`[/B]). This makes them methods of the `perlin` table, so they can be called using the `:`[/B] syntax (`[/B]perlin:method()`[/B]).

Doing an analysis like this is a big step in understanding the algorithms I need to use for scripting. I put a little extra effort into organizing and formatting my notes to share here. I thought people might find this sort of thing helpful, and it sort of fits in with the theme of this thread. If there's a positive response, I'll try to do more of these in cases wh ere I've gotten a script to working as intended.

emme, Sun, 02 Apr 2023 19:15:12 -0400
As you mentioned, ChatGPT can be quite helpful with these things, not only for writing scripts and functions, but for explaining them as well. Also, check out shadertoy.com if you haven't already. The shaders are written in GLSL, but there are a lot of great examples to learn from. Good luck with scripting :)

David Roberson, Mon, 17 Apr 2023 02:33:40 -0400
Yes, it's been really helpful (if occasionally frustrating) for improving my understanding of Lua. I've also found my way to shadertoy.com many times looking for ways to do certain things. I also recommend it, and ChatGPT can help convert the GLSL to Lua if you come across anything good there. Thanks, emme!

David Roberson, Sun, 08 Sep 2024 17:35:40 -0400
It's been a long time since I thought of posting here. The lack of discussion, while forgivable, has caused my to throw my scripting questions at ChatGPT or Copilot this past year. Today I had a chat I thought I'd share here. It might help others digging into the same topics, or even prompt some forum input.

Right. So, here you go:

Understanding Noise Generation Seeds (and then Diving Deeper)

I am working on noise generation scripts using Lua in Filter Forge. While I was at it, I found myself wondering what a seed exactly is. In terms of the noise generated, what does the seed do (break down the function in terms of it effects)?

Copilot: Certainly! Let's dive into the fascinating world of seeds in noise generation.

**What is a Seed?**
A seed, in the context of noise generation algorithms like Stable Diffusion (and even in other areas like procedural terrain generation), is simply a numerical value. It acts as the starting point for generating noise patterns. Here's the plain and simple breakdown:

1. **Seed Is Not the Noise Image Itself**: The seed itself is not the noise pattern you see in the final image. Instead, it's like the initial spark that sets the whole process in motion.

2. **Not All Parameters**: Contrary to misconceptions, the seed doesn't encapsulate all the parameters used for image generation. It's just the starting point, not the entire recipe.

3. **Not Tied to Specific Prompts or Characteristics**: The seed remains detached fr om specific text prompts, poses, clothing, backgrounds, or artistic styles. It's more about the underlying randomness.

**How Does It Work?**
When you provide a seed, the noise generator algorithm takes that number and uses it to create an initial noise pattern. But here's the interesting part: the noise isn't truly random. It's pseudo-random. In other words, given the same seed, the algorithm will reliably produce the same noise pattern every time. This repeatability opens up some cool possibilities:

- **Consistent Reproduction**: If you input the same seed, along with the same prompt and all the other parameters you used initially, you can reliably reproduce a generated image across multiple sessions. It's like having a secret recipe for noise!

- **Sharing and Tweaking**: Users can work off someone else's generated image by starting fr om the same seed, prompt, and parameters. Plus, minor tweaks—like adjusting the prompt or parameters—allow you to explore variations without drastically altering the overall composition.

- **Seed Characteristics**: Some seeds have been identified as having a higher probability of producing images with specific color palettes or compositions. Knowing these "lucky" seeds can give you a better chance of getting the output you desire.

So, in summary, seeds are like the cosmic dice roll that determines the initial noise, and fr om there, the algorithm weaves its magic to create the final image.

David Roberson, Sun, 08 Sep 2024 17:47:20 -0400
Heh. Guess that was too long to post. Rather than a series of clips, I'll just share the text for anyone interested. ^_^;

For the full transcript:
Understanding Noise Generation Seeds (and then Diving Deeper)

Help articles on Scripting (work in progress)

Vladimir Golovin — Tue, 14 Mar 2023 02:08:53 -0400

Vladimir Golovin, Mon, 07 Jun 2010 09:31:25 -0400
We're uploading unfinished Help articles on scripting to the Filter Forge wiki. The articles are incomplete, some text, examples and pictures may be outdated -- but anyway, it's something to start with. We'll update the articles when the new content is written (and when we have time to do that.)

Here's the list of articles that are currently uploaded:
- Getting Started with Scripting
- Referencing Inputs from Scripts
- Sample-Based Architecture

Kraellin, Mon, 07 Jun 2010 23:13:15 -0400

Quote
Create a Map Script component (located in the Scripting category on the Component Bar).

ok, what if we have no scripting category on the component bar? "Help Components" doesnt show any such thing either. is this something upcoming or am i missing something here? and yes, this version 2, latest update.

edit: and in looking further, what happened to the options? i no longer have an "Options" in the menu system.

edit: never mind, found the options. lol. dont get old ;) but i still cant find anything about scripting within the editor.

edit yet again: ok, seems i dont have the latest version. lol. stage 4 is out today. ok, forget i posted anything here :) :D

Mike Blackney, Tue, 08 Jun 2010 01:11:31 -0400
Forget? Impossible!! :D

One thing that took me a while to realise is that the x and y values are still floats when you're sampling in script. I thought they would be pixels (for some reason) then checked the wiki and suddenly it made sense that x+1 was returning the same thing.

Is there any method I can call to get the input image dimensions in script? Are there methods like this exposed, or are there plans to? Sorry if asking questions like this are doubling up on wiki work.

Vladimir Golovin, Tue, 08 Jun 2010 05:40:21 -0400

Quote
Mike Blackney wrote: I thought they would be pixels (for some reason)

Thank you for reminding me to upload the article on "Filter Forge's Sample-Based Architecture" :)

Quote
Mike Blackney wrote: Sorry if asking questions like this are doubling up on wiki work.

Don't worry. The help file is the #1 priority right now, and within the help file scripting is the most important chunk of work -- though I can't promise that we'll update the Wiki versions often, we're not using them for internal editing.

Vladimir Golovin, Tue, 08 Jun 2010 05:48:16 -0400

Quote
Mike Blackney wrote: Is there any method I can call to get the input image dimensions in script?

Yes. They are not documented yet, but here's the list of FF variables available in Lua scripts:

SIZE - value of the Size slider, available only to scripts that "make use of the global Size setting".

VARIATION - value of the Variation slider, available only to scripts that "make use of the global Variation setting".

OUTPUT_WIDTH, OUTPUT_HEIGHT - image width and height, pixels

SEAMLESS_REGION_WIDTH, SEAMLESS_REGION_HEIGHT - seamless region width and height, available only when the global Seamless Tiling checkbox is turned on.

SEAMLESS - state of the global Seamless Tiling checkbox, true of false.

Debugging tip: you can use the Color Inspector to display the value of a variable. Just return it in one of the RGB channels -- remember, FF is fully HDR :)

Vladimir Golovin, Tue, 08 Jun 2010 07:49:58 -0400
I've updated the original post with a link to a new article on sample-based architecture.

Mike Blackney, Wed, 09 Jun 2010 06:42:24 -0400
Thanks Vlad, that's brilliant! :D

BenBeckwith, Thu, 10 Jun 2010 21:45:53 -0400
Something that might help aspiring scripters (such as me) is if you provided images of how you would create the example scripts out of existing components (if possible). For example, the radial gradient script could be accompanied with the attached image. I understood the explanation, but it took me a few read throughs to match it all up and understand it. Then I confirmed it by rebuilding it with nodes. :)

BenBeckwith, Thu, 10 Jun 2010 21:54:43 -0400
Sorry, I totally forgot something. For added clarity...

Totte, Fri, 11 Jun 2010 00:20:23 -0400
Brilliant Ben!

Crapadilla, Fri, 18 Nov 2011 08:47:18 -0500
Are the wiki articles on Scripting obsolete? I'm asking because it appears that the finished versions of those articles can be found in the Help section of the website, nicely formatted and all shiny. ;)

If they are indeed obsolete, shouldn't we replace the wiki articles with links to the Help section? That might make things less confusing as to where to look for the 'definitive' scripting help.

David Roberson, Tue, 07 Mar 2023 23:35:51 -0500
Though it's more than a decade later, I srt of had the same question:

Quote
Crapadilla wrote: Are the wiki articles on Scripting obsolete?

I've been doing a lot of scripting as I strive to teach myself how to make better scripts. I've finally hit the point where I need more debugging info than the console errors. So, I started looking for the Filter Forge x64.log (for v.9) and found my way to a few forum posts and the wiki, but the instructions to look in "%APPDATA%\Local\Temp\..." didn't turn up the log. I had a fiter editor session going, so I expected it to be there.

Assuming the leads I followed are just out of date, I'm wondering where I should look for the log. I'd appreciate the help!

GMM, Thu, 09 Mar 2023 05:00:14 -0500

Quote
David Roberson wrote: but the instructions to look in "%APPDATA%\Local\Temp\..." didn't turn up the log.

The wiki is correct: if you have a 'print' function in your script, it will log the output to c:\Users\your_username\AppData\Local\Temp\Filter Forge x64.log

David Roberson, Fri, 10 Mar 2023 01:28:59 -0500
Great! So... What is the location of "Filter Forge x64.log" for Filter Forge 9 on Windows 10?

I've done a bit of poking around trying to track down the location of the "Filter Forge x64.log" for Filter Forge 9 on Windows 10. I've checked in:

C:\Users\<username>\AppData\Local\Temp\Filter Forge 9\ and C:\Users\<username>\AppData\Roaming\Filter Forge 9\

Since I'm asking, I obviously didn't find it at either of those places. Weird. The Temp location was mentioned in a post about using the log file, and I remember something about the log file only existing while Filter Forge is running (and the Filter Editor is open). After a bit more searching, I followed someone's advice to look for (or create) a Logs folder in the Roaming location, and restarted Filter Forge. Then, in the Filter Editor, I loaded a filter with a Map Script with known errors and selected it. I confirmed that errors were written to the console and then checked the Logs folder I created; it did not turn up in it or the respective Filter Forge 9 folders I could find.

I also looked for settings in Filter Forge Options > Logging to make sure I didn't need to enable log files to ensure one is created when Map Scripts are running. Logging does not show up in the Options, and it wasn't included in any of the available tabs, like Scripting. Also, only the internal Message Log is mentioned in the Filter Forge Help tool. If it isn't the case that the log file is only created when an error occurs while running a Map Script, it seemed the only option remaining was to contact Filter Forge Support to see if they can provide any additional information on how to enable the creation of log files.

If the log file has been eliminated, that really makes debugging script difficult. One line error messages in the Message Log of the Filter Editor isn't enough to debug whole arrays with indexing problems. Please tell me I've just been looking in the wrong places!

Hope you can give me good news,

David Roberson

GMM, Fri, 10 Mar 2023 06:42:39 -0500

Quote
David Roberson wrote: So... What is the location of "Filter Forge x64.log" for Filter Forge 9 on Windows 10?

The log file is still at c:\Users\your_username\AppData\Local\Temp\Filter Forge x64.log

Quote
David Roberson wrote: I've checked in: C:\Users\<username>\AppData\Local\Temp\Filter Forge 9\ and C:\Users\<username>\AppData\Roaming\Filter Forge 9\ Since I'm asking, I obviously didn't find it at either of those places.

You can't look in random locations and complain it is not at those places. The log can only be found at c:\Users\your_username\AppData\Local\Temp\Filter Forge x64.log

Quote
David Roberson wrote: the log file is only created when an error occurs while running a Map Script

The log file is created when Filter Forge crashes, or when a script (Map or Curve) generates an error.

David Roberson, Tue, 14 Mar 2023 02:08:53 -0400

Quote
GMM wrote: The log file is still at c:\Users\your_username\AppData\Local\Temp\Filter Forge x64.log

Great! As you could tell, I improvised when I did not find a log. Since I have different versions of Filter Forge, I thought it might make a difference on where the log might be.

Quote
GMM wrote: The log file is created when Filter Forge crashes, or when a script (Map or Curve) generates an error.

Thanks for that clarification.

Internal XY Lookup (or UV Remapping)?

David Roberson — Wed, 01 Mar 2023 12:01:53 -0500

David Roberson, Sun, 26 Feb 2023 18:30:54 -0500
I'm stuck on a script that is supposed to do two different coordinate transforms, each of which I've been able to turn into gradients that will remap in a get_sample_map(). The problem arises when it comes to applying one after the other, meaning I still need some kind of internal lookup function that will remap v or r, g, b, a values. This is something I've tried to figure out on my own at times over the past few years without success. If someone can help or provide an example script I'd really appreciate it.

Edit: In general, I am interested in learning how to do most of the basic transforms (like respective transform components) within a lua script (i.e. Offset, Scale, Flip... I've already been helped with Rotation by emme). On thinking about this, the obvious thing is that get_sample_map() essentially does a lookup if you provide x, y coordinates you calculate before it:
[CODE]function prepare()
ox,oy = get_slider_input(ORIGIN_X),get_slider_input(ORIGIN_Y)
d = math.rad(get_angle_input(ROTATION))
s,c = math.sin(d), math.cos(d)
end;

function get_sample(x, y)
local nx = c * (x-ox) - s * (y-oy) + ox
local ny = s * (x-ox) + c * (y-oy) + oy
local r,g,b,a = get_sample_map(nx, ny, SOURCE)
return r,g,b,a
end;
[/CODE]
So, I'm really interested in understanding what is happening in the get_sample functions.

David Roberson, Mon, 27 Feb 2023 00:03:19 -0500
Going off my last thought, I came up with this:
[CODE]function prepare()
-- custom get_sample function
end;

function get_sample(x, y)
local r, g, b, a = get_sample_gradient(x, y)
return r, g, b, a
end;

function get_sample_gradient(x, y)
local nr, ng, nb, na = x, y, (x + y) / 2, 1
return nr, ng, nb, na
end;[/CODE]

If I'm right about this, I can expand on this to create the internal lookup I'm after.

David Roberson, Mon, 27 Feb 2023 00:22:48 -0500
The next experiment succeeded pretty quickly! Since I worked it out on my own, I'm just updating for anyone who has an interest. It really goes to show how hard it can be understand scripting without good reference material or guidance. I was really stumped by my lack of experience with scripting in general and understanding of get_sample functions specifically:

[CODE]local sqrt, min, max, rad, pi = math.sqrt, math.min, math.max, math.rad, math.pi
local sin, cos, tan, asin, acos, atan2 = math.sin, math.cos, math.tan, math.asin, math.acos, math.atan2

function prepare()
-- inputs and precalculation.
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
ang_x = rad(get_angle_input(ANGLE_X) + 180)
ang_y = rad(get_angle_input(ANGLE_Y))
ang_z = rad(get_angle_input(ANGLE_Z) - 180)

cos_ax, sin_ax = cos(ang_x), sin(ang_x)
cos_ay, sin_ay = cos(ang_y), sin(ang_y)
cos_az, sin_az = cos(ang_z), sin(ang_z)
end;

function get_sample(x, y)
local nx, ny = map_spherical_rotations(x, y)
-- local r, g, b, a = get_sample_gradient(nx, ny)
local r, g, b, a = get_sample_map(nx, ny, SOURCE) -- for testing remap seams
return r, g, b, a
end;

function get_sample_gradient(x, y)
local nr, ng, nb, na = x, y, (x + y) / 2, 1
return nr, ng, nb, na
end;

function map_spherical_rotations(x, y)
-- coordinate rotations
local x = x * aspect * pi
local y = y * pi
local nx = cos(x) * sin(y)
local ny = sin(x) * sin(y)
local nz = cos(y)
-- local r, g, b, a = nx, ny, 0, 1
local ax1, ax2 = (nx * cos_ax) + (ny * sin_ax), (nx * sin_ax) - (ny * cos_ax)
local ay1, ay2 = (ax1 * cos_ay) - (cos(y) * sin_ay), (ax1 * sin_ay) + (cos(y) * cos_ay)
local az1, az2 = (ax2 * cos_az) + (ay2 * sin_az), (ax2 * sin_az) - (ay2 * cos_az)
nx = atan2(az1, ay1) * 0.159155 + 0.5
ny = acos(az2) * 0.159155 * 2
if OUTPUT_WIDTH / OUTPUT_HEIGHT == 2 then
nx = nx * 2 - 1
end
return nx, ny
end;[/CODE]
I really hope this helps a few people out.

David Roberson, Mon, 27 Feb 2023 05:00:48 -0500
I guess I spoke too soon. Once I tried to apply my "solution" it became clear that my premise was flawed. This version shows where I went wrong:

[CODE]local sqrt, min, max, rad, pi = math.sqrt, math.min, math.max, math.rad, math.pi
local sin, cos, tan, asin, acos, atan2 = math.sin, math.cos, math.tan, math.asin, math.acos, math.atan2

function prepare()
-- inputs and precalculation.
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
ang_x = rad(get_angle_input(ANGLE_X) + 180)
ang_y = rad(get_angle_input(ANGLE_Y))
ang_z = rad(get_angle_input(ANGLE_Z) - 180)

cos_ax, sin_ax = cos(ang_x), sin(ang_x)
cos_ay, sin_ay = cos(ang_y), sin(ang_y)
cos_az, sin_az = cos(ang_z), sin(ang_z)
end;

function get_sample(x, y)
local nx, ny = map_spherical_rotations(x, y)
-- reroute coordinates thru channels
local r, g, b, a = x, y, (x + y) / 2, 1
-- pass cords and channels to function
r, g, b, a = get_sample_gradient(nx, ny, r, g, b, a)
-- local r, g, b, a = get_sample_map(nx, ny, SOURCE) -- for testing remap seams
return r, g, b, a
end;

function get_sample_gradient(x, y, r, g, b, a)
-- channels pass thru without remapping
local nr, ng, nb, na = r, g, b, a
return nr, ng, nb, na
end;

function map_spherical_rotations(x, y)
-- coordinate rotations
local x = x * aspect * pi
local y = y * pi
local nx = cos(x) * sin(y)
local ny = sin(x) * sin(y)
local nz = cos(y)
-- local r, g, b, a = nx, ny, 0, 1
local ax1, ax2 = (nx * cos_ax) + (ny * sin_ax), (nx * sin_ax) - (ny * cos_ax)
local ay1, ay2 = (ax1 * cos_ay) - (cos(y) * sin_ay), (ax1 * sin_ay) + (cos(y) * cos_ay)
local az1, az2 = (ax2 * cos_az) + (ay2 * sin_az), (ax2 * sin_az) - (ay2 * cos_az)
nx = atan2(az1, ay1) * 0.159155 + 0.5
ny = acos(az2) * 0.159155 * 2
if OUTPUT_WIDTH / OUTPUT_HEIGHT == 2 then
nx = nx * 2 - 1
end
return nx, ny
end;[/CODE]

So, the original problem remains. I can generate the right gradients, but don't know how to use them without get_sample functions.

David Roberson, Wed, 01 Mar 2023 12:01:53 -0500
Just a thought I had last night, the essence of a get_sample function is just to sample a value at specific coordinates. If there are any transformations, they have to come between the sampled value and the returned value. The values can be generated or sampled via the usual get_sample functions. With some trigonometry involved, it's hard to imagine what is happening, for example, when my script generates spherically mapped noise. My mind knots up when a series of transformations needs to be done. Any light someone can shed on this is welcome, but of course I'll keep working on it too. I'll update each time I come up with any techniques or solutions.

Array In Function

James — Sat, 14 Jan 2023 07:57:07 -0500

James, Sun, 27 Jun 2021 03:47:02 -0400
So far I haven't tried using arrays in a script and I wanted to use one in a function, however the following code returns a error, any reason why?

[CODE]function prepare()
end;

function mat4({r1,r2,r3,r4})
local matrix = {}
matrix[1], matrix[2], matrix[3], matrix[4] = r1, r2, r3, r4
return matrix[1], matrix[2], matrix[3], matrix[4]
end

function get_sample(x, y)
return mat4({1.0,0.5,0.25,1})
end;[/CODE]

I'm using FF3, perhaps this is due to the version I am using or maybe a limitation in map scripts? or hopefully just an error in my code.

When using an array in the prepare function it seems to work though.

[CODE]function prepare()
matrix = {1.0,0.5,0.25,1.0}
end;

function get_sample(x, y)
return matrix[1],matrix[2],matrix[3],matrix[4]
end;[/CODE]

_Agentslimepunk, Sat, 14 Jan 2023 07:57:07 -0500
[CODE]function prepare()

end;

function get_sample(x, y)
-- Image generation code goes here.

mat4(1.0, 0.5, 0.25, 1)
local r = matrix[2]
local g = matrix[3]
local b = matrix[2] + y
local a = 1
return r, g, b, a
end;

function mat4(r1, r2, r3, r4)
matrix = {r1, r2, r3, r4}
return matrix

end;[/CODE]

Is this basically what you were after?

Seeking Help: Scripting a Rotation or Angle Map Script

David Roberson — Sun, 20 Nov 2022 02:51:45 -0500

David Roberson, Mon, 11 Jan 2021 21:20:51 -0500
I'll begin this post by saying I've spent half the day studying this problem, and trying to wrap my brain around the trigonometry and matrix calculations of affine transforms, and needed to take a break. Anyone who's visited the forums recently knows I've been working on spherical noise generators, and I started the day updating them. Before updating the Library, I paused to ask if there was anything I was leaving out. For the Perlin noise version, I did not have an Angle control, and I knew that there was an Angle input I could add to the component. The problem was, how do I make use of one, if I add it?

So, lots of research and reading commenced. I did poke around to see if I had a filter with a map script in it that used some form of rotation, but there really isn't an efficient way to do that kind of search. So, that left asking the forum if anyone knew of or could provide a script for reference. Of course, there's no telling how long it might take to get a positive response, but you know what happens if you never even ask. It will take me a while to work through this on my own, so I decided to put the request out there in the meantime.

As always, any help is appreciated.

David Roberson, Mon, 11 Jan 2021 22:04:57 -0500
On further consideration, I realize this might be a moot point, as far as my real objective is concerned. I'd gotten used to the quirks of taking 2D noise and compositing a spheremap, where playing with the Angle could produce interesting and useful variations. But, what I'm working with now is 3D noise. So, in that context, I'd really be trying to come up with rotation on x, y and z axes. That's probably too much to ask anyone to provide, however useful it'd be to me. If someone is up to the challenge, I'd love to see the example they'd come up with, but I'm not going to hold my breath.

I'd still like to know how to do 2D rotation, but it's more of an academic interest now that I've looked into it a bit.

David Roberson, Mon, 11 Jan 2021 22:11:03 -0500
While I'm still logged in, I might as well share the script for a little oddity I came up with. I found a tiny function to rotate a vector and dropped it into a map script to see what it'd do. I found the output perplexing!

The code is simple, just create a map script with an Angle input, and paste this in:

[CODE]function prepare()
angle = get_angle_input(ANGLE)
end;

function get_sample(x, y)
-- local r, g, b, a = get_sample_map(x, y, SOURCE)
-- local x, y = rotate(x,y,angle)
local nx, ny = rotate(x,y,angle)
local r = nx
local g = ny
local b = (nx + ny) / 2
local a = 1
return r, g, b, a
end;

function rotate(x, y, a)
local c = math.cos(a)
local s = math.sin(a)
return c*x - s*y, s*x + c*y
end[/CODE]

David Roberson, Sun, 06 Jun 2021 19:27:13 -0400
This is not the first time I've tried to use an angle control in a map script, only to get a mysterious "unexpected nil value" errors or the like. I thought this time was simple enough, an angle offset script. The error comes when I return v on the following:

[CODE]function prepare()
-- prepare
dis = 5 -- get_slider_input(DISTANCE)
dir = math.rad(get_angle_input(DIRECTION))
end;

function get_sample(x, y)
nx = math.cos(dir)
ny = math.cos(dir)
-- get source
v = get_sample_grayscale(x,y,SOURCE)
x = x + nx * dis
y = y + ny * dis
return v
end;[/CODE]

Anyone care to help?

David Roberson, Sun, 06 Jun 2021 20:23:56 -0400
And its Any Angle Offset v2.0 By uberzev to the rescue! I knew it was out there, but couldn't find it on my computer. Working on the map script helped me think of the right search string to locate it in the Library. Even so, I'm going to want to know what I'm doing wrong with my map script, so help would still be appreciated!

emme, Mon, 07 Jun 2021 09:48:28 -0400
The errors are because FF expects all the RGB values returned - you're only returning a single value. Using return v,v,v should fix the errors.

You also want to calculate the new coordinates before you sample the source image. Move the get_sample_grayscale below the new x/y coordinates.

I think there's a typo: nx = math.cos(dir) should use math.sin() instead.

Anyways, I don't think the script will rotate the image. Only offset it in a circular path.

Here is a script that rotates an image around a point:
[CODE]
function prepare()
ox,oy = get_slider_input(ORIGIN_X),get_slider_input(ORIGIN_Y)
d = math.rad(get_angle_input(ROTATION))
s,c = math.sin(d), math.cos(d)
end;

function get_sample(x, y)
local nx = c * (x-ox) - s * (y-oy) + ox
local ny = s * (x-ox) + c * (y-oy) + oy
local r,g,b,a = get_sample_map(nx, ny, SOURCE)
return r,g,b,a
end;
[/CODE]

David Roberson, Mon, 07 Jun 2021 15:18:16 -0400
As always, emme, thank you for your sage advice! I will try your corrections out and tell you how it goes. I was originally interested in rotating an image, or coordinate samples inside perlin noise, but for this last experiment I was going for the circular offset. That's something I was able to do with uberzev's snippet, but it's nice to see how to script it. I really appreciate the rotation script. That will be a lot of help with figuring things out with my other ambitions.

David Roberson, Mon, 07 Jun 2021 15:30:52 -0400
Okay, returning v,v,v did fix the error. I made the other corrections you suggested, but the resulting script behaves oddly, jumping around seemingly at random as I increase the angle. Here are the changes I made:

[CODE]function prepare()
-- prepare
dis = 0.5 -- get_slider_input(DISTANCE)
dir = math.rad(get_angle_input(DIRECTION))
end;

function get_sample(x, y)
nx = math.sin(dir)
ny = math.cos(dir)
-- get source
x = x + nx * dis
y = y + ny * dis
v = get_sample_grayscale(x,y,SOURCE)
return v,v,v
end;[/CODE]

David Roberson, Mon, 07 Jun 2021 19:50:00 -0400
On later thought, I wonder if part of the problem is that my circle offset script does not address X and Y Origins. I got up from a nap to pose that question, and I'll see if I can figure out how to test the theory myself next time I'm free to work on it. Thanks.

James, Thu, 08 Jul 2021 13:55:24 -0400
Did anyone ever figure out how to rotate an input around a central point like the rotate node?

I have seen the following GLSL code:

[CODE]float s = sin(angle);
float c = cos(angle);

return mat2(
c, -s,
s, c
);[/CODE]

It is similar to the function David posted in the 3rd post which didn't seem to do anything for me. I am not sure how to recreate the mat2 matrix part of the GLSL however so I haven't got anything I have tried working yet.

I tried the code above but that seems to move the image around a radius rather than actually rotating it.

emme, Sat, 10 Jul 2021 10:33:33 -0400

Quote
James wrote: Did anyone ever figure out how to rotate an input around a central point like the rotate node?

Check few posts above ;)

Quote
emme wrote: Here is a script that rotates an image around a point: [CODE] function prepare() ox,oy = get_slider_input(ORIGIN_X),get_slider_input(ORIGIN_Y) d = math.rad(get_angle_input(ROTATION)) s,c = math.sin(d), math.cos(d) end; function get_sample(x, y) local nx = c * (x-ox) - s * (y-oy) + ox local ny = s * (x-ox) + c * (y-oy) + oy local r,g,b,a = get_sample_map(nx, ny, SOURCE) return r,g,b,a end; [/CODE]

Quote

emme wrote:
Here is a script that rotates an image around a point:
[CODE]
function prepare()
   ox,oy = get_slider_input(ORIGIN_X),get_slider_input(ORIGIN_Y)
   d = math.rad(get_angle_input(ROTATION))
   s,c = math.sin(d), math.cos(d)
end;

function get_sample(x, y)
   local nx = c * (x-ox) - s * (y-oy) + ox
   local ny = s * (x-ox) + c * (y-oy) + oy
   local r,g,b,a = get_sample_map(nx, ny, SOURCE)
   return r,g,b,a
end;
[/CODE]

James, Sun, 11 Jul 2021 15:09:21 -0400
That works great thanks :)

I noticed when increasing the angle it travels in the opposite direction to the default rotate node, so I just put the angle in a lerp function making it decrease in value as then it matches the behaviour of the default rotate node.

David Roberson, Mon, 18 Jul 2022 04:15:09 -0400
@James

I revisited this thread to pick up emme's rotate script when I noticed your response, and I got curious about the lerp function you added. Could you explain how you used it? Given the same problem, I would have tried another method to invert the angle input. I'd be happy with just the code for the script, too. Thanks!

David Roberson, Sun, 06 Nov 2022 07:18:49 -0500
I have spent the past few days working on adding better rotation controls to map scripts derived fr om Planet Maker 3D by andyz. Along the way I visited Rotating 3D shapes wh ere I was able to fill in the blanks in my understanding of 3D rotations. I applied that to the script used in my current project, but I'm also interested in using the functions from that page to emulate the Angle control of Perlin Noise in a 3D Perlin Noise map script.

I made an attempt to convert the JS to Lua, but I think I need a more experienced set of eyes to tell if I'm on the right track. At the moment, I only have a vague idea how I'd use the functions in question.

Take a look:
[CODE]
-- rotation functions js to lua
function prepare()
-- input
local theta = math.rad(get_angle_input(THETA))
-- precalc, global vars for rotation functions
sin_theta = sin(theta);
cos_theta = cos(theta);
end;

function get_sample(x, y)
-- incomplete, pass array as var?
x, y, z = rotate_z3d(x,y,sin_theta,cos_theta), rotate_x3d(x,y,sin_theta,cos_theta), rotate_y3d(x,y,sin_theta,cos_theta)
end;

function rotate_z3d(x,y,sin_theta,cos_theta)
for node_index = 0, NODE_COUNT do
local NODE = {}
local NODE_COUNT
local node_index
if (node_index < nodes_length) then
NODE_COUNT = node_index - 1
break
NODE[node_index] = {x,y}
y = y * cos_theta - z * sin_theta
z = z * cos_theta + y * sin_theta
end

end;
function rotate_x3d(x,y,sin_theta,cos_theta)
local NODE = {}
local NODE_COUNT
local node_index
for node_index = 0, NODE_COUNT do
if (node_index < nodes_length) then
NODE_COUNT = node_index - 1
break
NODE[node_index] = {x,y}
y = y * cos_theta - z * sin_theta
z = z * cos_theta + y * sin_theta
end

end;
= function rotate_y3d(x,y,sin_theta,cos_theta)
local NODE = {}
local NODE_COUNT
local node_index
for node_index = 0, NODE_COUNT do
if (node_index < nodes_length) then
NODE_COUNT = node_index - 1
break
NODE[node_index] = {x,y}
y = y * cos_theta - z * sin_theta
z = z * cos_theta + y * sin_theta
end
end;[/CODE]

Here is the JS:

[CODE]// rotation functions from js

var rotateZ3D = function(theta) {
var sinTheta = sin(theta);
var cosTheta = cos(theta);
for (var n = 0; n < nodes.length; n++) {
var node = nodes[n];
var x = node[0];
var y = node[1];
node[0] = x * cosTheta - y * sinTheta;
node[1] = y * cosTheta + x * sinTheta;
}
};
var rotateX3D = function(theta) {
var sinTheta = sin(theta);
var cosTheta = cos(theta);
for (var n = 0; n < nodes.length; n++) {
var node = nodes[n];
var y = node[1];
var z = node[2];
node[1] = y * cosTheta - z * sinTheta;
node[2] = z * cosTheta + y * sinTheta;
}
};
var rotateY3D = function(theta) {
var sinTheta = sin(theta);
var cosTheta = cos(theta);
for (var n = 0; n < nodes.length; n++) {
var node = nodes[n];
var x = node[0];
var z = node[2];
node[0] = x * cosTheta + z * sinTheta;
node[2] = z * cosTheta - x * sinTheta;
}
};
[/CODE]

SpaceRay, Sun, 20 Nov 2022 02:51:45 -0500
Sorry that I can not help you as I have no knowledge of scripting, but I really admire all of you that are able to do it and be able to go beyond what can be done with the FF components and make such creative things that are not possible in other ways

Scripting a Spherical Noise Map Generator

David Roberson — Sat, 29 Oct 2022 10:46:05 -0400

David Roberson, Tue, 29 Dec 2020 19:43:23 -0500
A few weeks ago, I stumbled across an example Spherical Noise Map Generator using C++/libnoise. That got me to wondering if FF would be capable of doing it, too. I posted a Feature Request and emme helpfully supplied an example Map Script, pointing out that it could be further enhanced to multi-octave noise, and other cool things.

spherical_noise_v001.ffxml

I remembered one of the Script API I saved was for multi-octave perlin noise and went back to study it, for help making emme's example work along the same lines. Unfortunately, I'm pretty much a beginner with Lua, and it's been years since I've done any real coding, so I could not see a direct path to follow. It seems that the "multi-octave" portion of the script is already using a z-coordinate, so that struck me as a conflict even before I realized emme's 3-coordinate example sets up the variables in a very different way. As in, I barely understand the logic of what it's doing, so I can't follow the transition from my 2-coordinate multi-octave example to 3-coordinates.

Maybe somebody can help me with that. The API I'm referencing is: Script API - Multi-Octave Perlin.ffxml. This is going to be a learning project for me, and other features will come to mind, or variations along the same lines (I've mentioned exploring a way to do a Whorley noise spherical map generator, for example). I'm just not sure how much I have to study before I can figure this out on my own.

Whatever happens, I'll try to keep track of my progress here, for the benefit of anyone interested in the same challenge.

emme, Tue, 29 Dec 2020 21:11:06 -0500
I added some features to the script: octaves, roughness/detail, distortion and noise-profile. This multi-octave implementation probably isn't exactly the "correct" way to do it - I just did it the quick and dirty way :)

I think there is also a 2D Worley noise example script in the Noise-API help section. Not sure how easy it'll be to convert into 3D, but my guess would be, not super difficult. I'll check it out at some point.

In the original thread, you mentioned texture baking in Blender - I'll answer it here. After creating a UV-sphere, create a new material in the shading editor and add some texturing. Next, add a new empty image texture (alt+n -> texture -> image texture) and click the New -button. In the render properties tab, select Cycles for your render engine and you should see a Bake tab below. Select the bake type ect. and click Bake. You can now use the baked texture on your object or export it to disk.

David Roberson, Wed, 30 Dec 2020 03:37:24 -0500
Thank you, emme! I'll check out your added features now. I discovered pretty quickly that learning Lua is going to be a little harder than I first thought. The documentation I've found so far is a bit dry and quite a bit shy of tutorials I can pick up on quickly. I still think it's worth learning, and I hope the forums here will help with that. I already have a few ideas of what features I'd like the component to have, starting with the usual: probably map inputs for color, roughness, contrast, and possibly distortion, with scale (already there), angle, details (now added) and variation. I think I'd also like to be able to pan through the 3 coordinates interactively to explore and position the noise. I did pick up the whorley noise API, today. I'll be interested to see what you come up with--you'll probably figure it out way ahead of me :D .

As for Blender, the answer helps. I imagine I'd have already learned how to do it if I'd experimented with texture baking beyond learning that it could be done. The first time is always a bit daunting.

David Roberson, Fri, 01 Jan 2021 16:19:25 -0500
Emme, I'm no judge of best implementation, so I wouldn't criticize your roughness/detail and multi-octave method. It seems to work well enough for basic use. I can say that the difference between your method and the API example is greater than my analysis skills can parse. The multi-octave perlin example does a lot with the input values in the prepare() function to generate octave derived values used in the get_sample() function. The noise itself is ultimately used as the alpha matrix in a blend_normal() function that returns the composite foreground and background maps integration.

The map blending is not a high priority for me, when it comes to expanding on your script, since I'd have to supply spherically mapped inputs to get a usable result. Even though the same is true when it comes to mapped Roughness and Contrast, there are ways to mitigate their influence if I employ a circle curve gradient that masks out the top and bottom portions of the supplied maps. The effects I can get that way are useful in a lot of cases. Not that I'm getting any closer to implementing Roughness or Contrast in your script. I don't even have an example for how to do contrast adjustments, mathematically.

My scripting adventures may come to a quick end. It's looking like something I can't pick up on my own. I just can't find the kind of instruction or examples I can follow, and my math skills are probably not good enough to solve graphics problems without explicit examples. I'm only able to look at the script and understand what it's doing. I can't adapt it to something else. Sigh.

In any case, thanks again for your help, and your excellent examples.

David Roberson, Fri, 01 Jan 2021 18:30:59 -0500
I wrote a nice little post detailing my first update to emme's script, and it got discarded during preview as I was logged off the forum. Bother. Just to recap, what I remember, I found it easy to add offsets to the x, y and z coordinates via grayscale input. I tested it out with perlin noise inputs in seamless and non-seamless modes and the results were both seamless, so adding the values to the initial coordinate declarations worked fine. Obviously, the offsets can produce additional distortion, so extreme results are possible. I'm posting the script code for quick review, with the ffxml attached below.

I still need some tutoring or an example to follow up on adding Contrast or Roughness (independent of Details) to this. I just don't know the math for the first, and my example of the second is implemented very differently from emme's approach. I sort of understand what it's doing, but not well enough to adapt it.

[CODE]function prepare()
oct_max = get_intslider_input(NOISE_OCTAVES)
detail = 4 - get_slider_input(DETAIL) * 2 + 0.01
scale = get_slider_input(NOISE_SCALE) * 10 + 1
distort = get_slider_input(NOISE_DISTORT) *2
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
set_perlin_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
local v = 0
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
local s = 500
local amp = 1
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) * scale + vosx
local ny = math.sin(x) * math.sin(y) * scale + vosy
local nz = math.cos(y) * scale + vosz
for oct = 1, oct_max do
local d1 = get_perlin_noise(nx+1,ny,nz,s) * distort
local d2 = get_perlin_noise(nx+2,ny,nz,s) * distort
local d3 = get_perlin_noise(nx+3,ny,nz,s) * distort
if oct == 1 then v = get_perlin_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_perlin_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
s = s / 2
amp = amp / detail
end
v = get_sample_curve(x,y,v,NOISE_PROFILE)
return v,v,v,1
end;[/CODE]

emme, Fri, 01 Jan 2021 23:33:22 -0500
Added mappable detail (or roughness) and distortion. The noise profile should work for mappable contrast, but I just tried mapping it, and it breaks the seamlessness for some reason. Could be that the curve gets sampled incorrectly with non-square images, I'll have to look into that. Anyways, contrast is easy to adjust after the script, so I just added a mapped tone curve for that. Let me know if works ok.

Like you mentioned, all the input maps need to be in the same spherical format in order to maintain seamlessness. Mapping with seamless 2D perlin won't be seamless on a sphere - even if it looks seamless in 2D.

Pretty cool to play with the xyz offsets you added btw. Really helps with visualizing the projection :)

David Roberson, Fri, 01 Jan 2021 23:35:35 -0500
A quick little progress update, here's some thoughts on Brightness/Contrast adjustment adapted fr om an online source. I revised the examples from the two articles I found into rough Lua code, without changing any of the values given. I only updated the variable names to fit in with other scripting I've dealt with. I've noted which values before the code blocks. I assume I'll need to convert the values for a 0-1 range before proceeding?

Image Adjustment links to the Articles (copyright © 2008, 2010, 2015 Francis G. Loch) included.

Brightness Adjustment

Adjusting the brightness of an image is one of the easiest image processing operations that can be done. All that is involved is adding the desired change in brightness to each of the red, green and blue color components.

In pseudo-code it would go something like this (unstated, but assuming value range of 0-255)(also assuming brightness is a slider value, so technically declared in prepare() and omitted here):

[CODE]function get_sample(x,y)
local r, g, b, a = get_sample_map(x, y, COLOR)
local nr = truncate(r + brightness)
local ng = truncate(g + brightness)
local nb = truncate(b + brightness)
return nr, nb, ng, a
end;[/CODE]

Contrast Adjustment

The first step is to calculate a contrast correction factor which is given by the following formula (assuming the value in question is RGB in the 0-255 value range):

[CODE] f = 259 * (c + 255) / 255 * (259 - c)[/CODE]

In order for the algorithm to function correctly the value for the contrast correction factor (F [or f, in the line above]) needs to be stored as a floating point number and not as an integer. The value C [c] in the formula denotes the desired level of contrast.

The next step is to perform the actual contrast adjustment itself. The following formula shows the adjustment in contrast being made to the red component of a color:

[CODE] r = f * (r - 128) + 128[/CODE]

Translating the above formulas into pseudo-code would give something like this (assuming the value of contrast will be in the range of -255 to +255, wh ere negative values will decrease the amount of contrast and, conversely, positive values will increase the amount of contrast):

[CODE] factor = (259 * (contrast + 255)) / (255 * (259 - contrast))

function get_sample(x,y)
local r, g, b, a = get_sample_map(x, y, COLOR)
local nr = truncate(factor * (r - 128) + 128)
local ng = truncate(factor * (g - 128) + 128)
local nb = truncate(factor * (b - 128) + 128)
return nr, ng, nb, a
end;[/CODE]

The function truncate() just ensures that the new values of red, green and blue are within the valid range of 0 to 255.

The function truncate() in pseudo-code (assuming value range of 0-255):

[CODE] function truncate(value)
If value < 0 Then value = 0
If value > 255 Then value = 255
Return value
end;[/CODE]

As always, your thoughts are welcome. This is just a nudge in the direction of a -- hoped for -- mapped contrast control. That, and a mapped roughness control are my two main objectives for now.

emme, Fri, 01 Jan 2021 23:46:01 -0500
You might be overthinking it :)

You can already do mapped contrast with existing components. Since the operation is not directional or size dependent , it won't break seamlessness - as long as you use a spherically seamless input maps. Check my last post.

David Roberson, Sat, 02 Jan 2021 02:48:06 -0500
I'm sure I am, emme. I've been known to do that. Got the stubbornness gene from both parents, I guess! I missed your update with the mapped details/roughness and distortion while I was working, so my update this time contains my own solution for mapped roughness. I played a little with the details formula to get in a little extra roughness at the high end. I'll post the code for those who just want a glance at the script, before the attached ffxml with my current experiments in it.

One last thought, how do you enter a tab inside the script editor? Or do you compose the script outside it and just paste in the final version when you're done?

[CODE]function prepare()
oct_max = get_intslider_input(NOISE_OCTAVES)
-- detail = 4 - get_slider_input(NOISE_DETAIL) * 2 + 0.01 -- mapped alternate
-- scale = get_slider_input(NOISE_SCALE) * 10 + 1 -- mapped alternate
distort = get_slider_input(NOISE_DISTORT) * 2
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
set_perlin_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
local v = 0
local scale = get_sample_grayscale(x, y, SCALE) -- * 10 + 1 -- unsuitable range
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
local detail = 3.75 - get_sample_grayscale(x, y, DETAIL) * 2 + 0.01
local s = 500
local amp = 1
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) * scale + vosx
local ny = math.sin(x) * math.sin(y) * scale + vosy
local nz = math.cos(y) * scale + vosz
for oct = 1, oct_max do
local d1 = get_perlin_noise(nx+1,ny,nz,s) * distort
local d2 = get_perlin_noise(nx+2,ny,nz,s) * distort
local d3 = get_perlin_noise(nx+3,ny,nz,s) * distort
if oct == 1 then v = get_perlin_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_perlin_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
s = s / 2
amp = amp / detail
end
v = get_sample_curve(x,y,v,NOISE_PROFILE)
return v,v,v,1
end;[/CODE]

David Roberson, Sun, 03 Jan 2021 17:18:41 -0500
Apart from adding mapped distortion to my working script, I have not made any new progress, so this may be the final version I'll end up using unless I come up with something new I need the script to do. I've wondered about working with multiple noise instances to be blended into the main result, in keeping with the recommendation to make one Map Script to do what you need rather than have multiple Map Scripts in one filter. Even so, I have to prototype the composite with regular components to figure out exactly what I'm trying to accomplish before working out the script to do it internally.

Like before, here's the current script code, with the attached ffxml below:

[CODE]function prepare()
oct_max = get_intslider_input(NOISE_OCTAVES)
-- detail = 4 - get_slider_input(NOISE_DETAIL) * 2 + 0.01 -- mapped alternate
-- scale = get_slider_input(NOISE_SCALE) * 10 + 1 -- mapped alternate
-- distort = get_slider_input(NOISE_DISTORT) * 2 -- mapped alternate
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
set_perlin_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
local v = 0
local scale = get_sample_grayscale(x, y, SCALE) -- * 10 + 1 -- unsuitable range
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
local detail = 3.75 - get_sample_grayscale(x, y, DETAIL) * 2 + 0.01
local distortion = get_sample_grayscale(x, y, DISTORTION) * 2
local s = 500
local amp = 1
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) * scale + vosx
local ny = math.sin(x) * math.sin(y) * scale + vosy
local nz = math.cos(y) * scale + vosz
for oct = 1, oct_max do
local d1 = get_perlin_noise(nx+1,ny,nz,s) * distortion
local d2 = get_perlin_noise(nx+2,ny,nz,s) * distortion
local d3 = get_perlin_noise(nx+3,ny,nz,s) * distortion
if oct == 1 then v = get_perlin_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_perlin_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
s = s / 2
amp = amp / detail
end
v = get_sample_curve(x,y,v,NOISE_PROFILE)
return v,v,v,1
end;[/CODE]

David Roberson, Mon, 04 Jan 2021 16:37:35 -0500
Hey, emme. I've confirmed that mapped curves do break spherical seamlessness, unless their sources are spherically mapped. Even then, some curve utilities, like Repeat, still break it.

David Roberson, Mon, 04 Jan 2021 16:47:07 -0500
I had a system crash and lost my working ffxml, so I retrieved the one I posted here last. That's when I discovered it was also out of date. So, just a quick repost with the final tweaks, for anyone interested in the prototypes so far. Versions are noted inside, (most of my changes were to emme's v.002, so hers is the only v.003 script in it) so I dropped the version of the ffxml itself. The final change was making Distortion grayscale accept HDR values, since distortions in the +/-1 range are useful, and mapped values beyond it can be useful in some cases. I thought of adding strength sliders -- one for Distortion and a Percentage for the offsets -- to adjust the influence of mapped input, but decided that could be handled by adjustment components beforehand. It's easy enough to add if anyone feels they'd be useful, internally, in spite of being redundant when mapped inputs are not used.

David Roberson, Mon, 04 Jan 2021 17:13:37 -0500
Oops! Pointed out the wrong bad guy. Repeat did not break seamlessness after all. It was an Offset mapping of Amplitude that got weird. It didn't really break seamlessness as populate the background with fractional offsets of the source noise. It technically doesn't break the seam at top and bottom, it just creates an unwanted tiling within the perimeter.

David Roberson, Tue, 05 Jan 2021 20:16:38 -0500
I've been losing my work file in spite of regular saves, so I'm posting the new version while I'm still in the Filter Editor. I've checked that it did save this time, so I might be right that Projects are messing up the file somehow, but this time I made sure I was closed out of any open Projects.

The change was simply adding Foreground/Background map inputs, with my noise assigned to Opacity, with an HDR option for the inputs. Like emme said, an easy thing to add once I decided it was still worth having. I'd almost forgotten it was one of my original goals!

Here's the script code, with the attached ffxml, below:
[CODE]function prepare()
oct_max = get_intslider_input(NOISE_OCTAVES)
-- detail = 4 - get_slider_input(NOISE_DETAIL) * 2 + 0.01 -- mapped alternate
-- scale = get_slider_input(NOISE_SCALE) * 10 + 1 -- mapped alternate
-- distort = get_slider_input(NOISE_DISTORT) * 2 -- mapped alternate
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
set_perlin_noise_seed(get_intslider_input(NOISE_SEED))
if (get_checkbox_input(HDR)) then
hdr = true
else
hdr = false
end
end;

function get_sample(x, y)
local r, g, b, a = get_sample_map(x, y, BACKGROUND)
local r2, g2, b2, a2 = get_sample_map(x, y, FOREGROUND)
local v = 0
local scale = get_sample_grayscale(x, y, SCALE) -- * 10 + 1 -- unsuitable range
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
local detail = 3.75 - get_sample_grayscale(x, y, DETAIL) * 2 + 0.01
local distortion = get_sample_grayscale(x, y, DISTORTION) * 2
local s = 500
local amp = 1
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) * scale + vosx
local ny = math.sin(x) * math.sin(y) * scale + vosy
local nz = math.cos(y) * scale + vosz
for oct = 1, oct_max do
local d1 = get_perlin_noise(nx+1,ny,nz,s) * distortion
local d2 = get_perlin_noise(nx+2,ny,nz,s) * distortion
local d3 = get_perlin_noise(nx+3,ny,nz,s) * distortion
if oct == 1 then v = get_perlin_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_perlin_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
s = s / 2
amp = amp / detail
end
v = get_sample_curve(x,y,v,NOISE_PROFILE)
local opacity = v
r, g, b, a = blend_normal(r, g, b, a, r2, g2, b2, a2, opacity, hdr)
return r, g, b, a
end;[/CODE]

David Roberson, Tue, 05 Jan 2021 22:17:29 -0500
Since I lost what I was working on, once I finished reconstructing what I could still remember (last post), I thought I'd begin looking into other types of spherical noise. I quickly composed my own version of Spherical Uniform Noise and got it working in color and grayscale modes. Sadly, the results don't differ any from the API - Uniform Noise. You just get a uniform size noise, without polar distortion like I expected. Still, it was just a warm-up before trying to tackle something more challenging, like Cell Noise. I'm not yet sure if I can adapt the example to this, but at the moment it's the only kind I have an example for.

I'd be thrilled if anyone can provide (or post links to) scripts or coding samples for scripting/programming other types of Worley noise. I can't bug emme for everything (though some times I can't help myself :D)!

Just the code snip, this time:
[CODE]function prepare()
set_noise_seed(get_intslider_input(SEED))
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
color = get_checkbox_input(COLOR)
end;

function get_sample(x, y)
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) -- * scale
local ny = math.sin(x) * math.sin(y) -- * scale
local nz = math.cos(y) -- * scale
local v = get_noise(nx,ny,nz)
local r = get_noise(nx,ny,nz+1)
local g = get_noise(nx,ny,nz+2)
local b = get_noise(nx,ny,nz+3)
if color then
return r,g,b,1
else
return v,v,v,1
end
end;[/CODE]

David Roberson, Wed, 06 Jan 2021 03:20:39 -0500
Well, a little bit of progress is often followed by a lot of confusion. I quickly got lost trying to work out how to do Worley cells in 3D. I don't really know how to explain my confusion other than by commenting on the API script, and seeing if someone can point me back in the right direction. I also experimented, quasi-logically to see if I could at least make the 2D cells seamless, but there doesn't seem to be set_noise_seamless() or set_noise_seamless_region() functions to call.

[CODE]function prepare()
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2)
set_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
-- following block generates spherical coordinates...
-- local x = x * aspect * math.pi
-- local y = y * math.pi
-- local nx = math.cos(x) * math.sin(y) * scale
-- local ny = math.sin(x) * math.sin(y) * scale
-- local nz = math.cos(y) * scale
-- this part gets replaced with worley noise algorhythm
-- local v = get_perlin_noise(nx,ny,nz,500)
local sx, sy = x / scale , y / scale -- add sz = z / scale?
local cell_x, cell_y = math.floor(sx), math.floor(sy) -- add cell_z = math.floor(sz)?

local offset_x, offset_y
-- add offset_z -- no idea how this integrates with: for offset_z=-1,1 do ... add nest?
-- in nest, add dz = cell_z + offset_z + get_noise(?) or replace z value in dx/dy get_noise with cell_z + offset_z?
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, 0)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, 1)
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2) -- add in (sz - dz)^2 somehow? get cube root somehow?
min_dist = math.min(dist, min_dist) -- not even a clue here
end
end

local a = 1
min_dist = 1.0 - min_dist
return min_dist, min_dist, min_dist, a
-- obviously, this is changed from v to min_dist for each channel
-- return v,v,v,1
end;[/CODE]

David Roberson, Wed, 06 Jan 2021 14:25:03 -0500
I've been scouring the web for help on Worley noise, but the examples are in different scripting or coding languages and are nowhere near as succinct and clear as the API script I got from the Noise API page on the FF site. I'll keep looking over what I find, but I'm getting more new questions than answers. For example, how to implement different distance formulas for Euclidean, Manhattan, Chebyshev (sp?), etc.

These are the key to the various types of Worley noise you can get. A great overview of this is in the following video: Coding in the Cabana 4: Worley Noise

The video mentions several online resources you'd come across searching the web, which I've seen (I can retrieve the links if prompted, but again, they're not terribly hard to find). The real trick is really understanding what these pages contain. It's really quite the rabbit hole. To those who have become knowledgeable about this stuff, how did you learn it? I don't think you can google your way to expertise. If there are more explicit tutorials and examples out there, they're not turning up in my searches. I will keep sharing anything I learn, as I go, however.

David Roberson, Wed, 06 Jan 2021 16:06:19 -0500
Well, my "analysis" of Worley noise all falls apart the instant I finally notice I can't reference the global value z... unlike the x,y args in the get_sample(), it simply doesn't exist. So obvious it slipped past me entirely that the z coordinate I'm thinking of is only introduced in the noise function.

So, yeah, just ignore that whole post.

David Roberson, Wed, 06 Jan 2021 17:01:33 -0500
A little progress... I was partly on the right track with my analysis, after all. Once I provided a z coordinate, I was able to generate 3d Worley noise. It's still cartesian, rather than spherical, but the feature points used to calculate the distances are now arranged in x,y,z coordinate space.

Here's the code:
[CODE]function prepare()
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2)
set_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
local z_coord = get_sample_grayscale(x, y, Z_COORDINATE)
local sx, sy = x / scale , y / scale
local sz = z_coord / scale
local cell_x, cell_y = math.floor(sx), math.floor(sy)
local cell_z = math.floor(sz)

local offset_x, offset_y, offset_z
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
min_dist = math.min(dist, min_dist)
end
end
end

local a = 1
min_dist = 1.0 - min_dist
return min_dist, min_dist, min_dist, a
end;[/CODE]

Here's the output I got:

David Roberson, Wed, 06 Jan 2021 18:02:10 -0500
More progress! Once I had a bit more of a handle on 3d Worley noise (above), I was able to work out how to integrate emme's spherical approach. I'm not sure if "local nz = math.cos(y) * z" is really, technically, the right way to do this, but it works, with x,y remapped the default way. I was pretty surprised when it worked. I guess I'm starting to understand the math better, though I'm sure the research I've done has helped get it through my head.

Scaling needed a little adjusting, and the multiplier I went with doesn't zoom in quite as far as it could. I just liked seeing a few cells at the maximum Scale. I'll share the ffxml in my next post. I still need to figure out how to address the nth point as a variable, to get other permutations, i.e. 2nd closest, 3rd closest, etc. point. I also need to figure out how to apply the other distance formulas for Manhattan, Chebyshev, etc. That's where the other Worley type noises we're familiar come from, with formula variations. So, still work to do!

Here's the code:
[CODE]function prepare()
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2) * 5
set_noise_seed(get_intslider_input(NOISE_SEED))
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
end;

function get_sample(x, y)
local x = x * aspect * math.pi
local y = y * math.pi
local z = get_sample_grayscale(x, y, Z_COORDINATE)
local nx = math.cos(x) * math.sin(y)
local ny = math.sin(x) * math.sin(y)
local nz = math.cos(y) * z
local sx, sy, sz = nx / scale , ny / scale, nz / scale
local cell_x, cell_y, cell_z = math.floor(sx), math.floor(sy), math.floor(sz)

local offset_x, offset_y, offset_z
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
min_dist = math.min(dist, min_dist)
end
end
end

local a = 1
min_dist = 1.0 - min_dist
return min_dist, min_dist, min_dist, a
end;[/CODE]

And here's the example output:

David Roberson, Wed, 06 Jan 2021 19:00:38 -0500
Okay, I went ahead and added map inputs for Foreground/Background, and a Profile curve. The next step would be to implement Offset X/Y/Z, Detail and Distortion like my Spherical Perlin, but I'm not sure how they'd fit into the structure of my Spherical Cell Noise. I may have to see if emme has some advice, there, before proceeding. I'll skip the code this time and just share the output example. You can get the Map Script from the ffxml I'll be posting right after this.

David Roberson, Wed, 06 Jan 2021 19:01:35 -0500
One note of warning, the Z Coordinate is an HDR grayscale input, but it really should be a Value input; plugging in a grayscale image will give you a sort of tiled distortion, so just use it like a Value slider.

Here's my current work file:

David Roberson, Thu, 07 Jan 2021 14:59:32 -0500
In the hope of adding Detail and Distortion, I've tried a few things, including making a get_worley_noise() function, but my inexperience with Lua, or rustiness with coding and scripting in general, have been tripping me up. With the function, I'm having trouble with referring x,y,z parameters to the function and returning them as x,y,z values to the get_sample() that calls it. As for Detail and Distortion, I'm not sure where to apply the modifiers so they'll have the desired effect. I'm mostly breaking the distance mapping, in the way's I've tried so far. I'm pretty talented at breaking code, as opposed to fixing it. So, if there are any willing volunteers, I'll leave those objectives out there for anyone interested in lending a hand. I wish I was good enough at this to do it on my own, but I'm relying mostly on my intuition and scripting doesn't lend itself to intuitive approaches very often.

Oh, since a bit part of the goal here is learning, along the way, I'd be interested in any help with Lua. If you just post a sample function like what I'm after, I'm game to try and apply the lesson to my goal, myself. No, the forum is not seeing a lot of traffic, so it might take a while for anyone to bite. I'll keep trying until help arrives or I eventually figure it out. It got me halfway where I wanted with Spherical Worley Noise. Help is always appreciated, though.

David Roberson, Thu, 07 Jan 2021 16:39:09 -0500
I guess I spoke too soon. My get_worley_noise() function works after all. I just had some issue with the editing I was doing at the original time that was throwing up nil errors. Before scrapping the idea, I made one last attempt with a fresh cut-and-paste into the script editor, and it worked. I must have typoed a variable somewhere, before. I can never spot them. So, here's the script using the function (I'll see if there are other things I can do as far as Details and Distortion, now that I have this working):

[CODE]function prepare()
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2)
set_noise_seed(get_intslider_input(NOISE_SEED))
end;

function get_sample(x, y)
local a = 1
z = get_sample_grayscale(x, y, Z_COORDINATE)

v = get_worley_noise(x,y,z)

return v,v,v,a
end;

function get_worley_noise(x,y,z)
local sx, sy, sz = x / scale , y / scale, z / scale
local cell_x, cell_y, cell_z = math.floor(sx), math.floor(sy), math.floor(sz)

local offset_x, offset_y, offset_z
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
min_dist = math.min(dist, min_dist)
end
end
end
min_dist = 1.0 - min_dist
return min_dist
end;[/CODE]

David Roberson, Thu, 07 Jan 2021 17:29:23 -0500
Yay! Persistence pays off!

Once I had my Worley noise isolated, the previous approach to Detail and Distortion worked again. I now have my Spherical Cell Noise module caught up to my Spherical Perlin Noise. I'm going to tinker with it a bit more, before posting the ffxml, but here's the final script and a preview of the output:

[CODE]function prepare()
oct_max = get_intslider_input(OCTAVES)
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2) * 5
set_noise_seed(get_intslider_input(NOISE_SEED))
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
if (get_checkbox_input(HDR)) then
hdr = true
else
hdr = false
end
end;

function get_sample(x, y)
local r, g, b, a = get_sample_map(x, y, BACKGROUND)
local r2, g2, b2, a2 = get_sample_map(x, y, FOREGROUND)
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
local amp = 1
local s = scale
local detail = 3.75 - get_sample_grayscale(x, y, DETAIL) * 2 + 0.01
local distortion = get_sample_grayscale(x, y, DISTORTION) * 2
local x = x * aspect * math.pi
local y = y * math.pi
local z = get_sample_grayscale(x, y, Z_COORDINATE)
local nx = math.cos(x) * math.sin(y) + vosx
local ny = math.sin(x) * math.sin(y) + vosy
local nz = math.cos(y) * z + vosz
for oct = 1, oct_max do
local d1 = get_worley_noise(nx+1,ny,nz,s) * distortion
local d2 = get_worley_noise(nx+2,ny,nz,s) * distortion
local d3 = get_worley_noise(nx+3,ny,nz,s) * distortion
if oct == 1 then v = get_worley_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_worley_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
s = s / 2
amp = amp / detail
end
v = get_sample_curve(x,y,v,PROFILE)
local opacity = v
r, g, b, a = blend_normal(r, g, b, a, r2, g2, b2, a2, opacity, hdr)
return r, g, b, a
end;

function get_worley_noise(x,y,z,s)
local sx, sy, sz = x / s , y / s, z / s
local cell_x, cell_y, cell_z = math.floor(sx), math.floor(sy), math.floor(sz)

local offset_x, offset_y, offset_z
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
min_dist = math.min(dist, min_dist)
end
end
end
min_dist = 1.0 - min_dist
return min_dist
end;[/CODE]

David Roberson, Thu, 07 Jan 2021 21:39:07 -0500
Well, I did a little tinkering with my spherically mapped noises and submitted the final results to the Library. You should see them popping up in a few days, at most. The only thing I didn't really do, do to my lack of experience, was optimize the distance algorithms for the Worley noise. To do that, I have to use a sorted table and do a little more searching on the subject of Worley noises. In both cases, I hope to learn what I need to, since I still want to make other types of spherically mapped noise. I figured the work I've already done might help someone else if I made them available in the Library.

David Roberson, Fri, 08 Jan 2021 14:45:55 -0500
I'm kind of at a crossroads, with this project. I've gone about as far as I can working with the API Noise and valuable help fr om emme. Now I'm confronted with the challenges I discovered in the process of researching noise generation online. So, before starting anything today, I'm taking a moment to organize some of my thoughts. I'll begin with the loose threads I've already mentioned.

Quote
I still need to figure out how to address the nth point as a variable, to get other permutations, i.e. 2nd closest, 3rd closest, etc. point. I also need to figure out how to apply the other distance formulas for Manhattan, Chebyshev, etc. That's where the other Worley type noises we're familiar come from, with formula variations. So, still work to do!

And:

Quote
The only thing I didn't really do, do to my lack of experience, was optimize the distance algorithms for the Worley noise. To do that, I have to use a sorted table and do a little more searching on the subject of Worley noises.

The problem I'm having has to do with a feature of Worley noise I've seen in every example, except for the API Worley noise I actually used. In most implementations of Worley noise, there is a set of steps devoted to creating, distributing and querying the feature points, which are distance mapped in Euclidean, Manhattan, Chebyshev, etc. method. The API Worley Noise does not seem to openly address that step. I can't see where it determines which point is closest to a given point. I'd have to know that to impement a QuadTree -- the optimization I mentioned last. I'm pretty sure a QuadTree could be implemented in Lua; the structure is similar to Tech Noise Scrippet shared in the forums by ThreeDee (I can't find the thread at the moment, but I'll attach a sample image.Edit: You can find it here) There are other variations of Cell noise created by mapping to the nth closest point (1st, 2nd, 3rd, etc.). Those are also dependent on identifying and sorting seed points, by relative distance.

It's unfortunate that I'm such a novice at graphics scripting; I'm asking for help a lot, which has to bother people at times. I do make progress on my own, provided I have something to lean on, wh ere my own expertise is nil. I do look for answers outside the forum, but there are some very smart people here who do help out on occasion, So, I'll keep asking. But in a lot of ways, I'm flooding the forum (on my own thread, so why not?) mostly to keep track of what I'm doing, and how I'm doing it. If it helps others, fantastic. If it's annoying, well, I'm sorry for that. It gets me through, day to day, though, so it's worth it to me.

If you're still reading, and feel helpful (and of course have the knowledge to share and time to share it) I'd like to see other noise examples roughly on par with the API Worley Noise. I do wish FF had provided scripted examples for each of the Worley-based noises in FF. Collecting and preserving those here is one of the objectives of this thread. I think that's everything on my mind this morning. Today is going to be spent surfing for noise algorithms I can, hopefully, adapt for this project.

TTFN

David Roberson, Sat, 09 Jan 2021 14:41:27 -0500
So I finally stumbled across this thread -- Home > Forums > Beta 10.0 > Math: F1, F2, F3 + noise -- which clarified the whole F1, F2, F3 and Euclidian Distance, Manhattan Distance, or Chebyshev Distance terminology for the internal Worley noises. So now all I need is a script example for implementing each of these features in my spherical noise generator.

Quote
No. F1 is the closest feature point, F2 is the second closest point, F3 is the third closest point etc. (closest means "closest to the current sample coordinates). For every sample, the Worley noise calculates all feature points near the sample point, then sorts them by the distance to the sample point -- where the distance is not necessarily Euclidean. Various Worley-based components use different distance functions. IIRC, Blocks uses Chebyshev, Pyramids uses Manhattan, Stones uses Superquadratic, Techno uses Manhattan or Chebyshev, Cells and Chaffs are Euclidean or Superquadratic.

Quote

No. F1 is the closest feature point, F2 is the second closest point, F3 is the third closest point etc. (closest means "closest to the current sample coordinates). For every sample, the Worley noise calculates all feature points near the sample point, then sorts them by the distance to the sample point -- where the distance is not necessarily Euclidean.

Various Worley-based components use different distance functions. IIRC, Blocks uses Chebyshev, Pyramids uses Manhattan, Stones uses Superquadratic, Techno uses Manhattan or Chebyshev, Cells and Chaffs are Euclidean or Superquadratic.

I could not post a response in the Beta 10.0 thread, and it's already 11 years old, according to the last post, so it's a bit of a stretch, but I'm hoping to catch Vladimir Golovin's attention with this request for additional noise APIs to help with my project. I don't know if it really counts as a Feature Request, so I've held off on starting that kind of thread. I'll keep studying and trying to figure this out on my own, but I'm thinking I'll have to start over from scratch. The implementation of Worley noise I find elsewhere is done very differently, exposing the points to nth order sorting. I'm still looking for examples of other distance functions. I find references to them, but no examples of the formulas themselves in use.

David Roberson, Sat, 09 Jan 2021 18:51:14 -0500
Another victory for persistence! I had been looking for examples of Worley using different distance calculations when I should have just googled the four types I've come across: Euclidean, Manhattan, Chebyshev and Minkowski. That little shift in focus got me the results I was hoping for, and each of the formulas (with a partial exception for Minkowski) boiled down to one line of code.

I tested each one out and got decent results, though I'm clearly still missing whatever produces chaffs or stones. I did not find anything yet on superquadratic distance calculations. I did run into an odd problem when I tried to make the different distance methods controllable by an intslider. The "if" conditions generated a script error, saying "attempt to compare number with nil". I did a little testing assigning the intslider to set different rgba values and it worked outside the "for" loop, but not when it was inside it where the distance mapping needs to occur. Here's a simplified version of the script that's giving me trouble. Maybe someone else can figure out, or knows, what the problem is. Of course, I can just make a different map script for each type of distance mapping. It just seems like I should be able to switch modes in the same script.

[CODE]function prepare()
-- v.002
MIN_SCALE = 0.01
scale = math.max(MIN_SCALE, get_slider_input(SCALE) / 2) * 5
set_noise_seed(get_intslider_input(NOISE_SEED))
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
dtype = get_intslider_input(DISTANCE_TYPE)
p = get_intslider_input(P)
end;

function get_sample(x, y)
local x = x * aspect * math.pi
local y = y * math.pi
local z = get_sample_grayscale(x, y, Z_COORDINATE)
local nx = math.cos(x) * math.sin(y)
local ny = math.sin(x) * math.sin(y)
local nz = math.cos(y) * z
local sx, sy, sz = nx / scale , ny / scale, nz / scale
local cell_x, cell_y, cell_z = math.floor(sx), math.floor(sy), math.floor(sz)

local offset_x, offset_y, offset_z
local min_dist = 100
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
if dtype == 1 then
r,g,b,a = 1,0,0,1
elseif dtype == 2 then
r,g,b,a = 0,1,0,1
elseif dtype == 3 then
r,g,b,a = 0,0,1,1
else
r,g,b,a = 1,1,1,1
end
local dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
min_dist = math.min(dist, min_dist)
end
end
end

-- local a = 1
min_dist = 1.0 - min_dist
-- return min_dist, min_dist, min_dist, a
return r,g,b,a
end;[/CODE]

David Roberson, Mon, 11 Jan 2021 03:01:55 -0500
I spent the afternoon debugging my script and eventually tracked down the source of the error I was getting. By this point, I'd moved my distance calculations to their own function, so it may not technically be necessary. But, it works, so I'm leaving it in there as a sub-function of my Worley noise. In the process of debugging, I broke down what each part of the script was doing with comments. I'm leaving those in for the moment too, since I was left with a couple questions I still need answered, or rather parts that I hope someone else can explain.

When I got frustrated, I took a break and got the Contrast snippet I posted earlier working, so I can add that in next. I'll be reexamining the API Perlin Noise method of doing Roughness next, too.

For now, though, I'll post the new Spherical Worley Noise script, which gives the option of using Euclidean, Manhattan, Chebyshev or Minkowski distance mapping. My work file is getting a bit cluttered, and I'll eventually upd ate my submissions to the Library with the final versions I come up with. If someone really wants to see an ffxml for this version (and save themselves the trouble of configuring inputs for the script I'm posting) then I'll drop a copy of the Map Script into a new file and post it.

[CODE]function prepare()
-- v.006.5
-- added distance mapping - Euclidean, Manhattan, Chebyshev, Minkowski
-- prepare global noise constants
oct_max = get_intslider_input(OCTAVES)
set_noise_seed(get_intslider_input(NOISE_SEED))
-- adjust for spherical mapping - constant
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
dtype = get_intslider_input(DISTANCE_TYPE)
p = get_intslider_input(P)
--- set hdr state
if (get_checkbox_input(HDR)) then
hdr = true
else
hdr = false
end
end;

function get_sample(x, y)
-- get map inputs
local r, g, b, a = get_sample_map(x, y, BACKGROUND)
local r2, g2, b2, a2 = get_sample_map(x, y, FOREGROUND)
-- get offset map inputs or values
local vosx = get_sample_grayscale(x, y, OFFSET_X)
local vosy = get_sample_grayscale(x, y, OFFSET_Y)
local vosz = get_sample_grayscale(x, y, OFFSET_Z)
-- initialize noise amplitude
local amp = 1
-- get scale map or value and prevent s = 0
local s = get_sample_grayscale(x, y, SCALE)/2 * 5
if s == 0 then
s = 0.001
end
-- get detail and distortion map inputs or values
local detail = 3.75 - get_sample_grayscale(x, y, DETAIL) * 2 + 0.01
local distortion = get_sample_grayscale(x, y, DISTORTION) * 2
-- remap to sphere, get value for z
-- map input not viable, but value input necessary
local x = x * aspect * math.pi
local y = y * math.pi
local z = get_sample_grayscale(x, y, Z_COORDINATE)
local nx = math.cos(x) * math.sin(y) + vosx
local ny = math.sin(x) * math.sin(y) + vosy
local nz = math.cos(y) * z + vosz

-- get and distort each octave of spheremapped noise
for oct = 1, oct_max do
local d1 = get_worley_noise(nx+1,ny,nz,s) * distortion
local d2 = get_worley_noise(nx+2,ny,nz,s) * distortion
local d3 = get_worley_noise(nx+3,ny,nz,s) * distortion
-- modify 1st octave fully
-- then modify each octave's frequency and amplitude proportionately
if oct == 1 then v = get_worley_noise(nx+d1,ny+d2,nz+d3,s) else
v = (v + get_worley_noise(nx+d1/oct,ny+d2/oct,nz+d3/oct,s) * amp ) / (1 + amp)
end
nz = nz * 2
-- decrease scale for next octave
s = s / 2
-- decrease amplitude for next octave
amp = amp / detail
end
--- get profile curve - internal tonemapping
v = get_sample_curve(x,y,v,PROFILE)
-- set opacity to noise values
local opacity = v
-- blend foreground with background
r, g, b, a = blend_normal(r, g, b, a, r2, g2, b2, a2, opacity, hdr)
return r, g, b, a
end;

function get_worley_noise(x,y,z,s)
-- adjust x,y,z for scale
local sx, sy, sz = x / s , y / s, z / s
-- partition x,y,z into "integer" cells
local cell_x, cell_y, cell_z = math.floor(sx), math.floor(sy), math.floor(sz)
-- create offset variables for x,y,z
local offset_x, offset_y, offset_z
-- se t benchmark minimum distance
local min_dist = 10000
-- nested loop through x,y,z coordinate space via incremental offsets each
for offset_x=-1,1 do
for offset_y=-1,1 do
for offset_z=-1,1 do
-- what is really happening here?
local dx = cell_x + offset_x + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dy = cell_y + offset_y + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
local dz = cell_z + offset_z + get_noise(cell_x + offset_x, cell_y + offset_y, cell_z + offset_z)
-- option: create array of distances to seed points here?
-- option: get distance of random point from current point?
-- option: assign distances to array of distances for nth point distances?
local dist = distcalc(sx,sy,sz,dx,dy,dz)
-- compare distance to benchmark minimum distance for lesser value
min_dist = math.min(dist, min_dist)
end
end
end
-- what does this adjustment accomplish?
min_dist = 1.0 - min_dist
-- return value of current point
return min_dist
end;

function distcalc(sx,sy,sz,dx,dy,dz)
local dist = 0 -- returns nil value without this variable declaration
if dtype == 1 then
-- Euclidean
dist = math.sqrt((sx - dx)^2 + (sy - dy)^2 + (sz - dz)^2)
elseif dtype == 2 then
-- Chebyshev
dist = math.max(math.abs(sx - dx), math.abs(sy - dy), math.abs(sz - dz))
elseif dtype == 3 then
-- Manhattan
dist = (math.abs(sx - dx) + math.abs(sy - dy) + math.abs(sz - dz)) / 1.5
else
-- Minkowski
local pe = 1/p
dist = (math.abs(sx - dx)^p + math.abs(sy - dy)^p + math.abs(sz - dz)^p)^pe
end
return dist
end;[/CODE]

David Roberson, Mon, 11 Jan 2021 15:33:46 -0500
Okay, I hit a stopping point early today. I was seeing what I could accomplish working with the API Multi-Octave Perlin and discovered that the way it handles Roughness is not compatible with spherical mapping. Remapping was not that hard, but there is a stretching artifact along the "equator" that, at best, could only be minimized -- not eliminated. There also seems to be an issue with scale settings for completely zoomed in. What worked in Cartesian space, without modifications to the input scale, does not work even with modifications to scale in the sphere map.

I was able to map Roughness and Contrast (which was easy enough to add), so there's at least a v.001 that works. The ffxml has a v.002 started, current to where I left off. I'll post the code and file for anyone who wants to take a crack at this. I'm sure there are many people on the forums who would fare much better than I.

[CODE]function prepare()
-- v.002
-- constants
AMPLITUDE_CORRECTION_FACTOR = 1.731628995
ROUGHNESS_THRESHOLD = 0.00001
REMAINDER_THRESHOLD = 0.00001
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2
set_perlin_noise_seamless(SEAMLESS)
set_perlin_noise_seamless_region(SEAMLESS_REGION_WIDTH, SEAMLESS_REGION_HEIGHT)

-- input values
details = get_slider_input(DETAILS) * 10 + 1
OCTAVES_COUNT = math.floor(details)
NOISE_SIZE = get_slider_input(SCALE)
set_perlin_noise_seed(get_intslider_input(NOISE_VARIATION))
end;

function get_sample(x, y)
local r, g, b, a = get_sample_map(x, y, BACKGROUND)
local noise_r, noise_g, noise_b, noise_a = get_sample_map(x, y, NOISE)

local remainder = details - OCTAVES_COUNT
if (remainder > REMAINDER_THRESHOLD) then
OCTAVES_COUNT = OCTAVES_COUNT + 1
end

local roughness = ROUGHNESS_THRESHOLD +
get_sample_grayscale(x, y, ROUGHNESS) * (1.0 - ROUGHNESS_THRESHOLD)
local contrast = (get_sample_grayscale(x, y, CONTRAST) * 2) - 1
local factor = (259 * (contrast + 1)) / (1 * (259 - contrast))

OCTAVES = {}
local cell_size = (0.01 + NOISE_SIZE * 0.99) * 150
local scale = roughness
local octave_index
for octave_index = 1, OCTAVES_COUNT do
if (scale < ROUGHNESS_THRESHOLD) then
OCTAVES_COUNT = octave_index - 1
break
end
OCTAVES[octave_index] = {cell_size, scale}
cell_size = cell_size * 0.5
scale = scale * roughness
end

if (remainder >= 0.001) then
OCTAVES[OCTAVES_COUNT][2] = OCTAVES[OCTAVES_COUNT][2] * remainder
end

NORM_FACTOR = 0
for octave_index = 1, OCTAVES_COUNT do
NORM_FACTOR = NORM_FACTOR + OCTAVES[octave_index][2] ^ 2
end
NORM_FACTOR = 1 / math.sqrt(NORM_FACTOR)

-- ins ert spheremapping calculations
local x = x * aspect * math.pi
local y = y * math.pi
local nx = math.cos(x) * math.sin(y) -- * scale + vosx
local ny = math.sin(x) * math.sin(y) -- * scale + vosy
-- local nz = math.cos(y) * math.pi -- * scale + vosz
local alpha = 0

for octave_index = 1, OCTAVES_COUNT do
-- this minimizes stretching the most, still has artifacts
local nz = octave_index * math.cos(y) * math.pi
local size = OCTAVES[octave_index][1]
local opacity = OCTAVES[octave_index][2]
-- local d1 = get_perlin_noise(nx+1,ny,nz,size) -- * distortion
-- local d2 = get_perlin_noise(nx+2,ny,nz,size) -- * distortion
-- local d3 = get_perlin_noise(nx+3,ny,nz,size) -- * distortion
-- local noise_z = octave_index
-- -- ins ert spheremapped x,y,z coordinates
-- -- produces stretching along equator
alpha = alpha + opacity * (2 * get_perlin_noise(nx,ny,nz,size) - 1)
-- alpha = alpha + opacity * (2 * get_perlin_noise(nx+d1,ny+d2,nz+d3,size) - 1)
end

alpha = (alpha * NORM_FACTOR + AMPLITUDE_CORRECTION_FACTOR) *
(0.5 / AMPLITUDE_CORRECTION_FACTOR)
local alpha = truncate(factor * (alpha - 0.5) + 0.5)

return blend_normal(r, g, b, a, noise_r, noise_g, noise_b, noise_a, alpha)
-- return size,size,size,1
end;

function truncate(value)
if value <= 0 then value = 0 end
if value >= 1 then val ue = 1 end
return val ue
end;[/CODE]

David Roberson, Mon, 11 Jan 2021 22:51:03 -0500
Having run into a couple problems I could not solve, at present, I went ahead and spent part of the day updating my spherical noise scripts and posting the updates. Since it could take a while for those updates to go through, I'm wrapping up by posting copies here for anyone who doesn't want to wait.

David Roberson, Mon, 11 Jan 2021 22:57:57 -0500
Here is the other. It's slower, by a minute, but now offers four different variations (Euclidean, Manhattan, Chebyshev and Minkowski), as noted a couple posts ago. Manhattan gives a result most similar to Pyramids. Chebyshev falls somewhere between blocks and Techno -- and Minkowski offers a range between Euclidean (Cell noise) and Chebyhsev. Once you apply any of the possible distortions and levels of detail, they tend to become even more similar. Oh well.

David Roberson, Thu, 14 Jan 2021 03:54:24 -0500
Having reached the limit of what I could do with my current level of scripting ability, I've sort of drifted off into the land of Processing.org having found a massive resource in the videos of Daniel Shiffman. Having once studied things like Java and Javascript Processing should be much easier for me to pick up and use than Lua. My experience with C/C++ is more out of date, and it's difficult to find tutorials for Lua graphics scripting. I'm hoping to be able to take some of what I learn in Processing and apply them in Lua, at which point I'll come back to projects like the one I started here.

The Worley noise I created only has F1 distance mapping. I was not able to grasp how the script identified the closest feature point in its distance calculations. I will keep tabs on this thread, in case someone offers assistance with F2, F3 and F4 distance mapping. I don't know if they can apply equally to the four types of Worley noise I was able to get through different distance algorithms. That's something I'll need clarified too. I hope I'll be able to figure it all out eventually, but maybe I'll get help from the forum along the way. If either of those things happen, I'll take update my Spherical Worley Noise. If you've read through the thread this far, thank you and hopefully you found some of it useful.

TTFN

David Roberson, Wed, 26 Oct 2022 12:34:52 -0400
So, it's been a year and change since I thought about this, but I came back to it today and find the problem still stumps me:

Quote
David Roberson wrote: I was seeing what I could accomplish working with the API Multi-Octave Perlin and discovered that the way it handles Roughness is not compatible with spherical mapping. Remapping was not that hard, but there is a stretching artifact along the "equator"...

I compared this to a few other noise scripts I've done or used as examples, to try and understand why this seems to happen only with Perlin noise called using get_perlin_noise(). Or rather, the version in Egret's API Perlin Noise script. The octave blending emme provided an example did not have this problem. I would be inclined to keep using that, but the Roughness just isn't as nice as Egret's. I do hope an FF team member can chime in here, since Egret's implementation was based on the FF version.

I'll post a pic of what I'm talking about, since I'm just throwing this out there again to see if someone can shed some light on why this is happening or how to fix it.

David Roberson, Thu, 27 Oct 2022 05:40:25 -0400
Last night I did a bit of online research and found a different implementation of improved Perlin noise adapted for lua. So, today I worked on an update to my Perlin Spherical Noise map script. I have been able to generate a sphere and a spherical map using it. I discovered that the noise did not tile correctly as a flat plane, however, so I'm posting the code to see if anyone can suggest a way to make it properly seamless and not just repeating or completely hashed. The options to see the default presentation and my attempt to apply SEAMLESS_WIDTH and SEAMLESS_HEIGHT are commented off.

[CODE]-- 3d perlin sphere or map -- improved perlin noise
function prepare()
-- constants
-- AMPLITUDE_CORRECTION_FACTOR = 1.731628995
-- only used in depricated statement
ROUGHNESS_THRESHOLD = 0.00001
REMAINDER_THRESHOLD = 0.00001
aspect = OUTPUT_HEIGHT / OUTPUT_WIDTH * 2

-- input values
details = get_slider_input(DETAILS) * 10 + 0.0001
grain = (get_slider_input(GRAIN) * 5) + 0.0001
OCTAVES_COUNT = math.floor(details)
NOISE_SIZE = math.log( get_slider_input(SCALE) + 0.0000000001)
-- NOISE_SIZE = (1 - get_slider_input(SCALE)) * (5 * grain) + 0.0001

-- sphere block
radius = get_slider_input(RADIUS)

angle = math.rad(get_angle_input(ROTATION))
cosa1 = math.cos(angle)
sina1 = math.sin(angle)

tilt = math.rad(get_angle_input(TILT))
cosa2 = math.cos(tilt)
sina2 = math.sin(tilt)
-- end

-- noise block
--[[
https://gist.githubusercontent.com/kym...perlin.lua
Implemented as described here:
http://flafla2.github.io/2014/08/09/perlinnoise.html
]]--

perlin = {}
perlin.p = {}

--[[
-- hash lookup table as defined by Ken Perlin
-- this is a randomly arranged array of all numbers fr om 0 - 255 inclusive
local permutation = {151, 160, 137, 91, 90, 15,
131, 13, 201, 95, 96, 53, 194, 233, 7, 225, 140, 36, 103, 30, 69, 142, 8, 99, 37, 240, 21, 10, 23,
190, 6, 148, 247, 120, 234, 75, 0, 26, 197, 62, 94, 252, 219, 203, 117, 35, 11, 32, 57, 177, 33,
88, 237, 149, 56, 87, 174, 20, 125, 136, 171, 168, 68, 175, 74, 165, 71, 134, 139, 48, 27, 166,
77, 146, 158, 231, 83, 111, 229, 122, 60, 211, 133, 230, 220, 105, 92, 41, 55, 46, 245, 40, 244,
102, 143, 54, 65, 25, 63, 161, 1, 216, 80, 73, 209, 76, 132, 187, 208, 89, 18, 169, 200, 196,
135, 130, 116, 188, 159, 86, 164, 100, 109, 198, 173, 186, 3, 64, 52, 217, 226, 250, 124, 123,
5, 202, 38, 147, 118, 126, 255, 82, 85, 212, 207, 206, 59, 227, 47, 16, 58, 17, 182, 189, 28, 42,
223, 183, 170, 213, 119, 248, 152, 2, 44, 154, 163, 70, 221, 153, 101, 155, 167, 43, 172, 9,
129, 22, 39, 253, 19, 98, 108, 110, 79, 113, 224, 232, 178, 185, 112, 104, 218, 246, 97, 228,
251, 34, 242, 193, 238, 210, 144, 12, 191, 179, 162, 241, 81, 51, 145, 235, 249, 14, 239, 107,
49, 192, 214, 31, 181, 199, 106, 157, 184, 84, 204, 176, 115, 121, 50, 45, 127, 4, 150, 254,
138, 236, 205, 93, 222, 114, 67, 29, 24, 72, 243, 141, 128, 195, 78, 66, 215, 61, 156, 180
}

-- p is used to hash unit cube coordinates to [0, 255]
for i = 0, 255 do
convert to 0 based index table
perlin.p[i] = permutation[i + 1]
repeat the array to avoid buffer overflow in hash function
perlin.p[i + 256] = permutation[i + 1]
end
]]--

math.randomseed(get_intslider_input(SEED))
for i = 0, 255 do
perlin.p[i] = math.random(255)
perlin.p[256 + i] = perlin.p[i]
end

-- return range: [ - 1, 1]
function perlin:noise(x, y, z)
y = y or 0
z = z or 0

--[[
-- seamless tiling method needs revision - not part of original adaptation, attempt here produced overwhelming artifacts
-- check for seamlessness
if SEAMLESS then
x = x % SEAMLESS_REGION_WIDTH
y = y % SEAMLESS_REGION_HEIGHT
z = z % (SEAMLESS_REGION_WIDTH + SEAMLESS_REGION_HEIGHT) * 0.5
end
]]--

-- calculate the "unit cube" that the point asked will be located in
local xi = bit32.band(math.floor(x), 255)
local yi = bit32.band(math.floor(y), 255)
local zi = bit32.band(math.floor(z), 255)

-- next we calculate the location (from 0 to 1) in that cube
x = x - math.floor(x)
y = y - math.floor(y)
z = z - math.floor(z)

-- we also fade the location to smooth the result
local u = self.fade(x)
local v = self.fade(y)
local w = self.fade(z)

-- hash all 8 unit cube coordinates surrounding input coordinate
local p = self.p
local A, AA, AB, AAA, ABA, AAB, ABB, B, BA, BB, BAA, BBA, BAB, BBB
A = p[xi ] + yi
AA = p[A ] + zi
AB = p[A + 1 ] + zi
AAA = p[ AA ]
ABA = p[ AB ]
AAB = p[ AA + 1 ]
ABB = p[ AB + 1 ]

B = p[xi + 1] + yi
BA = p[B ] + zi
BB = p[B + 1 ] + zi
BAA = p[ BA ]
BBA = p[ BB ]
BAB = p[ BA + 1 ]
BBB = p[ BB + 1 ]

-- take the weighted average between all 8 unit cube coordinates
return self.lerp(w,
self.lerp(v,
self.lerp(u,
self:grad(AAA, x, y, z),
self:grad(BAA, x - 1, y, z)
),
self.lerp(u,
self:grad(ABA, x, y - 1, z),
self:grad(BBA, x - 1, y - 1, z)
)
),
self.lerp(v,
self.lerp(u,
self:grad(AAB, x, y, z - 1), self:grad(BAB, x - 1, y, z - 1)
),
self.lerp(u,
self:grad(ABB, x, y - 1, z - 1), self:grad(BBB, x - 1, y - 1, z - 1)
)
)
)
end

--[[
gradient function finds dot product between pseudorandom gradient vector
and the vector from input coordinate to a unit cube vertex.
]]--
perlin.dot_product = {
[0x0] = function(x, y, z) return x + y end,
[0x1] = function(x, y, z) return -x + y end,
[0x2] = function(x, y, z) return x - y end,
[0x3] = function(x, y, z) return -x - y end,
[0x4] = function(x, y, z) return x + z end,
[0x5] = function(x, y, z) return -x + z end,
[0x6] = function(x, y, z) return x - z end,
[0x7] = function(x, y, z) return -x - z end,
[0x8] = function(x, y, z) return y + z end,
[0x9] = function(x, y, z) return -y + z end,
[0xA] = function(x, y, z) return y - z end,
[0xB] = function(x, y, z) return -y - z end,
[0xC] = function(x, y, z) return y + x end,
[0xD] = function(x, y, z) return -y + z end,
[0xE] = function(x, y, z) return y - x end,
[0xF] = function(x, y, z) return -y - z end
}
function perlin:grad(hash, x, y, z)
return self.dot_product[bit32.band(hash, 0xF)](x, y, z)
end

-- fade function is used to smooth final output
function perlin.fade(t)
return t * t * t * (t * (t * 6 - 15) + 10)
end

function perlin.lerp(t, a, b)
return a + t * (b - a)
end

-- perlin octaves initialization
remainder = details - OCTAVES_COUNT
if (remainder > REMAINDER_THRESHOLD) then
OCTAVES_COUNT = OCTAVES_COUNT + 1
end

--[[
local roughness = ROUGHNESS_THRESHOLD +
get_slider_input(ROUGHNESS) * (1.0 - ROUGHNESS_THRESHOLD)

OCTAVES = {}
local cell_size = (0.01 + NOISE_SIZE * 0.99) * grain -- 5
local scale = roughness
local octave_index
for octave_index = 1, OCTAVES_COUNT do
if (scale < ROUGHNESS_THRESHOLD) then
OCTAVES_COUNT = octave_index - 1
break
end
OCTAVES[octave_index] = {cell_size, scale}
cell_size = cell_size * 2.0
scale = scale * roughness
end

if (remainder >= 0.001) then
OCTAVES[OCTAVES_COUNT][2] = OCTAVES[OCTAVES_COUNT][2] * remainder
end

NORM_FACTOR = 0
for octave_index = 1, OCTAVES_COUNT do
NORM_FACTOR = NORM_FACTOR + OCTAVES[octave_index][2] ^ 2
end
NORM_FACTOR = 1 / math.sqrt(NORM_FACTOR)
]]--
-- end
if get_checkbox_input(MODE) then
mode = 1
else
mode = 2
end
--[[
-- seamless tiling method needs revision - not part of original adaptation; change to "else mode = 0" to see default tiling
set_perlin_noise_seamless(SEAMLESS)
set_perlin_noise_seamless_region(SEAMLESS_REGION_WIDTH, SEAMLESS_REGION_HEIGHT)
]]--
end;

function get_sample(x, y)
local roughness = ROUGHNESS_THRESHOLD +
get_sample_grayscale(x, y, ROUGHNESS) * (1.0 - ROUGHNESS_THRESHOLD)
local contrast = (get_sample_grayscale(x, y, CONTRAST) * 2) - 1
local factor = (259 * (contrast + 1)) / (1 * (259 - contrast))
local n = 0
--[[
full implementation of mappped roughness and contrast requires coordinate remapping to the sphere.
this is already in use elsewhere, so it will be implemented after spherical map generation is complete.
block may move to conditional block per usage.
]]--

-- image generation
-- sphere block
if mode == 1 then
px = (x * 2.0) - 1.0
py = (y * 2.0) - 1.0
px = px / radius
py = py / radius
local len = math.sqrt((px * px) + (py * py))
if len > 1.0 then return 0, 0, 0, 0 end

z = - math.sqrt(1.0 - ((px * px) + (py * py)))

local tz = (cosa2 * z) - (sina2 * py)
local ty = (sina2 * z) + (cosa2 * py)
z = tz
py = ty

local tx = (cosa1 * px) - (sina1 * z)
local tz = (sina1 * px) + (cosa1 * z)
px = tx
z = tz
end
-- end

-- spherical map block
if mode == 2 then
local x = x * aspect * math.pi
local y = y * math.pi
nx = math.cos(x) * math.sin(y)
ny = math.sin(x) * math.sin(y)
nz = math.cos(y)
end
-- end

-- noise generation
OCTAVES = {}
local cell_size = (0.01 + NOISE_SIZE * 0.99) * grain -- 5
local scale = roughness
local octave_index
for octave_index = 1, OCTAVES_COUNT do
if (scale < ROUGHNESS_THRESHOLD) then
OCTAVES_COUNT = octave_index - 1
break
end
OCTAVES[octave_index] = {cell_size, scale}
cell_size = cell_size * 2.0
scale = scale * roughness
end

if (remainder >= 0.001) then
OCTAVES[OCTAVES_COUNT][2] = OCTAVES[OCTAVES_COUNT][2] * remainder
end

NORM_FACTOR = 0
for octave_index = 1, OCTAVES_COUNT do
NORM_FACTOR = NORM_FACTOR + OCTAVES[octave_index][2] ^ 2
end
NORM_FACTOR = 1 / math.sqrt(NORM_FACTOR)
local octave_index
for octave_index = 1, OCTAVES_COUNT do
local size = OCTAVES[octave_index][1]
local opacity = OCTAVES[octave_index][2]
if mode == 1 then
n = n + opacity * perlin:noise(px * size, py * size, z * size) -- (2 * -- - 1)
elseif mode == 2 then
n = n + opacity * perlin:noise(nx * size, ny * size, nz * size) -- (2 * -- - 1)
else
local z = octave_index
n = n + opacity * perlin:noise(x * size, y * size, z * size) -- (2 * -- - 1)
end
end
n = (n + 1.0) * 0.5
--[[
n = (n * NORM_FACTOR + AMPLITUDE_CORRECTION_FACTOR) *
(0.5 / AMPLITUDE_CORRECTION_FACTOR)
-- causes blowout - getting reasonable results without it
]]--
n = truncate(factor * (n - 0.5) + 0.5)
n = get_sample_curve(x, y, n, PROFILE)
return n, n, n, 1
end;

function truncate(value)
if value <= 0 then value = 0 end
if value >= 1 then value = 1 end
return value
end;[/CODE]

My attempt to impose seamlessness seems to conflict with the method used to implement octaves. It still produces noise, but in repeating blocks diminishing in octaves as well. That suggests two probable issues to resolve; first is seamless blending of the base noise, and second, getting properly scaled seamless tiling for each octave, to the lim it of octave_index. At the moment, I have no ideas on how to do that.

David Roberson, Thu, 27 Oct 2022 06:16:32 -0400
Looking at the spherical Perlin I produced, I had one idea regarding the mapping required for a seamless plane; basically, I need to get mapping coordinates for a torus, which curves in 3d space to create a perfect 2d planar mapping. I'll see if I can find the right function for this, but I'm making a note of it here in case someone else wants to try this idea out.

David Roberson, Sat, 29 Oct 2022 10:46:05 -0400
Since the standard Perlin Noise works for most of the things I'd need to be seamless-squared, I set that part of my scripting aside to focus on what could be done with the equirectangular sphere maps and the spherical projection I came up with so far. The goal of a good, fully procedural planet generator is still a bit of work away. I do have a nice preview of what can be done with these new map scripts. Using a downloaded Earth map, I made some very nice clouds and atmosphere using two map scripts, a few Perlin Noises (mostly to make stars and offset a Profile Gradient), a couple of curves and Scale components (to adjust the Earth map to a square workspace), and a few Math components.

Assigning number identifier to white parts of black/white image

Cato99 — Fri, 26 Aug 2022 23:45:20 -0400

Cato99, Fri, 26 Aug 2022 23:45:20 -0400
I would like to assign a number identifier to the white parts of a black and white image or pattern, and store the number in a script (not to be printed on the image/screen). See example images in the attached, the top row are the images I would have in Filter Forge, either through an 'image' or 'color control' component. The bottom row shows the numbers that would be assigned.

Going from left to right, top to bottom, the number assigned would be consecutive for each white area. Can we identify the bounds of each white area in one go in FF? Or do I need to step through, slowly scanning - eg. The first pixel/area that is white would be assigned the Number 1, then I guess comparison of the next pixel/area (left/right/top/bottom) would need to check if there was black, and if not, assign that Number 1 as well; otherwise if there is black, skip to the next white pixel/area and assign that as Number 2, and so on.

With the resulting numbers in the script, I would then create values that I can use to make each white area a different color/pattern fill/input depending on the number.

Can Lua scripting be performed in FF for this outcome? If so, does anyone have a starting example script that I could base my script on, as I am a beginner?

Creating a clamped range

Bobby_t — Fri, 12 Aug 2022 06:55:45 -0400

Bobby_t, Thu, 11 Aug 2022 12:55:42 -0400
Hi there,

I'm looking to create a script (couldn't find a component?) to be able to clamp a range of values.

In below diagram, I've tried to illusrate as best I can, I'm looking to input values on Y and have that map to a value range on X.

For example at Y value of 10 the range in X is locked to 0,5 (mid grey) at top of triangle.

At a range of Y 5, mid grey the x range would be between approx. 0.25 and 0.75

At 0 on Y, the X can be anywhere from white to black, 0 to 1

Bobby_t, Fri, 12 Aug 2022 06:55:45 -0400
I may of over complicated above issue, worked out a much easy way to do it. :?:

I was wanting to limit the amount a shape could move, the bigger the shape would get (y value) the less it could move, offset (x)

Scripting a Rotatable Gradient Sphere

David Roberson — Mon, 08 Aug 2022 00:15:23 -0400

David Roberson, Mon, 31 May 2021 17:27:09 -0400
I recently looked at and updated the Rotatable Sphere Snippet by ThreeDee. Unfortunately, I could think of no way to correct the distortions that are part of it, and started wondering how I'd make an undistorted version I could use in a filter designed to showcase a planet. The obvious thing to do is to try and create a Map Script that will produce a gradient sphere like the example (below) that could be used to map a surface using the Lookup component. Sadly, I have no idea how to do it.

If you think you can help I'd be very grateful, just a link to a good example would be appreciated. I am looking at the Raytracing Snippet by Egret as a starting point, so even help with mapping a gradient onto one of his spheres would be great.

Thanks for your attention.

David Roberson, Mon, 31 May 2021 20:20:44 -0400
I was able to get pretty far working with a Refraction based mapping to a rotatable sphere. Unfortunately, it's only fooling the eye; there's still unwanted distortion and not-quite full range of motion. A proper sphere mapping will take a bit of pseudo 3d scripting. Lua can do it, but most of the methods I've come across require external libraries. For what amounts to a sphere primitive, I don't think I would need to go that far.

Anyway, here's the ffxml for my rotatable sphere snippet:

David Roberson, Tue, 01 Jun 2021 17:01:44 -0400
I've been tinkering with the Raytracing Snippet by Egret, trying to map a gradient onto one of his spheres. I got as far as isolating a sphere in a bigger space with an associated uv surface, but it only seems to respond to the alpha channel. The RGB channels do not respond to the raytrace, so I get either a clear, refractive surface or a black one (reflections still work, too). I'll post what I've got here, in case someone can point out where I'm going wrong. l think this is on hold until then...

David Roberson, Mon, 20 Jun 2022 00:38:05 -0400
I succeeded in accomplishing half of the gradients needed to create a Rotatable Sphere Script -- a gradient from the north to south pole (is that the y-axis?). To complete my script I need some help with the math to produce the x-axis, basically an angle gradient from the far east to the far west. There's an example of this above. I have tried finding an example of cartesian to polar mapping for lua, but have had no luck. I'm hoping that is the solution I'm looking for.

[CODE]-- 3d sphere
-- produces rgb gradient mapped to a 3d sphere, but not correctly.
-- how would one map x:red and y:green gradients instead?
-- this is basically missing an angle gradient in the y-axis...
function prepare()
-- tilt & rotation precalc
-- it would be nice to know how this works!
toRad = 180/math.pi

radius = get_slider_input(RADIUS)

angle = get_angle_input(ROTATION)/toRad
cosa = math.cos(angle)
sina = math.sin(angle)

tilt = get_angle_input(TILT)/toRad
cosa2 = math.cos(tilt)
sina2 = math.sin(tilt)
end;

function get_sample(x, y)
local r, g, b, a = get_sample_map(x, y, SOURCE)
-- color gradient example
-- local r = x
-- local g = y
-- local b = (x + y) / 2
-- local a = 1
-- image generation
local px = (x*2.0) - 1.0
local py = (y*2.0) - 1.0
px = px/radius
py = py/radius
local len = math.sqrt((px*px)+(py*py))
if len > 1.0 then return 0,0,0,0 end

local z = -math.sqrt(1.0 - ((px*px)+(py*py)))

local tz = (cosa2 * z) - (sina2 * py)
local ty = (sina2 * z) + (cosa2 * py)
z = tz
py = ty

local tx = (cosa * px) - (sina * z)
local tz = (sina * px) + (cosa * z)
px = tx
z = tz

return px/2+.5,px/2+.5,px/2+.5,a -- r, g, b, a
end;[/CODE]

Here are a couple examples from other scripting languages...

[CODE] -- cartesian to polar (reference)
-- example 1
-- r = math.sqrt((cart.x * cart.x + cart.y * cart.y + cart.z * cart.z));
-- long = math.acos(cart.x / math.sqrt(cart.x * cart.x + cart.y * cart.y)) * (cart.y < 0 ? -1 : 1);
-- lat = math.acos(cart.z / radius) * (cart.z < 0 ? -1 : 1);
-- example 2
-- r = sqrt(x * x + y * y + z * z)
-- long = acos(x / sqrt(x * x + y * y)) * (y < 0 ? -1 : 1)
-- lat = acos(z / r)
[/CODE]

David Roberson, Mon, 20 Jun 2022 23:18:47 -0400
Since I've just been banging my head against a wall on this, here's an upd ate on my progress. This may clarify what kind of help I'm looking for, in case what I've already posted is unclear.

0

I am working on a Spherical Map Script that generates a linear gradient along the y-axis and an angular gradient around the y-axis in the green and red channels, respectively. I have been unable to find any documentation suited to this online, but have experimented using examples in Javascript and C#. The linear gradient has worked out fine, but the angular gradient (one describing a 360 degree arc around the y-axis) continues to elude me.

My working script is as follows.

[CODE]-- 3d sphere
-- produces rgb gradient mapped to a 3d sphere, but not correctly.
-- this is basically missing an angle gradient around the y-axis...
function prepare()
-- tilt & rotation precalc
toRad = 180/math.pi
-- toCir = 360/math.pi -- may or may not work for circumference...

radius = get_slider_input(RADIUS)

angle = get_angle_input(ROTATION)/toRad
cosa = math.cos(angle)
sina = math.sin(angle)

tilt = get_angle_input(TILT)/toRad
cosa2 = math.cos(tilt)
sina2 = math.sin(tilt)
end;

function get_sample(x, y)
local r, g, b, a = get_sample_map(x, y, SOURCE)
-- color gradient example
-- local r = x
-- local g = y
-- local b = (x + y) / 2
-- local a = 1
-- spherical mapping formulae (polar to cartesian, apparently)
-- local x = x * math.pi -- * aspect
-- local y = y * math.pi
-- conversion from r, lat, long to x, y, z
-- local nx = math.cos(x) * math.sin(y)
-- local ny = math.sin(x) * math.sin(y)
-- local nz = math.cos(y)
-- cartesian to polar (reference)
-- radius : distance from focus to surface
-- latitude : -90 to 90 degrees (math.pi/2), along y-axis (phi)
-- longitude : -180 to 180 degrees (math.pi) around y-axis (theta)
-- example 1
-- r = math.sqrt(((x * x) + (y * y) + (z * z)))
-- long = math.acos(x / math.sqrt((x * x) + (y * y))) * (y < 0 ? -1 : 1)
-- lat = math.acos(z / radius) * (z < 0 ? -1 : 1)
-- example 2
-- r = math.sqrt((x * x) + (y * y) + (z * z))
-- long = math.acos(x / math.sqrt((x * x) + (y * y))) * (y < 0 ? -1 : 1)
-- lat = math.acos(z / r)

-- image generation
-- shift origin to center and se t radius limits
local px = (x*2.0) - 1.0
local py = (y*2.0) - 1.0
px = px/radius
py = py/radius
local len = math.sqrt((px*px)+(py*py))
if len > 1.0 then return 0,0,0,0 end

local z = -math.sqrt(1.0 - ((px*px)+(py*py)))

-- cartesian to polar
-- r = math.sqrt((x * x) + (y * y) + (z * z))
-- lat = math.acos(z / r)
-- long = math.acos(x / math.sqrt((x * x) + (y * y))) * (y < 0) ? -1 : 1)
-- equation cannot accept boolean comparison
-- boolean syntax may not be valid in lua
-- test long = math.acos(x / math.sqrt((x * x) + (y * y)))

-- apply rotation and tilt
local ty = (sina2 * z) + (cosa2 * py) -- gradient along y-axis is correct
py = ty
local tz = (cosa2 * z) - (sina2 * py) -- not used before overridden
z = tz -- not used before overridden

local tz = (sina * px) + (cosa * z)
px = tx
local tx = (cosa * px) - (sina * z) -- gradient needs to go around y-axis
z = tz

-- return r, g, b, a
-- return px,py,z,a
return px/2+.5,py/2+.5,long,a
-- return px/2+.5,px/2+.5,px/2+.5,a
-- return long,long,long,a
end;[/CODE]

David Roberson, Wed, 22 Jun 2022 05:29:25 -0400
After several days of poking around I have only found one working example in which the x and y gradients can only be generated along their respective axes. I just can't puzzle out a method of generating a gradient around an axis using polar-to-cartesian and cartesian-to-polar coordinate conversions. Does that seem right? I may just be failing to do the cartesian-to-polar correctly, most likely due to the boolean operation inside the examples I found for other coding languages. I still have to say that the apparent logic of those equations makes it seem like longitude variable contains a circumferential gradient. You just can't pull it out using polar-to-cartesian equations. If I could, then a sampling of source images would be possible in a map script. Maybe that requires some form of computational uv mapping?

Any kind of feedback would be welcome here...

David Roberson, Wed, 22 Jun 2022 06:46:51 -0400
Well, I finally got a grip on how this map script works and the solution was so much simpler that what I'd been trying to do. Here's my solution:

[CODE]-- 3d vector sphere
-- produces rgb vector gradient mapped to a 3d sphere
function prepare()
-- tilt & rotation precalc
toRad = 180/math.pi

radius = get_slider_input(RADIUS)

angle = get_angle_input(ROTATION)/toRad
cosa = math.cos(angle)
sina = math.sin(angle)

tilt = get_angle_input(TILT)/toRad
cosa2 = math.cos(tilt)
sina2 = math.sin(tilt)
end;

function get_sample(x, y)
-- image generation

-- sphere generation and manipulation
-- origin to center
local px = (x*2.0) - 1.0
local py = (y*2.0) - 1.0
-- set sphere radius (max -- screen height)
px = px/radius
py = py/radius
local len = math.sqrt((px*px)+(py*py))
-- check radius and clip
if len > 1.0 then return 0,0,0,0 end

local z = -math.sqrt(1.0 - ((px*px)+(py*py)))

local tz = (cosa2 * z) - (sina2 * py)
local ty = (sina2 * z) + (cosa2 * py)
z = tz
py = ty

local tx = (cosa * px) - (sina * z)
local tz = (sina * px) + (cosa * z)
px = tx
z = tz
if z <= 0 then px = (0 - (1 - px)) end

return px/2+.5,py/2+.5,0,1
-- return px,py,0,1
end;[/CODE]

Edit: I may have spoken to soon.... On first glance the circumferential gradient looked right, but as soon as I tried to test it in a Lookup I discovered a problem. I'm inverting the values wrong, dealing with the -1 to 1 range. It's probably a simple fix but my brain is too tired to sort it out right now.

David Roberson, Wed, 22 Jun 2022 09:01:06 -0400
Well, the long and the short of it is that the process I've been working with is in the wrong coordinate system. The gradient sphere I have is based on the polar-to-cartesian coordinate system. That gives me x, y, z gradients in the three axes. What I want is gradients for theta and phi, or longitude and latitude. I'm actually getting values for theta and phi from my control sliders, which rotate the generated sphere. I'll try to see if I can sample those values, and if they (somehow) produce the correct gradients, but a little help would be appreciated, since I don't have any examples to work with like that.

David Roberson, Sat, 25 Jun 2022 06:18:06 -0400
I found a potential solution that would employ rotational offsets on three versions of the x-axis gradient fed as r, g, b components of an rgb2hsl function to produce a spherical angle gradient. Unfortunately, an odd problem popped up with the rotational offsets. They are not constant during rotation, which creates a messed up gradient. Am I doing them wrong here?

[CODE]-- 3d sphere
-- produces rgb gradient mapped to a 3d sphere.
-- an angle gradient can be derived using an extract hue component for x lookup
-- a get alpha component provides for y lookup
function prepare()
-- tilt & rotation precalc
toRad = 180/math.pi

radius = get_slider_input(RADIUS)

angle = get_angle_input(ROTATION)
angle = angle/toRad
angle1 = (angle + 120)/toRad
angle2 = (angle + 240)/toRad
-- offsets are correct at 0 but are not constant during rotation

cosa0 = math.cos(angle)
sina0 = math.sin(angle)

cosa1 = math.cos(angle1)
sina1 = math.sin(angle1)

cosa2 = math.cos(angle2)
sina2 = math.sin(angle2)

tilt = get_angle_input(TILT)/toRad
cosa3 = math.cos(tilt)
sina3 = math.sin(tilt)
end;

function get_sample(x, y)
-- input image; requires uvw mapping...
local r, g, b, a = get_sample_map(x, y, SOURCE)
a = 1

-- image generation
local px = (x*2.0) - 1.0
local py = (y*2.0) - 1.0
px = px/radius
px1 = px/radius
px2 = px/radius
py = py/radius
local len = math.sqrt((px*px)+(py*py))
if len > 1.0 then return 0,0,0,0 end

local z = -math.sqrt(1.0 - ((px*px)+(py*py)))
local z1 = z
local z2 = z

local tz = (cosa3 * z) - (sina3 * py)
local ty = (sina3 * z) + (cosa3 * py)
py = ty
z = tz

local tx = (cosa0 * px) - (sina0 * z)
local tz = (sina0 * px) + (cosa0 * z)
px = tx
z = tz

local tx1 = (cosa1 * px1) - (sina1 * z)
local tz1 = (sina1 * px1) + (cosa1 * z)
px1 = tx1
z1 = tz1

local tx2 = (cosa2 * px2) - (sina2 * z)
local tz2 = (sina2 * px2) + (cosa2 * z)
px2 = tx2
z2 = tz2

-- to do
-- internal hue extraction (hsb):
-- internal lookup on source image
-- add screen relative z-axis rotation (spin)

return px/2+.5,px1/2+.5,px2/2+.5,py/2+.5
-- return px/2+.5,px/2+.5,px/2+.5,0
-- return px1/2+.5,px1/2+.5,px1/2+.5,0
-- return px2/2+.5,px2/2+.5,px2/2+.5,0
-- return r, g, b, a
end;[/CODE]

David Roberson, Mon, 08 Aug 2022 00:15:23 -0400
I managed to solve the problem of scripting a rotatable sphere with the proper remapping gradients sometime last month, but am still tweaking and experimenting with the next logical steps. I never bothered to update this thread with my progress, and now there are too many different script versions; I can't decide which one to share. However, there's a good chance a few of them will find their way into filters. I have a number of planetary filters in the works, so you can expect to see some there. I'll probably submit one as a 3d rotatable sphere snippet (or even effect filter, since I can now map the input to a sphere, assuming it's prepared for spherical mapping). If I do, I'll come back and post the code that goes with it, for anyone who might just want to look at the script but doesn't need a working copy.

TTFN

Dilla's Scripting Blunders

Crapadilla — Thu, 28 Jul 2022 16:03:24 -0400

Crapadilla, Sun, 20 Nov 2011 13:31:39 -0500
Alrighty, I've been dipping a toe into the unknown waters of scripting lately. For some foolish reason I decided to begin work on a Logarithmic Spiral generator component. Spirals are so incredibly awesome, so I thought why not?

:| ;) :D

So far the basics look promising, but I'm only getting one revolution (or segment) of the spiral plotted, i.e. it does not spiral towards infinity or zero. I'm guessing there must be some mathematical reason for it, but currently I don't see it. :blush:

In case anyone less mathematically challenged than the current me feels like taking a look, here is the filter:

Indigo Ray, Sun, 20 Nov 2011 18:27:07 -0500
From wikipedia:

Quote
Many programming languages also provide the two-argument atan2 function, which computes the arctangent of y / x given y and x, but with a range of (âˆ’Ï€, Ï€].

You'll have to do a loop if you want a larger range, I think.

Crapadilla, Mon, 21 Nov 2011 04:25:12 -0500
Indeed. Thank you! :)

Quote
If desired an angle in the range [0, 2Ï€) may be obtained by adding 2Ï€ to the value if it is negative.

Sphinx., Mon, 21 Nov 2011 05:08:54 -0500
radialCoordinate = math.log(math.sqrt ( x^2 + y^2 ) * 30)
angularCoordinate = 0.5 + math.atan2 (x,y) / (2 * math.pi)
spiralGrd = angularCoordinate + radialCoordinate
spiralGrd = spiralGrd - math.floor(spiralGrd)

route spiralGrd to the output and take a look :-)

Crapadilla, Mon, 21 Nov 2011 06:29:38 -0500
Nice gradient! And more efficient, apparently. :)

But how does one implement proper aa_zones for this? And how does one offset the damned thing to the image center via script?

Sphinx., Mon, 21 Nov 2011 06:58:01 -0500
Well, I supplied the the code as a starting point. As such it does not make sense to have aa-zones for a gradient (there are no zones...). If you use the gradient to create that threshold like output, it makes sense to use the conditional ("if..then..else") to determine the aa_zone.

you can try using this as aa_zone though: math.floor(spiralGrd * 3), where 3 is the multiplication constant from the radialCoordinate calculation / 10. This should reduce moire aliasing in the center region, while skipping aa calc in the soft large gradients

For the centering you need to think "reverse", i.e. subtract 0.5 from x and y initially so you have 0,0 in the visual center region.

Crapadilla, Mon, 21 Nov 2011 09:06:36 -0500
Sphinx, thanks for your help. I'll get back to experimenting now...

James, Mon, 21 Nov 2011 09:06:42 -0500
Is that a spiral formula Sphinx? If i try to center the XY positions by subtracting a 0.5 value i get more of a radial remapped result from the input.

function prepare()
end;

function get_sample(x, y)

radialCoordinate = math.log(math.sqrt ((x-0.5)^2 + (y-0.5)^2 ) * 30)
angularCoordinate = 0.5 + math.atan2 (x,y) / (2 * math.pi)
spiralGrd = angularCoordinate + radialCoordinate
spiralGrd = spiralGrd - math.floor(spiralGrd)

r,g,b,a = get_sample_map(spiralGrd, spiralGrd, SOURCE)
return r, g, b, a
end;

Sphinx., Mon, 21 Nov 2011 09:25:12 -0500
James, don't use it for further lookup - just return the value, i.e.: return spiralGrd, spiralGrd, spiralGrd, 1

Dilla - try out radialCoordinate = math.log(math.sqrt ( x^2 + y^2 )) * 30 too, i.e. move the mul. constant outside. It is easier to control the "windings" this way.

James, Mon, 21 Nov 2011 09:32:01 -0500
Thanks, it seems no different doing that though. Testing with just a basic gradient to make things more visible i can see rings rather than a spiral -

function prepare()
end;

function get_sample(x, y)

radialCoordinate = math.log(math.sqrt ((x-0.5)^2 + (y-0.5)^2 ) * 30)
angularCoordinate = 0.5 + math.atan2 (x,y) / (2 * math.pi)
spiralGrd = angularCoordinate + radialCoordinate
spiralGrd = spiralGrd - math.floor(spiralGrd)

return spiralGrd, spiralGrd, spiralGrd, 1
end;

Or is that how it's suppose to be?

Crapadilla, Mon, 21 Nov 2011 10:13:21 -0500
James, you have to use the same offset on the angular coordinate as well, i.e.:

angularCoordinate = 0.5 + math.atan2 (x-0.5,y-0.5) / (2 * math.pi)

Sphinx., Mon, 21 Nov 2011 10:23:33 -0500
Oh I get it now James :-D well I meant:

add this as the first thing in the script, then you don't have to think more about it.

x,y = x - 0.5, y - 0.5

James, Mon, 21 Nov 2011 10:37:31 -0500
Thanks, that makes it work great :D

Crapadilla, Mon, 21 Nov 2011 11:28:51 -0500
This is so much fun! I couldn't resist turning this into a full-featured Spiral Gradient component. Submission to the library pending...

Take a look... constructive criticism on code optimization (and the AA_zones hack) is very welcome, cause - you know - it'll learn me. ;) :D

Also, I'm thinking about adding a 'Fixed Size' option.

Sphinx., Mon, 21 Nov 2011 13:07:13 -0500
Cool! Looks quite good - also codewise :)

About the aa hack: I think it would be better to do something like math.floor(spiralGrd * 3), since you can't for sure know that the given profile curve works well with your two constants (0.95 and 0.05).

I'd strip away the current aa stuff and simply return the above result.

Oh and another thing - you might want to check if blend_normal is faster than your current solution (honestly I don't know, since you're not doing alpha blending, but lerping instead which is much simpler)

Sphinx., Mon, 21 Nov 2011 13:14:26 -0500
Oh, I just realized that there is an even better aa_zone to return.

Find the line:

spiralGrd = spiralGrd - math.floor(spiralGrd)

and replace that with

aa_zone = math.floor(spiralGrd)
spiralGrd = spiralGrd - aa_zone

and ensure that aa_zone is not modified afterwards by old script etc..

Crapadilla, Mon, 21 Nov 2011 13:25:17 -0500

Quote
Sphinx. wrote: aa_zone = math.floor(spiralGrd) spiralGrd = spiralGrd - aa_zone

Oh yeah! That works like a charm! :)

James, Mon, 21 Nov 2011 14:26:16 -0500
One useful thing might be to maybe add the new Bezier curve control so the user could shape the profile with a custom curve.

Code wise everything seems quite good also. :)

Crapadilla, Mon, 21 Nov 2011 14:48:04 -0500

Quote
James wrote: Bezier curve control

Yup, sounds good. I'll schedule that into a future update.

Quote
Message log wrote: Script error (line 35): Invalid floating-point value passed to get_sample_curve

With Size, pixels at 1 the script throws an error. Hmmm!?.... :|

inujima, Mon, 21 Nov 2011 16:34:36 -0500

Quote
With Size, pixels at 1 the script throws an error. Hmmm!?....

Function math.log(x) returns nil value at x<=0.
By such a reason, the value of spiralGrd has been nil value at center coordinate. :)

James, Tue, 22 Nov 2011 07:03:39 -0500
Just wondering how can you fix this error mentioned, maybe with some sort of value limiting? or would it need to be fixed by the FF developers?

Not that i often use a size of 1 pixel but it would be useful to have a fix/workaround if anyone knows one. :)

inujima, Tue, 22 Nov 2011 07:47:24 -0500
It is necessary to rewrite so that zero must not be parameter of math.log().

For example
[CODE]
-- calculate spiral gradient map
radialCoordinate = math.log (math.sqrt ( spiralX*spiralX + spiralY*spiralY )) * windings
[/CODE]

rewrite like this

[CODE]
-- calculate spiral gradient map
local radial = math.sqrt ( spiralX*spiralX + spiralY*spiralY )
radial = math.max(radial, 0.00001)
radialCoordinate = math.log (radial) * windings
[/CODE]

Crapadilla, Wed, 23 Nov 2011 08:40:56 -0500
Dilla's Scripting Blunders -- Episode 2
The scripting n00b madness continues... ;) :D

Ok, I've got three points and their circumcircle drawn, but how do I draw the triangle between these points?

Crapadilla, Wed, 23 Nov 2011 11:38:28 -0500
Oh my, there sure are some interesting polygon hit-test algorithms out there -- exciting stuff to dig into... :eek: ;)

http://paulbourke.net/geometry/insidepoly/

Looks like my next scripting assignment is porting one of these to Lua. Personally, I'd choose the first one... 8)

Ghislaine, Tue, 29 May 2012 19:07:57 -0400
Hi Dilla

I just upload a filter tonight based on your Logarythmic spiral. This base has just a script map + an offset component. And it is great. Let me tell you that we could make wonders with it. I'm asking you if you would add some input in your script. I would appreciate much to work again with this logarythmic spiral with more possibilities. Thanks in advance.

I'm creating a second filter with yours. I have discovered a lot of spirograph forms just by playing with logarythmic spiral. I imagine that the possibilities would be multiplied at the infinity with few inputs added to your script. :)

Crapadilla, Mon, 04 Jun 2012 13:04:40 -0400
Ghislaine,

unfortunately I'm currently swamped in a project -- which means no time for filter authoring fun. However, feel free to post your suggestions here, and I might look into it once things have calmed down at work.

David Roberson, Fri, 22 Jul 2022 09:56:13 -0400

Quote
Ghislaine wrote: I'm creating a second filter with yours. I have discovered a lot of spirograph forms just by playing with logarythmic spiral. I imagine that the possibilities would be multiplied at the infinity with few inputs added to your script.

I could not figure out what filter you meant in this comment. Though it's been a while, do you remember which one it was?

Ghislaine, Tue, 26 Jul 2022 16:19:34 -0400
Hi dear !

I do not remember either.

Glad to get news from you. Have a nice day my friend. :)

David Roberson, Thu, 28 Jul 2022 16:03:24 -0400
Yeah, sometimes these things just slip our minds. Ah, well. No harm, no foul. Thanks for responding, and have a good day as well! :D

Spirals, Round Two

Sphinx. — Tue, 26 Jul 2022 21:09:15 -0400

Sphinx., Tue, 29 Nov 2011 03:42:26 -0500
Alright - I worked out a new basis for the spiral generation related to these two topics:

http://filterforge.com/forum/read.php?FID=11&TID=9142
and
http://filterforge.com/forum/read.php?FID=18&TID=9133

This new codebase supports two additional output modes: perpendicular gradient and division gradient. However it is not 100% complete yet and I need input from someone else.

There are two problems:

Output mode 1 is not correct - there is a very annoying split. Ideally this mode will index each "arm" with respect the given Division setting.

Output mode 2 is not always in 0..1 range, and the gradient is not perfectly perpendicular to mode 3.

All comments are welcome :-)

Sphinx., Tue, 29 Nov 2011 03:43:37 -0500
mode 1

Sphinx., Tue, 29 Nov 2011 03:43:55 -0500
mode 2

Sphinx., Tue, 29 Nov 2011 03:44:07 -0500
mode 3

Crapadilla, Tue, 29 Nov 2011 08:20:22 -0500

Skybase, Wed, 30 Nov 2011 01:46:20 -0500
You guys have no idea how happy I am. I just saw this and choked on a olive I just chewed on. :D

Sphinx., Wed, 30 Nov 2011 12:51:38 -0500
I guess I have to fix this myself if you're just going to sit there and eat popcorn and olives :-D

Well, erhm, I think I nailed it .. any comments/suggestions?

Sphinx., Wed, 30 Nov 2011 12:54:04 -0500
"Pics or it didn't happen!!"... ok then (Divide = 3, i.e. DIV = 3)

Crapadilla, Thu, 01 Dec 2011 13:08:10 -0500
Awesome, and versatile! I love that you can do archimedean spirals with this. :D

xirja, Wed, 07 Dec 2011 14:59:20 -0500
Truly!

I came up with a method that uses three bias curves, self modulated in series...

...but this script is much more elegant and leads to many interesting possibilities...

Sphinx., Thu, 08 Dec 2011 01:10:39 -0500
Cool stuff xirja!

I am working on improving "mode 2" (green ch. output) - the ramp should ideally be perpendicular to the spiral arm it represents. If you hook up a threshold you can easily see that the "angle" is not persistent...

David Roberson, Tue, 26 Jul 2022 21:09:15 -0400

Quote
Sphinx. wrote: I am working on improving "mode 2" (green ch. output) - the ramp should ideally be perpendicular to the spiral arm it represents. If you hook up a threshold you can easily see that the "angle" is not persistent...

Did you ever accomplish that improvement?

Bias Curve Formula?

fisholith — Fri, 22 Jul 2022 08:26:28 -0400

fisholith, Fri, 25 Jun 2010 21:43:05 -0400
Does anyone know off hand what the bias formula is?

I was building a curve script that handles a combination of curves I use pretty often, but I need to be able to build in a bias curve, and it occurs to me that I'm not sure what the function for it is. I know that the gain formula is a pair of bias curves, and I'll need to build a gain eventually too, but that obviously doesn't help in the short term.

GMM, Sat, 26 Jun 2010 05:00:34 -0400
The formulas were borrowed from
Christophe Schlick's "Fast alternative to Perlin's bias and gain functions", Graphics Gems IV, ed. Paul Heckbert, Academic Press, 1994.

Vladimir Golovin, Sun, 27 Jun 2010 10:10:40 -0400
Hint, hint: the above reply is a quote from Filter Forge help file ;)

David Roberson, Fri, 22 Jul 2022 08:26:28 -0400
I tracked down bias and gain functions based on that publication, though they're in javascript. I don't think they'll be a problem to convert to lua, though. I feel like I've done this before for a map script, but I'm trying it out with curve scripts this time. I wish there were more curve scripts featuring common and custom curve profiles.

Turning a script into a custom component

andyz — Wed, 06 Jul 2022 09:44:19 -0400

andyz, Wed, 06 Jul 2022 09:44:19 -0400
Hi it seems like scripts are very limited in re-usability. You can not even re-use the same script more than once in a filter without making a copy if I am correct.
It seems obvious that being able to add a lua script to the components section under a custom section would be ideal and very useful - but I think this is only on the wishlist so far

A script to uv map a sphere

David Roberson — Fri, 24 Jun 2022 00:50:00 -0400

David Roberson, Wed, 22 Jun 2022 05:57:32 -0400
I originally pursued a script that would render latitude and longitude gradients on a sphere, and succeed only in finding examples of latitude-equivalent gradients (though they did map to the sphere). Along the way, I started thinking that it would be simpler to map sample maps to a sphere inside the map script, rather than create gradients for use in Lookups.

The question is whether that is even possible. I have seen a map script that has internally generated pseudo-perlin noise uv(w) mapped in the noise generating function. You can find it in Planet Maker 3D by andyz.

David Roberson, Fri, 24 Jun 2022 00:50:00 -0400
While working on a spherical angular gradient, I realized what I want for "uv mapping" is essentially a lookup. I'm about 1 step away from solving the spherical angular gradient problem, having gotten as far as creating an rgb spherical gradient, which I can turn into an angular gradient once I find out how to sample hsb channels in the script (basically converting rgb to hsb internally). Finding documentation online is nearly impossible for Lua graphics scripting, so it would be very helpful to get help with those two things.

Script to be able to load hundreds of images from a folder into FF?

SpaceRay — Sat, 02 Apr 2022 04:27:47 -0400

SpaceRay, Sun, 26 Sep 2021 01:23:59 -0400
I have since long time ago had wished that FF could be able to load or import MULTIPLE images from a folder instead of ONLY ONE each time but it was not possible

Could there be any possible way with an Script to load hundreds of images into bomber plus taken from a selected folder? I mean all the images from that folder and not selectively

If not possible with a script could be maybe possible with an external tool that makes a bridge to do it?

What I want is to make this shown here

SpaceRay, Sun, 26 Sep 2021 01:27:58 -0400
Or bigger collage

SpaceRay, Sun, 26 Sep 2021 01:37:18 -0400
Also using FF it could be possible to randomly distribute the images with different slight rotations as shown here

SpaceRay, Sun, 26 Sep 2021 01:52:31 -0400
I thought that bomber plus would Not only import or load them, it would also apply some simple photo effects to each image and so you would make a unique collage that is not possible with any other software. I do not know if Studio Artist 5.5 could be able to do this

I remember that this was already asked some years ago and it was told that it was not possible to do because of the possible limitations of FF arquitecture and LUA scripting

But maybe could not made inside of FF, but Could there maybe done with an external tool that makes a bridge to be able to do it?

maybe someone that is new to FF that knows scripting could do it now

Thanks very much for any possible help

FFCreator, Sun, 26 Sep 2021 07:56:30 -0400
Some considerations without scripting.

You can add as many ColorMapControls in a filter as you want.
A ColorMapControl can contain an image that you choose (use the "Allow images" checkbox).
So designing a filter with multiple different images is not the problem (?)

But I assume you want to load all the (hundreds) images (in a folder) at once(?)
Each filter has a associated text file (right click on a filter name and choose "Locate File" to see its location).
An external tool that handles the filter (text) file can replace all the image filenames of the ColorMapControls (or do some more advanced stuff).

But I think to use 100 images in a filter you need to design a filter with 100 ColorMapControls before you can substitute the filenames.

SpaceRay, Sun, 26 Sep 2021 13:12:00 -0400
Thanks very much FFCreator

Quote
FFCreator wrote: You can add as many ColorMapControls in a filter as you want. A ColorMapControl can contain an image that you choose (use the "Allow images" checkbox). So designing a filter with multiple different images is not the problem (?)

Sorry that I did not explain it correctly and show what is really the problem. You are totally right that you can have a filter with a hundred images with a 10 map switch of color map control input (or even a thousands images with 10 groups of these 10 map switchs) and this is not the problem.

The problem is LOAD MANUALLY one by one EACH image into each one of the 100 color controls, that would take a very long time.

Here is Skybase that showed that it is possible to have 10 map switch input and he also is right that this is not a good way to do it as you would cry when you have to select each one of the color controls to load each one

SpaceRay, Sun, 26 Sep 2021 13:18:02 -0400

Quote
LAB#3015 Skybase page 22 Well somebody had to do it right? Here's everybody's nightmare come true: 100 input bomber.

The image above comes from this thread

Quote
FFCreator wrote: But I assume you want to load all the (hundreds) images (in a folder) at once(?)

YES, exactly, this is what I want, you nailed it. Sorry I did not tell exactly it above.

Quote
FFCreator wrote: But I think to use 100 images in a filter you need to design a filter with 100 ColorMapControls before you can substitute the filenames.

Of course, I agree that as I have showed above you must make first the filter with 100 Color controls and I can upload it here (I have to search for it first)

Quote
FFCreator wrote: An external tool that handles the filter (text) file can replace all the image filenames of the ColorMapControls (or do some more advanced stuff).

So do you mean that IF I take all the time needed to fill manually one by one each of the 100 color controls it could be possible then later to load another 100 different images with an external tool that would replace the filenames?

Sorry that I do not know about scripting or coding, How would the external tool know what the new images filenames are?

do you mean this?

ffsubstitute

Thanks very much for your help

SpaceRay, Sun, 26 Sep 2021 14:18:41 -0400
So, now I could try it, I have downloaded it and have seen that it already includes the filter with 100 color controls and a PDF with instructions, so I will read the instructions included and see If I can use it.

Thanks very much and is great that it is already available and ready to use.

I have searched in the forum and I found this from you

Quote
FFCreator wrote: I made a little tool "FFSubstitute". It is a GUI based tool to substitute multiple filenames of images in a Filter Forge (5) filter (actually in a copy of it). Images of Color Controls with names that match the pattern Image##xyz will be replaced (substituted) by the sel ected filenames in FFSubstitute. So it is possible to substitute 999 image names at once (Image##001 .. Image##999)! FFSubstitute can be used in every filter that has Color Controls with the property â€œAllow imagesâ€ set. Color Controls with names that donâ€™t match the pattern Image##xyz will not be changed. You can download it for free from my website. In the download package you 'll find an adapted version of the "100 input Bomber" filter (original autor Skybase) for demo purposes and instructions to use. I have tested the tool with Filter Forge 5 and the adapted "100 input Bomber filter". Let me now if it is useful for you.

Quote

FFCreator wrote:
I made a little tool "FFSubstitute".

It is a GUI based tool to substitute multiple filenames of images in a Filter Forge (5) filter (actually in a copy of it).
Images of Color Controls with names that match the pattern Image##xyz will be replaced (substituted) by the sel ected filenames in FFSubstitute. So it is possible to substitute 999 image names at once (Image##001 .. Image##999)!

FFSubstitute can be used in every filter that has Color Controls with the property â€œAllow imagesâ€ set. Color Controls with names that donâ€™t match the pattern Image##xyz will not be changed.

You can download it for free from my website.
In the download package you 'll find an adapted version of the "100 input Bomber" filter (original autor Skybase) for demo purposes and instructions to use.
I have tested the tool with Filter Forge 5 and the adapted "100 input Bomber filter".

Let me now if it is useful for you.

And I was in this thread and I was writing and answer but I totally forgot about it and really did not test it

regidark, Fri, 01 Apr 2022 06:25:40 -0400
Hello everyone! I would like to know if this tool "FFsubstitute" is available somewhere to download because it wouldn´t load the website.
Thanks a lot in advance

SpaceRay, Sat, 02 Apr 2022 04:27:47 -0400

Quote
regidark wrote: I would like to know if this tool "FFsubstitute" is available somewhere to download because it wouldn´t load the website. Thanks a lot in advance

Well I have it but is 1200 kb and the forum only allows 1000 kb so I would need to send it by email. So send me an message and I can send it.

Pattern Filling

ThreeDee — Wed, 30 Mar 2022 05:34:38 -0400

ThreeDee, Thu, 13 Sep 2012 14:03:15 -0400
Starting with the non-overlapping circles and moving toward pattern filling, now in Scripting mode.

Here is the first brute-force non-overlapping circles Script.

Not very sophisticated. I just take random locations and put a circle of random size there and make sure the radius isn't larger than the distance to the closest existing sphere. Lots of extra needless circles this way without really filling up the space.

Morgantao, Thu, 13 Sep 2012 16:50:45 -0400
Very nice to see your progress :)

Still have a bit of empty areas...
How about move + shrink strategy? I mean, you drop a circle at a random location, check for overlap (so far the same as what you did till now). Now instead of just shrinking the circle, how about nudging it's center a bit too?

uberzev, Thu, 13 Sep 2012 18:09:18 -0400
According to my measurements (External > Average) you've achieved 78.1% circle coverage.

Decent first effort. :D

ThreeDee, Thu, 13 Sep 2012 23:14:40 -0400

Quote
you've achieved 78.1% circle coverage

If you calculate it like that, filling a square with just one big circle will fill 78.5% of the image... :D

Quote
How about move + shrink strategy?

I have a few different steps planned.

The first obvious improvement would be to ingore any coordinates for new circles that are inside other circles (and thus have a radius of 0). And to ensure a minimum size for the circles in the initial circle-creation stage, so we don't get tons of those tiny dots.

But, more to the point, I have a different strategy planned, which works at least on paper, that is a fast way to do circle filling with no gaps in between. It's a bit more involved programming-wise. It is to fill the area so that any new circle created (apart from the first two) is always touching at least two existing circles.

A fancier version would take into account the original image, it's lightness value or local contrast (detail amount) in determining the radius. This way it gets closer ot the original challenge.

ThreeDee, Thu, 13 Sep 2012 23:29:05 -0400
The proper term is "circle packing". I just Googled "circle packing" and landed right on Quasimondo's Flickr images.

(Whatever happened to Quasimondo anyways? Haven't heard of him since 2008.)

The proper circle packing algorithms seem quite complex.

uberzev, Thu, 13 Sep 2012 23:30:23 -0400
Quasimondo was the guy (or one of the guys) who developed Aviary Peacock. I believe he stopped hanging here when he starting developing it.

You should email him and tell him we want him back.

ThreeDee, Fri, 14 Sep 2012 00:13:11 -0400
Just giving the circles some space around them makes it look better.

I finally read up on anti-aliasing zones and implemented it, so I don't have to set the antialiasing to "all pixels".

Skybase, Fri, 14 Sep 2012 00:14:55 -0400
Oooo these are interesting to see in FilterForge.

ThreeDee, Fri, 14 Sep 2012 03:18:05 -0400
Some improvements. A new circle is added to the table only if it is a valid circle (no overlap, above minimum size), so 600 circles fill the image in better than 2000 totally random circles did.

The index number is now used for shading as well (combined with an 5-color gradient and an elevation gradient).

I have one problem: For the life of me I can't seem to be able to handle getting out of the while-loop when the pattern is "full". So it just throws an error when I increase the "Number of circles" slider above the point where the pattern is full. (by "full" I mean when 100 consecutive attempts to place a new circle fail.)

uberzev, Fri, 14 Sep 2012 03:25:47 -0400
Nice work there! This should be made into an official component.

SpaceRay, Fri, 14 Sep 2012 03:51:53 -0400
WOW!!!! W O W !!! You are a genius ThreeDee, you have done a really great, nice and good work!! I like much what you have done until now.

AWESOME!

ThreeDee, Fri, 14 Sep 2012 05:44:21 -0400
Now this is starting to become fun. Image as color source.

Crapadilla, Fri, 14 Sep 2012 05:50:49 -0400
Nice!

Skybase, Fri, 14 Sep 2012 06:03:25 -0400
This will be the next FilterForge number one hit filter.

ThreeDee, Fri, 14 Sep 2012 06:03:29 -0400
With my luck, this feature will be included in the next beta version of V4... :|

ThreeDee, Fri, 14 Sep 2012 06:07:17 -0400
I would like to use the original image to modify the radius of the circles as well. For some reason math.random() is disabled for get_sample function :?: so looks like I need to create a pseudo random number function for this.

Skybase, Fri, 14 Sep 2012 06:36:49 -0400
By the way, here's a question. When sampling the color, are you deriving the mean or median? :o

ThreeDee, Fri, 14 Sep 2012 07:14:40 -0400

Quote
Skybase wrote: When sampling the color, are you deriving the mean or median?

Just the center point of the circle.

Okay, so I got the pseudo-random number function working, so now I can use the original image for size information. Darker areas make the initial circle sizes smaller.

Sharandra, Fri, 14 Sep 2012 07:26:28 -0400
Very cool, Threedee! Great that you took this challenge up! :D
I guess once you got it all working properly it could be any shape, not just circles?

ThreeDee, Fri, 14 Sep 2012 08:19:57 -0400
Circles are easier than random shapes as you can calculate the distance from their perimeter very easily. But yes, the ultimate goal is to be able to do this with any shape. Or even a number of different shapes.

I like how the Lionfish comes out.

ThreeDee, Fri, 14 Sep 2012 08:20:38 -0400
Maximum circle size variation gives a fractal-like look.

ThreeDee, Fri, 14 Sep 2012 08:32:06 -0400
Small size range.

ThreeDee, Fri, 14 Sep 2012 09:08:05 -0400
Ok, pretty good. But now let's go back to basics.

The packing density achieved with the current method is fairly good.

ThreeDee, Fri, 14 Sep 2012 09:09:09 -0400
However, when you compare it to a properly packed texture, you can see it can be vastly improved.

ThreeDee, Fri, 14 Sep 2012 09:48:55 -0400
Now, the math necessary to achieve that is way too complex for my taste, so here's my simplified approach/theory which should give a relatively good result:

Take two connected circles in the center and start drawing circles which touch the previous circle and the lowest available index circle filling in the space in clockwise direction.

Should be simple to implement and should give a good result.

The only foreseeable problem is what to do if the shape grows itself into an internal dead-end. So there needs to be an excape route when the next circle cannot be added in this wise.

Skybase, Fri, 14 Sep 2012 09:56:17 -0400
:o Interesting approach. I always imagined you needed some form of buffer for doing this.

SpaceRay, Fri, 14 Sep 2012 10:16:29 -0400
Nice, well done and interesting this two examples you have made

Of course that this canÂ´t be compared to the very tight and very compressed and VERY packed circles like this other example

BUT I think that although this is better, your example are not in bad at all, and are just different way, and I agree that surely to be able to make this very compact and tight packing would involve much more complex math and a different algorithm.

Please, continue your great work and keep getting it better and better :)

Quasimondo, Tue, 18 Sep 2012 07:20:05 -0400

Quote
(Whatever happened to Quasimondo anyways? Haven't heard of him since 2008.)

Hi guys,

it's been a few years but I just downloaded the latest version of Filter Forge only to discover that there is scripting possible now. Wow that's neat! I guess that might drag me right back in here. Looks like I have to learn Lua now.

Also saw the "Bomber" component (which did not exist back in the days when I was still quite active here) which I cannot help to remind me a quite a but of my "Autopainter" hub in Peacock ;-). But of course I can't deny that I might have taken the one or the other inspiration here when I made Peacock.

Seeing this thread makes me want to try out how my circle packing method works perfomance-wise with Lua: Starry Night Pie Packed
Cheers
Mario

ThreeDee, Tue, 18 Sep 2012 07:32:41 -0400
Awesome, Quasimondo has returned! :ff: Welcome back!

I love your implementations of circle packing, especially the flavor of fitting them into the largest available space.

Lua will be a piece of cake for you.

TD

Crapadilla, Tue, 18 Sep 2012 07:35:48 -0400
Quasi is alive! :beer: :D

SpaceRay, Mon, 26 Nov 2012 11:05:32 -0500
Please, any information update of this amazing and awesome filter project?

Is ThreeDee missing again? The last message is from 26 October, one month ago, and in this thread was in september 18 and now we are in November 26.

What ThreeDee have done here looks really nice and well done and does not necessarily need to be like the Quasimondo examples, I like it already just as the examples available above from ThreeDee

ddaydreams, Thu, 27 Dec 2012 23:11:44 -0500
It looked promising I hope something good will come from the effort. In the mean time I use peculator on my iphone. This level of math is way beyond me or I would give it shot in FF.

SpaceRay, Fri, 28 Dec 2012 02:44:51 -0500

Quote
ddaydreams It looked promising I hope something good will come fr om the effort.

I wish and hope that too, although I think that he has already got it right as it is now, as the image of the FF Lionfish is already well done as shown here.

Quote
ddaydreams In the mean time I use peculator on my iphone

YES!! The Percolator App for Iphone or Ipad is really excellent and amazing what it can do.

Although the problem with it is that is limited to a resolution of 2048 x 2048, and here in filter forge would not have a lim it, BUT you can use the "Live Trace" or "Image trace" of Adobe Illustrator or from Corel Draw and convert it to vector (it seems that it works very well) and then you can have the percolated image in ANY resolution you want.

PERCOLATOR USED THE WAY OF THREEDEE AND NOT FROM QUASIMONDO

ThreeDee wanted to get to the level of very tight circle packing that Quasimondo have shown in his beautiful and wonderful examples, BUT it seems that this is more complex than it seems, and so others app available, like Percolator is using the more separate and less space filling as shown already by ThreeDee in the examples above and it looks very nice too anyway.

I have not yet found any information related to the very tight and compressed circle packing that Quasimondo have shown and is using, and do not know how he has done it, perhaps is a own special programmed software made by himself or using something like the Processing language to make his own algorithm.

ddaydreams, Mon, 31 Dec 2012 18:59:39 -0500

Quote
YES!! The Percolator App for Iphone or Ipad is really excellent and amazing what it can do. Although the problem with it is that is limited to a resolution of 2048 x 2048, and here in filter forge would not have a lim it, BUT you can use the "Live Trace" or "Image trace" of Adobe Illustrator or from Corel Draw and convert it to vector (it seems that it works very well) and then you can have the percolated image in ANY resolution you want.

Quote

Yes convert peculator image to vector is probably a good option. I'll have to try that sometime

Skybase, Mon, 31 Dec 2012 20:12:47 -0500
so... well aside from our established group, anybody doing actual research on how this effect is achieved properly? :p

Might be interesting to see it implemented with this: http://en.wikipedia.org/wiki/Halton_sequence

ddaydreams, Mon, 31 Dec 2012 20:34:02 -0500
Apollonian sphere packing
http://en.wikipedia.org/wiki/Apollonian_sphere_packing

Skybase, Mon, 31 Dec 2012 22:41:59 -0500
That's probably the most direct manner, though given the fact that it's a pretty set thing, you don't have many choices for alternative design attempts.

ThreeDee's approach is actually kinda neat. If done right, you probably don't need trig because each circle is being drawn in a spiral form. So given the first x radius, draw the next circle next to it, and spiral outwards = probably a nice clean method.

//unrelated to filterforge....

On a totally unrelated FilterForge note... here's something I did a while ago. Colors derived from image. :) Self homework = make it fully original without deriving bits and pieces of code from everywhere.

ddaydreams, Mon, 31 Dec 2012 22:51:16 -0500
Skybase, what app did you do that in?

Skybase, Mon, 31 Dec 2012 23:11:05 -0500
Processing. ;)

Skybase, Mon, 31 Dec 2012 23:13:59 -0500
//more commentary unrelated to filterforge
A less elegant but hyper easy approach using StudioArtist 4. Program lets you do a lot of crazy things. Which is nice.

Betis, Sun, 24 Feb 2013 15:21:47 -0500
Hey guys, I came across this cool 3DS Max plugin that does this in 3D!
https://sites.google.com/site/autofill21/gallery

It's written in python, but it's open-source! Maybe similar methods could be applied to FF lua.

Skybase, Sun, 24 Feb 2013 21:25:51 -0500
autoPack is pretty cool. As more of a side-information related to autoPack, the plugin lets you load up protein molecules with studied structures and animation in various model modes. You use these to fill space up with cellPack. They were doing a contest a while ago promoting the cellPack thing. CellPack crashes a lot so I've only gotten it to work once unfortunately.

SpaceRay, Mon, 25 Feb 2013 20:46:43 -0500
If you may be interested in circle packing in 3D (sphere packing) I have found some time ago this very good and interesting tutorial for Cinema 4D --> Some kind of Sphere Packing in 3D

It shows how to make the sphere be packed in the tighest and closer one to each other in a dynamic way.

Quote
ddaydreams Skybase, what app did you do that in?

Skybase is using the Processing scripting language and if you want to have more information you can see this other thread with further links to know what it is about.

ddaydreams, Mon, 25 Feb 2013 20:55:26 -0500
Thanks SpaceRay

Skybase, Mon, 25 Feb 2013 23:09:48 -0500
SpaceRay, provided that tutorial, all you need to do is just add a repelling factor to each instance of a sphere. You can then turn up the ambient color and get flat-shaded circles for output. Cinema also allows you to sample colors based on image input. Pretty sure I remember I did that so the shader setup might be confusing but the actual process shouldn't be difficult.

ddaydreams, Sun, 27 Apr 2014 22:00:11 -0400
Did this filter that Threedee made in 2012 in FF make it into the FF library or did the ffxml file get shared somewhere in the FF forums or elsewhere online?

Skybase, Mon, 28 Apr 2014 02:23:51 -0400
lol ahhh good memories.

Crapadilla, Mon, 28 Apr 2014 06:45:05 -0400

Quote
Did this filter make it into the FF library?

Nope, I don't think it did.

Ramlyn, Mon, 28 Apr 2014 12:02:51 -0400
It would be nice to have it. :)

Borkus McJorkus, Fri, 08 Aug 2014 12:54:18 -0400
Has this filter been completed? And if so, where can I find it? For maybe a decade now, I've been looking for a filter that fills the selection with bubbles; this is as close as I've ever found.

Initialization problem

Sphinx. — Mon, 28 Mar 2022 08:52:41 -0400

Sphinx., Sun, 21 Aug 2011 07:41:22 -0400
I'm working on a filter with a rather heavy initialization section. In theory the initialization script part should execute one time (I'm testing with only CPU core), however I counted more than 60 executions :-S

Here is a dedicated test script that shows the problem (also attached, note it is unsafe due to the os.time() call):
[CODE]
function prepare()
do_initialize = true
stamp = os.time()
print("prepare ("..stamp..") ---------------------");
end;

function get_sample(x, y)
if do_initialize then
do_initialize = false
print("initialize ("..stamp.."); x = " .. x ..", y = "..y);
end
return 0,0,0,0
end;
[/CODE]

Here is the output (Filter Forge x86.log):

[CODE]
prepare (1313930290) ---------------------
initialize (1313930290); x = 0,00083333333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,12583333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,25083333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,37583333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,50083333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,62583333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,75083333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,87583333333333, y = 0,00083333333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,12583333333333
initialize (1313930290); x = 0,12583333333333, y = 0,12583333333333
initialize (1313930290); x = 0,25083333333333, y = 0,12583333333333
initialize (1313930290); x = 0,37583333333333, y = 0,12583333333333
initialize (1313930290); x = 0,50083333333333, y = 0,12583333333333
initialize (1313930290); x = 0,62583333333333, y = 0,12583333333333
initialize (1313930290); x = 0,75083333333333, y = 0,12583333333333
initialize (1313930290); x = 0,87583333333333, y = 0,12583333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,25083333333333
initialize (1313930290); x = 0,12583333333333, y = 0,25083333333333
initialize (1313930290); x = 0,25083333333333, y = 0,25083333333333
initialize (1313930290); x = 0,37583333333333, y = 0,25083333333333
initialize (1313930290); x = 0,50083333333333, y = 0,25083333333333
initialize (1313930290); x = 0,62583333333333, y = 0,25083333333333
initialize (1313930290); x = 0,75083333333333, y = 0,25083333333333
initialize (1313930290); x = 0,87583333333333, y = 0,25083333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,37583333333333
initialize (1313930290); x = 0,12583333333333, y = 0,37583333333333
initialize (1313930290); x = 0,25083333333333, y = 0,37583333333333
initialize (1313930290); x = 0,37583333333333, y = 0,37583333333333
initialize (1313930290); x = 0,50083333333333, y = 0,37583333333333
initialize (1313930290); x = 0,62583333333333, y = 0,37583333333333
initialize (1313930290); x = 0,75083333333333, y = 0,37583333333333
initialize (1313930290); x = 0,87583333333333, y = 0,37583333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,50083333333333
initialize (1313930290); x = 0,12583333333333, y = 0,50083333333333
initialize (1313930290); x = 0,25083333333333, y = 0,50083333333333
initialize (1313930290); x = 0,37583333333333, y = 0,50083333333333
initialize (1313930290); x = 0,50083333333333, y = 0,50083333333333
initialize (1313930290); x = 0,62583333333333, y = 0,50083333333333
initialize (1313930290); x = 0,75083333333333, y = 0,50083333333333
initialize (1313930290); x = 0,87583333333333, y = 0,50083333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,62583333333333
initialize (1313930290); x = 0,12583333333333, y = 0,62583333333333
initialize (1313930290); x = 0,25083333333333, y = 0,62583333333333
initialize (1313930290); x = 0,37583333333333, y = 0,62583333333333
initialize (1313930290); x = 0,50083333333333, y = 0,62583333333333
initialize (1313930290); x = 0,62583333333333, y = 0,62583333333333
initialize (1313930290); x = 0,75083333333333, y = 0,62583333333333
initialize (1313930290); x = 0,87583333333333, y = 0,62583333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,75083333333333
initialize (1313930290); x = 0,12583333333333, y = 0,75083333333333
initialize (1313930290); x = 0,25083333333333, y = 0,75083333333333
initialize (1313930290); x = 0,37583333333333, y = 0,75083333333333
initialize (1313930290); x = 0,50083333333333, y = 0,75083333333333
initialize (1313930290); x = 0,62583333333333, y = 0,75083333333333
initialize (1313930290); x = 0,75083333333333, y = 0,75083333333333
initialize (1313930290); x = 0,87583333333333, y = 0,75083333333333
initialize (1313930290); x = 0,00083333333333333, y = 0,87583333333333
initialize (1313930290); x = 0,12583333333333, y = 0,87583333333333
initialize (1313930290); x = 0,25083333333333, y = 0,87583333333333
initialize (1313930290); x = 0,37583333333333, y = 0,87583333333333
initialize (1313930290); x = 0,50083333333333, y = 0,87583333333333
initialize (1313930290); x = 0,62583333333333, y = 0,87583333333333
initialize (1313930290); x = 0,75083333333333, y = 0,87583333333333
initialize (1313930290); x = 0,87583333333333, y = 0,87583333333333
[/CODE]

Variable "do_initialize" should remain false, but for some reason it doesn't. "Prepare" is only executed once, so what the h*** is going on here? Is this related to the rendering "tiles"?

Sphinx., Sun, 21 Aug 2011 08:11:49 -0400
This is very annoying :-S I can't prepare the script in function Prepare because get_sample calls are not allowed (I need to analyze multiple image inputs to get average color of the inputs).

So I'm left with the option to analyze the images in the main get_sample function (with a similar initialization setup as described above). But the extreme overhead caused by the multiple executions (as described above) makes it practically unusable.. :evil:

We really need a middle way here: some sort of initialization function that allows get_sample calls and can produce data that is shared in all threads/tiles..

FF programmers.. any comments?

Igor Lorents, Mon, 22 Aug 2011 05:27:17 -0400
Sphinx, thank you for reporting the issue.

The problem seems to be in our architecture. Changes you've made in the Global table which contains definition for all global variables after the first initialization (which is made by calling the prepare() routine) do not propagate properly.
That's why your initialization code in get_sample() function executes each time when the new rendering block is started.
The problem should still persist even if you use single-threaded rendering, and your test sample illustrates it very well.

So, this issue seems to be a pretty large piece of work, and unfortunately I won't have time for it until the release of version 3.0.

Sorry for the inconvenience.

Sphinx., Mon, 22 Aug 2011 07:16:46 -0400
I see - after Prepare has been called you assume the global table is not changed and simply copy the table...

Could you possibly add some sort of "super global" table that works across tiles, or allow get_sample calls in prepare?

Igor Lorents, Mon, 22 Aug 2011 07:42:08 -0400

Quote
Could you possibly add some sort of "super global" table that works across tiles, or allow get_sample calls in prepare?

Unfortunately no, because the behavior of the suggested "super global" table is absolutely equal to the intended behavior of the global table. We'll just have to implement it properly :)

Sphinx., Mon, 22 Aug 2011 09:06:19 -0400
Sigh... well, that "bug" along with the darn unpersist error blocks several of my projects. Patience..

Thanks for the explanation anyways.

Sphinx., Thu, 17 Nov 2011 05:43:34 -0500
Alright, FF3 released - time to bring this up again :-)

The problem still persists:

Global variables are not truly global, but only "global" inside a given rendering block. This will ruin smart logic such as initialization regions.

A typical scenario: collect a set of samples and use their properties to determine global filtering (e.g. auto levels). This initial sample collection is only necessary to do once.

Sphinx., Fri, 21 Nov 2014 02:14:11 -0500
So, any news on this issue? Script filters with heavy prepare/initialization sections are unreasonably slow...

Sphinx., Fri, 21 Nov 2014 03:20:31 -0500
Here is ThreeDee's cool circle packer filter. It uses an initialization section to prepare some stuff based on sampler inputs. Its essentially the same as using the prepare method only you blocked the possibility to use sampler sources for preparation, so he has to use an init variable and do it in get_sample.. nothing weird about that design.

I stripped the actual rendering script so all this filter is doing in theory is that one initialization, however in reality this seems to be called for each of your internal temporary rendering tiles :eek:

[CODE]
function get_sample(x, y)

-- only on first run:
if init == 0 then
get_circles() --get_circles set init = 1
end -- if init == 0
local r,g,b = 1,1,1
return r,g,b,1,aa_zone
end;

[/CODE]

Ramlyn, Fri, 21 Nov 2014 09:26:01 -0500
Humm... so it repeats the same process also when it is not needed.

Sphinx., Fri, 21 Nov 2014 09:28:22 -0500
Yes, for each of those rendering blocks you see being completed during rendering.. and if you have multiple pass rendering enabled (that is default) it is number of blocks x number of passes..

ThreeDee, Sun, 23 Nov 2014 15:34:17 -0500
Hey, I had a thought:

How about using an unsafe script to store the precalculation to a (comma-delimited?) text file when a checkbox is activated. You can set it up so that only the first thread does this calculation and saving of the file by making sure the coordinates are less than 1/16th of the shorter dimension of the image (and init ==0). Other threads do nothing while the checkbox in on.

Then when the checkbox is clicked off the filter reads the precalculation file instead of doing the calculation. Hopefully this can be done during the Prepare() function so it doesn't have to be done for each thread.

This is similar solution to what Ken (with some help from the undersigned) did with the embedded external image:
https://www.filterforge.com/forum/read...sage120745

Won't be able to submit to library as it is an unsafe script. Otherwise I don't see why it wouldn't work.

Sphinx., Mon, 24 Nov 2014 02:26:58 -0500
Yes, that will probably do as a temporary workaround for private filters (since we can't submit unsecure filters).

However the main point of this 3 year, 3 months and 3 days old thread is still very valid: script filters with heavy global initialization are quite inefficiently executed.

I wish they had a "fastmode" render mode that skipped all the render block stuff all together. One render block to rule them all (and that one blocks resolution = the output image resolution). No magic, no preview, no multipass.. just raw to the bone processing.

Sphinx., Tue, 25 Nov 2014 05:52:44 -0500
Yum Yum.. http://lua-users.org/wiki/SaveTableToFile

ThreeDee, Wed, 26 Nov 2014 10:06:31 -0500

Quote
Sphinx wrote: I wish they had a "fastmode" render mode that skipped all the render block stuff all together.

Couldn't agree with you more. Lack of such an option makes script optimization a bitch.

Sphinx., Sun, 12 Jul 2015 13:44:12 -0400
Vlad, GMM anyone... are you going to address this multithreading performance issue in V5?

GMM, Mon, 13 Jul 2015 05:40:30 -0400
I hope this is going to be fixed at the time we implement LuaJIT which is supposed to be faster and better overall. I'm not sure LuaJIT will make its way into FF5 but it's in the works.

trung, Tue, 08 Sep 2015 22:13:11 -0400
longish iterative process, and not really necessary if you can use other commands

Sphinx., Sat, 21 Nov 2015 02:43:54 -0500
Filter Forge x86 5.006.38069.21538.

Problem still present - an init call that theoretically should called *once* is called for each rendering tile etc. :cry:

[CODE]function prepare()

do_initialize = true
stamp = os.time()
print("prepare ("..stamp..") ---------------------");
end;

function get_sample(x, y)
if do_initialize then
do_initialize = false
print("initialize ("..stamp.."); x = " .. x ..", y = "..y);
end

return 0,0,0,0
end;[/CODE]

Above script produces the following log output. Ideally we should see one line only.

Quote
Filter Forge x86.log Wrote: Filter Forge x86 5.006.38069.21538 Release, November 19, 2015 09:43 [21-11-2015 08:35:38 Rom, normaltid] prepare (1448091338) --------------------- initialize (1448091338); x = 0,00083333333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,12583333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,25083333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,37583333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,50083333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,62583333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,75083333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,87583333333333, y = 0,00083333333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,12583333333333 initialize (1448091338); x = 0,12583333333333, y = 0,12583333333333 initialize (1448091338); x = 0,25083333333333, y = 0,12583333333333 initialize (1448091338); x = 0,37583333333333, y = 0,12583333333333 initialize (1448091338); x = 0,50083333333333, y = 0,12583333333333 initialize (1448091338); x = 0,62583333333333, y = 0,12583333333333 initialize (1448091338); x = 0,75083333333333, y = 0,12583333333333 initialize (1448091338); x = 0,87583333333333, y = 0,12583333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,25083333333333 initialize (1448091338); x = 0,12583333333333, y = 0,25083333333333 initialize (1448091338); x = 0,25083333333333, y = 0,25083333333333 initialize (1448091338); x = 0,37583333333333, y = 0,25083333333333 initialize (1448091338); x = 0,50083333333333, y = 0,25083333333333 initialize (1448091338); x = 0,62583333333333, y = 0,25083333333333 initialize (1448091338); x = 0,75083333333333, y = 0,25083333333333 initialize (1448091338); x = 0,87583333333333, y = 0,25083333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,37583333333333 initialize (1448091338); x = 0,12583333333333, y = 0,37583333333333 initialize (1448091338); x = 0,25083333333333, y = 0,37583333333333 initialize (1448091338); x = 0,37583333333333, y = 0,37583333333333 initialize (1448091338); x = 0,50083333333333, y = 0,37583333333333 initialize (1448091338); x = 0,62583333333333, y = 0,37583333333333 initialize (1448091338); x = 0,75083333333333, y = 0,37583333333333 initialize (1448091338); x = 0,87583333333333, y = 0,37583333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,50083333333333 initialize (1448091338); x = 0,12583333333333, y = 0,50083333333333 initialize (1448091338); x = 0,25083333333333, y = 0,50083333333333 initialize (1448091338); x = 0,37583333333333, y = 0,50083333333333 initialize (1448091338); x = 0,50083333333333, y = 0,50083333333333 initialize (1448091338); x = 0,62583333333333, y = 0,50083333333333 initialize (1448091338); x = 0,75083333333333, y = 0,50083333333333 initialize (1448091338); x = 0,87583333333333, y = 0,50083333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,62583333333333 initialize (1448091338); x = 0,12583333333333, y = 0,62583333333333 initialize (1448091338); x = 0,25083333333333, y = 0,62583333333333 initialize (1448091338); x = 0,37583333333333, y = 0,62583333333333 initialize (1448091338); x = 0,50083333333333, y = 0,62583333333333 initialize (1448091338); x = 0,62583333333333, y = 0,62583333333333 initialize (1448091338); x = 0,75083333333333, y = 0,62583333333333 initialize (1448091338); x = 0,87583333333333, y = 0,62583333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,75083333333333 initialize (1448091338); x = 0,12583333333333, y = 0,75083333333333 initialize (1448091338); x = 0,25083333333333, y = 0,75083333333333 initialize (1448091338); x = 0,37583333333333, y = 0,75083333333333 initialize (1448091338); x = 0,50083333333333, y = 0,75083333333333 initialize (1448091338); x = 0,62583333333333, y = 0,75083333333333 initialize (1448091338); x = 0,75083333333333, y = 0,75083333333333 initialize (1448091338); x = 0,87583333333333, y = 0,75083333333333 initialize (1448091338); x = 0,00083333333333333, y = 0,87583333333333 initialize (1448091338); x = 0,12583333333333, y = 0,87583333333333 initialize (1448091338); x = 0,25083333333333, y = 0,87583333333333 initialize (1448091338); x = 0,37583333333333, y = 0,87583333333333 initialize (1448091338); x = 0,50083333333333, y = 0,87583333333333 initialize (1448091338); x = 0,62583333333333, y = 0,87583333333333 initialize (1448091338); x = 0,75083333333333, y = 0,87583333333333 initialize (1448091338); x = 0,87583333333333, y = 0,87583333333333

Quote

Filter Forge x86.log Wrote:

Filter Forge x86 5.006.38069.21538 Release, November 19, 2015 09:43 [21-11-2015 08:35:38 Rom, normaltid]
prepare (1448091338) ---------------------
initialize (1448091338); x = 0,00083333333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,12583333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,25083333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,37583333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,50083333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,62583333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,75083333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,87583333333333, y = 0,00083333333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,12583333333333
initialize (1448091338); x = 0,12583333333333, y = 0,12583333333333
initialize (1448091338); x = 0,25083333333333, y = 0,12583333333333
initialize (1448091338); x = 0,37583333333333, y = 0,12583333333333
initialize (1448091338); x = 0,50083333333333, y = 0,12583333333333
initialize (1448091338); x = 0,62583333333333, y = 0,12583333333333
initialize (1448091338); x = 0,75083333333333, y = 0,12583333333333
initialize (1448091338); x = 0,87583333333333, y = 0,12583333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,25083333333333
initialize (1448091338); x = 0,12583333333333, y = 0,25083333333333
initialize (1448091338); x = 0,25083333333333, y = 0,25083333333333
initialize (1448091338); x = 0,37583333333333, y = 0,25083333333333
initialize (1448091338); x = 0,50083333333333, y = 0,25083333333333
initialize (1448091338); x = 0,62583333333333, y = 0,25083333333333
initialize (1448091338); x = 0,75083333333333, y = 0,25083333333333
initialize (1448091338); x = 0,87583333333333, y = 0,25083333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,37583333333333
initialize (1448091338); x = 0,12583333333333, y = 0,37583333333333
initialize (1448091338); x = 0,25083333333333, y = 0,37583333333333
initialize (1448091338); x = 0,37583333333333, y = 0,37583333333333
initialize (1448091338); x = 0,50083333333333, y = 0,37583333333333
initialize (1448091338); x = 0,62583333333333, y = 0,37583333333333
initialize (1448091338); x = 0,75083333333333, y = 0,37583333333333
initialize (1448091338); x = 0,87583333333333, y = 0,37583333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,50083333333333
initialize (1448091338); x = 0,12583333333333, y = 0,50083333333333
initialize (1448091338); x = 0,25083333333333, y = 0,50083333333333
initialize (1448091338); x = 0,37583333333333, y = 0,50083333333333
initialize (1448091338); x = 0,50083333333333, y = 0,50083333333333
initialize (1448091338); x = 0,62583333333333, y = 0,50083333333333
initialize (1448091338); x = 0,75083333333333, y = 0,50083333333333
initialize (1448091338); x = 0,87583333333333, y = 0,50083333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,62583333333333
initialize (1448091338); x = 0,12583333333333, y = 0,62583333333333
initialize (1448091338); x = 0,25083333333333, y = 0,62583333333333
initialize (1448091338); x = 0,37583333333333, y = 0,62583333333333
initialize (1448091338); x = 0,50083333333333, y = 0,62583333333333
initialize (1448091338); x = 0,62583333333333, y = 0,62583333333333
initialize (1448091338); x = 0,75083333333333, y = 0,62583333333333
initialize (1448091338); x = 0,87583333333333, y = 0,62583333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,75083333333333
initialize (1448091338); x = 0,12583333333333, y = 0,75083333333333
initialize (1448091338); x = 0,25083333333333, y = 0,75083333333333
initialize (1448091338); x = 0,37583333333333, y = 0,75083333333333
initialize (1448091338); x = 0,50083333333333, y = 0,75083333333333
initialize (1448091338); x = 0,62583333333333, y = 0,75083333333333
initialize (1448091338); x = 0,75083333333333, y = 0,75083333333333
initialize (1448091338); x = 0,87583333333333, y = 0,75083333333333
initialize (1448091338); x = 0,00083333333333333, y = 0,87583333333333
initialize (1448091338); x = 0,12583333333333, y = 0,87583333333333
initialize (1448091338); x = 0,25083333333333, y = 0,87583333333333
initialize (1448091338); x = 0,37583333333333, y = 0,87583333333333
initialize (1448091338); x = 0,50083333333333, y = 0,87583333333333
initialize (1448091338); x = 0,62583333333333, y = 0,87583333333333
initialize (1448091338); x = 0,75083333333333, y = 0,87583333333333
initialize (1448091338); x = 0,87583333333333, y = 0,87583333333333

Indigo Ray, Wed, 24 May 2017 22:36:38 -0400
FF 7.001: Still a problem. Really hampers the scripting feature in FF.

I adapted Sphinx's code to output an image instead of text ( :!: unsafe script):

Indigo Ray, Wed, 24 May 2017 22:39:28 -0400
If function prepare() was called once, this image would be completely black.
Instead, there are 64 boxes, meaning it was called 64 times! For a little 600x600 image!

Sphinx., Thu, 12 Oct 2017 02:42:31 -0400
Any news on this issue?

This is a major performance issue in advanced scripts...

GMM, Thu, 12 Oct 2017 07:02:18 -0400
I'm afraid no news for FF7 in this matter.

Sphinx., Thu, 12 Oct 2017 07:47:22 -0400
That is bad news :-(

Here is a simple graphic summary of the issue - and I'm not sure the estimated 64 tiles is really correct as previous tests showed even more init calls

Sphinx., Fri, 02 Aug 2019 06:46:09 -0400
GMM/Vlad - is this issue going to be addressed in V9 at some point?

GMM, Fri, 02 Aug 2019 06:52:29 -0400
I'm afraid not in V9 :(

Sphinx., Fri, 02 Aug 2019 07:56:22 -0400
Sigh! I guess its more profitable adding new bells and whistles than polishing/fixing the existing ones (Psst... loop sample cache!). Oh well, true global initialization would also be needed for green to gray conversion I guess. Fingers crossed. Thanks for the answer :-)

Rico, Mon, 28 Mar 2022 03:54:01 -0400
Wow, this thread is nearly 11 years old!

I am trying to work on circle-packing, like many others before me. I have made some good headway building on ThreeDee's excellent work, but the primary problem is the inability to cache properly, which is tied to this initialisation issue. I want to build my tables once and once only.

Dear moderators can you tell us if this will ever be fixed please? Thank you.

GMM, Mon, 28 Mar 2022 08:52:41 -0400

Quote
Rico wrote: Dear moderators can you tell us if this will ever be fixed please?

Ever? Probably yes.
Soon? I'm afraid not.

What's current status of Mac batch rendering options?

Lorenzosart — Fri, 25 Feb 2022 18:55:40 -0500

Lorenzosart, Fri, 25 Feb 2022 14:05:31 -0500
I'm a non-coding artist who needs a script to apply all presets of one filter to a single image file. None of the solutions I've found via these forums seem to work on my Mac mini running Monterey 12.2.1.

If none exist, I'll pay someone to create one... assuming I can afford it. :-)

Any ideas/pointers/volunteers?

SpaceRay, Fri, 25 Feb 2022 14:22:16 -0500
Well, for Mac there is only one option available that may work

Filter Forge External tools part

FFBatchmaster by Totte

Sorry that I do not know if it may be working right on Monterey

Quote
Lorenzosart wrote: If none exist, I'll pay someone to create one... assuming I can afford it.

It depends of how much you want to spend, I do not know, maybe , there is a possible alternative, you can install Parallels Windows software emulator that works on Monterey and you could use the other many External tools available for windows. Even there is now a 3 days sale Parallels mac bundle for same price

You can use the FF trial version if you only need for this time

The main problem is that for longer use you will need another FF license for windows unless you have the FF 11 Studio that includes two licenses

Lorenzosart, Fri, 25 Feb 2022 18:55:40 -0500

Quote
SpaceRay wrote: It depends of how much you want to spend, I do not know, maybe , there is a possible alternative, you can install Parallels Windows software emulator that works on Monterey and you could use the other many External tools available for windows.

Thanks for the information. Even though running Parallels to gain access to the Windows tools is appealing, I doubt that I'd have much success. I'm old enough (74) to know that my brain does not work linearly and I have been so spoiled by the Mac--which I've used since 1984--that even navigating Windows may be a challenge for me.

I'll try it, but would much prefer something that is native to the Mac environment.

Scripting is like magic for people like me, so I don't even know how to offer an appropriate pay incentive. $500? More? I can pay via any of the normal channels like PayPal, or I can pay in ETH if given a wallet address. This is: My LinkTree

Script to load random image into a filter?

Ilmeni — Mon, 31 Jan 2022 18:17:07 -0500

Ilmeni, Sat, 29 Jan 2022 15:29:57 -0500
Hi all! Is it possible to load a random image from a folder into a filter, either via script or via color control?
Or maybe to open a random image with the image component in a filter?
thank you for your help! :)

Sphinx., Mon, 31 Jan 2022 03:05:34 -0500
That is not possible. Not by script either, unless you write your own image importer.. that is a lot of work.

What you can do is to randomly pick an image from a number of predefined image inputs.

Or if you can use the commandline renderer it should be an easy thing achieve with a little powershell or similar. But that of course rules out the GUI and any interaction.

Ilmeni, Mon, 31 Jan 2022 18:17:07 -0500
Thank you! :)

Setting a single pixel?

James — Sun, 27 Jun 2021 01:35:29 -0400

James, Fri, 25 Jun 2021 23:35:52 -0400
I have made various scripts in Lua that do distortions, curve ops and color effects etc but so far I have been confused how to set a single pixel.

What I want is to simply set the r,g,b,a value at an x,y position. Does anyone have a script snippet for this? Thanks

Theob, Sat, 26 Jun 2021 10:19:04 -0400
Have you had a look here. Hope it may help :)

James, Sat, 26 Jun 2021 14:01:11 -0400
The closest thing I can find in the library is the pixel art generators in the Bearestroika filter. These use an array however, I don't want to have to set a whole array of colours each time but simply set one pixel of an image inputs colour. There should be a simpler way but so far my experiments have failed but I'm guessing there will be a fairly simple solution.

So say for example I want to set 0,0 of images width and height to 255,0,0,1.0 which should make the very first pixel red.

emme, Sat, 26 Jun 2021 14:30:26 -0400
As you probably know, FF works with sample coordinates, not with pixel coordinates - so there isn't really a simple way to set pixel values like you would on a bitmap based system.

You can use the global variables OUTPUT_WIDTH and OUTPUT_HEIGHT to get the image dimensions in pixels and use those calculate the pixel coordinates.

For example:

[CODE]
function prepare()
px,py = get_slider_input(PX),get_slider_input(PY)
w,h = OUTPUT_WIDTH, OUTPUT_HEIGHT
px,py = math.floor(px*w), math.floor(py*h)
end;

function get_sample(x, y)
local v = 0
if math.floor(x*w) == px and math.floor(y*h) == py then v = 1 end;
return v,v,v
end;
[/CODE]

Note that this only works with square images. Some extra code is needed to compensate for different aspect ratios.

Rachel Duim, Sat, 26 Jun 2021 14:39:50 -0400
Another thing to know, FF is pixel aware. Although this only draws lines and not points, you can use this example to set single pixels if you wish: Pixel Image with Grid

James, Sat, 26 Jun 2021 15:03:47 -0400
Thanks emme, that basically does what I want but due to the sample coordinates system you mention your script steps a bit too much each pixel value increased and also when the input value is max it seems to make the pixel vanish.

Another thing I noticed is if you don't use a slider input and just set px,py = 1,1 instead then the pixel vanishes. Also how would you increase the pixel size from 1x1 to say 10x10?

My goal was to port some lua scripts that draw various things using a set pixel function but it seems that due to the sample coordinates system there would be problems.

Also thanks for the reply Rachel Duim, currently I only have FF version 3 so I can't check the map script that filter uses. The script emme posted is basically what i want but there is the few issues I mention.

emme, Sat, 26 Jun 2021 15:51:03 -0400
Yes, the way the SliderControl UI works doesn't allow for much precision. ValueControl outputs fractional values, but I don't think it's available in FF3. You can also manually ins ert fractional values to the SliderControl for more precision, or set an IntSlider range to match the image dimensions. These are not great solutions, but that's the best you can do. The pixel coordinates can of course be precisely set via code.

For a quick and dirty fix for the rounding problem, just subtract 0.5 from w and h in the if statement.

[CODE]if math.ceil(x*w-0.5) == px and math.ceil(y*h-0.5) == py then v = 1 end;[/CODE]

Yeah, I mean you could make a list / array of all the se t pixel instructions and just loop through them, but that would not be very efficient in FF :)

James, Sat, 26 Jun 2021 16:12:05 -0400
Thanks emme, that code makes the pixel disappear if set to 0,0 however but I fixed it using an if statement:

[CODE]function prepare()
px,py = get_slider_input(PX),get_slider_input(PY)
w,h = OUTPUT_WIDTH, OUTPUT_HEIGHT
px,py = math.floor(px*w), math.floor(py*h)
end;

function get_sample(x, y)
local r = 0
local g = 0
local b = 0
local a = 1

if px == 0 and py == 0 then
if math.floor(x*w) == px and math.floor(y*h) == py then
r = 255
g = 0
b = 0
a = 1
end;
else
if math.ceil(x*w-0.5) == px and math.ceil(y*h-0.5) == py then
r = 255
g = 0
b = 0
a = 1
end;
end;

return r,g,b,a
end;[/CODE]

I made a script where I convert the setPixel part into a function but for me it doesn't work in FF3, possibly due to the fractional values thing. Could someone confirm if the following script works in later versions?

[CODE]function prepare()
w,h = OUTPUT_WIDTH, OUTPUT_HEIGHT
end;

function setPixel(x1,y1,w,h,px,py,r,g,b,a)
px2,py2 = math.floor(px*w), math.floor(py*h)
if math.floor(x1*w) == px2 and math.floor(y1*h) == py2 then
end;
return r,g,b,a
end

function get_sample(x, y)
local r = 0
local g = 0
local b = 0
local a = 1

setPixel(x,y,w,h,1,1,255,0,0,1)

return r,g,b,a
end;[/CODE]

If it doesn't work in later versions perhaps my code is broken somehow but it looks as if it should work.

Edit - Maybe the developers could a a new node "Pixel Script" in FF11 which can correctly set pixels and maybe also do html5 canvas style things like drawing lines and rectangles etc with simple code. That would allow for all sorts of interesting scripts to be made.

emme, Sat, 26 Jun 2021 16:44:53 -0400
Slight modification, should work now more or less :)

[CODE]
function prepare()
w,h = OUTPUT_WIDTH, OUTPUT_HEIGHT
end;

function setPixel(x1,y1,w,h,px,py,r,g,b,a)
px2,py2 = math.floor(px*w), math.floor(py*h)
if math.floor(x1*w-0.5) == px2 and math.floor(y1*h-0.5) == py2 then
return r,g,b,a
else
return 0,0,0,1
end;
end

function get_sample(x, y)
local r,b,g,a = setPixel(x,y,w,h,0.5,0.5,255,0,0,1)
return r,g,b,a
end;
[/CODE]

James, Sat, 26 Jun 2021 16:52:23 -0400
Thanks that show me an output. :)

Rachel Duim, Sun, 27 Jun 2021 01:35:29 -0400
If anyone is interested, here is setting a single pixel in FF7 without lua.

Wanted: Curve Script Examples

David Roberson — Sun, 20 Jun 2021 09:34:45 -0400

David Roberson, Mon, 10 May 2021 12:50:00 -0400
I've been searching the forums for examples of Curve Scripts I could use to learn how to do custom curves or curve ops, and so far have come up empty. So, I'm just putting the request out there, if anyone has Curve Scripts they'd be willing to post and share. My initial goal is to create a curve ops type of script that can provide Start, End, Minimum and Maximum sliders for Bezier and composite curves. Eventually, I'll have a day free to just experiment, but I'd like to have those four controls to start with. I can usually find formulas for different curve profiles online, but those examples are welcome too.

James, Sun, 20 Jun 2021 09:34:45 -0400
I just submitted a texture called Techno Panels which uses a custom Curve Operator script which basically takes the input and applies tangent (tan) maths to it. It shows how to use minimum and maximum sliders on a curve.

If your interested the code is:

[CODE]function prepare()
mn = get_slider_input(MINIMUM)
mx = get_slider_input(MAXIMUM)
end;

function get_sample(x, y, t)

a = get_sample_curve(x, y, t, SOURCE)

v = math.min(math.max(math.tan(a), mn),1) * mx

return v
end;[/CODE]

A Not-Quite Arbitrary Distance Mapping

David Roberson — Wed, 20 Jan 2021 20:06:22 -0500

David Roberson, Mon, 18 Jan 2021 22:27:23 -0500
I'm not entirely sure what I've done with this script. I was trying for a script that would do distance mapping of an arbitrary shape, using the function I created for my Spherical Worley Noise. The problem is, it doesn't respond to a binary mask at all. What I got instead was a kind of split distance mapping of the bevel of an arbitrary shape. Whimsically, I turned that into a little heart scrippet, but I'm really curious about how I got the result I did. Here's the code:

[CODE]function prepare()
dtype = get_intslider_input(DISTANCE_TYPE)
p = get_intslider_input(P)
end;

function get_sample(x, y)
local v = get_sample_grayscale(x, y, SOURCE)
local min_dist = 10000
for x = 0, 1 do
for y = 0, 1 do
local dist = distcalc(x, y, v, v)
min_dist = math.min(dist, min_dist) --
end --
end --
-- min_dist = 1.0 - min_dist
v = min_dist

return v, v, v, a
end;

function distcalc(sx,sy,dx,dy)
local dist = 0
if dtype == 1 then
-- Euclidean
dist = math.sqrt((sx - dx)^2 + (sy - dy)^2)
elseif dtype == 2 then
-- Chebyshev
dist = math.max(math.abs(sx - dx), math.abs(sy - dy))
elseif dtype == 3 then
-- Manhattan
dist = (math.abs(sx - dx) + math.abs(sy - dy)) / 1.5
else
-- Minkowski
local pe = 1/p
dist = (math.abs(sx - dx)^p + math.abs(sy - dy)^p)^pe
end
return dist
end;[/CODE]

David Roberson, Mon, 18 Jan 2021 22:59:54 -0500
I suppose the question I should be asking is, how do you reference the x and y components of a sampled image. In the example above, I stuck v in for x and y on a whim and was surprised to get any kind of result. I had tried doing vx, vy = get_sample_grayscale(x, y, Source) but got an error saying dy was a nil value when I provided vy in my function call with vx. I can't recall another script I've seen that features a reference to the x and y from a sample image.

Indigo Ray, Tue, 19 Jan 2021 19:40:29 -0500
David, I also have trouble with scripting in FF, but don't you need to specify a step size for your loops?

The function get sample iterates over x and y (pixels)
When you call get_sample_grayscale(x, y, SOURCE)
it gives you the brightness at each sample point - there's only one output
You can input something other than "x" and "y" to do a transformation

Distance Transform is iterative a.k.a. slow. See our efforts here. But these were not scripting methods.

David Roberson, Wed, 20 Jan 2021 18:05:42 -0500
Indigo, I modeled my script after the API Worley Noise script, so my loops follow its example. I didn't really think about step size, and wonder if you have an example where it is used properly I could see?

Good point about how get_sample iterates over an image. Unfortunately, most examples of distance mapping I've seen (in various scripting languages) iterate over x and y per pixel (which I do) and have access to the x and y coordinates you sample the distance from. I'm not sure I'm getting that part entirely right. I'm still learning about transformations in Lua, so I don't quite know what you mean in your fourth point. Can you elaborate?

Thanks for the link! I'll check it out!

David Roberson, Wed, 20 Jan 2021 19:11:00 -0500
Just to clarify my objectives in this script, I am trying to map distance from the current x,y in my nested loop and the closest pixel of value 1. I'm getting distance from both 0 and 1 with distance mapping in between, centered around the 0.5 value. I'm clearly not identifying those white pixels (or sample points) in an effective way. So, yes, I am getting distance mapping, but in a useless context of an existing bevel.

Please tell me someone gets what I'm obviously missing here?

David Roberson, Wed, 20 Jan 2021 20:06:22 -0500
Okay, looking at it again, the problem I am running into is tied to the get_sample_grayscale() part, which gives me the value (brightness) of the current sample, but my distance calculations are designed to compare the position of the current sample and the nearest "brightest" point. Without a way of getting the coordinates for that I'm not providing the equation what it needs. Worley noise was working inside a cell grid in some way I'm not understanding very well, but which was defined in x and y coordinates.

I still can't figure out how I get the results I'm getting from a bevel, but I'm guessing it's the result of feeding a value between 0 and 1 as if that was a coordinate. I really wish there were more documentation for Lua graphics scripting. I may eventually sort this out, but it's not going to be easy.

Script syntax error on last line/column of script

David Roberson — Mon, 11 Jan 2021 15:21:40 -0500

David Roberson, Sun, 10 Jan 2021 21:08:03 -0500
This has popped up on several scripts I've worked on recently in FF10. Sometimes the code runs, and sometimes it doesn't. In this following example, it doesn't and I'm not sure if there's a real error there I'm not seeing or if this is a bug I should report. If I exclude the truncate() parts, it works, but then I could end up going beyond the 0-1 range with the output. I could live with that and use an inactive Invert to clamp output in the next step, but this function ought to be able to take care of it.

[CODE]function prepare()
contrast = get_slider_input(CONTRAST)
factor = (259 * (contrast + 1)) / (1 * (259 - contrast))
end;

function get_sample(x,y)
local r, g, b, a = get_sample_map(x, y, COLOR)
local nr = truncate(factor * (r - 0.5) + 0.5)
local ng = truncate(factor * (g - 0.5) + 0.5)
local nb = truncate(factor * (b - 0.5) + 0.5)
return nr, ng, nb, a
end;

function truncate(value)
if value < 0 then value = 0
if value > 1 then value = 1
return value
end; [/CODE]

Chris Goldthorpe, Sun, 10 Jan 2021 21:34:56 -0500
I think that you need to terminate the if statements with "end"

if value < 0 then value = 0
end
if value > 1 then value = 1
end

Rachel Duim, Sun, 10 Jan 2021 23:41:49 -0500
Yep, here is more info:
4.3.1 – if then else

David Roberson, Mon, 11 Jan 2021 02:41:01 -0500
Yep. I didn't catch it until I referred back to the manual. Rusty coding habits and inexperience tripped me up! It might have been easier if the log had linked to the problem line, but it was redirecting me to the very end of the script. That's why I seem to get the same error in other scripts. I suppose that qualifies as a "bug" but I suspect FF already knows about it.

Thanks for the feedback, Chris and Rachel!

Chris Goldthorpe, Mon, 11 Jan 2021 11:58:50 -0500
David Roberson, the error can't be detected until the last line because that's the earliest that the compiler can be sure that the syntax is invalid. If you see something like

if value < 0 then value = 0
if value > 1 then value = 1

the second if statement falls within the first then clause and the compiler will be waiting for two "end" statements to follow. It would be nice if the error messages were more informative, i.e. missing end statement.

David Roberson, Mon, 11 Jan 2021 15:21:40 -0500
Good explanation for why the log links to the end of the script in such cases. It would be nice, though, if the syntax check responded first, since that usually does highlight the correct line. (Though, really, these are the things I should be learning to catch myself, so no complaints after thinking it through.)

Thanks again!

Is QuadTree Optimization Practical for use in Map Scripts?

David Roberson — Fri, 08 Jan 2021 15:16:29 -0500

David Roberson, Fri, 08 Jan 2021 15:16:29 -0500
I came across this topic while researching Worley Noise, and thought it'd be great if it helped speed up my Spherical Worley Noise. Of course, the first question to ask, before pulling on this thread and going through all the work trying to implement the idea in Lua, is: Is it practical?

I'm still not sure how the API Worley Noise identifies the closest seed point to any given point, so as yet I don't even have a place to insert a QuadTree. Even so, the idea is there and I can't help but wonder if Lua would spend too much time constructing and utilizing a QuadTree to save a meaningful amount of processing the way I assume it does now, by querying every pixel in the frame. Since the Spherical Worley Noise is at least 10x slower than the Spherical Perlin Noise I made, some kind of optimization is sorely needed!

Multiple Curve Inputs

David Roberson — Fri, 01 Jan 2021 22:03:28 -0500

David Roberson, Fri, 01 Jan 2021 22:03:28 -0500
This was sort of a "what the hell" moment, but I discovered you can add multiple curve inputs to a Map Script. I'm not sure what I'd use it for, except to have one for noise profile and a second one for a contrast profile (though I could continue using the Minimum/Maximum parameters on the profile). It just struck me that I might want a different contrast profile fr om the noise profile. Of course, I still have not figured out what I'm doing, as far as adjusting contrast goes...

It did get me wondering how other people might exploit this, and how they'd manage the script to use it. In my current script, I modify the sample with the noise profile as the last step before I return the sample. I assume I'd have to have two last steps wh ere I modify the sample with the value of the noise profile, then modify it again with the contrast profile before returning the final sample.

I'm curious to see what happens, when I test it...

Edit: Okay, splicing in the extra curve works. Probably redundant and superfluous, but it does work. Of course, all of this was me just playing with a workaround for a mapped contrast adjustment.

Lúa language instructions briefly explained with examples

SpaceRay — Fri, 06 Nov 2020 16:31:07 -0500

SpaceRay, Fri, 06 Nov 2020 16:31:07 -0500
I have just found this searching for another thing and maybe it could be useful perhaps for someone that understand how to use the LÚA scripting, although this is mostly for beginners

I do not understand it, but I leave it here in case it may be helpful

Chad Vandy Lua Language Github

Batch Rendering Wrapper

MachinesInMotion — Sun, 04 Oct 2020 06:02:58 -0400

MachinesInMotion, Tue, 21 May 2013 20:13:29 -0400
Hey Guys!
I threw together a little wrapper program that that runs FF over files directly from the command line (no XML file needed). It's been working for me, and hugely simplifies the process of running FF over a large number of files.

Usage: ffbat filename filter preset
Examples:
ffbat File.png Eyecraft 0
Outputs a copy of File.png with the Eyecraft filter applied(File.png -> File_Filter.png, etc)

ffbat * GlowingText 0
Outputs a copy of every file in the directory with the GlowingText filter applied(File1.png -> File1_Filter.png, etc)

Download Here

Instructions: Extract the zip somewhere and add that location to your path. It should work on its own from there.

Alternatively, download the source and install PIL, then add to your path and run it with ffbat.py file filter preset

Notes:
1) This scans common installation directories to get to the actual executable. If you installed Filter Forge somewhere else (like on a drive that isn't C), you'll have to add your Filter Forge bin directory to your path as well.
2) You need to have the filter in the "My Filters" pane for this to work, so if you are using a library filter, make a copy in My Filters (open the filter editor on it) before running this script.

Python source (Requires PIL to compile):
[CODE]
import glob, os, sys, shutil, subprocess
from PIL import Image
from _winreg import *

print "Usage: ffbat source filtername preset\n"

try:
presetValue = int(sys.argv[3])
except:
print "Error: invalid preset"

#Set up the xml files
xml = open("temp.xml", 'w')
xml.write("""<?xml version="1.0"?>
<Tasks>
<GlobalSettings>
<RenderingOptions>
<UseMultithreading value="true"/>
<Dither value="true"/>
<Progressive value="true"/>
<OptimizeBlurs value="true"/>
<AntiAliasBitmapComponentSources value="false"/>
<Jitter value="0"/>
<TemporaryFilesLocation value=""/>
<RAMUsageLim it value="60"/>
<NormalMapFlipY value="false"/>
</RenderingOptions>

<DefaultFormat value="JPG"/>
<BMP>
<BitDepth value="32"/>
<FlipRowOrder value="false"/>

<JPG>
<Quality value="98"/>
<FullPrecision value="true"/>
</JPG>
<TIF>

<FloatFormat value="false"/>
<IncludeTransparency value="true"/>
<ImageCompression value="LZW"/>
</TIF>
<TGA>
<BitDepth value="32"/>
<IncludeTransparency value="true"/>
<FlipRowOrder value="false"/>
</TGA>
<PNG>
<BitDepth value="16"/>
<IncludeTransparency value="true"/>
<ImageCompression value="BEST"/>
</PNG>
<EXR>
<BitDepth value="32"/>
<IncludeTransparency value="true"/>
<ImageCompression value="PIZ"/>
<FlipRowOrder value="false"/>
</EXR>
<PFM/>

</GlobalSettings>""")
for name in glob.glob(sys.argv[1]):
img = Image.open(name)
width, height = img.size
xml.write("""
<Task>
<Image value="{0}" width="{1}" height="{2}"/>
<Selection value=""/>
<Result path="{3}" format="{4}"/>
<Filter value="{5}"/>
<Preset value="{6}"/>
</Task>""".format(name, width, height, name[0:-4] + "_filter.png", "PNG", sys.argv[2]+".ffxml", sys.argv[3]))
xml.write("\n </Tasks>")
xml.close();
copied = False
#Set up the ffxml
try:
shutil.copyfile(os.getenv("AppData") + "/Filter Forge 3/My Filters/" + sys.argv[2] + ".ffxml", os.getcwd() + "/"+sys.argv[2] + ".ffxml")
copied = True
except:
pass
try:
shutil.copyfile(os.getenv("AppData") + "/Filter Forge 2/My Filters/" + sys.argv[2] + ".ffxml", os.getcwd() + "/"+sys.argv[2] + ".ffxml")
copied = True
except:
pass
try:
shutil.copyfile(os.getenv("AppData") + "/Filter Forge/My Filters/" + sys.argv[2] + ".ffxml", os.getcwd() + "/"+sys.argv[2] + ".ffxml")
copied = True
except:
pass

#Run filter forge at all reasonable locations.
filtered = False
for string in """FFXCmdRenderer-x86-SSE2.exe
"C:\Program Files (x86)\Filter Forge 3\Bin\FFXCmdRenderer-x86-SSE2.exe"
"C:\Program Files\Filter Forge 3\Bin\FFXCmdRenderer-x86-SSE2.exe"
"C:\Program Files (x86)\Filter Forge 2\Bin\FFXCmdRenderer-x86-SSE2.exe"
"C:\Program Files\Filter Forge 2\Bin\FFXCmdRenderer-x86-SSE2.exe"
"C:\Program Files (x86)\Filter Forge\Bin\FFXCmdRenderer-x86-SSE2.exe"
"C:\Program Files\Filter Forge\Bin\FFXCmdRenderer-x86-SSE2.exe"
""".split("\n"):
try:
subprocess.call(string + " temp.xml")
break
except:
pass

os.remove("temp.xml")
if copied:
os.remove(sys.argv[2]+".ffxml")[/CODE]

ThreeDee, Wed, 22 May 2013 06:54:02 -0400
Great! Sounds also perfect for putting video or animation frames through a filter.

ThreeDee, Thu, 23 May 2013 15:01:46 -0400
Hi MachinesInMotion,

I attempted to use this batch tool but it doesn't run and I cannot figure out why.

I have extracted the zip in the folder C:/admin/ffbat and have a bunch of jpeg images in the folder C:/admin/ffbat/images. I am trying to run a filter with the name AnimatedLensFlares, first preset. The filter is in My Filters.

As per the instructions I would gather the command should be:

ffbat\ffbat images\* AnimatedLensFlares 0

With that I get the result:

[CODE]Usage: ffbat source filtername preset

Filter Forge command line renderer, version 3.014.
© 2006-2012 Filter Forge Inc. All rights reserved.
Professional Edition
License Name: ThreeDee.[/CODE]

There are no error messages but nothing gets processed either.

Any ideas?

ThreeDee, Thu, 23 May 2013 15:19:37 -0400
Does this require that the images are .PNG files to work?

ThreeDee, Thu, 23 May 2013 15:36:32 -0400
Ok, I managed to get one specific file to render with the following command:

ffbat\ffbat ffbat\images\flare_MVI_8235_00000.png AnimatedLensFlares 0

ThreeDee, Thu, 23 May 2013 15:43:17 -0400
And finally a number of files with this:

ffbat\ffbat ffbat\images\*.png AnimatedLensFlares 0

(It did not work without ".png")

I also suspect that this will only work if there are no spaces in file and folder names, correct?

ThreeDee, Thu, 23 May 2013 16:04:52 -0400
Works fine with jpegs as well if I put "*.jpg", so it must be related to folder options (whether you show or hide known file extensions).

SpaceRay, Fri, 24 May 2013 14:11:42 -0400
Thanks for sharing it with the forum, and it looks good, but regretably I am bad using command line applications, and try to avoid it, and would like much better any GUI based one and that could work well and be updated to be used with FF 3.0 or FF 4.0 as the others available seen in this other thread here does not work right, at least the windows versions

Also your good Batch rendering wrapper is only for batch rendering one image or a folder with just one filter and one preset.

I have suggested before the following

Quote
WHAT WOULD BE GOOD TO BE ABLE TO DO AS BATCH PROCESSING IN FILTER FORGE For example I have one single image and want to: * be able to select a group of filters ( for example 20 filters) and apply all of them to this same image, also it would be needed to be able to choose which one of the filters preset will be applied, so the result will 20 images. * be able to select a group of filters (for example 5) and a group of presets of these filters (for example 20 filters and choose 3 presets of each filter) and apply them all to this same image, so the result will be 100 images. * be able to select a group of filters and a different amount of presets fr om each filter, perhaps 2 presets fr om filter 1, 4 presets fr om filter 2, 1 preset fr om filter 3, etc. and apply all of them to the same single image so you will have lots of different versions of the same image with different filters and presets. For example I have 40 images in a folder and want to: * be able to apply the same filter and same preset to all the 40 images. Result 40 images * be able to apply a group of filters, with one preset each one, to all the 40 images. Result 40 images * be able to select a group of filters (for example 5) and a group of 3 presets to each, and so you will get as result 600 images. * Be able to select (as above already described) a group of filters and a group of presets and apply all of them to all the 40 images.

Quote

WHAT WOULD BE GOOD TO BE ABLE TO DO AS BATCH PROCESSING IN FILTER FORGE

For example I have one single image and want to:

* be able to select a group of filters ( for example 20 filters) and apply all of them to this same image, also it would be needed to be able to choose which one of the filters preset will be applied, so the result will 20 images.

* be able to select a group of filters (for example 5) and a group of presets of these filters (for example 20 filters and choose 3 presets of each filter) and apply them all to this same image, so the result will be 100 images.

* be able to select a group of filters and a different amount of presets fr om each filter, perhaps 2 presets fr om filter 1, 4 presets fr om filter 2, 1 preset fr om filter 3, etc. and apply all of them to the same single image so you will have lots of different versions of the same image with different filters and presets.

For example I have 40 images in a folder and want to:

* be able to apply the same filter and same preset to all the 40 images. Result 40 images

* be able to apply a group of filters, with one preset each one, to all the 40 images. Result 40 images

* be able to select a group of filters (for example 5) and a group of 3 presets to each, and so you will get as result 600 images.

* Be able to select (as above already described) a group of filters and a group of presets and apply all of them to all the 40 images.

earthbound, Mon, 16 Nov 2015 17:20:48 -0500

Quote
* be able to select a group of filters ( for example 20 filters) and apply all of them to this same image, also it would be needed to be able to choose which one of the filters preset will be applied, so the result will 20 images. . . . * be able to apply the same filter and same preset to all the 40 images. Result 40 images

SpaceRay: Begging your pardon since the last post in this thread approaches three years ago, but while I don't know whether any existing tools accomplish those objectives, I know a tool I wrote and released does (the last I searched for something that can do those things, I didn't find it, so I coded my own).

I've searched the forums and found everything I could about external/batch tools (the last time I searched, well before coding my own solution, I only found two--there are many), and updated the main page of the wiki with them:

http://www.filterforge.com/wiki/index.php/Main_Page#PC

If you know anything I missed, please let me know, or better yet, update the wiki yourself :)

The tool I wrote that accomplishes those things, I announced here: https://www.filterforge.com/forum/read...&TID=13617

With some more work, my tool can do all of those things you want (which I didn't quote all of them).

earthbound, Mon, 16 Nov 2015 22:38:12 -0500
Oh, sheesh--after pouring through the forums and finding so many tools, I listed them all at the wiki *except for the one here, where I announce my wiki edits)*. :blush: Sorry about that! Updating wiki to include this here one :)

SpaceRay, Sun, 04 Oct 2020 06:02:58 -0400

Quote
earthbound wrote: I listed them all at the wiki except for the one here, where I announce my wiki edits).

thanks for including all the available tools in the FF wiki as seen here

The link from the first post is broken and not available

But in the FF Wiki I have seen that there is this link that I think is a new updated for this tool Download it from Github here

In the link page is not clear about version of FF is compatible.
Does it work with FF 9?

Thanks for any possible help

Tottes MegaSwitch

Totte — Sun, 30 Aug 2020 12:50:46 -0400

Totte, Fri, 02 Jul 2010 01:22:32 -0400
OK, here is my MegaSwitch component, in a sample filter to show it off.

StevieJ, Fri, 02 Jul 2010 11:12:07 -0400
I can't look at it yet due to the current V2 problem.....but got me thinking that a script could be made so that each switch could be drop-menu labelled in the controls.....when I get more advanced with scripting of course..... ;) :)

Crapadilla, Sat, 03 Jul 2010 14:57:32 -0400
What's up with the attachment file names?

Totte, Sat, 03 Jul 2010 16:45:53 -0400

Quote
Crapadilla mysteriously wrote: What's up with the attachment file names?

My best guess, a fubar up bug that is broken.

Carl, Sat, 03 Jul 2010 18:47:14 -0400
it only open as xml file for me [ same problem with all these attachments on the site since they changed server ], this happen once before a couple of years ago but for the life of me I can't recall how to get round it, pitty as I would use this :(

Vladimir Golovin, Sun, 04 Jul 2010 02:21:53 -0400

Quote
Crapadilla wrote: What's up with the attachment file names?

We'll fix this soon.

Smacky, Sun, 04 Jul 2010 16:37:09 -0400
Hi all. This is my first post, but i thought I could be of help.

Carl wrote

"it only open as xml file for me [ same problem with all these attachments on the site since they changed server ], this happen once before a couple of years ago but for the life of me I can't recall how to get round it, pitty as I would use this "

My workaround for this issue is to right click on the file link, choose "save target as" and give the file a new name with ffxml as the extension. Once you've downloaded the file, move it into your "My Filters" folder, then restart FF. Seems to work well with most.

Totte, I like the idea, but I can't get your megaswitch filter to work. Produces the same output no matter what the setting is. I've looked at the script, but my programming days are long behind me. Perhaps it is some incompatibility between Mac OS and Windows (which is what I am using).

Cheers,
Smacky

Totte, Sun, 04 Jul 2010 18:15:38 -0400
Did you slide the variation slider? Strange, cause it should pick on out the the maximum inputs set (1-16), where 1 is rather silly as it will be only one to choose from.

Smacky, Sun, 04 Jul 2010 19:31:55 -0400
No, I was definitely using the itemcount slider. Since you mentioned the variation slider I tried an experiment where I changed the value of the V slider to something else, and got some pretty curious results. With variation set to 1, the filter always outputs the #1 input, no matter what itemcount is set at. If I change variation to something else, the output is more or less random, although most of them are still input #1. Very strange, and I would guess some kind of bug in V2.

Smacky

Smacky, Sun, 04 Jul 2010 19:45:31 -0400
Totte.

I had another look at the script and found the problem, I think.In the prepare function there is a line that goes:
"index = math.mod(VARIATION, itemcount)"
I'm not sure what this line is meant to do, but if I change it to:
"index = itemcount"
the filter seems to work as advertised.
Cheers.
Smacky

Totte, Mon, 05 Jul 2010 00:42:14 -0400
Smacky: the filter works as intended.

Itemcount sets how many of the 16 inputs that are currently in use.
using Variation-slider, the output will be psuedo-randomly picked from one of those 16 inputs using the "index = math.mod(VARIATION, itemcount)" line.

The problem really is "no way to explain that" except in - - comments in Lua.

Carl, Mon, 05 Jul 2010 01:24:06 -0400
Thanks Smacky [ and hi ] I'll give that a try :)

Edit; work perfectly thanks again Smacky

Totte, Mon, 05 Jul 2010 01:39:04 -0400
I guess the problem is that you want a controllable switch, not a random switch, which this is. The changes you made Smacky transformed it to a controllable switch, from a random switch (which is what I created). Maybe have a second input saying (controllable/randomized), which will be the best of both worlds...

Posted a new version on 4eyes.

Sphinx., Mon, 05 Jul 2010 01:46:25 -0400
Hi Totte,

I just realized that the input constants, e.g. INPUT_1 contains simple index values.
To get the value of an input constant, write error(INPUT_1) or whatever the name of the input is. In your case there is a perfect relation with the actual index variable in your script, making the big conditional obsolete:

function get_sample(x, y)
return get_sample_map(x, y, index)
end;

should work just fine.

This could have been different, but you obviously first added all the inputs (in correct order) and then itemCount input. That is why their value matches your index.

Smacky, Mon, 05 Jul 2010 11:43:01 -0400
Oops. My apologies. I did think you were demonstrating how to make an oversized switch component, when you were obviously going for something more interesting. My bad. I'll shut up now.

Totte, Mon, 05 Jul 2010 13:37:45 -0400
@Sphinx . They were added, they reordered, as otherwise they came 1, 10,11,12,13,14,15,2,3 etc....
I will check your approach, but I think it will fail as I have reordered them, but a nice idea.

@Smacky: lol - now you got Both.

Sphinx., Mon, 05 Jul 2010 14:23:24 -0400
Ok, perhaps it can add a little randomness then, hehe

SpaceRay, Sat, 28 Jan 2012 19:44:59 -0500
Hello, Please could you explain how this works for a beginner that does not know nothing about scripts ?

I have downloaded it, replaced the big number name for the Megaswitch name and clicking over it is installed in FF 3.0

The problem for me comes when I try to use it, as the slider DOES NOT work and nothing happens when changing from one to another.

Surely I am making something wrong.

Do you need to modify the script to use it ?

How do you select from the 16 sources, just using the selector slider and choosing one of the numbers ?

Morgantao, Sun, 29 Jan 2012 06:25:58 -0500
Spaceray, download the updated version below (from totte's website) and uncheck IsRandomizable. Be sure that Variations is NOT set to 1. That way you can have all 16 outputs with the selector slider.

Other than tat don't ask me how this thing works, as it's WAY over my head.
I would love to see an example of this megaswitch in action in a proper filter, just to try and understand how to implement it, but I guess that's up to the masters of the FF universe to decide if they have the time to do that :D

SpaceRay, Sun, 29 Jan 2012 09:14:48 -0500

Quote
Morgantao wrote: Spaceray, download the updated version below

Thanks very much for the new updated version, I have downloaded it. In wich TotteÂ´s website is this available ? In the one of his profile or other different ?

Quote
Morgantao wrote: uncheck IsRandomizable. Be sure that Variations is NOT set to 1. That way you can have all 16 outputs with the selector slider.

WOW!! Thanks very much for this suggestion and instruction on how to use it, I knew I was doing something wrong and did not work and was because I used variations=1 , after changing the variation to a higher number it works perfectly well selecting the source between the 16 available.

Quote
Morgantao wrote: Other than that don't ask me how this thing works, as it's WAY over my head.

Well, I do NOT need to ask anything more, and really do NOT need to know how it works inside the script to be able to use it.

You do not need to understand and know how electricity works to use it, do you?, you just plug the electrical appliance you want to use in wall socket and use it, donÂ´t care how and why it works :D

And if for you this is WAY over your head, imagine to me !!! ItÂ´s WAY WAY WAY BEYOND over my head 1000 meters :D

For me making and understanding script would be like be able to touch Lava with my naked hands :D

Morgantao, Sun, 29 Jan 2012 17:35:43 -0500
In that case for me it's like putting out a campfire with my tongue :D

SpaceRay, Sat, 11 Aug 2012 15:23:18 -0400

Quote
Morgantao wrote: Spaceray, download the updated version below (from totte's website) and uncheck IsRandomizable. Be sure that Variations is NOT set to 1. That way you can have all 16 outputs with the selector slider.

Please, is there some good way that Variation is NOT set to 1 when downloading the filter.

The only way I have found is to make the presets have a different variation number but do not know if this is a good way or there can be another one.

Thanks again to Totte for this MegaSwitch

Morgantao, Mon, 13 Aug 2012 14:18:24 -0400
SR, you can always edit the ffxml file and change the variation of the default preset

Totte, Sat, 18 Aug 2012 02:10:32 -0400
Just saw this discussion, hope you having fun with it.

SpaceRay, Sat, 18 Aug 2012 03:12:27 -0400

Quote
The only way I have found is to make the presets have a different variation number but do not know if this is a good way or there can be another one.

I have seen that this works right and as always that is loaded a filter it loads the first (or the last default filter) filter preset it will always move the variation to the one on the preset and be higher than one, so there is no more problem.

Quote
Morgantao SR, you can always edit the ffxml file and change the variation of the default preset

This would be IF you could not do it inside FF, but you can do it and update any preset (that is not a factory preset) with the right values of variations, so there is no problem.

Quote
Totte: Just saw this discussion, hope you having fun with it.

Yes, thanks to you there is the possible thing to have a 16 switch instead of the normal 12 one

Thanks again to Totte for this MegaSwitch

Totte, Sat, 18 Aug 2012 03:21:32 -0400
You can make that 100 if you just spend more time editing the script

SpaceRay, Sat, 18 Aug 2012 03:21:51 -0400
I have made a great, interesting and useful discovery in this filter

YOU CAN HAVE AS MANY SWITCHS AS YOU WANT WITH THIS SCRIPT AND NOT ONLY 16

I was wondering if it would be possible to make a 20 switchs megaswitch instead of the 16 available now, and I was going to make this request when I have seen that he Map script component has an Input Editor on the settings tab and there you can configure any amount of switchs AND also customize other possible connections required if needed for this component.

So now this filter has risen much itÂ´s value and is even better than what I thought.

Thanks again to Totte for this MegaSwitch

Totte, Sat, 18 Aug 2012 03:22:53 -0400
As I said, just add more code.... more inputs... and your done

Skybase, Sat, 18 Aug 2012 03:25:16 -0400
Yes one of these days there will be a component with 1000 inputs.

SpaceRay, Sat, 18 Aug 2012 03:34:08 -0400
Thanks Totte, we wrote the post both at exactly the same time :D but yours when first than mine.

Quote
Totte wrote: As I said, just add more code.... more inputs... and your done

What is very good on this is that you do not need to modify the inner code of the script and do not have to modify the script itself, it is very easily done with the "Input editor" available to add any more inputs you want and configure them as you want without any problem, which is great.

Quote
Skybase wrote: Yes one of these days there will be a component with 1000 inputs.

:D
Well considering that FF does NOT make a selection of the components that are behind the switch and ALL of them are included in the results components (wich is a very bad thing) it would be impossible to make this AND keep it working right and being fast and usable :D

SpaceRay, Mon, 15 Jun 2015 00:40:36 -0400
This is really a missing gem from the forum, and it deserves to be known more, as this is very useful, interesting and good way to go over the limitation of filter forge and that you can not have more than 12 elements in the switch, with this great megawitch from Totte, totally recommended if you ever need to have more than 12 elements for a switch

SpaceRay, Tue, 16 Apr 2019 21:51:00 -0400
I bump this again as the FF 8 switch is still having the limit and this switch is much better with up to 16 elements by default but it seems that it can be upgraded with more elements

Quote
Totte wrote: You can make that 100 if you just spend more time editing the script

BUT the problem is that when you do it, then you get an error message from the IntSlider as seen here

Quote
The Incoming value range (1...20) exceeds the maximum range of this input (2...17) To fix this, lower the amount

So is there then a problem that IntSlider does NOT allow more a higher amount of 17 ??? Or I am missing something ?

HERE BELOW I ATTACH THE MODIFIED VERSION

As you can see if you go over 16 values it does nothing, although the script is modified. IF you can explain it would be much appreciated.

Thanks for any help

Here is what I have done to modify the filter

I have been wondering how to do this and until know I have not known how to do it, and now I found how to do it

Just add

elseif ( index ==17) then inp=INPUT_17
elseif ( index ==18) then inp=INPUT_18
elseif ( index ==19) then inp=INPUT_19
....

and then go to the Input Editor and click on new input and add as many additional inputs as you have added to the script

you need to add a name and then use the INPUT_17 (being 17 the corresponding number of each new input created)

you can put the name as you want and do not have to be Input and the number

then go to ItemCount and Selector components and increase the number of inputs to the total amount

THE BELOW FILTER IS FOR FF 8.0 DOES NOT WORK ABOVE 16 inputs

Rachel Duim, Tue, 16 Apr 2019 23:38:51 -0400
SpaceRay, this works in FF7 and FF8. I have taken out the randomize and item count, something is not right about randomization (which should work in the prepare section but is not working). This has 20 inputs to the switch. The problem you were having was probably in the input editor for the integers numbers. A side note, I could not edit this on the Mac, editing the script constantly crashed in FF7 and FF8 when trying to change the range of integer numbers in the input editor.

SpaceRay, Wed, 17 Apr 2019 00:16:27 -0400

Quote
rachelduim wrote: This has 20 inputs to the switch. The problem you were having was probably in the input editor for the integers numbers.

Great, Thanks very much for fixing it for 20 inputs and it works right as you have done it

BUT if I try to add any additional input I get the SAME error as before but now the limit is 21 instead of 17

Quote
The Incoming value range (1...21) exceeds the maximum range of this input (2...21) To fix this, lower the amount

Rachel Duim, Wed, 17 Apr 2019 00:42:46 -0400
Ok, your issue is probably this, click the Map Script. Go to the Input Editor. Scroll down to Numeric Inputs and highlight Selector. Then change the Maximum Value to whatever you need, then click OK. I'm hoping this is the part you missed.

totte, Wed, 17 Apr 2019 01:16:44 -0400
Cool this old little baby still is popular;-)

Rachel Duim, Wed, 17 Apr 2019 21:53:50 -0400
A greatly simplified version, the ELSEIF's are not needed. Works in FF7 & FF8.

SpaceRay, Sun, 30 Aug 2020 12:50:46 -0400

Quote
rachelduim wrote: A greatly simplified version, the ELSEIF's are not needed.

Thanks very much for making this much simplified version

it works correctly also on FF 9

will see how it works

Be able to make a Blend Modes control WITH names with LUA scripting?

SpaceRay — Mon, 04 May 2020 08:35:10 -0400

SpaceRay, Fri, 17 Apr 2020 04:39:56 -0400
Sorry if this may be a silly and mistaken idea, as I do not know about scripting or how FF handles the showing of names on the Settings panel

It has been already 10 years, and there is still no way to show the names of the blend modes in the settings control, and it can only be shown correctly each selected blend mode name inside the remapper inside the filter.

So as there has not been anyone that have built any possible solution for this using FF components (In a simple and easy way), I wonder if it could be possible to show the names that appear in the remapper in the settings controls of the filter using LUA scripting

Thanks for any possible help and sorry again if this is a bad and wrong idea

I made for FF 4.0 this filter snippet for is not easy to setup and it clutters the settings controls

Blend Modes WITH names

Skybase, Fri, 17 Apr 2020 22:18:56 -0400
This isn't doable.

There's no dynamic way to control text in the settings tab.

Beat, Sun, 03 May 2020 19:28:12 -0400

Quote
Skybase wrote :This isn't doable. There's no dynamic way to control text in the settings tab.

Is this inherently impossible, or just not possible with the current FF application?
I mean, would the architecture of FF, with an adaption by the makers, be able to comply to the request of SpaceRay?
I would very much welcome it.

Skybase, Mon, 04 May 2020 01:55:06 -0400

Quote
Is this inherently impossible, or just not possible with the current FF application? I mean, would the architecture of FF, with an adaption by the makers, be able to comply to the request of SpaceRay?

Ah just the current program won't let that happen.

I generally think this is better implemented through drop down menus instead.

Dynamically changing names of technically what's understood to be static elements i.e. text in a control box, seems like calling for trouble. I can easily abuse this to confuse the crap out of you all lol. Unless you really can tell that the element is supposed to change based on variables then it'd make better sense.

But why do that when we rather have practical things like drop down menus?

SpaceRay, Mon, 04 May 2020 03:34:12 -0400

Quote
Skybase wrote: But why do that when we rather have practical things like drop down menus?

I totally agree with you and it really true that the best way would be surely to have drop down menu on the settings and would be the best way to do it but...

Quote
Skybase wrote: I generally think this is better implemented through drop down menus instead.

...I started this thread because Vladimir has already put that it was very difficult or not possible to make drop down menu in FF as it seems is very difficult and hard with the current way it is programmed

Quote
Vladimir Golovin wrote in 2006 already 14 years ago!!: Dropdown (a.k.a List Control) was put on indefinite hold because it was going to take too long to implement (it requires a serious redesign of Filter Forge's infrastructure for control components).

Dropdown list

SO as said, I agree with you and agree also that it would be the best way but it has not been possible in 14 YEARS, so I do not think they will do it this way and this is why I suggested this possible alternative

IF WITH LUA IS NOT POSSIBLE

Quote
SpaceRay wrote: If the dropdown is the problem, is not really needed and surely there could be other possible alternative way, for example just use a text slot as it happens already in the remapper inside the filter where it is shown the name of the selected blend mode, so it would appear the name in the settings control instead of a number

Beat, Mon, 04 May 2020 08:35:10 -0400
Definitely, native dropdown menus would be BEST.

Quote
Vladimir Golovin wrote in 2006 already 14 years ago!!: Dropdown (a.k.a List Control) was put on indefinite hold because it was going to take too long to implement (it requires a serious redesign of Filter Forge's infrastructure for control components).

Quote
SpaceRay wrote: If the dropdown is the problem, is not really needed and surely there could be other possible alternative way, for example just use a text slot as it happens already in the remapper inside the filter where it is shown the name of the selected blend mode, so it would appear the name in the settings control instead of a number

I am sure that Vladimir is right, but as SpaceRay points out, it seems to be possible inside the editor, with the remapping. I am curious what makes it so hard to do the same in the Settings?

Maybe a bit off topic, but it would be nice if all the 19 Blend Modes used by PS, would be available in the Blend Component. I really miss Exclusion and Subtract. I know I can make them with RGBMath (at least Subtract), but I feel that they should all be together in the Blend Component.

Is Possible to use LUA script found on internet inside FF Map script?

SpaceRay — Sun, 12 Apr 2020 18:09:28 -0400

SpaceRay, Sun, 12 Apr 2020 02:33:19 -0400
First I want to say that I am very sorry if I am saying something wrong, or silly things, or I am mixing things and I am mistaken about this

I have though that if I do not know how to use LUA, there are surely some other that do know well how to use it and that they share their scripts to be used by others and could maybe be used with FF in some way

1 - what I do not know is what kind of LUA scripts would be compatible with FF and work inside for a filter, as I have no idea how the FF LUA works in comparison with the other LUA scripts.

2 - As FF only is able to use just one Scrip on each map script, so could you combine different map scripts to work together?

3 - How do you know how to configure the inputs (in the FF input editor) that the script would need or that are needed from a LUA script?

4-How similar or different is FF LUA to the. other LUA script available on internet?

5- Is not possible to use on FF if the LUA scripts is used as a command-line program?

Maybe I should leave it and not do this at all if I do not have any LUA scripting knowledge

For example

FLOOD FILL LUA SCRIPT

I have found this Flood Fill LUA script

https://github.com/Yonaba/FloodFill/bl...r/main.lua

but I have seen that it uses more than one script because if I copy the Main file to FF it tells me that that there are some missing things and is because these missing things are other additional scripts that are separate. I wonder if it would be possible to put all the parts in just one script or combine multiple Map scripts to make it work?

when looking at thw whole project you can find the other missing parts

This is the master main file of the FloodFill

https://github.com/Yonaba/FloodFill

I have copied to a FF filter the main file but as said it has missing things

Sphinx., Sun, 12 Apr 2020 09:26:43 -0400
This kind algorithm requires a bitmap. It is not possible to create bitmap based scripts in Filter Forge.

When looking at other lua scripts, you always have to think about the procedural sampling approach in FF - will it fit into that? If you see something that process maps or tables (discrete processing), it is likely not to work in FF.

That said - you CAN use other libraries etc, but unless you copy it all into the same script block, you have to refer the external lua files on your hard drive, and that will only work in unsafe mode, and it is not easy debugging these setups. It is also likely to become very slow due to the way FF initialize in every rendering block.

SpaceRay, Sun, 12 Apr 2020 18:09:28 -0400
Thanks very much for your answer and help and is valuable

Quote
Sphinx. wrote: This kind algorithm requires a bitmap. It is not possible to create bitmap based scripts in Filter Forge

Yes, is right, I already knew that this flood fill would need a bitmap grid as source image that would be filled but then I continue reading and discover something I did not know

Quote
Sphinx. wrote: It is not possible to create bitmap based scripts in Filter Forge

OH! I did not know that you can not use any bitmap based thing in the script, and is very good to know it, so then it limits much what can be done with a FF LUA script as many of the scripts available uses a bitmap in the script as they are graphical scripts

Now I understand why the FF hyperbolic script does not have any color control or image source inside the script

From your answer I also understand and know even more why the scripting is not used more and is more difficult to use it

Thanks again for explaining it

Why is not used much more the LUA scripting to make filters?

SpaceRay — Fri, 03 Apr 2020 03:36:17 -0400

SpaceRay, Mon, 30 Mar 2020 03:33:09 -0400
I have seen that there are really just a few filters that use scripting and as seen on the scripting part of the forum, there has been very few post about this topic in seven years.

what do you think about why is not used more with FF?

Is it really so hard and difficult to be able to use the LUA to get things that are not possible with FF components?

Sorry much that I do not have knowledge about coding and scripting

It is supposed to be a great powerful and useful tool to do things, but in all these years is not really used much, even the FF company employees or Vladimir has not made any filters with scripting as far as I know.

in 2010 started this thread

Script-component-based filter ideas

but the all these things has not been done in FF as far as I know

How many of the FF users know really how to use the LUA scripting?

Sphinx., Mon, 30 Mar 2020 07:04:38 -0400
I can think of many reasons.

1. No need to script: The discussion you refer to is back from the V1 days. No math components, no bomber, no loop, no shapes, no transforms (except a weird version of Offset)... scripting would make so many things easier. But now FF is quite versatile and many new native and advanced components has added since scripting.

2. Too advanced for the major user segment.

3. Performance issues (first scripting was slow and buggy, then it became fast and buggy, now it is slow and stable). Personally this has been very frustrating to me and put an effective stop to my scripting projects. It doesn't pay to fix and I can understand that.

4. No sharing/submissions: I think there are many scripts "out there", but they just don't make it to the forums/library for some reason (incentives, relevance, unfinished state etc). Also "unsafe" scripts can't be submitted

AndrewA1988, Mon, 30 Mar 2020 23:07:11 -0400
1. Not enough builtin functions.

2. Because of #1, it's more difficult to find examples that are 1) easily transferable to FF and 2) don't require you to re-invent the wheel. This makes the learning curve probably higher than it has to be.

3. FF probably doesn't have the user base for it right now. Someone who knows how to script is probably using a different program (Substance Designer, etc.).

Ramlyn, Tue, 31 Mar 2020 02:01:04 -0400
I use scripting a lot in my filters. I guess about 1/5 of my filters have some original component. But, as you can easily see, they are very simple components. For example, what I do the most is having a customized switch, to increase the number of choices.

As Sphinx and AndrewA1988 said, many people have no idea about how to use Lua. Me too. Even in my free time I'm trying to learn, I'm still far from making innovative components.

There are already components doing many of the things that are possible to do. Then it is difficult to think about some script doing something completely new.

Anyway......... it would be nice to make someway a library of scripting. And trying to make new components.
There are sometimes ideas that have never been developed by Filter Forge. Most of the cases for obvious reasons: they would be simply a variation of an already existing component. But they would be useful to develop some particular filter. A typical example is the non overlapping particle for the bomber. I guess, for doing it, it would make necessary to completely re-program the bomber, creating someway a "Bomber ++". We already have two bombers and making a third may not have much sense. But in some filter it would be nice to have it.

SpaceRay, Fri, 03 Apr 2020 03:36:17 -0400
Thanks really very much for all the comments, they are good and useful to understand more about this topic

Quote
Sphinx. wrote: 2. Too advanced for the major user segment.

Quote
AndrewA1988 wrote: 3. FF probably doesn't have the user base for it right now. Someone who knows how to script is probably using a different program (Substance Designer, etc.).

Quote
Ramlyn wrote: As Sphinx and AndrewA1988 said, many people have no idea about how to use Lua. Me too. Even in my free time I'm trying to learn, I'm still far from making innovative components.

This is what I think more as usually many people that are in design and art, does not like to learn scripting because they are visual persons that are much more tending to use visual scripting with nodes instead with code lines, like for example myself.

And for people that are using scripting I think they use other kind of software that has more possibilities like for example Processing.org or Phyton, or others.

Quote
Ramlyn wrote: Anyway......... it would be nice to make someway a library of scripting. And trying to make new components.

YES, This is what I have been thinking, that as it is available the scripting, it could be used for making new components that could do things that are not possible (or difficult or complex) to do with FF components, and do new things, as FF has a great potential, but of course is needed much knowledge and time to learn it and know what is possible and how to do it.

Projective Transform (Four point transform)

Sphinx. — Wed, 19 Feb 2020 04:40:24 -0500

Sphinx., Mon, 05 Jul 2010 07:10:53 -0400
I translated some parts of a graphics library I'm co-developer on, so now we have a true four point projective transformation, and it supports both ways (i.e. you can transform "back" by using opposite setting for Inverse parameter).

I added some additional parameters, Percentage, Clip X and Clip Y. Percentage works similar to Percentage in the other transformations.

I will publish it eventually, but I post it here first to get some feedback on the design. Also I'm unsure about license compatibility when submitting to the online library.

Sphinx., Mon, 05 Jul 2010 07:15:05 -0400
Here is a moderate example with clipped x and y:

Sphinx., Mon, 05 Jul 2010 07:15:44 -0400
And here is a more extreme unclipped example:

ThreeDee, Mon, 05 Jul 2010 08:27:58 -0400
Sphinx,

This is awesome to say the least! It will open a whole world of possibilities in mapping images onto 3D surfaces.

As to the interface, it is workable as it is. The 'inverse' checkbox should work the other way though, IMO. Right now it is checked when you do the original transform, and unchecked for inverse transform.

For a possible improvement, it would be helpful to be able to show just a tranformed grid overlayed on the input image. This would be particularly useful for alignment when removing perspective with inverse transformation.

TD

ThreeDee, Mon, 05 Jul 2010 08:36:18 -0400
Oh, and could the clip function have some sort of invert choice as well? With some settings, the transformed image splits and goes through the opposeite edges of the image. (Or is this the way it is supposed to go?)

Sphinx., Mon, 05 Jul 2010 09:20:10 -0400

Quote
The 'inverse' checkbox should work the other way though, IMO. Right now it is checked when you do the original transform, and unchecked for inverse transform.

I guess that makes sense from how you see it visually. Theoretically or codewise it is the other way around though (i.e. it uses the inverse matrix when Inverse is checked). Maybe there is a better term for that input.

Quote
could the clip function have some sort of invert choice as well? With some settings, the transformed image splits and goes through the opposeite edges of the image. (Or is this the way it is supposed to go?)

Well, the thing is that for correct output the transform only support convex quadrilateral polygons. I was not sure how to handle this and decided to leave it as is - any ideas on what to with concave settings?

Sphinx., Mon, 05 Jul 2010 09:49:49 -0400
Hmm, I could constrain the points so that you can't make a concave polygon.. the sliders would then stop having any effect if you make a concave polygon..

ThreeDee, Mon, 05 Jul 2010 11:06:40 -0400

Quote
Sphinx. wrote: I guess that makes sense from how you see it visually. Theoretically or codewise it is the other way around though (i.e. it uses the inverse matrix when Inverse is checked). Maybe there is a better term for that input.

You could call it 'Inverse Transform' and switch the checkbox polarity.

Quote
Sphinx. wrote: Well, the thing is that for correct output the transform only support convex quadrilateral polygons. I was not sure how to handle this and decided to leave it as is - any ideas on what to with concave settings? Hmm, I could constrain the points so that you can't make a concave polygon.. the sliders would then stop having any effect if you make a concave polygon..

I see. Then contraining the points might be a good idea. It is not all that important, more of a cosmetic handling. Now that we've gone there: should there be some way of indicating when the points are clipped? Such as a red exclamation point at the corner (which you can turn off)? That's just a thought. In the big picture, it's irrelevant for the basic function of the filter, which is a fantastic piece of work.

SpaceRay, Wed, 05 Sep 2012 23:29:22 -0400

Quote
ThreeDee This is awesome to say the least! It will open a whole world of possibilities in mapping images onto 3D surfaces.

I am sorry to ask, but do not know how this would help mapping images onto 3D surfaces unless you mean doing this inside FF in some way, although FF does not have 3D surfaces.
Sorry if I am telling perhaps silly things here.

As Sphinx has put already, this is related to this other thread Quadrilateral Challenge by uberzev

ThreeDee, Thu, 06 Sep 2012 05:23:07 -0400

Quote
SpaceRay wrote: I am sorry to ask, but do not know how this would help mapping images onto 3D surfaces unless you mean doing this inside FF in some way, although FF does not have 3D surfaces.

Yes, I mean internally in FF. For instance, if you were to make a script that calculated the corner points of the three visible faces of a 3D rotating cube, you could use this script to render the input image on each face.

You could pretty much make any rectanglarly faceted filled 3D shape with the input image on each face with it.

Which reminds me that it would really be a good idea to write a script that calculates the transformation of any point in 3D space.

In fact, 3D transformation may already be included in one of the more advanced scripts from Sphinx. Or in Raytracing by Egret. Haven't dug into them that deep.

(By 3D transformation I mean rotation around X, Y and Z-axis.)

CFandM, Thu, 06 Sep 2012 07:51:28 -0400
Great Work Sphinx.. :pimp: :beer:

AndrewA1988, Wed, 12 Feb 2020 02:51:13 -0500
Does anyone still have this snippet? Attachment goes to a "not found" page.

Sphinx., Sun, 16 Feb 2020 08:24:49 -0500
I'm not sure why the older forum attachments are not working anymore (GMM? Vlad?).

Here it is

AndrewA1988, Tue, 18 Feb 2020 21:38:17 -0500
Thanks Sphinx!

GMM, Wed, 19 Feb 2020 04:40:24 -0500

Quote
Sphinx. wrote: not sure why the older forum attachments are not working anymore

We restored this particular attachment. If you any other older attachment doesn't show up, let me know.

Noisy Fractal Rendering

Sphinx. — Sun, 31 Mar 2019 11:52:36 -0400

Sphinx., Thu, 10 Jun 2010 03:24:49 -0400
I'm currently working on some fractal scripts which produce extreme range output (much like strange attractor fractals) which is clamped to either 0 or 1, and the real "magic" takes place in the super-sampling process: here the actual visible gray tones are produced.

My problem is that I can't do tone mapping because the mapped colors are either from the 0 or 1 area in the color gradient (because the super-sampling that produces intermediate grays is taking place post everything).

So how would you get around this problem? By writing a custom super-sampling step?
The only semi build in way I can figure out is to use a blur at very low radius and then enable anti-aliasing for bitmap based components, but AFAIK this is not a setting stored in the filter.

Perhaps we need a new result mode: Gradient Mapped Result, much like how the elevation gradient works, but the mapping is done post super-sampling.

Here is an output example, first half shows super-sampled output, second half shows direct output:

Crapadilla, Thu, 10 Jun 2010 04:02:35 -0400
Wow! :eek: :)

earthbound, Sat, 30 Mar 2019 23:36:55 -0400
Is this script published anywhere? That output is pretty dang cool.

Sphinxmorpher, Sun, 31 Mar 2019 11:52:36 -0400
I looked for it - I think I found it, but the filter doesn't render anymore (script error) :-/ I'll post it here if I can manage to fix it.

Scripting question and maybe assistance :)

Grimbly — Thu, 29 Nov 2018 21:21:47 -0500

Grimbly, Thu, 29 Nov 2018 21:21:47 -0500
I would like to make a Map Script component that outputs a color range based on the amount of content in an image. I'm going to be batch processing a few thousand images. Each image has varying amounts of content and transparency. I'm not sure how to script such a thing or whether I should be trying to total the amount of blank space vs the amount of content in the image.

Any advice, sample scripts, or existing similar scripts would be very helpful.

Simple additon

DigitalMirrors — Mon, 15 Oct 2018 18:55:10 -0400

DigitalMirrors, Mon, 15 Oct 2018 13:49:37 -0400
Could someone help me with how to handle simple addition. I found a post on using RGB math and could not get it to work as I wanted.

I'd like to be able to add numbers and use them on repetitions. So say you take two gradients. Say I have the first one set to 6 repetitions and I wanted the second gradient to have 1 more repetitions making it 7.

This seems like it should be simple but I'm not getting it can anyone help?

emme, Mon, 15 Oct 2018 16:56:49 -0400
Two ways you can do this. You can check "use remapping" in the control settings and add an offset of 1 in the remapper.

Alternatively you can use an RGB math node to add the offset, but you need to also remap the value going into the math node correctly. For example, if you have an IntSlider outputting values 1-5, you need to remap to 0-4 in HDR values.

You can check out the remapping in this filter.

DigitalMirrors, Mon, 15 Oct 2018 17:11:00 -0400
Thank you! I appreciate the help. I'd like to understand the different ways to do this.

On the RGB math example how would I increase the increment from 1 to 2 in source B?

Also, is there a way to do this with the math script? I've read those as well but cannot figure it out.

emme, Mon, 15 Oct 2018 18:01:54 -0400
You can check HDR in the Source B color picker and set any value for the increment. I suggest reading the HDR Colors page in the manual to learn more. You can also control the increment with another IntSlider. (added in the example)

Sure, using a script would work too. I've added one in the example that outputs the base value in the red channel and value + increment in the green channel.

DigitalMirrors, Mon, 15 Oct 2018 18:04:30 -0400
Wow, 8) thank you again emme. I will go through this today.

Rachel Duim, Mon, 15 Oct 2018 18:17:39 -0400
Here is another way to do it using Free Gradient with division instead of the Profile Gradient with addition. A little more complicated but more flexible.

emme, Mon, 15 Oct 2018 18:53:22 -0400
Yes, my examples were more about addition and less about gradients :)

I agree, generally better to use free gradient instead.

DigitalMirrors, Mon, 15 Oct 2018 18:55:10 -0400
I really appreciate the input from both of you. It's been very helpful. I'm having fun playing with your examples.

Thanks!

Scripting help

Ramlyn — Wed, 04 Jul 2018 01:17:01 -0400

Ramlyn, Sat, 30 Jun 2018 22:41:26 -0400
I have a filter that one of our members made and that contains a Map Script. Unfortunately, after the last updates, because of the new FF settings, this Map Script doesn't work anymore. Does anybody know how to correct the error? I tried to contact the author, but he doesn't answer or come in the forum anymore.

Indigo Ray, Sun, 01 Jul 2018 11:54:34 -0400
See Here.

The solution was simple: Changing the name of some of the variables. Let me know if you find any other filters with the same problem.

GMM, Mon, 02 Jul 2018 06:50:27 -0400
Also see this and this.

FF7 no longer allows you to override system variables like MODE. We can't submit an update in the author's behalf, and inujima hasn't responded to our emails. It can be easily fixed by renaming the variables.

Ramlyn, Wed, 04 Jul 2018 00:57:56 -0400
Indigo Ray and GMM, thank you very much! :D :D :D

Before I tried to modify it, but I probably did something wrong.

Ramlyn, Wed, 04 Jul 2018 01:17:01 -0400
Indigo Ray. I updated some of my filters containing this map script too, adding credits to you. ;)

The Pursuit for Paths

ThreeDee — Tue, 01 May 2018 02:33:31 -0400

ThreeDee, Sat, 07 Apr 2012 13:50:54 -0400
Fo the longest time, I've been wondering how to realize something resembling freehand paths in FF. Today I made my first real breakthrough in this. This simple little picture has a story to tell.

ThreeDee, Sat, 07 Apr 2012 13:59:23 -0400
The story is that it is "drawn" from two (random) noise gradient inputs which give the X and Y coordinates OVER TIME for a single point.

With the help little script that I put together, the location of this point over time is drawn all the same time onto the canvas.

I will describe this in more detail in the near future.

SpaceRay, Sat, 07 Apr 2012 14:42:16 -0400
WOW!! This could be very interesting and and could be something very good for FF to have freehand paths!!

Nice example you have put and amazing that this comes from two noise gradients inputs with a script and... the other things you have used

I will wait for your more detailed description

Put a note, do not disturb, GENIUS working :D

Morgantao, Sat, 07 Apr 2012 17:26:22 -0400
I love how it's a closed path, and not just a random squigly line going nowhere.
Genius at work indeed! 8)

ThreeDee, Sun, 08 Apr 2012 04:13:23 -0400
So here's how it works, in more detail:

There are three inputs to the script, grayscale maps for X and Y and an integer slider for number of points.

The grayscale maps are simply two noise gradients.

ThreeDee, Sun, 08 Apr 2012 04:16:54 -0400
The script tells how many samples to take from left to right on these gradients.

ThreeDee, Sun, 08 Apr 2012 04:18:36 -0400
And converts the gray values at these points to X and Y positions.

ThreeDee, Sun, 08 Apr 2012 04:19:53 -0400
With ten points that looks like random points, but as you increase the number of points, you start getting a line. Here is the same with 128 points.

ThreeDee, Sun, 08 Apr 2012 04:20:36 -0400
And finally, we connect the dots:

ThreeDee, Sun, 08 Apr 2012 04:23:06 -0400
When you change the variation, you get a different x and y points and a different resulting line.

ThreeDee, Sun, 08 Apr 2012 04:24:29 -0400
When you scale up the noise, you get simpler shapes.

ThreeDee, Sun, 08 Apr 2012 04:27:36 -0400
And smaller scale noise gives you more scribbles for your money.

SpaceRay, Sun, 08 Apr 2012 04:30:21 -0400
WOW!! Wonderful results!! Like very much how you have been able to make the scribbles from LOTS of points multiplied to form lines. Great work.

ThreeDee, Sun, 08 Apr 2012 04:32:06 -0400
Different types of noise inputs give different results. Block noise gives you more angular lines.

ThreeDee, Sun, 08 Apr 2012 04:49:26 -0400
A contrasty cells noise tends towards the edges...

Due to the complexity of the line, I had to use 1000 points here, so it is pretty slow. Nevertheless, quite a charming little scribble.

ThreeDee, Sun, 08 Apr 2012 04:52:57 -0400
But wait, now the fun really starts: Two sine curves fed in as inputs gives you...

ThreeDee, Sun, 08 Apr 2012 04:59:23 -0400
Did you guess what two sine curves blended together would make?

ThreeDee, Sun, 08 Apr 2012 05:07:21 -0400
Or three?

ThreeDee, Sun, 08 Apr 2012 05:11:37 -0400
Just add elevation gradient:

ThreeDee, Sun, 08 Apr 2012 05:17:55 -0400
Never gonna look at a sine curve the same way again.

ThreeDee, Sun, 08 Apr 2012 05:49:17 -0400
Thought you would never ask. Yes, you can use it for surface filters as well, although render times rapidly get into the CPU- and patience-testing ranges.

xirja, Sun, 08 Apr 2012 08:12:32 -0400
2d parametric curves in FF, an excellent breakthrough! Does it use a bomber and how are the points connected? Is it possible to get variable line thickness as a function (x^2+y^2)^(1/2) like this:

http://www.youtube.com/watch?v=Md1q2oShx8A

ThreeDee, Sun, 08 Apr 2012 09:05:26 -0400

Quote
Does it use a bomber and how are the points connected?

No, it is a script that draws the points and the lines in between. Currently the lines are straight lines.

Quote
Is it possible to get variable line thickness as a function (x^2+y^2)^(1/2) like this:

Yes, this can be easily included in the script.

ThreeDee, Sun, 08 Apr 2012 09:10:40 -0400
Here's the line drawing scrippet.

The nice thing is that the script calculates the distance from the line and end points, so you can vary the line thickness by just thresholding the output.

ThreeDee, Sun, 08 Apr 2012 09:52:32 -0400

Quote
Is it possible to get variable line thickness as a function (x^2+y^2)^(1/2)

Actually, no need to put it in the script, you can just threshhold it with a circular gradient:

ThreeDee, Sun, 08 Apr 2012 11:27:34 -0400
Heh, the next step was easier than I expected...

Not real fast in rendering, but it's the real thing.

ThreeDee, Sun, 08 Apr 2012 11:47:18 -0400
Okay, so what to do with all this?

Inputting actual X and Y values is quite tedious, for to make the above Bezier curve, you have to use 8 inputs, x and y values for all four points defining the curve. So that makes 8 sliders

It seems the more sensible approach is to use the built-in noises as sources for x and y information.

Or to program the values mathematically for such things as a fractal tree. Or for wireframed 3D objects. Or road maps between cities. Or tessalation patterns.

Now off to figuring out how to filled those closed shapes...

ThreeDee, Sun, 08 Apr 2012 12:00:26 -0400
Oh yeah, one more thing. The script output actually looks like the picture below. It gives the distance from the nearest line. Then it can be put through a threshold or other things to give the desired line weight etc.

ThreeDee, Sun, 08 Apr 2012 13:38:47 -0400
It wasn't too hard getting the fills. But now it is slow as molasses with both the line and the fill, so needs some optimization.

lipebianc, Sun, 08 Apr 2012 13:51:23 -0400
This is awesome, ThreeDee!!!!
You're raising the bar in the filter construction territory! :ff:
Thank you for your efforts, congratulations and respect for your achievement!

xirja, Sun, 08 Apr 2012 15:01:49 -0400
Totally! Splines AND filling, oh yeah! Looking forward to this one! Also its nice to have opacity on the filling so that you can get gradations on the overlaps, such as:

SpaceRay, Sun, 08 Apr 2012 15:37:51 -0400

Quote
lipebianc wrote: This is awesome, ThreeDee!!!! You're raising the bar in the filter construction territory!

I totally agree with lipebianc and I say the same as you.

Congratulations for your work.

Quote
xirja wrote: Totally! Splines AND filling, oh yeah!

WOW! very well done and very beautiful geometric shape, good work.

ALSO like very much all the beautiful and awesome works you have in your website here

Skybase, Sun, 08 Apr 2012 21:21:29 -0400
Sweeet! Love the script, very simple but so awesomely done!

Kraellin, Sun, 08 Apr 2012 21:58:45 -0400
3D, did you mean the line drawing scrippet to draw more than straight lines, cause that's all it seems to do?

ThreeDee, Mon, 09 Apr 2012 04:39:17 -0400

Quote
3D, did you mean the line drawing scrippet to draw more than straight lines, cause that's all it seems to do?

Yes, that scrippet demonstrates drawing just one line. I'm still trying to come up with a more sensible path-drawing filter that I could submit to the filter library. Maybe I'll make something out of the sine curve input version. That will include the multiple-line drawing script.

ThreeDee, Mon, 09 Apr 2012 08:18:17 -0400
I put the Sine-O-Graph filter in the queue, so you'll be able to dissect it. It is actually a fairly simple script.

xirja, Mon, 09 Apr 2012 08:56:10 -0400

Quote
Actually, no need to put it in the script, you can just threshhold it with a circular gradient

Oh right :D , the power of threshhold!

Quote
Or to program the values mathematically for such things as a fractal tree. Or for wireframed 3D objects. Or road maps between cities. Or tessalation patterns.

Many exciting possibilities there for sure.

Quote
But now it is slow as molasses with both the line and the fill, so needs some optimization.

And then I go and suggest opacity, bumping my graphic. I'm really not a smart ass most days, really :|

Quote
ALSO like very much all the beautiful and awesome works you have in your website here

Thanks SpaceRay, those were done in Mathematica (totally script and pixel based), so to be able to do something similar in Filter Forge is the tops. I've already found FF to be far superior in doing density plots using the scripting component; in a pixel based environment it is painfully slow.

...scalpel...check 8)

ThreeDee, Mon, 09 Apr 2012 11:43:00 -0400
A slight modification, giving two separate inputs for x and y (line beginning points and line end points) gives us for instance this:

ThreeDee, Mon, 09 Apr 2012 12:31:09 -0400
Improved version of the same.

ThreeDee, Mon, 09 Apr 2012 13:18:10 -0400
With color added.

Ghislaine, Mon, 09 Apr 2012 15:07:55 -0400
Great ! I love wireframed 3D objects. The last example is awesome. For more comprehension, because all this seems to me a bit complicated, can you post the settings for the last one when your Sine-O-Graph filter will be in the library, please ? :)

ThreeDee, Tue, 10 Apr 2012 12:06:05 -0400
Hi Ghislaine,

The last example is a different version of the script, so you can't do it with the Sine-O-Graph. Not sure if this one is going to end up in the library.

Ghislaine, Tue, 10 Apr 2012 14:17:21 -0400
3D wrote

Quote
Not sure if this one is going to end up in the library.

Please, it would be kind if you share this one with us. Hoping I will see this other wonder in the library. Thanks for sharing the version 1. :)

ThreeDee, Tue, 10 Apr 2012 14:19:15 -0400
Revisiting the good old fractal tree, this time with actual lines and overlap...

Skybase, Tue, 10 Apr 2012 14:45:48 -0400
Of course you'd do that lol. Sounds like the next step is to go even above and beyond. L-Systems? hehe

ThreeDee, Tue, 10 Apr 2012 15:37:52 -0400
Seems to be going in that direction. Meanwhile, here's the next step on the tree. now I seriously have to optimize the path drawing function, for it takes longer this way than without scripting!

xirja, Tue, 10 Apr 2012 16:45:40 -0400
Oh dear, molasses. I was hoping you were on some old machine. As soon as 'BitMap Buffer' and 'Table Memory Limit' are feasible, then matrix math can be used and then no more 'while' function to step through right?

ThreeDee, Wed, 11 Apr 2012 05:56:33 -0400
Well, yes. But first, I have a different issue to deal with, which is that the script does the full math to calculate the distance of every line segment at each point. If I first check whether the current point is within the bounding box of the path segment (including line weight) and skip those that aren't, I should be able to speed up the process considerably.

CFandM, Wed, 11 Apr 2012 08:39:45 -0400
Some Great work ThreeDee.. :)

Sphinx., Thu, 19 Apr 2012 02:21:16 -0400
ThreeDee... FYI:
http://blog.gludion.com/2009/08/dista...curve.html

Btw. I have a 570% faster version of your sine-o-graph running now :-) I will publish when ready

Pixel dimensions of image

Spiney — Sun, 28 Jan 2018 12:28:38 -0500

Spiney, Sat, 20 Jan 2018 14:04:39 -0500
Hi there, I'm new :)

Is there a variable I can plug to get the image x and y dimension in pixels?
Reason I ask is I want to calculate x and y derivatives on a per pixel basis without having to specify them as inputs.

emme, Sat, 20 Jan 2018 14:45:50 -0500
Hi,

In the result -component, check advanced mode and you'll be able to add image width/height components from there.

Rachel Duim, Sat, 20 Jan 2018 15:04:50 -0500
####

Spiney, Sun, 28 Jan 2018 12:28:38 -0500
Thanks!
I ended up using OUTPUT_WIDTH and OUTPUT_HEIGHT as described in some other thread.

is Random Variation on each run even possible in FF?

artyqwerty — Sun, 26 Nov 2017 07:17:23 -0500

artyqwerty, Sun, 26 Nov 2017 07:17:23 -0500
I must be missing something... Such simple functionality as default generation of new variation of Fractal Clouds or Noise filters is missing in FF. A user is forced to go into settings and manually change Variation value.

Is it possible to mimic default Photoshop filter behavior (by scripting or otherwise) and force FF to produce random variation on each run (CTRL+F).

I (and I think many other FF users) will greatly appreciate any code snippets or tips on how to achieve it. Frankly without this feature FF becomes nearly useless for me due to reliance of Photoshop actions in my workflow.

TIA

Curve Switch

Ramlyn — Sat, 14 Oct 2017 14:12:40 -0400

Ramlyn, Sat, 14 Oct 2017 12:36:53 -0400
I was trying to make a Curve Switch.
It may sound a very simple thing, but I have no experience in scripting and my switch is not working well.

So....
If I start from a switch for map inputs, as the one below :

function prepare()
end;

function get_sample(x, y)
local r, g, b, a
local value = math.floor(get_sample_grayscale(x, y, SELECTOR)*5+.001)
if value == 0 then r, g, b, a = get_sample_map(x, y, INPUT01) end
if value == 1 then r, g, b, a = get_sample_map(x, y, INPUT02) end
if value == 2 then r, g, b, a = get_sample_map(x, y, INPUT03) end
if value == 3 then r, g, b, a = get_sample_map(x, y, INPUT04) end
if value >= 4 then r, g, b, a = get_sample_map(x, y, INPUT05) end
return r, g, b, a
end;

How would this change in case of curve inputs?

Indigo Ray, Sat, 14 Oct 2017 13:42:48 -0400
I'm not sure what you already know, so...

There is a curve switch component, but maybe you need this as part of a script.
Use the curve script component, not the map script component.
When you create the inputs with the input editor, it tells you how to call each input.

If the script runs but doesn't look right, maybe you have a logic error somewhere. Example: is the script calculating 'value' as you intended?

Tip: Instead of writing 'if...then...end' a bunch of times, you can use 'elseif' and 'else' (see the Lua manual)

Ramlyn, Sat, 14 Oct 2017 14:12:40 -0400
Thanks Indigo Ray. I already know almost nothing. I'm simply trying to understand how it works.

What I would like to do is a Curve Switch with more than the 12 inputs of the standard one.

Possibly, I would prefer not to go much far away from the structure of the previous simple switch, otherwise I may not be able to easily change it later.

Then......
As first, a curve doesn't use r,g,b,a. I should change it with c.
Could it be something like :
if value == 0 then c = get_sample_curve(x, y, INPUT01) end
?

The grayscale input can be ok for the selector of the switch?
Should I also add t, or x and y are enough?
As return values, I saw that in other scripts are used c, c, c, 1.
But I'm not sure.

Attempt to unpersist an external Lua function

Sphinx. — Mon, 19 Sep 2016 09:55:16 -0400

Sphinx., Tue, 22 Feb 2011 10:16:32 -0500
I was going to continue work on a large script filter (mandelbulb renderer) in the newest filter forge release - now I get a new error I've never seen before:

Lua Critical Exception: Attempt to unpersist an external Lua function

My script used to work - was something changed recently related to loading external script files?

Sphinx., Wed, 23 Feb 2011 04:48:15 -0500
I tried to look up the error on Google, but it seems to be Filter Forge specific - what does it mean?

Sphinx., Thu, 24 Feb 2011 03:22:21 -0500
Anyone? I can't seem to make any of my script filters with external references work due to this error :cry:

Sphinx., Thu, 24 Feb 2011 03:57:51 -0500
Ok - the error is not related to the initial include call:

in Map Script script I tried:
[CODE]dofile("C:\\Users\\Sphinx\\test.lua");[/CODE]

where "test.lua" contains:
[CODE]
function prepare()
-- This function is called once,
-- before the rendering begins.
-- Use it for querying non-mapped
-- inputs and precalculation.
end;

function get_sample(x, y)
-- Image generation code goes here.
local r = x
local g = y
local b = (x + y) / 2
local a = 1
return r, g, b, a
end;
[/CODE]

This works just fine. I guess the error is related to actual script code in my external files. However the scripts used to work, so I need to know what that (new?) error message is about..

GMM, Thu, 24 Feb 2011 04:36:23 -0500
So, the above script works? Please attach the one that doesn't work.

Sphinx., Thu, 24 Feb 2011 05:17:26 -0500
I can't do that as the whole "application" use several lua libraries .. to much to set up for a simple test case.

I just want to know what triggers that error message in general (and what it means.. "unpersist" is not very clear to me). Then I can debug the actual problem myself...

GMM, Fri, 25 Feb 2011 09:26:27 -0500

Quote
Sphinx. wrote: in the newest filter forge release

Could you let me know the exact FF build which started to show issues? (there have been different builds of 2.009 on the website).

Now, a story about unpersisting. As you know rendering in Filter Forge is performed in separate passes. When you call prepare(), the Lua subsytem needs to save its results for future passes â€” for instance, if an unsafe script queries system time it should be consistent for all passes. We employ a third-party lib for that. In Lua jargon saving the result of a function is called persisting, and restoring the saved result is called unpersisting.

I understand all of the above is of little help to debug your problem, but if you could set up a test base our developers promise to look into it :)

Sphinx., Sat, 26 Feb 2011 06:01:50 -0500
Alright I located the problem - it is related to a change in global variable visibility..

The testcase is rather simple:

1. Create a new lua file, test.lua, with the following content:
[CODE]
function prepare()
t = 1
end;

function get_sample(x, y)
--t = 0.5
return t,t,0,1
end;
[/CODE]

2. Create a new filter and drop a new Map Script, enter:
[CODE]dofile("C:\\test.lua")[/CODE]
Or the path to where you put the test.lua file (remember "\\" as directory delimiter format, e.g. "C:\\Users\\GMM\\test.lua"

FF will now complain because global variable t is not registered properly (this used to work earlier).

Comment out t assignment in prepare and enable t assignment in get_sample - now it works.

The unpersist error is just a more complex version of this problem. I can send you a testcase for the unpersist error (I can't attach here due to file attachment restrictions), where should I send to?

GMM, Mon, 28 Feb 2011 04:59:23 -0500
Thanks for the info, we'll look into it.

Quote
Sphinx. wrote: where should I send to

Please send to info@filterforge

Sphinx., Mon, 28 Feb 2011 10:19:49 -0500
You should have a complete example in your inbox now :)

Sphinx., Mon, 07 Mar 2011 03:13:01 -0500
I'm still unpersisting my *** off here ;) Any news on the issue?

GMM, Wed, 09 Mar 2011 07:07:13 -0500
The developers are still unpersisting your test case :) We'll try to fix this by the release of the 3.0 beta.

Sphinx., Tue, 03 May 2011 07:38:49 -0400
Just tested in FF3B1 .. bug is still there :-(

GMM, Mon, 19 Sep 2016 09:55:16 -0400
Should be fixed in 5.011 â€“ please check.

Move to Center

xirja — Sun, 24 Jul 2016 07:55:36 -0400

xirja, Mon, 10 Jun 2013 17:48:53 -0400
Not sure if this problem can only be solved by a script, but I need an arbitrary point to be moved to the origin. Without knowing the initial distance from the center, how to move the point TO the center?

xirja, Mon, 10 Jun 2013 17:50:32 -0400
Best attempt attached below

xirja, Mon, 10 Jun 2013 17:53:57 -0400
I should have said polygon/ellipse/etc instead of point, but isn't a point really just an area or volume anyway in the real world, 0 dimensional, ha! ;)

ThreeDee, Tue, 11 Jun 2013 02:47:21 -0400
I would do it like this if radius was known. Twice as complicated if radius is not known, for you have to establish distance from both edges and average the result. (FF4)

ThreeDee, Tue, 11 Jun 2013 02:59:36 -0400
Unknown radius like this. Not very fast a method, but works.

ThreeDee, Tue, 11 Jun 2013 03:01:43 -0400
Better methods very likely exist.

xirja, Tue, 11 Jun 2013 07:31:05 -0400
Oh the glory of the motion blur! Genius. Thank you. :) I'll see if I can stumble upon any better way.

ThreeDee, Wed, 12 Jun 2013 07:41:47 -0400
You may wanna try scripting part of it, namely finding the distance fr om the edges after the initial horizontal (or vertical) motion blur and threshold. Might improve the speed, as you would need to do it for just one horizontal row and column of pixels, wh ereas the motion blur is pretty calculation-intensive.

BTW, the same method can be used to remove all white area around the image for an automatic "scale-to-fit", and other things of that nature.

xirja, Sun, 24 Jul 2016 07:55:36 -0400
:) Just used this technique for an isometric perspective walk through, and found that 7 is more accurate than 10 for the repeat on the gradient prior to blur. Must be that it is the closest prime number on the low side of 10.

LuaGL - OpenGL for LUA 5.2 - Could this be possibly used inside FF

SpaceRay — Fri, 15 Jul 2016 05:48:53 -0400

SpaceRay, Sat, 09 Nov 2013 10:21:35 -0500
I have found this website showing that there is available a library that provides access to all of the OpenGL (up to version 1.3) and works with LUA 5.1 or 5.2

LuaGL - OpenGL for LUA

This is a free software and has the same license than LUA

I wonder if this could be used in some possible way inside Filter Forge to make it faster and be able to use OpenGL with FF

And it seems that theres is much more information available on Google for this topic as can be seen here

Skybase, Sat, 09 Nov 2013 21:43:13 -0500
FF doesn't work like that.

SpaceRay, Mon, 11 Nov 2013 05:12:03 -0500
Thanks, I already thought that it would not be possible to use it directly through LUA scripting, but was not sure.

Would be possible that FF developers could use this LuaGL modifying the internal code of FF software?

I mean that FF could use OpenGL through this LuaGL instead of directly modifying the code to use OpenGL

Skybase, Mon, 11 Nov 2013 08:50:07 -0500
lol you should probably check out what OpenGL is geared for vs how this program works.

JesusSheep, Wed, 13 Jul 2016 09:59:43 -0400
In that case for Wondows DirectX otherwise Maybe OpenCL.

Skybase, Thu, 14 Jul 2016 01:08:27 -0400
Look, in the end people are using terms like OpenCL/GL/DirectX/CUDA interchangeably like as if you slap this on something and it suddenly becomes faster. It doesn't work that way. People seem to misunderstand the the purpose of those frameworks and why we use them for a program.

Again, I'm not denying the idea. I just think that saying "openCL" is like as empty of a thought as saying "64bit" on a thread about bacon and eggs. It doesn't mean you're right or wrong, it just doesn't persuade / direct anything.

In general, I think this is all a natural progression of technology. I think its fantastic we're seeing all this stuff but I also thing people don't understand the spectrum of what's going on behind the hood. I basically think it's a blind statement overall. You really have to think: there's a reason why FF runs on CPU at this point in time. Why there is this wall between the CPU and GPU. And why everything works the way it does.

[Multiple edits: added all the extra stuff later]

SpaceRay, Thu, 14 Jul 2016 06:22:24 -0400
When I did put this thread, was NOT trying to tell that FF could be able to use OpenGL for all filters through LUA, as this would be silly and not possible.

Sorry for the possible confusion

What I wanted to tell, and failed to explain, was that perhaps some few filters that use already LUA could be able to use this one of the first post.

BUT then after, thinking more about it, I agree with Skybase, that the LUA included in FF does not work in the same way, as is not possible

sorry for putting this before really thinking twice about it and if it was really possible

JesusSheep, Thu, 14 Jul 2016 09:17:34 -0400
In Generialist terms Opencl ,DirectX12,OpenGL are forms of GPU Accelateration .Though The later two are more platform specific and used for different puposes then the first. Line drawing and rotating both benifit from those. As for photos Photoshop already has that as an option (OpenCL).

Skybase, Fri, 15 Jul 2016 05:48:53 -0400
In general FF's code only runs on CPU. So any form of acceleration I bet would take a pretty epic rewrite of the whole program. The thing I'm just trying to tell you is that its no better mentioning any of these frameworks anyway. And the conversation has stalled unless we get a breakthrough in GPU programming.

And like because I've been online on these forums for so long I noticed how people just kinda dump those GPU frameworks without really looking at the context of the program. I think its a form of misunderstanding. But I don't blame people for that. And maybe time has passed enough that we get some bright awesome future. But until then I just don't see the reason to just make threads/posts just to mention an already discussed framework.

I'm really not saying that any of this is wrong. I just don't see any further development with the threads and posts that changes the situation.

SpaceRay, sorry! I was trying to address JesusSheep. Lol no worries.

Table memory limit?

Sphinx. — Mon, 30 May 2016 13:33:58 -0400

Sphinx., Tue, 08 Jun 2010 07:52:30 -0400
I'm getting some strange results with large tables. Do you have some limit to how large tables can be or memory usage in general for a script?

Vladimir Golovin, Tue, 08 Jun 2010 07:54:49 -0400
Uh, no idea. We'll look into this.

Edit: Could you post the sample script here?

Sphinx., Tue, 08 Jun 2010 07:59:59 -0400
Yep - it may very well be errors in the script though ;)

script:

Quote

function setPixRGBA(buf,cx,cy,r,g,b,a)
cx = math.floor(cx)
cy = math.floor(cy)
--zero indexed!
if (cx >= 0) and (cx < OUTPUT_WIDTH) and
(cy >= 0) and (cy < OUTPUT_HEIGHT)then
i = (cx + cy * OUTPUT_WIDTH) * 4 + 1
buf[i] = r
buf[i + 1] = g
buf[i + 2] = b
buf[i + 3] = a
end
end;

function getPixRGBA(buf,cx,cy)
cx = math.floor(cx)
cy = math.floor(cy)
--zero indexed!
if (cx >= 0) and (cx < OUTPUT_WIDTH) and
(cy >= 0) and (cy < OUTPUT_HEIGHT)then
local i = (cx + cy * OUTPUT_WIDTH) * 4 + 1
local r = buf[i]
local g = buf[i + 1]
local b = buf[i + 2]
local a = buf[i + 3]
return r,g,b,a
end
return {0,0,0,0}
end;

function createBitmap(buf, src)
local sx = 1 / OUTPUT_WIDTH
local sy = 1 / OUTPUT_HEIGHT

for j=0,OUTPUT_HEIGHT-1 do
for i=0,OUTPUT_WIDTH-1 do
local r,g,b,a = get_sample_map(i*sx, j*sy, src)
setPixRGBA(buf, i, j, r,g,b,a)
end
end
end

function prepare()
bitmap = {}
initialize = true
end;

function get_sample(x, y)
if (initialize == true) then
createBitmap(bitmap, SOURCE)
initialize = false
end

-- do not work:
--local r,g,b,a = getPixRGBA(bitmap, x * OUTPUT_WIDTH, y * OUTPUT_HEIGHT)

-- works, but with error:
local r,g,b,a = getPixRGBA(bitmap, 300, 300)

return r,g,b,a
end;

Sphinx., Tue, 08 Jun 2010 08:17:31 -0400
Hmm, I think its something else that fails, even a very small bitmap buffer causes the same problem.. still learning this lua stuff

Dmitry Sapelnikov, Wed, 09 Jun 2010 01:32:28 -0400
Heh, I've fixed this =)
Script code after bug fixing:

Quote

function setPixRGBA(buf, cx, cy, r, g, b, a)
local cx = math.floor(cx)
local cy = math.floor(cy)
--zero indexed!
if (cx >= 0) and (cx < OUTPUT_WIDTH) and
(cy >= 0) and (cy < OUTPUT_HEIGHT)then
local i = (cx + cy * OUTPUT_WIDTH) * 4 + 1
buf[i] = r
buf[i + 1] = g
buf[i + 2] = b
buf[i + 3] = a
end
end;

function getPixRGBA(buf,cx,cy)
local cx = math.floor(cx)
local cy = math.floor(cy)
--zero indexed!
if (cx >= 0) and (cx < OUTPUT_WIDTH) and
(cy >= 0) and (cy < OUTPUT_HEIGHT)then
local i = (cx + cy * OUTPUT_WIDTH) * 4 + 1
local r = buf[i]
local g = buf[i + 1]
local b = buf[i + 2]
local a = buf[i + 3]
return r, g, b, a
end
-- Fixed(Egret): return {0, 0, 0, 0} is incorrect here
return 0, 0, 0, 0
end;

function createBitmap(buf, src)
-- Fixed(Egret): it's a proper conversion from the filter coords to
-- the image coords
local scale = 1 / SIZE

for j=0, OUTPUT_HEIGHT-1 do
for i=0, OUTPUT_WIDTH-1 do
local r,g,b,a = get_sample_map(i*scale, j*scale, src)
setPixRGBA(buf, i, j, r, g, b, a)
end
end
end

function prepare()
bitmap = {}
initialize = true
end;

function get_sample(x, y)
if (initialize == true) then
createBitmap(bitmap, SOURCE)
initialize = false
end

-- Fixed(Egret): it's a proper conversion from the filter coords to
-- the image coords
local r,g,b,a = getPixRGBA(bitmap, x * SIZE, y * SIZE)
return r,g,b,a
end;

Dmitry Sapelnikov, Wed, 09 Jun 2010 02:11:07 -0400
The problem which caused nils was tiny.

But an approach used in the script makes it good "don't do it!" example (Sphinx, I'm sorry :( Of course it's not your fault, just lack of info about scripting)

For all FF script programmers:
Never create tables or another kind of caches without really serious purpose. Caches in scripts consumes memory really hard because caches are independently created for each rendering thread. (For exapmle, if you've got double-core processor and "use all CPU(s)" option is enabled in FF options, script component creates at least 3 copies of one cache: 2 for filter preview rendering threads, and 1 for component thumbnail rendering.
BTW, I've got independent infrastructure for components which need caching. And we haven't implemented it in script components yet.

Dmitry Sapelnikov, Wed, 09 Jun 2010 02:15:48 -0400
Another point of discussion is coordinate systems used in FF.
We are going to post an wiki article about it this week.

Vladimir Golovin, Wed, 09 Jun 2010 02:37:10 -0400
Egret, good point -- we should mention per-thread Lua state duplication in the help articles.

Sphinx., Wed, 09 Jun 2010 03:31:08 -0400
Ah, of course! Remains of my first implementation where I tried to store channels in a small table for each rgba pixel/sample, but that didn't work out (maan I wish I could drag off the script tab and maximize it ;) hint hint)

About the memory consumption - yes I did notice things got slow with the "large" table. I am really just testing/learning things by trying out familiar concepts from earlier projects.

Are you saying that the complete script is copied for each thread or what is going on? It would be quite useful if you somehow could declare a shared variable cross threads and script components, perhaps in some sort of read only state to avoid changing data problems. Or the other way around: declare that a script is not suitable for multithreaded processing.

I think that you will see several attempts to implement bitmap filters, perhaps something can be done in this regard (some sort of bitmap filter script component which is wrapped by your general bitmap filter framework, with cache tiles etc).

Igor Lorents, Wed, 09 Jun 2010 03:45:23 -0400
Also, I'd like to mention an important thing about component sampling.

Filter Forge core can take samples not only in [0..Size-1] bounds. We have to take some samples outside this area to make the proper supersampling of border pixels.
That's why, your execution path went through the line I marked with bold below.

Quote
function getPixRGBA(buf,cx,cy) local cx = math.floor(cx) local cy = math.floor(cy) --zero indexed! if (cx >= 0) and (cx < OUTPUT_WIDTH) and (cy >= 0) and (cy < OUTPUT_HEIGHT)then -- skipped.... return r, g, b, a end return 0, 0, 0, 0 end;

You can easily check that by adding the following line before the second return statement:

Quote
error (string.format("%d, %d", cx, cy))

After that, you'll see something like this in the log window:

Quote
Script error (line 28): -1, -1.

Generally, I agree with Vladimir and Egret. Thanks for your post, Sphinx. Your code sample uncovers a lot of things which must be thoroughly explained in our help articles.

Vladimir Golovin, Wed, 09 Jun 2010 04:00:05 -0400

Quote
Sphinx. wrote: (some sort of bitmap filter script component which is wrapped by your general bitmap filter framework, with cache tiles etc

This is planned, but it won't make it into the official release of 2.0.

xirja, Mon, 14 Nov 2011 04:44:08 -0500
:cry: Perhaps with the official release of version 4.0?

Crapadilla, Sun, 01 Mar 2015 04:23:25 -0500
:cry: Perhaps with the official release of version 5.0, then?

Rachel Duim, Sun, 18 Oct 2015 15:09:17 -0400
Add my vote. I get very slow rendering if I use the FXAA map script component in a filter with a bomber. It has no arrays, but a lot of variables (over 50, necessary given the complexity of the script). Please come up with some way to deal with these memory issues.

xirja, Mon, 30 May 2016 13:33:58 -0400
Does version 6 help this by eliminating the 32 bit 3 GB limit?

A "Stones"-like noise with triangular forms?

Tim2501 — Mon, 16 May 2016 00:58:06 -0400

Tim2501, Sun, 17 Jun 2012 17:18:21 -0400
I'm currently working on a broken-glass filter and had some good results with the "Stones"-noise. I'm using a low treshold on it to determine the breaking-lines and an if-module on a solid-filled version od "Stones" to determine the areas of single shards.

My problem is that, while glass usually breaks into shards with 3 or 4 edges, "Stones" often delivers shapes with 5 or 6 edges, which makes the whole thing look pretty unrealistic.

Is it possible to make or modify a script so it delivers a triagular-stones-noise?

Unfortunately I cant script at all, so any help will be greatly appreciated.

Thanks in advance! ;)

uberzev, Mon, 18 Jun 2012 04:07:54 -0400
A few triangle ideas here...

Tim2501, Mon, 18 Jun 2012 07:37:53 -0400
This idea occurred to me too.
Unfortunately, the triangles must not overlap each other, because I need the grooves betwen them to determine my breaking-lines.
Also, overlapping triangles often produce concave forms within each other, which would look pretty unrealistic as shards :/

Morgantao, Mon, 18 Jun 2012 14:49:31 -0400
Uberzev, maybe your smooth stone mosaic can be adapted to make triangles or square instead of ovals, or eggs?

uberzev, Mon, 18 Jun 2012 22:32:59 -0400

Quote
Uberzev, maybe your smooth stone mosaic can be adapted to make triangles or square instead of ovals, or eggs?

The underlining math of my filter is the same as Worley Cell noise, and I don't believe that formula offers triangles.

uberzev, Mon, 18 Jun 2012 23:01:02 -0400
This do anything for you?

uberzev, Wed, 04 Jul 2012 03:57:49 -0400
The solid-fill version of chaffs makes some decent triangles...

SpaceRay, Sun, 29 Jul 2012 00:28:34 -0400
Thanks very much for the Offset Edges filter that I like much

SpaceRay, Sun, 29 Jul 2012 00:30:45 -0400
I have modified it to be able to fill the beautiful triangular shapes created by this with images but what I really have done is only fill the lines and background :(

SpaceRay, Sun, 29 Jul 2012 00:33:53 -0400
And this other one that is the opposite, with higher width of the edges

SpaceRay, Sun, 29 Jul 2012 00:34:55 -0400
And here is the simple modification

Skybase, Sun, 29 Jul 2012 00:35:35 -0400
I'm going to poke you to try something more fancy than masking :p

SpaceRay, Sun, 29 Jul 2012 00:39:39 -0400
What would be really good is to be able to make the image FOLLOW and fill the shapes made by this filter with this setting shown here

So the image would be shattered and cut to fill the inside of the white shapes of this pattern shown here and have some kind of shading so it would look more something like a 3D style

Skybase, Sun, 29 Jul 2012 01:07:14 -0400
Like this?

SpaceRay, Sun, 29 Jul 2012 05:05:11 -0400
Of course that what I made above was very simple and nothing fancy, was just a quick test.

Quote
Like this?

OH, yes, this is what I was talking about. Be able to modify the source colors into the shapes. Well done!! Like it much

Also would be good if possible to make the real photo image broken into pieces to fill the irregular shapes and not only the source colors

Skybase, Sun, 29 Jul 2012 05:18:47 -0400
Yup of course you can do that.

Skybase, Sun, 29 Jul 2012 05:23:07 -0400
lol want to give it a shot yourself and then should I just reveal how it was done? :p

SpaceRay, Sun, 29 Jul 2012 09:32:11 -0400
On this one I think it has been very easy to make and to solve :) looking at how this was done.

Sorry I did not see it before.

Here is the FF Lionfish

Although when trying to convert it to images instead of solid colors I still have a problem, but will see why this happens

SpaceRay, Sun, 29 Jul 2012 09:47:45 -0400
and here is another example

SpaceRay, Sun, 29 Jul 2012 09:49:46 -0400
BUT now is needed to give some kind of darkening and lighting shadows so it is not very flat

SpaceRay, Sun, 29 Jul 2012 10:13:08 -0400
Using the Blast Shadows by Threedee I have got this other version but all of them have uniform shadows and although it looks nice and good is not exactly the effect I would like

SpaceRay, Sun, 29 Jul 2012 10:17:47 -0400
And the bottom FF Lionfish is better with the Blast Shaodws than the above one, at least from my point of view

SpaceRay, Sun, 29 Jul 2012 15:55:58 -0400
Sorry to ask a possible basic question, but why the Chaffs work very well when using solid fill, but when you uncheck it to have the full image source it does not work in the same way?

I mean that the source image is not distorted to the shapes, like it happens when using solid fill, and i have tried also different settings and none of them work in the same way if solid fill is unchecked.

Skybase, Mon, 30 Jul 2012 23:32:08 -0400
Here's what your help docs say about "solid fill"
"If turned on, each noise "cell" is filled with a uniform random tint within the color range defined by the Noise and Background parameters."

What you're really seeing when you disable "solid fill" is the noise pattern being applied on the background with the same color values at the same pixel areas. So your noise + background colors are the same, therefore there seems to be no difference but it's drawing the noise just as it would, you just can't see it.

SpaceRay, Tue, 31 Jul 2012 03:28:03 -0400
Thanks Skybase for your answer, I also went to see the help docs to see if I was doing something wrong or there something I did not know, but seems that as you say well, it works only when the solid fills is activated, because if not not you canÂ´t see the effect

I asked this because I have seen that on other component (do not remember which one) I have seen that when unchecking the solid fill checkbox the effect keeps being the same but with the full real source image instead of one solid color, so I thought that in this one would work in the same way, but I was wrong.

And as you have shown in the above example there are other ways to make this WITH the source image and not a solid color, although I still do not know how.

SpaceRay, Fri, 15 Feb 2013 02:15:52 -0500

Quote
SpaceRay What would be really good is to be able to make the image FOLLOW and fill the shapes made by this filter with this setting shown here So the image would be shattered and cut to fill the inside of the white shapes of this pattern shown here and have some kind of shading so it would look more something like a 3D style

Quote
Skybase Like this?

Quote
SpaceRay OH, YES, this is what I was talking about. Be able to modify the source colors into the shapes. Well done!! Like it much Also would be good if possible to make the real photo image broken into pieces to fill the irregular shapes and not only the source colors

Quote
Skybase lol want to give it a shot yourself and then should I just reveal how it was done?

Well, I have tried to make this SECOND example shown above here with the real photo images instead of plain colors, have not had any sucess as I do not know how to make it because if I uncheck the "solid fill" setting in the Chaffs component, all is lost :(

Please, Skybase could you be so kind to tell HOW you have done it?

Thanks very much

Skybase, Fri, 15 Feb 2013 12:55:43 -0500
Screenshot explains much of the way I worked on it. It's honestly kinda lazy.

Notes: The rotate component uses the original chaffs component that was in Uberzev's filter. The colored chaffs component can also be used to derive rotation values, however you should desaturate it, but this is up to you. Two chaffs components should have the same variation value, otherwise they'll have different results.

SpaceRay, Fri, 15 Feb 2013 17:46:35 -0500
WOW!! Thanks very much for explaining it and for making this screenshot and taking the time to explain it with texts and arrows, very good and well done.

I will try it and see what I can do.

Thanks again

SpaceRay, Wed, 16 Oct 2013 04:23:19 -0400
I forgot to tell that I have tried this that you have shown above with the instructions and works very well :)

Thanks very much Skybase for all the help given already and for caring and taking the time to make this screenshot with the detailed instructions that have been very useful and helpful.

Now the next step is to be able to combine different images filling the shapes and not using only one source image, and the example on how to do it is shown with the Mondrian filter by Skybase but without the instructions given already above I would not have been able to understand and use it

Thanks also to uberzev for making the Offset Eddges filter above and sharing it here in the forum and also to ThreeDee for making the great Shadows snippet

Here are some examples I have done, although the filter stills needs some work for it to work right and some more controls, also there is a bad problem using the "Size, pixels" setting as it gives very unwanted results, so I have replaced it with Scale, and although it works it does not give the same result.

SpaceRay, Fri, 18 Oct 2013 07:22:00 -0400
also I will see how it works using other noise components instead of he chaffs used here an what results could be get

LexArt, Mon, 28 Mar 2016 23:58:16 -0400
I have just discovered this and it seems to be very interesting and nice effect, thanks uberzev, Skybase and SpaceRay for all this thread

I will try to understand it and see what can be done with this.

Please, SpaceRay could you share the filter of your last example shown? it looks very good and nice

thanks

SpaceRay, Sat, 02 Apr 2016 03:50:13 -0400

Quote
LexArt wrote: Please, SpaceRay could you share the filter of your last example shown? it looks very good and nice

Glad you like and find it nice, regretably, these are old filters, and I have them on a backup hard drive, so I may be able to find it when I search in the these hard drives and see if I still have it

Ramlyn, Sat, 30 Apr 2016 00:42:02 -0400
An experiment similar to Stones/Cells :

Ramlyn, Sat, 30 Apr 2016 00:50:37 -0400
The same filter with circular shapes instead of triangles :

LexArt, Sat, 14 May 2016 04:23:56 -0400

Quote
Skybase wrote: Screenshot explains much of the way I worked on i

i had put in the FF forum search "fill a shape" and found agin this thread that I did not remember and it seems that this may explain in some way what I have asked in this other thread about Hexagon Parade by Skybase

e

Please, Skybase, can you tell if this is the same as the technique used for Hexagon Parade?

Does the source image to be feed into the rotate component must be in grayscale shades or grayscale gradient to work?

Thanks

Skybase, Sat, 14 May 2016 07:01:22 -0400
Hexagon parade does something completely differently so this method wouldn't be the same.

The rotate component requires a grayscale input (anything really) for rotation values and an input source image that gets rotated.

SpaceRay, Sun, 15 May 2016 00:42:56 -0400

Quote
LexArt wrote: Please, Skybase, can you tell if this is the same as the technique used for Hexagon Parade?

Yes, as said by Skybase, although it may look similar, is not at all the same as he has told also on another part of the forum

I can not help on understanding how this works, as I also do not understand it, but you can try and experiment and test things and see what happen and see if you can get something similar or that you may like

SpaceRay, Mon, 16 May 2016 00:58:06 -0400

Quote
LexArt wrote: Does the source image to be feed into the rotate component must be in grayscale shades or grayscale gradient to work?

LexArt did you notice and seen that what Skybase is refering and telling, comes from the uberzev offset edges filter? i mean the black and white chaffs

This comes from my idea derived frrom this filter by uberzev

Compilation of Random Space Filling Tiling articles for FF Filters

SpaceRay — Sat, 14 May 2016 04:34:08 -0400

SpaceRay, Sun, 29 Jul 2012 04:39:04 -0400
I have made this other thread How would you make this variable dots pattern in FF?

Quote
uberzev wrote: Would need to be a custom script...

So I have been looking for this and I do not have the experience, knowledge or skills to make any kind of scripts to be able to do this so I decided to put here a compilation of the information I have found if it could help and be interesting and useful to someone

Compilation of Random Space Filling Tiling articles for FF Filters

The main and very useful and great link given by uberzev

Random space filling tiling of the plane

all the above examples shown comes from this website
____________________________________________________

Paul Bourke's "tiling of the plane" work was inspired by John Shier, a computer artist who integrates random numbers in his creations.

http://john-art.com/

On page 5 of his Gallery you can find lots of examples showing Random Space Filling

Gallery 5 examples

________________________________________________________

AND is also very interesting this 10 Page article made in PDF from Paul Bourke and Jhon Shier explaining all this topic of Random Space Filling

Filling Space with Random Fractal Non-Overlapping Simple Shapes

Fr om the Processing Software website

Space Filling Algorithm

This has two interesting links to BOX FITTING APPLET

A region of space is filled through exhaustive placement of slowly expanding boxes

What is very interesting is that this is an working applet wh ere you can make your own BOX FITTING designs! Do not miss the opportunity to try it yourself

and with gradient colors

PACKING ALGORITHM

Another name for Space Filling can be Packing Algorithm

Packing Algorithm

If I find more I will put it here

SpaceRay, Mon, 26 Nov 2012 10:50:27 -0500
Please, Anyone could have any other information, link, software or way to do this WITHOUT having to program it, without scripting, or code it myself?

Or if someone else have done it already and is available to just use it in some way.

AND more important for me, that IS AVAILABLE for Windows 7, as I have seen one that is only for MacOS

I could use Photoshop or Illustrator in Windows 7 (if there could be possibly any plugin or addon)

Skybase, Mon, 26 Nov 2012 11:35:29 -0500
Studio Artist 4.

It's a VERY VERY specific piece of feature you're looking for so it's mildly hard to find them especially at the level of power you're looking for. Just as a hint on looking for things like this, it could be achieved via various means as well. I tried using a physics engine to make circles spread and self-organize. It's pretty cool. Did that in Maya. :)

I sense you're desperate after seeing you've bumped 3 or 4 threads on the same matter. That's probably not the best of forum behaviors in general. Don't let your feelings run you doing that. One post should be enough for a question, otherwise it starts becoming ridiculous, like you're begging for attention. Not good. :p And hey, I do business with art and I can really say the same rules apply. ;)

SpaceRay, Tue, 11 Dec 2012 04:21:46 -0500
Thanks for your comment and suggestion of Studio Artist 4, I have tried and it seems that it could be possible to make but still I am not sure how to do it right as I am very beginner in this sofware and is a complex one to make special effects.

I am not desperate for this :D , but would like to be able to have a way to make this. Sorry to have bumped 3 or 4 threads about this, but they had different things, I will try to not make it if I can. Sorry for showing and seems and feeling that I am begging for this.

Quote
Just as a hint on looking for things like this, it could be achieved via various means as well. I tried using a physics engine to make circles spread and self-organize. It's pretty cool.Did that in Maya.

What various means?

What Physics engine?

and how to make the circles spread and self-organize?

Is this only in Maya? only as 3D ? and what about a 2D version that is not in a very expensive software?

Thanks very much for your help and your comments that are appreciated and right

LexArt, Sat, 14 May 2016 04:34:08 -0400
searching for "fill shape" on the forum I have discovered this thread and it looks very beautiful and great, like them much, but I think that FF is not able to make this

Quote
Skybase wrote: Studio Artist 4. It's a VERY VERY specific piece of feature you're looking for so it's mildly hard to find them especially at the level of power you're looking for. Just as a hint on looking for things like this, it could be achieved via various means as well. I tried using a physics engine to make circles spread and self-organize. It's pretty cool. Did that in Maya.

Hi, I have never sen this software, I have just searched it on google and found it, but it costs 399$, although there is now a offer for 299$, but do not know if it is worth it, and have seen it was released in 2012 and has not been updated since then, so it may feel that they do not keep updating it

please, have you tried yourself with studio artist to make this kind of things shown here?

Thanks

Scripiting Library.

Lucato — Sat, 26 Mar 2016 00:57:27 -0400

Lucato, Tue, 08 Jun 2010 12:15:23 -0400
Hey FF team, congratulations for the new step. Really interesting this new feature. I'll check it out.

Do you guys intend to make a library for scripts as for filters? I mean, where members can share theirs scripts? It would be cool for those like me that aren't so good with programming languages. ;0)

For a while, folks would use this thread for posting their scriptings in case they want to share it with the community. ;0)

Cheers.

Skybase, Tue, 08 Jun 2010 12:16:51 -0400
+1 a searchable script repository would be awesome :D

ThreeDee, Wed, 09 Jun 2010 02:38:47 -0400
Awesome.

Here's my first "Scrippet" (script snippet): Proportional gradient.

Lucato, Wed, 09 Jun 2010 03:17:15 -0400
Great! Thanks ThreeDee for sharing it!

ThreeDee, Wed, 09 Jun 2010 03:32:29 -0400
Hi Lucato, you're welcome!

Here's another one with pixel-based control.

Pixel-Based Grid

Carl, Wed, 09 Jun 2010 04:27:02 -0400
Good idea Lucato, I too am script handicapped, thanks ThreeDee 8)

Crapadilla, Wed, 09 Jun 2010 05:13:38 -0400
It will be interesting to see whether we can generate some patterns from the wishlist now via the new script components. Of course, I'm blissfully (and hopelessly) unencumbered when it comes to scripting, so others will have to give it a shot. :D

Anyone up for a Logarithmic Spiral? 8)

Vladimir Golovin, Wed, 09 Jun 2010 05:24:56 -0400
ThreeDee, nice grid!

(The code could use a little beautification -- e.g. you may drop 'local' for r, g, b and a. Our programmers like to stick it to every variable, while I'm in favor of using it only where it's actually needed because it makes the code less readable.)

Lucato, Wed, 09 Jun 2010 05:27:49 -0400
Yup, nice one 3D! Thanks again.

ronjonnie, Wed, 09 Jun 2010 05:49:07 -0400
Good morning everyone, :)

Hi ThreeDee,

I agree with Lucato, a nice one. ;)
Thank you.

I wondered if you ever finished your filter?
I need your help please.
http://www.filterforge.com/forum/read...ssage84442

Thanks,
Have a GREAT day. :)

Ron

Crapadilla, Wed, 09 Jun 2010 07:59:07 -0400
I've been playing with ThreeDee's "Proportional Gradient" script, and it appears that the resulting gradient is still affected by Size even if the flag is turned off. Is there a way to make Map Script components independent of Size?

Speaking of flags, what is their use?

Vladimir Golovin, Wed, 09 Jun 2010 08:43:36 -0400

Quote
Crapadilla wrote: Is there a way to make Map Script components independent of Size?

Yes, but I don't have a code snippet handy -- perhaps Egret can post one. It involves the SIZE variable.

Sphinx., Wed, 09 Jun 2010 08:55:39 -0400
Dilla, I think its something along these lines if you want x and y independent of size:

function prepare()
SCALE = SIZE / math.min(OUTPUT_WIDTH, OUTPUT_HEIGHT)
end;

function get_sample(x, y)
local x_no_size = x * SCALE
local y_no_size = y * SCALE
end;

dmorrill, Wed, 09 Jun 2010 09:09:15 -0400

Quote
Vladimir Golovin wrote: (The code could use a little beautification -- e.g. you may drop 'local' for r, g, b and a. Our programmers like to stick it to every variable, while I'm in favor of using it only where it's actually needed because it makes the code less readable.)

Just as an exercise in getting more familiar with Lua, I took the liberty of simplifying the code a bit:

Quote

function prepare()
    griddistx = get_intslider_input( GRID_DIST_X )
    griddisty = get_intslider_input( GRID_DIST_Y )
    gridthick = get_intslider_input( GRID_LINE_THICKNESS )
    tf = { [true] = 0, [false] = 1 }
end;

function get_sample(x, y)
    local zx = math.mod( math.abs( x ) * OUTPUT_WIDTH, griddistx )
    local zy = math.mod( math.abs( y ) * OUTPUT_HEIGHT, griddisty )
    local w = tf[ (zx < gridthick) or (zy < gridthick) ]
    return w, w, w, 1
end;

dmorrill, Wed, 09 Jun 2010 09:34:03 -0400
Following up on my previous post, here's a variation on ThreeDee's scrippet that allows you to set the grid line color and fill to arbitrary color or map values...

Lucato, Wed, 09 Jun 2010 09:45:14 -0400
Regarding the Grid Script, shouldn't it show on the right and bottom side a thin line too as those shown at the top and left side once it is squared image?

Skybase, Wed, 09 Jun 2010 10:04:31 -0400
Hmm... well, I just began playing around with LUA. But aside from the advanced stuff it's really nice how you can throw in any formula and end up with pretty cool stuff.

Here's a classic and a tribute to my highschool math formula that was saved on a TI-83

function prepare()
value1 = get_slider_input(NUMBER)
end;

function get_sample(x, y)
w = (x+(value1)*3*math.sin(y*x))*0.2
u = (w+(value1)*3*math.sin(y*x))*0.2
return w, u, w, a
end;

dmorrill, Wed, 09 Jun 2010 10:35:01 -0400

Quote
Lucato wrote: Regarding the Grid Script, shouldn't it show on the right and bottom side a thin line too as those shown at the top and left side once it is squared image?

Probably, but that will require a bit more code than the current one. But on the other hand, it tiles much better the way it is now :)

dmorrill, Wed, 09 Jun 2010 10:44:33 -0400
Here's the first script component I wrote yesterday (I'm still fairly new to FF, so it took me a while to figure out where the component was being stored). This one takes two input maps and outputs a new map organized as a variable size grid whose cell contents are randomly chosen from matching regions of the input maps (sort of like the game of Concentration). The color of the (optional) grid lines can also be specified using another input map/color.

For some reason, the script input editor won't allow me to set the lower bound of the line thickness input to 0, so the grid line thickness is 1 less than what you actually specify (i.e. if you set 1, no grid lines are drawn, setting 2 sets a grid line width of 1, ...).

ThreeDee, Sat, 12 Jun 2010 03:20:05 -0400
Bubbles Scrippet

With random number generator and tables you can do object-type noises, like bubbles.

The drawback is that you have to sample each pixel as many times as you have objects, so 100 objects takes 10 times as long as 10 objects.

ThreeDee, Sat, 12 Jun 2010 03:21:25 -0400
Scrippet itself

ThreeDee, Sat, 12 Jun 2010 04:14:26 -0400
Random Noise Scrippet

Lua doesn't allow random numbers in the get_sample(x,y) function, so I wrote this Scrippet to get around that with a pseudorandom number generator function.

In other words, here's how to make plain random noise.

Vladimir Golovin, Sat, 12 Jun 2010 04:34:03 -0400

Quote
ThreeDee wrote: Lua doesn't allow random numbers in the get_sample(x,y) function, so I wrote this Scrippet to get around that with a pseudorandom number generator function.

ThreeDeee, this is a very interesting and important topic -- we're thinking about providing an API for randomness that is not prone to patterning artifacts of random number generators seeded by sample coordinates, and, at the same time, don't have the problems associated with Perlin-based noise (e.g. reduced dynamic range.)

(I haven't checked the snippet yet -- too busy writing the help.)

Vladimir Golovin, Sat, 12 Jun 2010 04:36:40 -0400

Quote
ThreeDee wrote: Random Number Generator Scrippet.ffxml

Oh, looks good so far. I'll have the guys examine and test it, perhaps we'll go with a similar approach.

ThreeDee, Sat, 12 Jun 2010 04:38:21 -0400
Drop Ripples

Variation on Bubbles.

ThreeDee, Sat, 12 Jun 2010 04:39:06 -0400
Ripples Scrippet

ThreeDee, Sat, 12 Jun 2010 04:50:54 -0400

Quote

Vladimir Golovin wrote:

Quote
ThreeDee wrote: Random Number Generator Scrippet.ffxml

Oh, looks good so far. I'll have the guys examine and test it, perhaps we'll go with a similar approach.

Hi Vladimir,

Glad you find it useful. Yes, it would be nice to have that functionality, and a way to connect it to the global Variation slider if at all possible.

TD

Vladimir Golovin, Sat, 12 Jun 2010 04:54:44 -0400

Quote
ThreeDee wrote: and a way to connect it to the global Variation slider if at all possible.

You can the VARIATION variable, which is visible to scripts that have the "Makes use of the global Variation setting" flag turned on in their Script Settings.

As for our planned randomness API, we may decide to pre-seed it with VARIATION automatically (while allowing to add a "local" seed.)

ThreeDee, Sat, 12 Jun 2010 05:45:30 -0400

Quote
Vladimir Golovin wrote: You can the VARIATION variable, which is visible to scripts that have the "Makes use of the global Variation setting" flag turned on in their Script Settings. As for our planned randomness API, we may decide to pre-seed it with VARIATION automatically (while allowing to add a "local" seed.)

Variation slider: Oh, excellent, got to check that out. Haven't gotten that far in investigating the possibilities.

Randomness API plan sounds good.

ThreeDee, Sat, 12 Jun 2010 05:48:09 -0400
Random Lines

Similar to Bubbles, this Scrippet uses a table to store a number of lines (x-coordinate, y-coordinate, angle and value) and then calculates the distance of the current point to it, using the value that is highest at a given point.

ThreeDee, Sat, 12 Jun 2010 05:48:34 -0400
Scrippet

ThreeDee, Sat, 12 Jun 2010 05:57:34 -0400

Quote
Lucato wrote: Regarding the Grid Script, shouldn't it show on the right and bottom side a thin line too as those shown at the top and left side once it is squared image?

Hi Lucato,

Actually, no. The point of the script is to demonstrate using PIXEL values instead of relative values.

The built-in components use values relative to the size of the image, while the Grid Scrippet uses fixed pixel values that don't change with the image size. Thus you can be sure your gridlines are always (for example) 10 pixels apart, whether the image is 600px or 126px or 6748px square.

ThreeDee, Sat, 12 Jun 2010 06:01:51 -0400
An interesting sort of thing happens when you reduce the Size, Pixels with the Lines Scrippet. The lines cross mainly in the original image area, since their coordinates fall there, but do continue in the whole image area.

ronjonnie, Sat, 12 Jun 2010 10:25:03 -0400
Good morning Everyone, :)

Hey ThreeDee,

Thanks for the Scrippets, they are very cool & most helpful, to help us all learn.
Speaking of learning, reminds me of a project I am having trouble with, I was in great hopes that you would please help me with it? ;)

http://www.filterforge.com/forum/read...5&TID=7411

Have a GREAT day. :)

Ron

ThreeDee, Sat, 12 Jun 2010 10:54:09 -0400

Quote
ronjonnie wrote: Speaking of learning, reminds me of a project I am having trouble with, I was in great hopes that you would please help me with it? Wink

Hi Ronjonnie,

That Water Splash filter was an unfortunate victim of my operating system upgrade -- it no longer exists.

But maybe I'll get inspired to rebuild it with 2.0 one of these days.

TD

ThreeDee, Sat, 12 Jun 2010 11:14:24 -0400

Quote
Vladimir Golovin wrote: You can the VARIATION variable, which is visible to scripts that have the "Makes use of the global Variation setting" flag turned on in their Script Settings.

Ok, thanks, I got that now. You can control the variations by calling math.randomseed(VARIATION) during prepare.

Without this, the random numbers were different EVERY time, even when using a stored preset, which is fine if you wanted it to be that way, but if the variation happed to the exact one you wanted to keep...

TD

ronjonnie, Sat, 12 Jun 2010 11:42:31 -0400
Hey ThreeDee,

Thank you for the reply. I thought you were mad at me for something & I could not figure out what that would be. :?:

I am SO SORRY to hear the bad news about the loss of the Water Splash filter! :cry: That has to be one of the most SUPER COOL & Most useful filters I have seen in a long time!
PLEASE PLEASE find the time to rebuild it, I love it & can make good use of it. OK. :) :) :) :)

Have a GREAT weekend!

Ron

Totte, Sat, 12 Jun 2010 14:43:11 -0400
ThreeDee, real cool stuff you got here ;-)

StevieJ, Sat, 12 Jun 2010 19:55:02 -0400
Thanks for sharing, guys.....they are helping me to learn it.....especially like the Lines Scrippet..... 8)

Carl, Sun, 13 Jun 2010 07:17:13 -0400
cool ThreeDee

......... not having a clue on scripting, is it possible to write a script which allows you to bring a second image into the editor? If it is, is any one interested in writing it, I'm sure alot of people would use it :)

Totte, Sun, 13 Jun 2010 07:57:18 -0400
Carl, check out the Berestrokia sample from Vlad/Egret. I have an idea of writing a tool to create a bomber particle builder from a png.

Only problem, I wont make a Windows version, will be Mac OS X only.

ronviers, Tue, 15 Jun 2010 10:23:41 -0400
Can we embed pastebins?
[paste]pastebinTest[/paste]

Carl, Wed, 16 Jun 2010 01:59:49 -0400

Quote
Totte wrote: Berestrokia sample from Vlad/Egret

where was that Totte? your gona have to give up that mac and give windows a go ;) :)

Kraellin, Sun, 20 Jun 2010 15:58:52 -0400
more, more, more!

Dmitry Sapelnikov, Mon, 28 Jun 2010 02:19:31 -0400
ThreeDee, where have you got the noise formula for your RNG snippet?
Could you give me a link?

ThreeDee, Wed, 30 Jun 2010 05:25:56 -0400

Quote
Egret wrote: ThreeDee, where have you got the noise formula for your RNG snippet? Could you give me a link?

Hi Egret, sent you the link by mail yesterday as the forum was read-only.

TD

Totte, Wed, 30 Jun 2010 05:43:21 -0400

Quote
Carl said something like: where was that Totte?

http://www.filterforge.com/download/b...pting.html

ThreeDee, Wed, 30 Jun 2010 05:49:38 -0400
Tech Noise

Fractal square noise of in sizes from 1/2 to 1/2^n.

ThreeDee, Wed, 30 Jun 2010 05:53:38 -0400
Hmm. That file name changed radically from what I uploaded. Hope it works...

The basic output is this, iterations and bevel size are adjustable:

ThreeDee, Wed, 30 Jun 2010 05:56:19 -0400
Image sample, using a blend of two Tech Noise components as a height map in a Surface filter.

Idea: Multiple Subtractions from Source Image

Mehmet Sensoy — Mon, 08 Feb 2016 19:41:42 -0500

Mehmet Sensoy, Sat, 06 Feb 2016 07:46:28 -0500
Hello all,
Trying to understand filter forge and using map/curve script components.
Recently I had an idea to subtract one source image from multiple other sources.

Is it possible to make ;

Main Input : Source Image
Input : Subtract Image 1
Input : Subtract Image 2...5

with map script component.

Don't you think it would be useful?

Thank you,
Best Regards.

Indigo Ray, Sat, 06 Feb 2016 10:32:33 -0500
Do you mean (series):
Output = Source - Image1 - ... - ImageN

Yes, this is possible. Just do it channel-wise (R,G,B).

---

Or do you mean (parallel):
Output1 = Source - Image1
...
OutputN = Source - ImageN

This may be possible. Map scripts, like all other components, have only one output. However, if seamless tiling is OFF, you have an unlimited plane (x,y) to work with.

Or do you mean something else?

Mehmet Sensoy, Sat, 06 Feb 2016 11:47:56 -0500
Hello,
Thank you for your answer;

I have created 5 inputs and written this code (without a coding knowledge:))
Of course it's not working at the moment,
Looking for your help.

[CODE]function prepare()
end;

function get_sample(x, y)

local originalimage = get_sample_map(x, y, SOURCE)
local image1 = get_sample_map(x, y, IMAGE1)
local image2 = get_sample_map(x, y, IMAGE2)
local image3 = get_sample_map(x, y, IMAGE3)
local image4 = get_sample_map(x, y, IMAGE4)

local originalimage - local image1
local originalimage - local image2
local originalimage - local image3
local originalimage - local image4

OUTPUT = get_sample_map(x, y, originalimage)

r,g,b,a = get_sample_map(x, y, OUTPUT)
local r = x
local g = y
local b = (x + y) / 2
local a = 1
return r, g, b, a
end;[/CODE]

Skybase, Sun, 07 Feb 2016 07:15:39 -0500
*kinda side track*

Shouldn't this be easier with just the default RGB math? Or am I missing something about the original idea.

ThreeDee, Sun, 07 Feb 2016 13:19:17 -0500
What is the supposed final output of this filter?

Say, you were using five of the built-in images. Once you've subtracted number two from number one, you have a darker image with features from both. What do you do with the third, fourth and fifth image?

Mehmet Sensoy, Sun, 07 Feb 2016 13:40:12 -0500
Actually what I am trying to achieve is to make 5-10 level separation and using bomber component (or other) create luminosity based size or repeat difference. Say brighter areas particle size for 50 px and darker areas for 10 px.

For example there is a similar filter; https://filterforge.com/filters/471.html

But additionally I would like to add custom particle and other options.

By the way I'm doing luminosity separation like this ; https://filterforge.com/filters/13579.html

Do you think if it is possible to minimize node amount using map scripts and so...?

Thank you.

Skybase, Sun, 07 Feb 2016 21:48:27 -0500
I'm pretty sure this is faster using default FF components than the map script. Likely will depend on a bajillion factors, but this should be doable with default FF stuff. As far as I understand it, it'd be pretty flexible too.

It'd be cool to do stuff with the map script regardless.

ThreeDee, Mon, 08 Feb 2016 03:32:36 -0500
Ok, I see. I'm still not understanding where subtracting a number of images from the main image fits into this. Maybe I'm thinking about a different kind of subtracting from what you are referring to. If you mathematically subtract one image from another, by the time you've subtracted two images from a source image you pretty much have a black image as a result.

Rachel Duim, Mon, 08 Feb 2016 13:49:38 -0500
Here's my take on subtractive merging. When you subtract three images together, the result is no longer in the required 0-1 range for viewing. So I added some RGB math and a gamma component to bring the image back into range. In this example I am not doing any luminance masking.

Rachel Duim, Mon, 08 Feb 2016 13:52:12 -0500
Other things to note about this method. The order of subtraction is important and will drastically change the results. Typically at least one of the images will appear as a photo "negative". Here's the filter. No controls, just an illustration of the problem.

Mehmet Sensoy, Mon, 08 Feb 2016 14:53:03 -0500
Hello,
I have attached file, it's not like what I want to achieve.
I want to make 10 level luminosity masking. Then attaching them to pattern components (for testing I have used checker component here..) Then multiblending them again. Like adaptive size tiling filter. So my main goal asking that question was because after luminosity masking and checker pattern some patterns overlap eachother.
Only way working is using double-size repeats; for example :
-100 and -80 levels : 64 repeat w/h
-80 and -60 levels : 32 repeat ...

But here I have faced with a problem that maximum repeat value is 100.
So even I started with 2...it goes 2-4-8-16-32-64-128(!) So impossible. (This technique worked for 5 level separation)

Please check my filter and help.
By the way may be there would be smarter way to separate levels if so please let me know.
Best Regards.

Rachel Duim, Mon, 08 Feb 2016 15:22:01 -0500
I think there is an easier way to mask the levels. Here is a snippet showing another method.

Mehmet Sensoy, Mon, 08 Feb 2016 16:10:08 -0500
Thank you Rick,
I applied your method and attached file. It's getting closer, I tried to do with 5 level separation because of the reason I've mentioned in my previous post. But with 10 levels it might give better results and also I would like to scatter image(s) as particles using that technique. Any ideas? Especially for 10 level separation and repeating issue (or size increments).

Thanks again.

Betis, Mon, 08 Feb 2016 16:15:44 -0500
It's a very strange output but I do believe this is what you're after based on the filter you uploaded Mehmet.

Mehmet Sensoy, Mon, 08 Feb 2016 16:37:26 -0500
Thank you Betis,
I'm going to check it right now, please check my latest attachment. If there would be a way to increase separation levels it would look more natural. And also as you may notice I again it's going somewhere else (but this one also looking good as well:) ) But in my first question I was wondering how to avoid overlapping tiles or mosaics. That was because I had asked subtraction methods. I guess for example on top layer - it would be darker areas and repeat amount would be 100 but when it's lighter repeat value might decrease. Till that part it's ok but I'm trying find a way to avoid overlaps.

Mehmet Sensoy, Mon, 08 Feb 2016 16:54:09 -0500
Thank you Betis,
I'm going to check it right now, please check my latest attachment. If there would be a way to increase separation levels it would look more natural. And also as you may notice I again it's going somewhere else (but this one also looking good as well:) ) But in my first question I was wondering how to avoid overlapping tiles or mosaics. That was because I had asked subtraction methods. I guess for example on top layer - it would be darker areas and repeat amount would be 100 but when it's lighter repeat value might decrease. Till that part it's ok but I'm trying find a way to avoid overlaps.

Rachel Duim, Mon, 08 Feb 2016 18:56:23 -0500
This latest filter (5 Level) produces halftoning! When you use the dot shape, it looks exactly like halftoning. So you have halftoning with a selectable shape for the dot.

Rachel Duim, Mon, 08 Feb 2016 19:38:16 -0500
This is a completely different take on this. I produced similar results with 1 bomber using the image luminosity to control the size of the particles directly at the bomber+ size input.

Rachel Duim, Mon, 08 Feb 2016 19:41:42 -0500
And here's the modified filter. Feel free to use it or discard it. 8)