Frees up the CSS color.

inthar — Today at 4:45 AM

May I suggest rd?

inthar — Today at 6:48 PM

I think this way of defining log is a bit confusing from the perspective of standard math notation. How about making the binary operation l?

It's not great that the meaning of ^11 changes depending on context.

• Absolute reference
• Reflected reference
• Inverted reference

Limits on the maximum scale size and computation (gas).

Component-wise min/max on monzos.

Leaves room for more numeric flavors in the future.

Break into issues as necessary

Root scale declaration
# = 4::8

Rest
. (one beat)
.. (two beats)

Beat duration declaration
. = 300ms

Time signature declaration
T = 4 (four beats per bar)

Barline
| (runtime error if in the wrong place according to the time signature)

Repeated section
|: foo bar :|x3

Duration literal
d1/2 (half a beat)

Duration labeling
3/2 d2 (a fifth from 1/1 lasting two beats)

Time advancing
1/1 5/4 3/2 . 2/1 (root, third, fifth, rest, octave)
[editor's note: Feels fragile. How is 440 Hz not 440 followed by 1Hz?]

Duration extension
(empty statement)

Pedal
1/1 ?? 5/4 3/2 (root lasts for three beats here)

Rewind
1/1 , 6/5 , 3/2 (this is a simultaneous chord)

Playhead
|> (start playback from last occurrence)

Playstop
>| (stop playback when encountered)

Timestamp
T

Jump to timestamp
@T

Duration multiplication
&
n => n & 3 (mainly useful for mapping)

The browser can use them as is.

Less this.get('$') as Interval[] acrobatics.

dX — Today at 7:23 AM

also u should add somethig to make it so that you can auto color the notes
(i dont like the color grey and am lazy)

frostburn — Today at 7:25 AM

So you'd like this to be a toggleable preference and for the app to auto color every time?

dX — Today at 7:27 AM

i was thinking it'd be a thing you can do in the modify scale category but thats also good

(-2)^3 is -8 so (-8) /_ (-2) should be 3.

#0 is always 1/1
#1 is $[0]
Indices that go beyond the size of the current scale stack like they do in Scala/Scale Workshop.

This is more relevant to making music tracks than making scales.

marvel = <1200.5978, 1901.3543, 2785.0245, 3369.7682]!

s is a useful variable name that should be overrideable.

s = %Hz

Needs updates to default string representation too.

1_234_567

This shouldn't clash with anything if it's solo.
1,5 lime "fifth"

Use prefix c to multiply by 2.
Use prefix ` to divide by 2.

https://en.xen.wiki/w/Chain-of-fifths_notation

Same as ^?

Basically text-based diamond-MOS but with fractional JS semantics.

29791 rdc 31 should be 31 but seems to evaluate to 1 instead.

Domain info is needed for correct formatting.

It might be nice to see temperament at the top of the source instead of at the bottom. Would play nicer with the lattice too if it was the UI's responsibility to apply tempering.

LiftPizzas — Today at 8:39 PM

Maybe even "z" or "h" as a prefix/suffix to signify hertz
Something single-key is way better. It's only one or two more keys, but it really adds up when you're trying to enter a bunch of them. 🙂
Especially if you're 10-keying the numbers.

PI = 3.14159r instead.

Frees up ! for movement in time. (Probably going to be the same as XenPaper's -.)

[3^i red 2 for i of [-11..11]]

import * from prelude
import {mtof, PI} from prelude
import * as utils from utils#v0.1.0@frostburn
export riff plusOne x {x+1}

The FJS accidentals take at least two characters to do anything so a single arrow which always points in to right direction could help.
Don't bother with mids, we already have neutrals and half-augmented for that.

Duration is how long the note sounds.
Logical duration is how much space the note takes up.

! extends duration and logical duration.
? extends duration only.
. extends logical duration only.

If there is no note on the sheet yet a special Silence note is created to hold the implied durations.

Reflection.

0.5° 🌜 — Today at 1:35 PM

BTW also how about considering simple typing annotations (just matching types at runtime when a function is called, before any possible type errors in calls to primitives in its body) if all values can be split into a small set of disjoint types (like ratio, logarithmic interval, number, pitch; were frequencies distinct from all of those too?; then scale of pitches and... what else was there?). In that case it would be simple to annotate and check, but for user-defined functions that don’t conform to those types one would need to drop annotations (and runtime checks) to some of the parameters

Extend gcd and lcm to multiple parameters for
gcd(...$)

reversed, reduced etc.