![]() ![]() Oh yeah, left click on the little record buttons in each Audio 1 and 2 track, so that they are both blinking. You should now be able to use/hear each mic. Repeat Steps 1-3, except this time, under Input: select “3-4 (DuelingYetis)” It’s the button with the dial on it, next to the button with the scissors (Editors button).ģ - In the Smart Controls Window, press the “i” button (info button). Also, I have Audio Effects checked, for whatever that’s worth.ġ - Track Header Components > Show Record Enable.Ģ - Open Smart Controls Window. Goto GarageBand menu > Preferences > Audio/MIDIīuilt-in Output and DuelingYetis should be selected. And now you can only hear/use the other microphone. Repeat previous process, except this time select Input 3 + 4. You’re at the Software Instrument / Audio / Drummer window again. Right now you can only hear/use one of the microphones. ![]() Make sure "I want to hear my instrument" is unchecked, select microphone at the top and hit “Create.” Software Instrument / Audio / Drummer window Under details, select DuelingYetis as Audio Input. The first Yeti occupies inputs 1 and 2, while the second occupies 3 and 4.Īggregate device created, now exit Audio Midi Setup and goto GarageBand. These are stereo mics, so each has 2 inputs and 2 outputs. ![]() ![]() Of course, without access to the OS X source code or to a USB analyzer this is all relegated to an unsubstantiated hypothesis.Ĭheck box under “use” for each Yeti Stereo MicrophoneĮxtra note - The numbers under “in” and “out” refer to number of inputs and outputs, not their designated locales. I suspect that Apple wants Mac users to have this extra layer of reliability and is therefore pushing responsibility onto device manufacturers to always include this optional field. Then imagine your 6 year old decided to unplug your microphones and plug them back in to different ports (and in a different sequence than they were originally connected.) Wouldn't it be nice if the computer could still identify them and assign them to your recordings correctly? Well, if they both have unique serial numbers it could. Now, imagine labeling a microphone as "Lead Vocals" and another as "Harmony" or something so that you can simply pick them up and know what they are for without having to trace them back to the computer. I'm sure Apple is looking to avoid this sort of thing. This can obviously bloat and reduce the performance of the Windows registry. If you ever attach the non-sn having device to a new port then Windows will create a new registry node for it. This includes ports on any USB hubs you attach. Moreover, if you attach an identical device to the original port Windows will think it is the original device since there is no way for Windows to know it is not (see the next paragraph.) So, for a single physical device, Windows can potentially create an instance node in the registry for every USB port on your system. Then, if you move it to another port Windows will attempt to install it again. When you attach a device with no serial number to a Windows PC it associates it with the specific USB port to which it is attached. In case you're wondering why Apple would do this, I have some guesses. I no longer have access to a USB protocol analyzer so I cannot confirm what is exactly occurring. It is then either deinitializing the first instance and initializing the new instance or it is just not allowing the new instance to be initialized. As such, when different instances of the same device are attached OS X treats them as the same device with the same (albeit null) serial number. Apple seems to be requring a serial number even though the spec says it is optional. But for "simple" devices, some manufacturers do not include a serial number. Most vendors include a unique serial number for their devices. SerialNumber is an optional field in the USB device descriptor. Having developed USB devices in the past, I suspect Apple is not conforming to the USB standard properly. ![]()
0 Comments
Leave a Reply. |