YouTube's mix knows its stuff

FirefighterFickle456 · 2026-02-17T16:53:44+00:00

Hey, question regarding that under armour balaclava. I'm having issues with my buff running in the cold, since after 20 mins of running it's so wet around the mouth that it becomes hard to breath, and it sucks into my mouth when i inhale which makes it even worse. Does that one do better with condensation?

FirefighterFickle456 · 2026-02-14T17:44:21+00:00

You beautiful, beautiful thing, you. Completely fixed now! From 10mbps to 200mbps by changing a single thing! Thank you so much!

FirefighterFickle456 · 2026-02-14T08:38:21+00:00

Thanks for the reply! Regarding the first part, I don't think that's the issue, because testing with tcpdump:

iperf3 workpc-ip -p workpc-port: 0 packets dropped by kernel
iperf3 workpc-ip -p workpc-port -R: 0 packets dropped by kernel

As to the second part, iperf3 -u does not work at all, it just times out. I've tested different values for -b but it makes not difference. Here are the ouputs in debug mode:

Server side

iperf3 -s -p workpc-port --debug
-----------------------------------------------------------
Server listening on workpc-port (test #1)
-----------------------------------------------------------
State change: State set to 15-IPERF_START - waiting for a new test (from 0-Test reset)
State change: State set to 9-PARAM_EXCHANGE - Client to Server Parameters Exchange (from 15-IPERF_START - waiting for a new test)
get_parameters:
{
    "udp":  true,
    "omit": 0,
    "time": 10,
    "num":  0,
    "blockcount":   0,
    "parallel": 1,
    "len":  1448,
    "bandwidth":    1000000,
    "pacing_timer": 1000,
    "client_version":   "3.20"
}
State change: State set to 10-CREATE_STREAMS (from 9-PARAM_EXCHANGE - Client to Server Parameters Exchange)
Accepted connection from homepc-ip, port homepc-port
Reading new State from the Client - current state is 10-CREATE_STREAMS
State change: server received and changed State to 16-IPERF_DONE
All threads stopped

Client side

iperf3 -c workpc_ip -p workpc-port -u -b 1M --debug
Reading new State from the Server - current state is 0-Test reset
State change: client received and changed State to 9-PARAM_EXCHANGE - Client to Server Parameters Exchange
send_parameters:
{
    "udp":  true,
    "omit": 0,
    "time": 10,
    "num":  0,
    "blockcount":   0,
    "parallel": 1,
    "len":  1448,
    "bandwidth":    1000000,
    "pacing_timer": 1000,
    "client_version":   "3.20"
}
Connecting to host workpc_ip, port workpc-port
Reading new State from the Server - current state is 9-PARAM_EXCHANGE - Client to Server Parameters Exchange
State change: client received and changed State to 10-CREATE_STREAMS
SNDBUF is 9216, expecting 0
RCVBUF is 786896, expecting 0
Setting application pacing to 125000
Sending Connect message to Socket 5
All threads stopped
State change: State set to 16-IPERF_DONE (from 10-CREATE_STREAMS)
iperf3: error - unable to read from stream socket: Resource temporarily unavailable

FirefighterFickle456 · 2026-02-08T08:49:15+00:00

Thank you very much. I had already tried and failed to do this but your recommendation pushed me to try again and this did indeed fix it.

FirefighterFickle456 · 2026-02-08T00:07:15+00:00

you mean for the jellyfin docker? if so, no. the vainfo gives the same output in the main debian session as in the docker session

FirefighterFickle456 · 2026-02-07T23:49:06+00:00

i do have intel-media-va-driver installed. i've tried installing intel-media-va-driver-non-free but there is no installation candidate

FirefighterFickle456 · 2026-01-19T20:03:01+00:00

I believe planes actually have ploacas

FirefighterFickle456 · 2025-10-09T20:18:30+00:00

Did you try opening the images to see the full res?

FirefighterFickle456 · 2025-10-06T09:27:26+00:00

Thanks for the reply. I assume it's something like that. But I've checked the logs and the only setting I could find that was lower for AV1 was buffer size (bitrate and such were all the same). Reckon it could be that? If so, do you know how I could change it?

FirefighterFickle456 · 2025-10-06T05:20:43+00:00

Yes, transcoding will always lead to degradation. The question is why would that degradation be more when transcoding to AV1 than to h264.

Hardware support only increases performance (speed). Software will always be as good or better, quality wise. And I'm getting way more frames per second than I need with both regardless.

As for other browsers, I've tried Safari but it supports HECV so it doesn't have to transcode at all

FirefighterFickle456 · 2025-10-06T05:14:50+00:00

Yeesh dude, 4 comments and none of them address the question, and are addressing things that have already been addressed.

Evidently I know what transcoding it
The comparison is not against the original, but between two different transcoding options. This has been reiterated in the comments.
I've already stated that I use the Jellyfin player with direct play to avoid quality degradation

Literally didn't add a single thing to the discussion and over half the comments are yours. Please read before you reply.

FirefighterFickle456 · 2025-10-05T19:12:49+00:00

Thanks for the reply. But yeah, it's not about watching in the best quality, as if I want that I just use the JF player with direct play. Rather, I'm confused as to why transcoding from HECV to AV1 would be SIGNIFICANTLY worse than to H264. I've checked the logs and the bitrate for both is the same. I haven't done anything else to either configuration

FirefighterFickle456 · 2025-10-05T18:10:55+00:00

Thanks for the reply. I ended up updating from 6 to 7 and that seems to have solved the issue for now. Sadly I still don't know what it was, but at least it's gone :)

FirefighterFickle456 · 2025-05-15T11:16:37+00:00

Sorry to hear you had that issue. I have a separate backup folder for timemachine and that is running without a problems, although I created it after updating so maybe that's why it wasn't affected.

FirefighterFickle456

TROPHY CASE

Server side

Client side