dktr0 / punctual Goto Github PK

Hi David,
I've been preparing a demo for my workshop on my laptop and finding a significant number of unexpected things occurring with continuous functions.

I've verified the same issues are operating system independent, so I believe it's related to hardware not drivers:

1. sin behaves like saw
   https://youtu.be/Vpp4NWBaqaM

2. spin with a time graph outputs to the entire screen space for a brief period every cycle, but then resets the spin so it doesn't complete a cycle
   https://youtu.be/e3omnOFhIRE

the punctual-standalone-0.4.2.zip release doesnt include style.css from this repo, so running the app presents a somewhat confusing white screen.

Not sure if this is the right place for it...

I was just trying a frequency-modulation expression as a position, and it seems like the values go out of range somewhere.

In audio, frequency modulation works exactly as you would expect.

sin ((sin(220) + 1) * 220) * 0.2 >> centre;

// sounds basically the same as SuperCollider
a = { SinOsc.ar((SinOsc.ar(220) + 1) * 220, 0, 0.2).dup }.play;

OK, let's translate that to graphics:

-- no FM, this is OK
circle [sin(0.05) * 0.5, sin(0.06) * 0.5] 0.25 >> rgb;

But:

-- huh?
circle [sin(sin(0.01) * 0.02 + 0.03) * 0.5, sin(0.06) * 0.5] 0.25 >> rgb;
circle [sin(0.05) * 0.5, sin(0.06) * 0.5] 0.25 >> green;

sin(0.01) * 0.02 + 0.03 should range between 0.03 +- 0.02 = 0.01 to 0.05, but the white circle quite obviously moves much faster than the green one at times. That would be explained only if the calculation is being done incorrectly. But the calculation seems to be correct for audio. I'm mystified.

Forcing order of operations with extra brackets doesn't help: sin(sin(0.01) * 0.02 + 0.03) and sin((sin(0.01) * 0.02) + 0.03) appear to behave identically.

lpf (saw (23m)) (250 ~~ 350 $ sin 1) 10 * (-20) db >> left;
lpf (saw (23m)) (300 +- 50 $ sin 1) 10 * (-20) db >> right;

Why are these not the same? I might expect some phase shift on the modulator but the right channel seems totally wrong.

Option #3 from discord - using y = fract (abs x) to remap input range so that it mirrors out around 0 and tiles infinitely - is probably the way to go.

Hi dr. 0,

So found that commeting does not really works as one would except:
If you have a line of code, that you want to comment out, then Punctual will give you an error if you do not also remove the ending semicolon of that line:
No comments:

Error when trying to make a comment, after removing the semicolon:

Comment accepted, but now you have to remember to add the semicolon if you want to use your code again:

And it looks to be the same in Estuary:

All the best
Søren Peter

like move but with an implicit tile 1 so that things wrap.

useful for implementing/emulating XOR, among other many things, no doubt!

None of the examples in the Punctual Reference in the browser work, eg sin 440 => centre

Hi there, I discovered Punctual through a workshop last week, and it seems really fun and interesting. However, I was wondering what functions I may be missing from the documentation? I know of several things, such as fdbk and fb, which don't appear in the REFERENCE.md. Is there a recommended way in the code to "grep" for the list of current functions?