Live data from Hacker News

Asahi Linux Progress Linux 7.0

asahilinux.org

271–280 of 385 posts

Re: Asahi Linux Progress Linux 7.0

#271
post #129

Earlier quoted context omitted.

The following is actually the most surprising part to me. > This is quite limiting, as it forces PipeWire to waste CPU cycles (and therefore battery life) on resampling audio streams that are not either 48 or 96 kHz. So the Asahi team thinks that only supporting 48 or 96 kHz wastes battery life by forcing the software to resample audio streams. But why does Apple still do this? Presumably Apple has a very high commit…

Presumably Apple can resample audio streams extremely cheaply.

I mean the algorithms for that are known, and PipeWire/PulseAudio implements them competently. But it still has to be done.

Re: Asahi Linux Progress Linux 7.0

#272

Earlier quoted context omitted.

[flagged]

I am not sure how what happened can be considered "being outed", the vtuber's puppeteer was obvious from day one to anyone who was paying any attention at all, it is just that a lot of people decided to uphold the kayfabe. (And I don't blame them, at least before the lkml crashout it was a pretty fun character.)

While there is overlap between vtuber communities and HN, the culture is quite different. When one does come up, it is eternally September on HN. In vtuber communities/culture, the persona of the vtuber is treated as entirely separate from the person behind it, even in cases where it's exceedingly obvious (e.g. someone leaves an agency to work independently).

At the very least, it is rude to disseminate, draw attention to, or even speculate aloud about the identity of the person behind the avatar. Typically it's considered harassment/doxxing (I believe this is because vtubing culture is largely derived from Japanese idol culture, which appears to be structured around dealing with stalkers). That is to say, "upholding the kayfabe" is a bare-minimum of respect.

I could see why people on the Asahi team considered HN to be a host of harassment, considering even a cursory search of HN turns up comments "compiling evidence" about Asahi Lina's identity (including one still-up comment that straight-up links to Kiwi Farms, which is almost certainly done for purpose of harassment). I'm not sure if Hacker News ought to be moderating comments that deconstructs pseudonyms where clear effort has been made to separate it from the person behind them, but I also empathize with not wanting to be linked to accordingly.

Re: Asahi Linux Progress Linux 7.0

#273
post #266

Earlier quoted context omitted.

do we ever get apple engineers rolling thru here or on mastodon? wish stuff like this wasn't such a black box behind the scenes. i think the only time ive ever run into an apple engineer was on mastodon related to gptk it was interesting to see they actually are quite tuned into what is possible on these devices and what that could mean for gaming. despite being a developer toolkit to help studios get a read on the w…

> do we ever get apple engineers rolling thru here or on mastodon? wish stuff like this wasn't such a black box behind the scenes. Very rarely. I believe because Apple has a culture of secrecy and contractually forbids employees from sharing details about their work in most circumstances (and actually enforces this).

damn. that sucks.

Re: Asahi Linux Progress Linux 7.0

#274
post #254
post #250

Earlier quoted context omitted.

Even back then, it could play more than one stream. You had to have a sound card or kernel drivers that supported it (and all non-obsolete ones did by the time pulse audio came out). I still don’t know what purpose pulseaudio serves, other than adding latency and making stuff less reliable. PipeWire is better, but it turns out you can just use OSS under freebsd these days, and everything just works, but with lower la…

Nonsense - HDA systems were overwhelmingly the majority of Linux systems at that point, and didn't have any hardware support for multiple streams. OSS with software mixing was a commercial product that wasn't upstream. ALSA had userspace mixing but it was very much not an out of the box experience, and didn't take advantage of hardware capabilities in the way Pulseaudio did to reduce wakeups and power consumption.

ALSA had DMIX by default, all that before Pulseaudio. I remember Knoppix and a few more doing that.

Re: Asahi Linux Progress Linux 7.0

#275
post #254
post #250

Earlier quoted context omitted.

Even back then, it could play more than one stream. You had to have a sound card or kernel drivers that supported it (and all non-obsolete ones did by the time pulse audio came out). I still don’t know what purpose pulseaudio serves, other than adding latency and making stuff less reliable. PipeWire is better, but it turns out you can just use OSS under freebsd these days, and everything just works, but with lower la…

Nonsense - HDA systems were overwhelmingly the majority of Linux systems at that point, and didn't have any hardware support for multiple streams. OSS with software mixing was a commercial product that wasn't upstream. ALSA had userspace mixing but it was very much not an out of the box experience, and didn't take advantage of hardware capabilities in the way Pulseaudio did to reduce wakeups and power consumption.

Do you think starting with "Nonsense" makes your argument better heard?

Re: Asahi Linux Progress Linux 7.0

#276

Earlier quoted context omitted.

I had a P14 Thinkpad for work and had all sorts of issues with Wayland and streaming and what not. There's no issues on the Mac side things just work.

Does it have a dGPU? My simple Intel iGPU Thinkpad hasn't had any noticeable Wayland-related issues in the past 3-4 years.

This is the delulu Linux world thinking all over again. “Just get one with no dGPU, just this chipset, just this and this escoteric thing” and you’ll be fine.

Re: Asahi Linux Progress Linux 7.0

#277
post #129
post #12

>.. macOS only ever programs CS42L84 to operate at either 48 or 96 kHz, we could only add support for those two sample rates to the Linux driver .. > However, CS42L42 supports all the other common sample rates, and while the register layout and programming sequence is different, the actual values programmed in for 48 and 96 kHz are the same across both chips. What would happen if we simply took the values for all oth…

The following is actually the most surprising part to me. > This is quite limiting, as it forces PipeWire to waste CPU cycles (and therefore battery life) on resampling audio streams that are not either 48 or 96 kHz. So the Asahi team thinks that only supporting 48 or 96 kHz wastes battery life by forcing the software to resample audio streams. But why does Apple still do this? Presumably Apple has a very high commit…

Likely because the only speakers Apple cares about are Airpods/Airpod max so they are free to only pick the 2 most common sample rates.

Re: Asahi Linux Progress Linux 7.0

#278
post #238

Earlier quoted context omitted.

Imagine LCD screen capable of emitting from IR to UV and people up in arms because laptop vendor software limits output to visible spectrum.

Come on, don't do that here. You can see in the thread I replied to there are practical benefits for supporting additional sampling rates.

Practical reasons vanished ~20 years ago, about the time Microsoft dropped hardware audio acceleration and switched to software audio mixing. Resampling is ear transparent and eats less than 1% of one slowest possible CPU core.

Re: Asahi Linux Progress Linux 7.0

#280
post #250
post #226

Earlier quoted context omitted.

In the time before PulseAudio, when it was ALSA (and OSS).

Even back then, it could play more than one stream. You had to have a sound card or kernel drivers that supported it (and all non-obsolete ones did by the time pulse audio came out). I still don’t know what purpose pulseaudio serves, other than adding latency and making stuff less reliable. PipeWire is better, but it turns out you can just use OSS under freebsd these days, and everything just works, but with lower la…

Sure, sure. I remember a time when I didn't have a sound card that supported it and couldn't play multiple streams at a time; this is a thing that really happened. I did eventually go out and buy a soundcard to enable multiple streams.
Post reply on HN