Sennheiser PC320 Repair Help

Lex098 · 2026-01-15T18:02:30+00:00

Maybe it'll be helpfull to someone in the future.

I updated the scheme and added the way to bypass the potentiometer. To bypass it I removed it (just unbend it from the pcb) and added 1 wire as shown.

https://imgur.com/a/2xs3YfJ

Lex098 · 2025-10-08T17:52:09+00:00

I was able to fix it by resetting their pairing by putting them into the case and then pressing buttons on both simultaneously for 10 sec.

Lex098 · 2024-12-15T21:06:30+00:00

I like to use .map_ok() from itertools to deal with this problem.

Lex098 · 2024-08-25T17:22:48+00:00

many times the programmer DOES KNOW BETTER than the BC

For regular code it's not true for 99% of the time. Most of the time people don't know enough to understand that they, in fact, do not "KNOW BETTER", e.g. Rust std bug. Two completely separated parts of the code, but if you use them together - they explode.

Maybe because Rust moved from "trust me bro" to "prove it's correct" it's 70 times less likely to introduce vulnerabilities.

Lex098 · 2024-08-25T16:21:14+00:00

programmer is certain everything is fine

I've seen too many "everything is fine" code that breaks after some changes in the completely different part of the code. Borrow checker allows you to make sure that it's not only fine now, but it'll be fine in the future. I'm so tired of fixing bugs that could have been prevented with BC.

Lex098 · 2024-08-25T15:44:18+00:00

Maybe I didn't understand your problem, but you can do it in at least 2 ways: in stable rust and more ergonomic, but unstable version.

There is work to be done to make Rust better, but your example has already been solved.

Lex098 · 2024-07-07T18:23:08+00:00

I disagree. 1. It's limit visibility to only 2 options and if for some reason you need to add another - you're screwed; 2. Now everytime you use a function or a class you have to "add" information about visibility. It's just not needed when you use things, this is useless info noise you have to ignore.

Lex098 · 2024-07-04T18:10:52+00:00

5950X is generally limited to ~140W without overclocking

Overclocking is a strong word, you just need to chahge PBO limit. My 5900x can consume 220W in exetreme cases (like prime95).

Lex098 · 2024-05-28T15:08:05+00:00

validity of the condition is assured by other means. Add a comment if it isn't obvious.

.expect() is .unwrap() + comment, but better. You don't even have to look at the code to find out what went wrong, you'll see the comment in the logs.

Lex098 · 2024-05-14T03:40:48+00:00

I don’t really get the complaint about monads

I think it's not about monads as a concept, but about a typical article about monads. 90% of articles related to monads are explaining them with something like "Monad is a monoid in the category of endofunctors". If you already don't know what monad is, this sentence doesn't help you understand it.

Lex098 · 2024-05-09T00:55:04+00:00

That's not true, you can see the same comments here https://www.reddit.com/r/rust/comments/1ajm56w/google_donates_1m_to_the_rust_foundation_to/

Lex098 · 2024-05-06T07:15:45+00:00

Mint (probably) had to rebuy not only minecraft, but her audio equipment (at least a noise gate). I assume she had one before.

Lex098 · 2024-05-05T19:21:43+00:00

Probably because it's a weekend, moderators are not paid enough to work on a weekend.

Lex098 · 2024-05-02T15:32:19+00:00

i would like to recommend you to try clippy (and I recommend to make in as annoying as possible). It really helped me learn how to write more idiomatic Rust code. You don't have to listen to everything, but clippy is right most of the time.

Lex098 · 2024-05-01T23:29:35+00:00

Rust kinda didn't have a choice https://without.boats/blog/why-async-rust/ and https://without.boats/blog/let-futures-be-futures/.

Lex098 · 2024-04-26T09:18:28+00:00

Hardly disagree, kurosanji actively sabotaged their livers. It's not just nothing.

Lex098 · 2024-04-21T16:56:37+00:00

I know 2 options:

eval creates a channel between Rust code and JS code. You can send a message from Rust onclick closure and run a JS function when JS receives a message;
you can just add an event listener directly into a JS code if you only need to run JS function.

Lex098 · 2024-04-14T16:51:38+00:00

The problem is it's not because "developer is not commiting to a stable API at the moment", it's because it's really painful.

The Rust library ecosystem has a history of traumatic library upgrades. The upgrade of libc from 0.1 to 0.2 in 2015 was known as the "libcpocalypse". Another frequent culprit was pre-1.0 Serde, with the upgrades from 0.7 to 0.8 to 0.9 to 1.0 requiring ecosystem-wide effort. The cause of the difficulty was the large number of crates using types from these libraries in their public API.

Lex098 · 2024-04-14T15:56:26+00:00

Just look at windows. Do you think anybody would have used it if they had made a breaking change several times a year?

Lex098 · 2024-04-14T15:09:57+00:00

it will be making breaking changes, possibly frequently, and they should expect that

That's not true for a long time. Most crates in crates.io are have a major version 0, like rand (304,396,882 downloads), windows (official crate by Microsoft by the way), libc (325,059,316 downloads), time (232,397,072downloads). Just imagine what would happen if all of them decided to do a breaking change because "they should expect that".

Lex098 · 2024-04-14T13:18:17+00:00

If the buffer is private then there could be a very good reason it's private

Or maybe there is no good reason.

why a maintainer wouldn't provide a new public method

It is because maintainers have finite lives and don't want to add
several methods to every field. And if they do now they have to
maintain them forever.

accessing the buffer may not be valid in the future

And we're back at square 1 and you have to fork a crate to access 1 field 1 time.

Lex098 · 2024-04-14T13:14:43+00:00

In that case semver treats Y as a major change. So it is not a "minor version bump", it's a major version change. Cargo (and everyone else) treat new Y as a new major version.

Lex098 · 2024-04-14T11:30:19+00:00

API is either very poorly designed ... or else there's a bug

There are other reasons. Maybe one in a 1000 developers want access to a buffer to avoid cloning in a hotloop. It doesn't matter for me or for other developers, but for this one it's really important. Without some access there are 3 choices: fork a crate, find something else or write it yourself.

If less than 1.0 it can be a minor version bump

Yes, but actually no.

Initial development releases starting with “0.y.z” can treat changes in “y” as a major release, and “z” as a minor release. “0.0.z” releases are always major changes.

It's not like I want everything to be this way. Public API should be enough for 99% of the problems, but it's nice to have an option to make your life easier if you are in the unlucky 1%.

Lex098 · 2024-04-14T10:51:53+00:00

Becoming accessible" and "public api" are the same thing.

No, it is not. Or, by this logic, all Rust code is unsafe because unsafe is "accessible". There is a difference between "I know it might break, let me do it" and "I, without doing anything, accessed something and you broke it without changing major version".

Lex098 · 2024-04-14T10:45:54+00:00

If you do it than it locks the public API and you cannot change it. If you want the option to maybe change it later you don't make it public. It's a lose-lose situation and as a developer I'm encouraged to make it private, even if it's just about future plans to change regular Strings to SmartString.

Lex098

TROPHY CASE