I use Loopback for virtual audio sources. This is super helpful because I create an audio source, which is my microphone and the guest's (guests') audio, and treat it as one input source. I use this audio source as the audio source for live captioning. - Source: dev.to / about 2 months ago

No, it's very easy: https://existential.audio/blackhole/ Blackhole is Free and Open Source. Also, Rogue Amoeba has a product called "Loopback". It's not cheap, but it's another alternative: https://rogueamoeba.com/loopback/. - Source: Hacker News / 9 months ago

This is the basic idea, but there are other apps which can make it easier. I prefer using Audio Hijack for the EQ part and sending it to a pass-through device set up in Loopback (which, for this use case, functions the same as BlackHole). Source: 9 months ago

- Loopback 2 by Rogue Ameba to create a pass-thru from the soundboard (Farrago, also by Rogue Ameba) to Skype so everyone can hear me talking in addition to the soundboard on the same line. Source: 12 months ago

At the risk of further complicating matters, you could try combining sources or otherwise experimenting with Loopback, an app that's designed to do all kinds of audio routing stuff. Source: about 1 year ago

Helm Dashboard is an open-source project by Komodor that offers a visual and user-friendly way to manage and visualize all the Helm charts installed in your clusters. Instead of using the terminal, you can leverage the Helm Dashboard's intuitive UI to perform a variety of tasks that make working with Helm a breeze. Here are some of its key features:. - Source: dev.to / 10 months ago

Speaking of tools that I think I could talk an employer into buying, how about something to help with troubleshooting Kubernetes? Komodor is an observability tool that gives you insight into what’s happening with your clusters and workloads. As distributed applications have become more complex, they’ve become more difficult to troubleshoot, and Komodor gives you an integrated view of your Kubernetes resources. Not... - Source: dev.to / about 2 years ago

Monitoring changes in the entire Kubernetes stack requires specialized skills particularly in the effective analysis of ripple effects and context-based approach in troubleshooting problems. A K8s-native troubleshooting solution like Komodor ensures that the troubleshooting process is undertaken in an independent and efficient manner. It institutes systematization to address the chaos that is usually present when... - Source: dev.to / almost 3 years ago

You can find more info on https://komodor.com or DM me (full disclosure: I work for Komodor at the moment). Source: almost 3 years ago

For Troubleshooting: Komodor Komodor is a troubleshooting tool that has been gaining popularity in the Kubernetes dev community. What Komodor offers is the ability to gain a full view of all changes across the entire k8s stack - and their ripple effects - to streamline the usually laborious task of understanding what went wrong, when something goes wrong. - Source: dev.to / almost 3 years ago