spectrome / patchcab Goto Github PK

When I run yarn build in my local checkout, the screenshots it produces in modules/ directories all use the default (seriffed, in my case) fonts rather than the expected Routed Gothic.

I thought perhaps it was just my own modules but this happens even when I run yarn build in the main @patchcab/modules package too, e.g:

I added some logging to capture the js dev console output in screenshot.ts and it says this, which may be relevant:

PAGE LOG: %c * Tone.js v14.7.77 *  background: #000; color: #fff
PAGE LOG: The resource http://localhost:3000/assets/routed-gothic.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
PAGE LOG: The resource http://localhost:3000/assets/routed-gothic-wide.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

If I pause and inspect the elements in devtools, it looks like they have the proper font-face property (and the files apparently loaded successfully, per the logs above), it just isn't rendering the right font.

I hesitate to really call this a "bug" since vercel seems to generate these screenshots without this issue when it runs build, so I suspect the problem is somewhere on my end, but do you have ideas for things I should double-check?

So far, I've tried:

• in screenshot.ts: adding --font-render-hinting=none to puppeteer.lauch args
• in index.html:
  • adding type="font/woff2" to the <link rel="preload"... links for the fonts
  • changing font-display to block' in the @font-face` CSS rules

Kind of grasping at straws here. Any other ideas?

Environment:

• OS: macOS 10.15.6
• Browser (the one launched by puppeteer): Chromium Version 88.0.4298.0 (Developer Build) (x86_64)

Is this feature request for a module or Patchcab in general?

• [ x ] Module

Describe the solution you'd like
Oscilloscopes IRL usually have a "triggered sweep" feature:
https://en.wikipedia.org/wiki/Oscilloscope#Triggered_sweep

It would be nice for the included OSC module to offer this as well.

It's very helpful for understanding the shape of a periodic wave.

I would be happy to write up PR for this if you don't already have plans to implement it.

This is a super cool project by the way! I had started to build something similar (using Web Components instead of Svelte, but whatever...) and this saves me a ton of work!

Hi Richards!
I found a small bug in Patchcab.
I added a new module and it appeared on top of the existing one. Now I cannot move them, they are stuck.
The only way to move them is to delete one of them.

Thank you for making such a wonderful open source modular web synthesizer!

Describe the bug

When running npx patchcab, these lines in bin.ts cause my ./modules directory to be destroyed:

./modules seems to be a source directory - why is it being deleted?

To Reproduce

• git clone
• yarn install
• npm run build
• npx patchcab

Environment:

• Ubuntu 20.04
• vscode

Vercel does not find the patchcab binary from ./modules directory on the build step.

Is this feature request for a module or Patchcab in general?

• Module
• General

First of all, I'm mindblown that this exists - THANK YOU! ❤️❤️❤️❤️

I found this repo when I had the idea to implement an LFO on a completely non-audio related project. I was thinking that it would be really nice to have modular-style cv tools that could modulate any JS variable, especially if it was playable and patchable (like the slider values of a stylegan toy or something)

How difficult would it be to package a small single row instance of patchcab as a svelte component to be dropped into any app? I'm imagining a CV out module that you could drop in a <slot /> and bind each jack to whatever variable you want and use it in your app.

That way you could use LFOs, sequencers, noise, etc to control literally anything, even outside of a musical context!