The new variable name is `kNumber_Of_Channels` for number of channels. You can also go up to 16 (or more?) channels instead of the stock 2, which is great for multiple participants in a jacktrip session, among other things. Just change around some variables: `kDevice_Name`, `Manufacturer_Name`, `kPlugIn_BundleID`, `kBox_UID`, `kDevice_UID`, `kDevice_ModelUID`, and then the Blackhole.driver folder it spits out after build. The unsung hero of Blackhole is the ability to easily build a new one, meaning you can have infinite sets of audio devices with custom names. Is it possible you have some very specific requirements that no one else does? Maybe, but I’ve landed on the idea that this a really a form of procrastination - where the “paying attention” part of the process is being pushed off until sometime later, and really just makes more work in the long run. What’s their secret? They just pay attention and take notes the first time through. You seem to be aspiring to use a techie solution to this, but would it really work in practice, and be worth the effort?Ĭonsider that 99.9% of people are able to function pretty well without having to refer back to a full recording of every meeting they’ve ever had.

Having a full recording of everything implies that at some point you have to actually process the content (take notes, etc.), and you’re really just setting yourself up for taking double the amount of time than it would if proper notes were taken in the first place.

I think a lot of people take this approach of recording everything (or at least try to once the idea of recording meetings is available), but you really need to think about whether it’s going to solve the problem you think you have.

Virtual audio driver for windows