#asahi · 2022-06-11 08:50
marcanbut I'm sure that can all be worked out#asahi · 2022-06-11 08:50
marcanand for firewire specifically I have an issue with multiple streams getting aligned I need to look into#asahi · 2022-06-11 08:49
marcan(for latency and quality and CPU usage reasons; for audio production you really don't want magic resampling behind your back)#asahi · 2022-06-11 08:49
marcanthe only thing that I need to dig deeper into pipewire for is I want to learn how it handles sample alignment and resampling, because I'm a bit worried about the automagic resampling stuff and would like some guarantees that e.g. it will never happen on certain audio paths as long as certain conditions are met#asahi · 2022-06-11 08:48
marcanand only reason I didn't ship it for the first alpha is I didn't have time to do any userland work at all#asahi · 2022-06-11 08:48
marcanyup, only reason I don't use pipewire on my main machine is the firewire audio driver issue#asahi · 2022-06-11 08:48
marcanbut jack auto switching without a sound server is definitely not needed for that :p#asahi · 2022-06-11 08:47
marcanyes, I do music production on Linux and I think I can make M1s some of the best systems to use for that#asahi · 2022-06-11 08:47
marcanbut, on the other hand, if you really care about latency to the millisecond level, you'd probably be using JACK with zero jack switching smarts anyway, everything managed manually#asahi · 2022-06-11 08:46
marcanthat is completely up to the software layer, and I personally care deeply about latency and want to work on improving that in PipeWire too#asahi · 2022-06-11 08:45
marcanthough of course that means you need a sound server for proper functionality#asahi · 2022-06-11 08:45
marcaneverything's a lot simpler if we just keep all this out of the kernel and let userspace deal with multiple streams and whatever timing it wants to use#asahi · 2022-06-11 08:45
marcanwhat a mess#asahi · 2022-06-11 08:45
marcanif you're switching codecs for a single stream, how do you align the software volume change with the mux switch? you'd have to soft mute, switch, soft unmute, and time it all properly#asahi · 2022-06-11 08:44
marcanconsider that software has to coordinate software volume scaling with codec volume scaling#asahi · 2022-06-11 08:44
marcanmuxing is a problem in general, because it creates race conditions#asahi · 2022-06-11 08:44
marcanwhich works quite well in modern systems#asahi · 2022-06-11 08:44
marcaneverything is a separate stream, implement policy in userspace#asahi · 2022-06-11 08:44
marcanhence the trend has been towards just doing it all in software#asahi · 2022-06-11 08:43
marcanespecially with hardware that tried, and failed, to share streams between speakers and HP jacks#asahi · 2022-06-11 08:43
marcanat the time this was all a mess#asahi · 2022-06-11 08:43
marcanmy first laptop, a core2duo, had "5.1" speakers, and needed sound server support for upmixing, and I had to hack up the ALSA driver (that patch did get merged though lol) to allow opening the device in different channel modes because you could have things like the jacks in 2.0 mode or 5.1 mode, and that would mismatch with the speakers#asahi · 2022-06-11 08:42
marcanby the way, this has been broken for *decades*, it's just more obvious with modern systems#asahi · 2022-06-11 08:41
marcannobody's going to force anyone to use a sound server, but if you don't you have to accept that your apps are going to be outputting to one stream, and only one stream, and without any ability to EQ except for what you can do with ALSA plugins, and changing the setup will require a restart of the app or at least stopping/restarting audio#asahi · 2022-06-11 08:40
marcanthe point is, not using a sound server means you don't have a layer between apps and hardware, which means apps see the hardware directly, which means you don't have a place to put the logic required for things like EQ and jack switching to work properly#asahi · 2022-06-11 08:39
marcanthat's what we have sound servers for#asahi · 2022-06-11 08:39
marcanand how does your app know to close one device, open the other device, and change EQ profiles?#asahi · 2022-06-11 08:38
marcansince alsalib does not help you there#asahi · 2022-06-11 08:38
marcanmps: you need a sound server for that to work mid-stream without application support#asahi · 2022-06-11 08:37
marcanit is the case on many modern systems that you cannot switch a single stream between headphones jack and speakers anyway#asahi · 2022-06-11 08:37
marcanpovik: so basically if you can do it trivially, sure why not, but otherwise I would absolutely not try to spend any effort putting together some mechanism to make it work#asahi · 2022-06-11 08:36
marcansince presumably you'd always be using some sort of output#asahi · 2022-06-11 08:36
marcanchadmed: for that use case you wouldn't need headphone jack switching anyway#asahi · 2022-06-11 08:36
marcanI mean with auto-switching#asahi · 2022-06-11 08:36
marcanpovik: single stream + no sound server is not a supported use case in practice, IMO, due to the EQ issue#asahi · 2022-06-11 05:28
marcanit would of course be a waste of CPU power when headphones are in use though, in that case#asahi · 2022-06-11 05:28
marcanif it's just muting multiple streams I guess you could have software always send the plain jack version + EQ/crossover'd speaker version at once with an ALSA plugin...#asahi · 2022-06-11 05:27
marcanif single stream, I wouldn't bother. can't do the EQ properly in that case without a sound server, so I have no interest in supporting it (mps: you want features like jack hotplug with modern hardware, use a sound server. that's what the hardware design + kernel design requires.)#asahi · 2022-06-11 05:26
marcanpovik: what's the story with the mux-based switching? is this for a single stream going to speakers or to headphones, or for muting multiple streams?#asahi · 2022-06-09 09:37
marcanI guess they shoved the keyboard controller into the main SoC now, sounds like something they'd do#asahi · 2022-06-09 09:36
marcanhopefully it's similarly trivial :)#asahi · 2022-06-09 09:36
marcandockchannel is trivial#asahi · 2022-06-08 18:17
marcanupdating OS firmware is just doing what the installer does again#asahi · 2022-06-08 18:17
marcanwhich we haven't figured out yet#asahi · 2022-06-08 18:16
marcanupdating system firmware is the ramdisk dance that sven mentioned#asahi · 2022-06-08 18:16
marcanthe problem isn't the GPU, it's that everything needs to be updated together#asahi · 2022-06-08 18:16
marcanTherefore, to update OS firmware (including GPU firmware), we first need to update system firmware.#asahi · 2022-06-08 18:16
marcansepkov[m]: There is system firmware and OS firmware. The OS firwmare can be updated the way we install it, but it always has to be equal to or older than system firmware.#asahi · 2022-06-07 12:12
marcanjannau: on 12.x I assume? we should fix the 13.0 beta NVMe issue I opened before this release#asahi · 2022-06-05 22:40
marcandcpext firmware is 1:1 identical to dcp firmware, so other than potentially the flow/callbacks being a little bit different in the dcpext case, the driver should work without any changes