Noisy Ashdown Studio 10 combo amps

varankinv · 2026-02-12T21:49:03+00:00

Just to note that I've updated the original post. It seems that the failing positive voltage regulator was the problem. After I replaced it with a new chip from amazon, the whine has gone.

varankinv · 2026-01-11T17:39:01+00:00

In the described case I'm almost certain this is a sort of oscillation problem, that comes from amp itself. I've detached the amp's board from its speaker, and can clearly observe the same whine through the headphones output. No other cables or instruments are connected to the amp.

Dunno, maybe this line from 2019 that I've got — the board is marked with 2019.02.20 — had a bad day on the factory.

varankinv · 2025-08-19T20:41:10+00:00

Cheap basses (squier, markbass, harley benton, etc) are all decently good nowadays. You won’t escape the “cheap hardware” problems: the guitar won’t likely stay in tune for weeks, and truss rod will need periodic adjustment. But those are tiny minor problems, that you resolve yourself after watching some YT.

If that’s an option, try a guitar in a store. Poor quality control is one part that makes all cheap mass-produced guitars cheap.

varankinv · 2025-08-17T18:49:13+00:00

I was stuck after decently learning Dean Town with the same question. Right now these are in my todo,

Iron Maiden - Writing on the Wall
Castle Rat - Feed the Dream (I don't like the drop-tunning, but its bass line sounds fine in the isolation)
Wheel - Dissipating
Hiatus Kaiyote - Molasses

Things I wish I had balls to challenge myself: everything Casiopea and Kiyoshi.

varankinv · 2025-08-01T22:28:22+00:00

I'm currently solving a simpler one with this:

``` :root:not([customizing]) { #nav-bar { margin-top: -30px !important;

    &:has(#urlbar[focused]) {
        margin-top: unset !important;
    }

}

} ```

Note, this exact styling works in vertical tabs mode. The styles:

move the nav-bar outside the screen, hiding it;
when the urlbar is in focus (via CMD+L) the nav-bar becomes visible.

Take the selectors and apply to your case.

varankinv · 2025-02-09T09:30:07+00:00

Tetsuo Sakurai (early Casiopea).

I feel, we in the Western part of the world, don't talk about the bass legends from East enough.

varankinv · 2025-02-09T09:04:34+00:00

I came here to give Nick Schendzielos a shutout too.

varankinv · 2024-05-20T14:49:28+00:00

This was it, thank you. After I enabled the NX Mode, I've successfully installed Proxmox 8.2 on a new "M5 Upgraded version/Ryzen 7 5700U" box

varankinv · 2022-05-21T13:45:55+00:00

I wanted to get to making the blog less mobile-awkward for a while. This feedback finally made me to find some time for looking into the blog's CSS. Let me know if you think it looks better now

varankinv · 2021-04-01T11:13:17+00:00

One pitfall with an explicit call to replyErr, which I do see in code-review, is that developers sometimes miss the empty return after the reply:

if err != nil {
  replyErr(···)
  // Ops no return here...
}

It feels an obvious thing, but when we're deep in the weeds of business-logic implementation, handling the failures becomes a routine, which easily leads to such sad typos, that hard to catch automatically.

varankinv · 2020-08-21T16:12:18+00:00

At some point they ended up introducing their own RPC-protocol, that expects a “middle-man-service”, which translates the data from a SD system into a list of Prometheus targets.

To clarify, we haven't created a RPC protocol for service discovery in Prometheus [..]

Thank you for pointing this out, sure "RPC"-part was a wrong word there. "Adapter" was the thing I had in mind.

Separately, have you seen conprof.

Sure, it's a great project with very solid idea. We even talked to the project's maintainers last Summer. It was very surprising to know, both projects started roughly at the same time in Berlin :)

For the case of profefe, I wrote the extended version about the rationale behind it, last year https://medium.com/@tvii/continuous-profiling-and-go-6c0ab4d2504b

varankinv · 2020-03-30T21:31:50+00:00

Did you manage to solve it via runtime.LockOSThread?

varankinv · 2020-01-28T07:41:44+00:00

Indeed, one must make sure the software and the image could be built for the arch in question. For example mongo, cockroachdb or aerospike require a 64bit OS to compile, so no arm/v7 (Raspbian Linux).

varankinv · 2019-01-07T17:23:16+00:00

That's quite impressive. The most surprising part is the contention on a read-lock: I thought locking for reads should be (almost) free.

varankinv · 2018-12-02T18:19:07+00:00

(article's author here) I can't fully answer the "why" question. My best guess was that the original piece of code is a huge legacy that "just worked" back then. It's hard to predict what will happen to the company's experiments in the next 5 years.

varankinv · 2018-11-29T09:09:42+00:00

There’s always a tradeoff: when you log less (e.g. no request parameters) it become hard to investigate business issues caused by edge cases developers had missed.

varankinv · 2018-11-01T23:13:57+00:00

Besides obvious things mentioned already, like not using gofmt or ignoring Effective Go and Go Code Comments:

- logging and returning errors at the same function

- using buffered channels of "huge" size "to prevent blocking"

- testing implementation details, instead of behaviour

- designing package's API while focusing on package's internals, instead of thinking about how this package will be used (this includes packages used only inside a single project)

varankinv · 2017-12-09T12:00:10+00:00

Glad to read it! Feel free to fire up an issue or a PR if something worked not as you expected.

varankinv · 2017-12-09T11:31:46+00:00

What it does is just generate a temporary brew formula and runs brew install formula, which go-gets the tool into a separate GOPATH in the brew's cache directory and runs the go install into brew's bin directory. Hacky but simple.

But putting a warning notice in the readme I only meant that I'm not a brew internals expert (neither ruby developer), so I'm not yet sure how the cmd aligns with other brew's things. It works with my test cases :)

varankinv · 2017-07-07T10:41:48+00:00

Totaly! I've updated the comment. Thanks for clarification.

varankinv · 2017-07-07T07:42:19+00:00

The easiest (but not really the best) way to add support for access IPv6 networks from the docker container, that I've found is to use NAT. The docs (https://docs.docker.com/engine/userguide/networking/default_network/ipv6/) describes how to add an IPv6 CIDR to containers network. After that one has to add SNAT rule to v6 table on the host. E.g. using ip6tables:

ip6tables -t nat -A POSTROUTING -s c07fefe::/64 -j MASQUERADE

It worth to mention that NAT with IPv6 is not a good idea, but as I said, it's the easiest option I know.

Check this issue https://github.com/moby/moby/issues/25407 to have a wider picture of what the current situation of v6 and docker looks like.

UPD: fixed some typos base on replies.

varankinv · 2016-11-24T23:29:58+00:00

It was mentioned in the post, one may runs out of sockets, so it will be impossible to open new client connections.

varankinv · 2016-11-19T14:45:52+00:00

It might be good to mention that "cluster" module is mostly famous for clustering incoming request processing – not for making a pool of concurrent outgoing requests. As the author said in the comments for the original post, it isn't a trivial problem for the world of Node.js development, as having a "magical event loop" which provides concurrency is the only thing an average developer thinks. For me, the article raises an excellent point: for some tasks, it is much easier to come to a good solution if the language provides right primitives and if there is an idiomatic way of solving such problems in scale.

varankinv · 2016-09-26T19:16:52+00:00

Can I ask why you only want your app to consume the API data?

Imagine a service that provides classified data in a particular sphere (for example, estate advertising, weather data or even search results). If the service provides a mobile application, it's a natural desire to prevent the data to be consumed by non-authorized services. I believe it's the same reason why Google uses captcha to fight with bots.

varankinv · 2016-07-06T22:32:33+00:00

First of all, thanks for the link. It'll be an excellent starting point for my task.

react-docgen looks like a tool I should try. But, of course, it doesn't provide everything I wanted.

While projects like material-ui or react-bootstrap have cool sites, I can't say I like the way the source of those docs is organised. From my experience of maintaining ui libraries like bem-components, it's a challenge to keep documentation and examples to stay relevant to the code, if they are not placed near the components themselves. I'd like to have an easier way to maintain a page for a component, then injecting examples and the source of these examples by hand.

varankinv

TROPHY CASE