#
…

2023-10-30

00:06ydalton has quit [Ping timeout: 480 seconds]
00:10Xe has quit [Quit: WeeChat 4.0.2]
00:18holiday has joined #asahi
00:18holiday has quit [Remote host closed the connection]
00:25Xe has joined #asahi
00:32Brainium has joined #asahi
00:59Xe has quit [Read error: Connection reset by peer]
01:15Xe has joined #asahi
01:42marcanthe speakers will just be quiet without speakersafetyd, yes (not unusably quiet even, they're loud to begin with)
01:42marcanthe whole point of speakersafetyd is *raising* the max volume caps from worst-case. worst-case is basically what you get on every other laptop.
01:43marcanso without speakersafetyd, on paper, it should be as loud as your average laptop (which is a lot quieter than Macs)
01:43marcanin practice we are really conservative with the caps and other manufacturers push it and blow up their speakers *cough Dell and VLC fiasco cough* so it's probably less, but not like unbearably quiet
01:43marcan-20dB is the safety level
01:44marcanwhich is, perceptually, 1/4 the loudness
01:45marcanthis is also different from lowering the volume the normal way, because the normal way uses DSP to do equal-loudness adjustment, so lower levels have more bass (to sound similar). the -20dB pad is hardware so it will sound tinnier at that volume (just like every other laptop again, almost nobody but Apple does equal-loudness compensation)
01:45marcanand yes if speakersafetyd dies the kernel turns down the speakers. automatically if the process dies, or after a 250ms timeout.
01:46marcanthat's why there's a whole bunch of kernel-side interlocks involved
01:48Nefsen402"Dell Tech Support is denying warranty service for speaker damage if the popular VLC Media Player is installed on a Dell laptop" Oh those mfs that makes my blood boil
01:49marcanthey were overdriving the speakers *and* forgot the I Won The Loudness War safety factor (or didn't care).
01:49marcan // Worst-case peak power is 2x RMS power
01:49marcan let peak_pwr = 10f32.powf(amp_gain / 10.) / new_speaker.z_nominal * 2.;
01:49marcanpeak power for an audio signal is *2 times* the power of a full scale sine wave (e.g. a full scale square wave)
01:50marcanwhich incidentally is precisely the total power of that song, all throughout.
01:51marcan(that song is engineered to have absolute maximum output power, and loudness by proxy)
01:51artemist has joined #asahi
01:52marcanbut most manufacturers don't know that, they just say "1W speakers so max volume is 1W RMS nominal" where "nominal" is calculated using a sine wave as it always is, and then VLC starts clipping your audio at >100% volume and that happens
01:53lena6 has quit [Remote host closed the connection]
01:53marcan(but that won't melt a speaker that quickly and it's not IWTLW level with VLC, Dell were also definitely overdriving them to begin with)
01:53Nefsen402They 100% asked the engineers and were given two choices: Forever be hated because they nerf the loudness of their laptops or they get hated by the few that blow up their speakers
01:54Nefsen402Of course engineering proper software is too hard for them
01:54marcanpretty sure nobody asked anything, most laptop manufacturers just *do not care* about any of this
01:54marcansome engineer somewhere put in 1W speakers and configured the amps for 1W and that's that
01:54IknoweD has joined #asahi
01:54marcanmeanwhile every phone manufacturer cares about this because you have to on phones to get *any* volume out of speakers that small lol
01:55marcanwhich is why pretty much every phone uses smart amp technology like Apple (usually done in firmware though)
01:59Nefsen402Oh yeah, I'm not talking about them shipping a broken product, I'm talking about them doubling down on their broken product and voiding waranties instead
01:59marcanif anyone wants to learn more, marketing slides: https://www.ti.com/jp/lit/ml/slyp715/slyp715.pdf (Apple version in page 15 "non-integrated")
02:00marcanand the algorithm is described here: https://www.ti.com/lit/an/slaa857/slaa857.pdf (using an iPhone 7 speaker as the example, cough cough I wonder who they were working with)
02:01marcanthat (well the thermal part) is what speakersafetyd implements
02:01marcan(Apple don't use excursion protection, it's turned off in all their configs)
02:01IknoweD has quit [Read error: Connection reset by peer]
02:02Nefsen402So speakersafetyd is going above and beyond so my woofer doesn't mechanically hit the chasis?
02:02marcanno, we don't do excursion protection either
02:03i509vcbFrom what I'm reading, this is effectively controlled overdriving to make the sound louder?
02:03marcanit's not "overdriving"
02:03marcanspeakers care about average power
02:03marcanmost music has a lot lower average power than the aforementioned worst-case song
02:03marcanso you can play it a lot louder and not blow your speakers
02:04marcanthis is *especially* true once you have 2-way systems with a tweeter, since the tweeter will usually end up with a tiny fraction of the total power
02:04marcanbut a worst-case signal like a 5kHz square wave would send max power to the tweeter
02:04marcanbut that never happens with real things people listen to
02:04john-cabaj has joined #asahi
02:04marcanif you were designing a system with safe absolute maximum power, like dumb amp systems, you'd have to cripple your volume to make that safe
02:05Nefsen402Isn't metal music super compressed and distorted basically by default? I would think that genres like that would go a little closer to blowing things up. Is a pure full power square wave *that* much more powerful?
02:05marcanvery much so
02:05marcanjust look at the actual LUFS numbers
02:06marcan-14 is the YouTube normalization standard, -9 is typical crunchy CD, -6 is where things start getting stupid, -3 is what ISTR some idiotic EDM producer boasted. IWTLW is **+3**.
02:07marcanthat means IWTLW is **4 times** the sound power of the idiotic EDM producer, give or take (okay LUFS isn't RMS power but you get the idea)
02:07marcanbut also what I said about tweeters, metal music isn't putting all its power in the tweeter range is it :p
02:13Nefsen402Do they this sort of smart amp stuff with big concert installations? What if I told you you could carry around half the amount of gear for your tour if you added a bit of software?
02:16Brainium has quit [Quit: Konversation terminated!]
02:16john-cabaj has quit [Ping timeout: 480 seconds]
02:19marcanyes, big speaker systems have running average power limiters of some sort
02:19marcanit's different tech to the microspeaker stuff but a similar concept
02:20marcanjust like with macs, there's a lot of DSP and fancy processing that goes into big concert installations
02:20marcanplus with a concert you know how loud you're going to be anyway, it's not like you need to handle an arbitrary input
02:22Nefsen402My mind got blown when they did things like bunching up subwoofers in specific patterns to create constructive interferance and doing the naive thing of just putting two sets of subwoofer pairs for both channels at the ends of the stage makes for something that's harder to tune
02:22Nefsen402and they also do DSP? I can kind understand how you need experts for that sort of thing
02:25marcanof course they do DSP :)
02:25marcanheck I help run some events in Spain and we have a pretty simplistic speaker array (4 points plus subwoofers) and we have a DSP rack unit for it
02:26marcanand that isn't even an event where audio is particularly well done :p
02:26marcan(not that I'm in charge of it either, if I were I'd care a lot more :p)
02:28Nefsen402My entire audio setup is a usb headphone amp (hate onboard because you can hear static and whatever when you got the computer under load) and headphones with no DSP anywhere to be found and I'm really impressed by it. Apparently I'm left in the dust by probably 30 years
02:31marcanNefsen402: https://github.com/jaakkopasanen/AutoEq/tree/master/results find your headphones there, throw the IR into a convolver plugin, and enjoy balanced sound :)
02:32tpw_ruleslove to convolute
02:32Nefsen402Ah yes, sennheiser hd 650 is listed
02:33Nefsen402They got tunes for pre 2020 models? I don't know when I bought these things
02:52Nefsen402Holy crap, my headphones got freaking transformed! Thanks marcan!
03:00gabuscus has quit []
03:15Bogdan51 has joined #asahi
04:04gabuscus has joined #asahi
04:12crabbedhaloablut has joined #asahi
04:15marvin24 has joined #asahi
04:18marvin24_ has quit [Ping timeout: 480 seconds]
05:49i509vcb has quit [Quit: Connection closed for inactivity]
07:00HardWall has joined #asahi
07:29ydalton has joined #asahi
07:44hightower3 has joined #asahi
07:50hightower2 has quit [Ping timeout: 480 seconds]
08:05tmbrwn has joined #asahi
08:07tmbrwnhi folks
08:22HardWall has quit [Quit: This computer has gone to sleep]
08:34ydalton` has joined #asahi
08:35ydalton` has left #asahi [#asahi]
08:37ydaltoneh, i looked again at the source of speakersafetyd and it seems it doesn't "shut off" the speakers as in a previous commit, and now it sets it to a safe state (worst-case as marcan puts it)
08:39j`eyydalton: thats what I said too!
08:41ydaltonit looks like that behavior changed last week, maybe i should be keeping up with the source more often...
08:42j`eyydalton: I think that's how it always worked
08:43ydaltoneither it did change or the comment was inaccurate
08:44ydaltonbut yeah, volume going quieter is a lot better than cutting out out of nowhere :)
08:45j`eyI think maybe that comment was just there before anythign had really been written
08:45ydaltonyep, it dates back to the first commit
08:48ydalton has left #asahi [ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.0.92)]
08:50HardWall has joined #asahi
08:55tmbrwnhey folks, I'm getting back into desktop linux after a long break from it
08:57tmbrwnthe asahi alpha has been a lot of fun, kind of the perfect way to nudge me back into linux
08:58tmbrwnI'm gonna lurk for a while, and try to see if there's a way I can help contribute to this project
09:00j`eytmbrwn: welcome
09:03zerdox has joined #asahi
09:11ciggi has quit [Ping timeout: 480 seconds]
09:15zerdox has quit [Ping timeout: 480 seconds]
09:15zerdox has joined #asahi
09:29HardWall has quit [Quit: This computer has gone to sleep]
09:30HardWall has joined #asahi
09:32ciggi has joined #asahi
09:55Szadek has quit [Ping timeout: 480 seconds]
10:42Szadek has joined #asahi
11:23zerdox has quit [Ping timeout: 480 seconds]
11:23zerdox has joined #asahi
11:32zerdox has quit [Ping timeout: 480 seconds]
11:36PaulFertser has quit [Ping timeout: 480 seconds]
12:08delsol has joined #asahi
12:32zerdox has joined #asahi
12:40zerdox has quit [Ping timeout: 480 seconds]
12:43Moprius has joined #asahi
12:43Szadek has quit [Quit: Ping timeout (120 seconds)]
12:47le0n has quit [Remote host closed the connection]
12:49PaulFertser has joined #asahi
12:50c10l has quit [Quit: Ping timeout (120 seconds)]
12:51skipwich has quit [Remote host closed the connection]
12:55Agua has joined #asahi
12:58novafacing9926 has quit [Read error: Connection reset by peer]
13:03Szadek has joined #asahi
13:07zerdox has joined #asahi
13:07c10l has joined #asahi
13:08le0n has joined #asahi
13:13novafacing9926 has joined #asahi
13:19skipwich has joined #asahi
13:23zerdox has quit [Ping timeout: 480 seconds]
13:31john-cabaj has joined #asahi
13:40speee has joined #asahi
13:41speeei am fiddling around with linux for 20 years now, but it was always a big pain with the hardware! i am very happy that marcan and the asahi linux team really *care* about doing it right, so maybe i will finally be happy with hardware support on a linux machine :) thank you very much!
13:42speeei will buy a m3 max studio then or something, and replace my big loud tower in the office :)
13:42speeeI only work in VMs, so good x86 VM support would be the last great thing i need, ARM windows does not support all apps unfortunately :-/ and UTM x86 is too slow... :(
13:43speeeor maybe just store a x86 server in the basement for VMs :D :D
13:43speeebut with energy prices these days, that is also not recommended...
13:44speeebut just wanted to say, i am so happy that finally someone really cares for linux on a specific range of hardware to get it done right :-)
13:44speeethe year of asahi linux final release is will be the year of the linux desktop as well! :)
13:44j`eyUTM x86 uses qemu.. which will be the same as asahilinux
13:45speeeyeah, but maybe M3 will be fast enough for that. that had nothing to do with asahi, i just mentioned it!
13:45speeei hope qemu can implement that x86 memory map trickery things apple does for rosetta2, so that these VMs will be faster in the future :) or maybe you can create a x86 VM with fexemu someday, which can windows x86 fast then? i dont know :)
13:48speeealso i hope there will be a good RDP client someday for linux, that is as fast than native on windows and supports all features of the modern rdp protocol rdp10
13:54speee has quit [Quit: Page closed]
13:57leiotry gnome-connections
13:58i509vcb has joined #asahi
14:19SalimTer- has quit [Remote host closed the connection]
14:20SalimTerryLi has joined #asahi
14:38ximm has joined #asahi
14:41ximm has quit [Remote host closed the connection]
14:45Moprius has quit [Quit: bye]
15:14SalimTerryLi has quit [Quit: ZNC - https://znc.in]
15:15SalimTerryLi has joined #asahi
15:17holiday has joined #asahi
15:36delsol has quit [Remote host closed the connection]
16:03possiblemeatball has joined #asahi
16:08billak has joined #asahi
16:45joshheyse has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
16:45joshheyse has joined #asahi
16:53jrj has joined #asahi
16:54jrj has quit []
16:58joshheyse has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
16:58joshheyse has joined #asahi
17:08jrj has joined #asahi
17:29cy8aermarcan: thanks for AutoEq. I now have great eq settings for my HD414 (yep the yellow thingie from 1968)
17:42billak has quit [Remote host closed the connection]
17:44possiblemeatball has quit [Quit: Quit]
18:00jrj has quit []
18:29possiblemeatball has joined #asahi
18:40mkurz has joined #asahi
18:43Moprius has joined #asahi
18:44Moprius has quit []
18:52holiday has quit [Quit: WeeChat 4.1.0]
19:24john-cabaj has quit [Quit: john-cabaj]
19:25john-cabaj has joined #asahi
19:41kdb424 has quit [Ping timeout: 480 seconds]
19:42j`eyjanneg: what's happening when I quit my WM, and go back to the tty and DCP logs a lot of stuff?
19:44ptudor_ has joined #asahi
19:44ptudor has quit [Read error: Connection reset by peer]
19:45kdb424 has joined #asahi
19:49mkurzRegarding the Webcam support on MacBook Pro M1 Pro 14 inch: It works for me, I also copied over the appleh13camerad file and ran asahi-fwupdate, restarted and also the calibration warnings in dmesg disappeard. However I have the feeling that the image contains"noise", compared when using macOS. Is it just a feeling or do others experience the same=
19:54lewurm has quit [Ping timeout: 480 seconds]
19:59SalimTer- has joined #asahi
20:03jannegj`ey: whatever the dcp firmware prints to its syslog. so some logs from powering the display off and on
20:04SalimTerryLi has quit [Ping timeout: 480 seconds]
20:07lewurm has joined #asahi
20:08j`eyoh, so it powers down from the WM and then back on again for the tty..?
20:12ChaosPrincessmkurz: same machine, same noisy webcam
20:16billak has joined #asahi
20:16mkurzChaosPrincess: Good, so it's not just me. I guess things will improve with time...
20:17kidplayer666 has joined #asahi
20:17kidplayer666It's not like webcams are renown for quality anyways
20:17kidplayer666and not like most videocall software even transmits at full quality...
20:18kidplayer666I swear I never got any more than 480p out of Zoom on any machine, even using a full hd webcam
20:19kidplayer666and the transmittion from others was always a low quality mess
20:20jannegj`ey: no, I misread. swithing from WM to tty might involve a modeset. dcp should first print "set_digital_out_mode(color:111 timing:55)". numbers will differ of course
20:20ChaosPrincessgeneric aliexpress sludge webcams - yes, whatever apple is using is actually not terrible.
20:21ChaosPrincessand macos does manage to remove that noes
20:21jannegmkurz: things will not improve by itself over time
20:22zerdox has joined #asahi
20:23kidplayer666Chaos Princess: I've tried good webcams, with fairly high quality when run locally, but as soon as it is a video call, it's a crappy schmoo
20:24kidplayer666janneg: you probably understood it, but he probably meant that eventually someone would get tired of the quality and work on it themselves
20:25mkurzjanneg: I know, unfortunately I am lacking the skills and time to improve such things in Asahi, that's why I donate instead.
20:25ChaosPrincesskidplayer666: that noise does not seem to be a result of video compression
20:25kidplayer666Also, I know it's currently not a priority (given the general state of biometrics in Linux is kinda meh), but I'm curious how hard it actually is to develop the Touch ID driver
20:26kidplayer666Chaos Princess:
20:26kidplayer666but it doesnt matter
20:26kidplayer666if it all becomes schmoo
20:26kidplayer666In a video call which is where you need it
20:26billak has quit []
20:27ChaosPrincessare you intentionally annoying me into recording both macos and asahi, compressing it to 240p and comparing the results
20:27ChaosPrincessw.r.t touch id - you can't, you need to do sep first
20:30j`eyjanneg: aha, a modeset, makes sense
20:32kidplayer666Chaos Princess: well, no, but seeing that I'm annoying enough for you to go do it is fairly funny
20:32j`eykidplayer666: do sep = write a SEP driver
20:33billak has joined #asahi
20:33billak has quit [Remote host closed the connection]
20:35kidplayer666the hell is SEP?
20:35j`eySecure Enclave processor
20:35kidplayer666what i found was
20:37j`eyyou wont get linux hits cos it's not on linux yet :P
20:37kidplayer666and im supposing that that is the thing that throws errors
20:38kidplayer666during the recovery environment
20:39ChaosPrincessyes, sep signs the boot policy and complains when there is something it does not like
20:40kidplayer666Aaaand fedora just froze
20:41kidplayer666Hopefully nothing gets borked
20:41kidplayer666Otherwise I’m kinda screwed
20:41kidplayer666Also, is it just me or asahi has unusually high memory consumption?
20:42kidplayer666When compared to using Linux on some random laptop
20:43ChaosPrincessprobably gpu stealing a bit too much memory.
20:44kidplayer666but it already shows off the maximum "physical memory" as being 700 mb
20:44ChaosPrincesswhere are you getting those values from?
20:45kidplayer666system monitor?
20:45kidplayer666even htop shows these somewhat weird results
20:48ChaosPrincessyou have both firefox and vscode open on a 8gb machine, that doesnt look strange.
20:49ChaosPrincessi _think_ whatsapp is also electron but dont quote me on that
20:49kidplayer666But even with everything closed
20:49kidplayer666It’s 4GB plus 1,5 GB in swap
20:49kidplayer666I may be not used to using KDE or gnome while on Linux
20:50kidplayer666But previous encounters even with these DE’s weren’t this memory intensive
20:50kidplayer666I’m pretty sure
20:51ChaosPrincessbooted my 8gb m1 mbp to kde with nothing open except konsole - using less than a gb, + 3-ish gb for disk cache
20:51kidplayer666Also why the hell doesn’t KDE freaking let me alter the shutdown time for trackpad after typing on GUI
20:51ChaosPrincessthats a libinput thing, not kde iirc
20:52kidplayer666Maybe system monitor shows off cache as occupied ram?
20:52kidplayer666Though htop doesn’t make it that easy to read
20:53ChaosPrincessthats normal top, not htop
20:53ChaosPrincesshtop shows a pretty bar
20:53kidplayer666I mix in the two
20:53kidplayer666Sorry for everyone around
20:54ChaosPrincessmaybe try sorting by mem% ?
20:54kidplayer666Ah now it makes sense
20:55kidplayer666Htop really helps
20:55kidplayer666Should come in standard
20:55kidplayer666Only 2.8GB are actually being used (including swap)
20:56kidplayer666I’m still curious though, cause it’s not the first time I accidentally get a system crash due to running out of memory
20:57ChaosPrincessyou got a 8gb laptop in $CURRENT_YEAR, thats imo to be expected
20:58kidplayer666yes, i know...
20:58kidplayer666but a certain someone has a massive markup on selling memory upgrades
21:03marvin24_ has joined #asahi
21:06marvin24 has quit [Ping timeout: 480 seconds]
21:07kidplayer666on ma desktop i have a weird 32 GB
21:13kidplayer666Chaos Princess: I'm curious though, did you check it?
21:14ChaosPrincesswhat, camera?
21:14yc has joined #asahi
21:21ChaosPrincessyep, noise still visible
21:21ChaosPrincessand it also somehow managed to sync with the light frequency and have vertical rolling dark bands
21:21kidplayer666wellm them it do be a heck of a lot more than I expected
21:21kidplayer666that+s some luck
21:24leioisn't there some stuff to counter that? I've seen settings in some places where you tell it if you have 50Hz or 60Hz electricity (and some auto-detect)
21:34jannegisp has a setting command for 50 / 60 Hz
21:42Agua has quit [Remote host closed the connection]
21:42Agua has joined #asahi
21:42Pouet78 has joined #asahi
21:45Pouet78Hello, I just discovered this project. One question I have and not in FAQ is : Does the project can be useful for Virtual Machines running on top of MacOS? If yes, is there a way to install it this way?
21:47ChaosPrincessno, this project is for native hardware support, while vms emulate a "generic" arm64, not a mac. If you want to run something in a vm, just install the upstream arm64 release of your favourite distro
22:01Guest4743 has quit [Remote host closed the connection]
22:19HardWall has quit [Quit: This computer has gone to sleep]
22:29Pouet78OK, but maybe later, vms could emulate a Mac and get benefits from there?
22:30Pouet78Virtualize more than emulate in fact...
22:30j`eyPouet78: what's the goal?
22:31j`eyyou can already virtualize arm64 on macOS
22:31Pouet78Better perfs and integration?
22:32Pouet78I have no direct use for me now, just reflexions...
22:32j`eyI don't think there's a benefit to be made there
22:33ChaosPrincessarguably, a generic platform is better for performance since you can use paravirtualized hardware instead of emulating real one
22:33leiomaybe there are some small opportunities for passthrough of something specific, if anything at all
22:42overholts has quit [Quit: overholts]
22:42Skyrix_ has joined #asahi
22:43Skyrix_ has quit []
22:43overholts has joined #asahi
22:46mkurzAnyone using Google Pixel Buds Pro? They are working great using A2DP/AAC, however microphone is not working (HSP/HFP, no matter if using CVSD or mSBC). It seems other reporting this problem as well using Asahi: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2689 Maybe this is a bluetooth problem?
22:48ah-mkurz: i had this too in fedora with airpods pro. on ALARM it always just worked for me. I messed about with wireplumber etc. settings and then it randomly started working, but I never got down to what exactly it was
23:04Pouet78 has quit [Remote host closed the connection]
23:06kdb424 has quit [Read error: Connection reset by peer]
23:08psykose has quit [Ping timeout: 480 seconds]
23:09kdb424 has joined #asahi
23:12crabbedhaloablut has quit []
23:23mkurzah-: you remember which settings you changed?
23:27Agua has quit [Remote host closed the connection]
23:32kdb424 has quit [Quit: Ping timeout (120 seconds)]
23:37mkurzAccordingt to https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2689#note_2148413 it might be an Asahi bluetooth issue: "the btmon traces do not show any incoming audio data after Enhanced Setup Synchronous Connection although they should. I don't believe currently that something can be done on Pipewire side about this."
23:38mkurz"Someone needs to verify if the same headset device works with a different Bluetooth adapter than on Asahi. If yes, then likely it's Asahi bluetooth kernel driver or firmware issue."
23:40psykose has joined #asahi
23:44mkurz has quit [Remote host closed the connection]
…