BlackHole VS Windows-driver-samples

I did something similar using BlackHole , with an old Mac, not as fast, but I'm quite happy with the results.

This tip is certainly good, but I prefer to use blackhole in combination with standard quicktime, then compress the video to mp4 without losing quality using handbrake.

Use the built in screen recorder with the cmd + shift + 5 hotkey and then pair it with the free internal audio capture software blackhole or vb-audio cable.

FYI, in the audio industry AI is artificial intelligence, not audio interface. Especially these days when AI is becoming increasingly present in all facets of production, it's probably best to disambiguate. DAC would be more clear (digital to analog converter), or you can just say 'interface'.   If you're on Mac there are several options. My preference is for Blackhole which is open source and free. If you've never used github before, it can be kind of intimidating, but just scroll down and read the downloading/installation instructions and it will walk you through it. There are tons of other ones though like Jack, soundflower, etc.   If you're on PC, your options are somewhat more limited. Cable has come up on a few past searches, but since my PC is used strictly as a virtual instrument server, I don't have personal experience with it.

Or, if you want something even more lightweight, you can record computer audio with the macOS screen recording tool using BlackHole: https://github.com/ExistentialAudio/BlackHole

I found Blackhole and got it configured by creating aggregate device and it basically picks up the audio from the built-in speakers via the built-in mic. I then use QuickTime to do a screen recording and pick the aggregate device as the input.... it works but I'd much rather be able to capture the audio from the Bluetooth headset because I usually work with the laptop closed using two external monitors.

Great app. Blackhole is free tho.

If you're looking to do livestreams, you'll probably want to route the audio from Logic straight into whatever streaming app you're using. Use software like BlackHole or Jack (or something like those) to create a virtual audio device. Read through some manuals or watch a tutorial for nitty gritty, but you'll basically end up routing the output from your track to a virtual audio device, then use that same device as the audio input for your livestream software.   BlackHole is free and open source (don't download an "app" from one of those sketchy macUpdate places). If you've never used github, it can look a little intimidating, but just scroll down and read the installation instructions and they'll walk you through it.

https://github.com/ExistentialAudio/BlackHole -- For BlackHole you'll need a throw away email, for others you need money.

The state machine example is definitely a very fitting use of goto, but it reminds me of another thing that seems to have become a rare skill but is very useful: flowcharting. Besides making people comfortable with goto in general, it also helps visualise control flow in ways that a lot of programmers these days don't realise, and it's unfortunate that a lot of courses seem to have omitted its teaching.

Also worth reading is "GOTO Considered Harmful Considered Harmful": https://news.ycombinator.com/item?id=11056434

And here Microsoft provides us with lovely example of such ridiculous nesting.

That's a very memorable example, but ultimately the true cause of that monstrosity is a clearly stupid API design; this is the API for a file picker, the recommended replacement for an existing one that they wanted to deprecate. In the existing one, you fill in a structure and call a single function with a pointer to it. In its replacement, you need to call a dozen methods on an object, and check for "possible" errors on each call, even if probably 99% of them only do things like assign to a field in a now-opaque structure and can never produce an error. Then the example code must've been edited by someone with severe gotophobia. (Not all MS code is like that --- they have plenty of other example code that uses goto, e.g.: https://github.com/microsoft/Windows-driver-samples/blob/mai... )

The source code for the sample can be found here. Check this code out to a local folder and use the included visual studio solution to open it up. You should be able to build this code as is; if it's telling you that you need spectre mitigated libraries to build it you can either acquire those via the visual studio installer or go to Project Properties > C++ > Code Generation > Spectre Mitigation and select disabled (I have it enabled so disabling it could cause issues, probably not though).

This project was my first experience working with device drivers, and uses the Windows devcon utility to disable and re-enable a device driver.

So a quick look at the Wikipedia site of "Virtual Audio Cables" reveals that it's based in n a custom windows driver. Based on that I would start here

Given that they're essential and worth about $1.8 million, then, it sounds like the proper solution would be to argue for the budget to engage a developer to write, test and sign a replacement driver. (Especially since the Intel 82930 USB test board is literally used by Microsoft as an archetypal example device in USB driver development documentation.)

Maybe corresponding Windows API? https://github.com/microsoft/Windows-driver-samples/tree/master/audio/simpleaudiosample and https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/getting-started-with-wdm-audio-drivers.

Well yes. But Linus is right on that one.

I wouldn't say Windows drivers were C++, more like "C with Classes" (and maybe a little bit C++)

Also, Windows drivers are usually much more convoluted than Linux drivers https://github.com/microsoft/Windows-driver-samples

A more practical resource are the various driver samples Microsoft provides: https://github.com/microsoft/Windows-driver-samples