Aus der 11. Sitzung des Hauptausschusses des Parlamentarischen Rates vom 30. November 1948

cross-posted from: https://lemmy.ftp.rip/post/199402

I've built a few DIY kits and have never run into any issues until now. And I'm not even sure if I messed up the build or the design of the module is just wonky... Turning up the decay past 11 o'clock or so causes the volume of each hit to vary, and fluctuate wildly if turned up all the way, as can be seen in the image.

I can sorta replicate the issue in the simulated circuits linked in the manual - it seems like the volume of each hit depends on what direction the wave was moving when a new hit is triggered. In some cases the volume goes up, because of resonance, in others it goes down as the newly triggered wave is muffled by being out of phase with the previous one. Interestingly the issue disappear of the pitch is turned all the way up.

Anyone else having this issue, or did I fuck up the build?

cross-posted from: https://lemmy.ftp.rip/post/199402

I've built a few DIY kits and have never run into any issues until now. And I'm not even sure if I messed up the build or the design of the module is just wonky... Turning up the decay past 11 o'clock or so causes the volume of each hit to vary, and fluctuate wildly if turned up all the way, as can be seen in the image.

I can sorta replicate the issue in the simulated circuits linked in the manual - it seems like the volume of each hit depends on what direction the wave was moving when a new hit is triggered. In some cases the volume goes up, because of resonance, in others it goes down as the newly triggered wave is muffled by being out of phase with the previous one. Interestingly the issue disappear of the pitch is turned all the way up.

Anyone else having this issue, or did I fuck up the build?

I've built a few DIY kits and have never run into any issues until now. And I'm not even sure if I messed up the build or the design of the module is just wonky... Turning up the decay past 11 o'clock or so causes the volume of each hit to vary, and fluctuate wildly if turned up all the way, as can be seen in the image.

I can sorta replicate the issue in the simulated circuits linked in the manual - it seems like the volume of each hit depends on what direction the wave was moving when a new hit is triggered. In some cases the volume goes up, because of resonance, in others it goes down as the newly triggered wave is muffled by being out of phase with the previous one. Interestingly the issue disappear of the pitch is turned all the way up.

Anyone else having this issue, or did I fuck up the build?

https://mastodon.ftp.rip/@dotmatrix/109268948523995319

My cat recently decided to go to town on one of my ELAC speakers. I contacted their support in order to buy a replacement driver, and they straight up sent me one for free :)

So, shoutout to ELAC for a very pleasant customer experience.

So I'm currently trying to set up an instance, and I'm unable to upload pictures. The following toaster appears: https://imgur.com/d0MUhUb

And in the logs I see this:

2023-06-25T10:48:11.127198782Z 2023-06-25T10:48:11.127080Z  WARN lemmy_server::root_span_builder: Request error: error sending request for url (http://localhost:8080/image): error trying to connect: tcp connect error: Address not available (os error 99)
2023-06-25T10:48:11.127262799Z Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("localhost")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 99, kind: AddrNotAvailable, message: "Address not available" })) })

I have a pictrs container up, and set the following options in lemmy.hjson:

  pictrs_config: {
    url: "http://pictrs:8080"
    api_key: "apikey"
  }

Also tried it with pictrs_url: "http://pictrs:8080" (as described here), but that didn't help either. Why is lemmy trying to access localhost:8080 rather than pictrs:8080?

Edit: This has been resolved, thanks to @slashzero@hackbox.social: https://lemmy.ml/comment/948928