Depends on the thing it’s doing and how low level it expects to access the storage.
The things you named are pretty much made to work with each other in mind so there’s no issue.
Weird issues can happen if two things try to write the same file.
I’ve done variations of this concept, but I never tried that in NixOS.
Something that should be pretty universal though, is to keep it read-only everywhere except one read-write container.
Generally speaking, having multiple containers with write access to the same folder is a recipe for headaches.
sleep deprivation and coke would explain so much
Also, the crackling might be something about the sampling rate. It’s been a while since since I poked around with audio, but I vaguely remember changing the default sampling rate and restart pulseaudio or something like that.
In my case, I think the onboard audio device is in the same group as the motherboard chipset, which would explain the host crashing when passing through.
Hmmm… I do have audio coming out of a guest VM under proxmox, but I’m passing through a whole GPU which includes audio through its HDMI.
The on-board audio might not be in an iommu group that can be passed without breaking something else, which would likely prevent booting the host correctly.
Honestly, I think I’d just go with a USB dongle for the audio. Easier to passthrough, likely better audio quality too and shouldn’t be too expensive.
You can pass either a USB device id or a port (or group of ports, depending on how it’s grouped)
No not yet
A lot of that slinky filament looks grounded or marked by the extruder gear. If it only happens on longer prints, ambient temperature might simply rise too much over time. Even the best extruder cooling fan can’t help much if the ambient air is too hot.
I need to vent my enclosure when doing super long prints or when printing hotter stuff like PETG.
Bat me up, scotty.
If I’m honest? probably nowhere near enough.
The 46 hours is assuming it moves at 300mm/s on that axis for 46 hours, which just isn’t the case.
I say this, but as a ballpark figure this is still useful. Even if typical prints probably take longer than that to reach 50km on an axis, that still tells me I certainly don’t lubricate them as often as I should.
Maybe that’s something printer firmwares could one day be modified to calculate and warn the user about.