phab

Fourier Audio | Full-Stack Engineer | Full-Time | Remote / London, Visa | https://fourieraudio.com/join

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an UK pro-audio startup backed by one of the world's biggest entertainment technology groups, looking for passionate engineers driven by a desire to build seriously excellent pro-audio products. We want people with an eye for detail, who relish the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent. You’ll join a focused and driven team intent on changing the (live audio) world.

Our stack:

- Rust & Typescript (Electron+React)

We offer:

- Remote or Office

- Startup vibe, experienced group stability

- Work on gear used on the biggest gigs in the world

I can answer any questions (email in profile, include HN in subject). Full details and to apply:

- https://fourieraudio.com/full-stack-engineer

Fourier Audio | Full-Stack Engineer | Full-Time | Remote / London, Visa | https://fourieraudio.com/join

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an UK pro-audio startup backed by one of the world' biggest entertainment technology groups, looking for passionate engineers driven by a desire to build seriously excellent pro-audio products. We want people with an eye for detail, who relish the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent. You’ll join a focused and driven team intent on changing the (live audio) world.

Our stack:

- Rust & Typescript (Electron+React)

We offer:

- Remote or Office

- Startup vibe, experienced group stability

- Work on gear used on the biggest gigs in the world

I can answer any questions (email in profile, include HN in subject). Full details and to apply:

- https://fourieraudio.com/full-stack-engineer

Fourier Audio | Full-Stack Engineer; Quality & Reliability Lead | Full-Time | Remote / London, Visa | https://fourieraudio.com/join

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an UK pro-audio startup, looking for passionate engineers driven by a desire to build seriously excellent pro-audio products. We want people with an eye for detail, who relish the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent. You’ll join a focused and driven team intent on changing the (live audio) world.

Our stack is Rust & Typescript (Electron+React); I can answer any questions (email in profile, include HN in subject).

Full details and to apply:

- https://fourieraudio.com/full-stack-engineer

- https://fourieraudio.com/quality-reliability-lead

Fourier Audio | Full-Stack Engineer | Full-Time | Remote / London, Visa | https://fourieraudio.com/join

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an early-stage UK pro-audio startup, looking for passionate full-stack engineers driven by a desire to build seriously excellent pro-audio products. We want someone with an eye for detail, who relishes the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent. You’ll join a focused and driven team of 5 intent on changing the (live audio) world.

Our stack is Rust & Typescript (Electron+React); I can answer any questions (email in profile, include HN in subject).

Full details and to apply: https://fourieraudio.com/full-stack-engineer

I found this article enlightening; an example of where a little formalism/structure (in the notion of the four registers) really helps identify the missing pieces in the wider picture.

I did find the use of the term "register" slightly jarring given its somewhat overloaded nature between its natural language meaning, used here, and also the sense of "a specific place in which to store a datum". Reading the Wikipedia page on the term, I came across "diatype", which to me seemed to convey the same meaning without the potential confusion from the polysemantics of "register"...?

Fourier Audio | Rust+TypeScript | Remote (UK) / London | https://fourieraudio.com/founding-engineer-4-22/

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an early-stage UK pro-audio startup, looking for seriously excellent engineers to build seriously excellent pro-audio products. We want people with an eye for detail, who relish the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent.

You'll join as employee #4/5/6 in a focused and driven team intent on changing the (live audio) world.

Our stack is Rust, TypeScript (Electron+React) & ChucK; happy to answer any questions (email in profile, include HN in subject).

Full details and to apply: https://fourieraudio.com/founding-engineer-4-22/

Fourier Audio | Rust+TypeScript | Remote (UK) / London | https://fourieraudio.com/founding-engineer-4-22/

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an early-stage UK pro-audio startup, looking for seriously excellent engineers to build seriously excellent pro-audio products. We want people with an eye for detail, who relish the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent.

You'll join as employee #4/5/6 in a focused and driven team intent on changing the (live audio) world.

Our stack is Rust, TypeScript (Electron+React) & ChucK; happy to answer any questions (email in profile, include HN in subject).

Full details and to apply: https://fourieraudio.com/founding-engineer-4-22/

What does brandifious mean? A google search doesn't return anything.

You're right, it's Vim + a bunch of other editors, but when you scan the page that's not what you read - it scans as "Dark theme for vim", not "Dark theme for vim and a bunch of other editors"

I found the auto-retyping-animation product description on the site very misleading. As I scanned the page I read "Dark theme for Vim", and was immediately confused. Only when I returned to the top of the page did I notice that there was some silly animation which "retyped" Vim for a variety of other editors.

Why not just accurately say what it is?

Fourier Audio | Founding Full-Stack Engineer | Full-Time | Remote / London | https://fourieraudio.com/jobs

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an early-stage UK pro-audio startup, looking for a seriously excellent full-stack lead engineer driven by a desire to build seriously excellent pro-audio products. We want someone with an eye for detail & who relishes the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent.

You’ll join as employee #3 in a focused and driven team intent on changing the (live audio) world.

Our stack is Rust, Typescript (Electron+React) & ChucK; I can answer any questions (email in profile, include HN in subject).

Full details and to apply: https://fourieraudio.com/founding-engineer/

There's some french guy who made some maths that might help with this, idk ;)

--pb, CTO of Fourier Audio Ltd.

I'm not sure it makes sense to separate "vertical" correctness from "horizontal" correctness when it comes to "did the feature behave" though; to extend the example in TFA, if your fade progress went from 0->0.99 but then stopped before it actually reached 1 for some reason, you might find that you still had a (small, but still present) signal on the output, which, if the peak-peak amplitude was < 0.1, the test wouldn't catch.

Obviously any time you're working with floating-point sample data the precise values of floats will almost always not be bit-accurate against what your model predicts (sometimes even if that model is a previous run of the same system with the same inputs as in this case); it's about defining an acceptable deviation. I guess what I'm saying is that for audio software, a peak-peak error of 0.1 equates to a signal at -20 dBFS (ref DBFS@1.0) (which of course is quite a large amount of error for an audio signal), so perhaps using higher-resolution graphs would be a good idea.

(Has anyone made a tool to diff sixels yet? /s)

This approach is neat for observability, but it's worth noticing that it essentially quantises all of your samples down to the vertical resolution of your graph. If you somehow introduced a bug that caused an error that was smaller than the step size then these tests wouldn't catch it.

(e.g. if you somehow managed to introduce a constant DC-offset of +0.05, with the shown step size of 0.2, these tests would probably never pick it up, modulo rounding.)

That said, these tests are great for asserting that specific functionality does broadly what it says on the tin, and making it easy to understand why not if they fail. We'll likely start using this technique at Fourier Audio (shameless plug) as a more observable functionality smoke test to augment finer-grained analytic tests that assert properties of the output waveform samples directly.

Fourier Audio | Founding Full-Stack Engineer | Full-Time | Remote / London | https://fourieraudio.com/jobs

Fourier Audio is revolutionising the way audiences experience audio by reinventing the tools used by designers to shape sound for live productions.

We’re an early-stage UK pro-audio startup, looking for a seriously excellent full-stack lead engineer driven by a desire to build seriously excellent pro-audio products. We want someone with an eye for detail, who relishes the challenge of a wide remit with scope to innovate. We believe in freedom & responsibility; working with excellent people and letting them be excellent.

You’ll join as employee #3 in a focused and driven team intent on changing the (live audio) world.

Our stack is Rust, Typescript (Electron+React) & ChucK; I can answer any questions (email in profile, include HN in subject).

Full details and to apply: https://fourieraudio.com/founding-engineer/

all fucked up

And they have a fun interactive game you can play to defuse the bomb too! https://www.damninteresting.com/interactive/zab/

I have no need for MS packages, and so I simply

  for broken_apt_repository in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $broken_apt_repository; done

https://www.google.com/search?client=firefox-b-d&q=NOMFP

(It's a quote from the UK political satire series "The Thick Of It", in which the character Malcolm Tucker remarks, "NOMFP. N-O-M-F-P. Not My Fucking Problem. I quite like that. Did you like that? I'll use that quite a lot today.")

The packages.microsoft.com repositories are regularly broken, which results in perennial build failures if you use GitHub Actions which includes it by default.

GitHub's response to "your default configuration is broken" was basically "welp, NOMFP":

https://github.com/actions/virtual-environments/issues/3410

This should really have a [2019] tag

https://pages-themes.github.io/cayman/

Of course, slow moment. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Clearly I'm missing something - in BadKarma, why does the compiler not baulk at sk_filter being passed a struct amp_mgr* instead of a struct sock* as expected? A type confusion like that ought to be prevented during typecheck, no?

https://en.wiktionary.org/wiki/%D8%A8%D8%B3%D9%85_%D8%A7%D9%...

I spent a summer interning with MIPS hardware when they were owned by Imagination. It's kinda odd to see something you helped make die (be killed?) like this.

Strong "not with a bang but a whimper" vibes in my office today.

The last release was in 2018, the changelog is inaccurate (https://sourceforge.net/projects/cscope/files/cscope/v15.9/)

The changelog on that page is inaccurate, the last release was in 2018 (https://sourceforge.net/projects/cscope/files/cscope/v15.9/)

This very elegantly explains how passband-style frequency based smoothing algorithms work... without trying!

It's interesting that they state that the train was moving, but not how fast. My understanding was that one of the challenges with doing good mobile broadband on trains (esp. for VoIP applications) is how seamlessly you manage the handover between cells makes a big difference to real-world usability. If the train was going pretty slowly that would obviously make your time-per-cell a lot higher / % of time spent performing handoff a lot lower...