Blue Yeti and Korg PadKontrol together
It's good to see that GB recognises Yeti as a stereo mic and that my Korg PadKontrol works like a dream with very low latency...however, I decided to push my luck and boot up GB with both the Yeti & Korg plugged into the powered USB hub.
GB didn't like this one bit! Both Yeti & Korg lit up but the app became unresponsive and then the ipad crashed completely (I thought I'd bricked it!)
So my question is: Has anyone managed to have more than one usb device spliced into GB via the HUB?
I know that you can only have one armed track at the moment and so don't really need to have multiple input devices attached at the same time. However, it would be really cool to not have to be pulling cables in and out every time you want to change instruments.
I know I'm asking a lot from this amazing little app but I am sure that it will evolve rapidly and become the number one portable DAW for years to come.
A few things to check. Make sure each track is assigned to the correct mic. Make sure the yeti is working by tapping on it to see if the track meter responds. Make sure you don't have any effects on the track. Make sure your aggregate mic settings are correct in the Audio Midi setup utility.
Similar Messages
-
I Have set my Audio Midi Setup under Audio Devices to Aggregate Devices and selected M-Audio MobilPre USB and Blue Yeti Microphone.
I plugged my MobilPre into one USB port on my MacBook and the Blue Yeti Mic into the other USB on my MacBook. So I have two inputs
and I set each device for OUTPUT as the HeadPhones from the Blue Yeti Mic. I still cannot record the vocals on the blue yeti and the Guitar on the MobilPre
At the same time even though both show the rec button is active on both. What do I need to do to get these to both work recording at the same time?I'm not sure what you mean by "mixed with audio in Alsamixer". Can you clarify?
With that said, my problem did mysteriously fix itself after some update (presumably to alsa). Unfortunately, I noticed it in passing one day while I was changing the volume of something in pavucontrol, so I don't remember the exact update that caused it to work. But yes, my current setup does work now: I can listen to audio through my DAC and use the Yeti for recording. However, I have found that use of the Yeti crashes Google Hangouts, although it works perfectly in every other program I've tried.
As documentation, here is my current working setup (it is very similar to the above): in PulseAudio, the DAC is set to be a Digital Stereo (IEC958) output. The Yeti (called an 'Integrated Rate Matching Hub' in pavucontrol) is set to be an Analog Stereo Input. In the input devices section, I have the Yeti's volume set to around 58% (-14.31 dB), which is past the base volume a fair ways but produces decent levels for recording. The DAC's volume is set to 100% (0dB gain, the DAC takes care of the level). In alsamixer, I have the mic level for the Yeti set to 40.
Edit: This is a long-time-later edit, but let me say that when you have multiple USB audio devices, what USB hub and in what order they are connected seems to matter a great deal. If you can't get your Blue Yeti to work, try moving it to a different set of USB ports (controlled by a different controller) on your motherboard. This magically fixes the issue for me.
Last edited by rwiggins (2014-12-14 00:26:39) -
First, Happy New Year!!!
I am trying to control UtraBeat with my Korg padKontrol.
I currently am getting the pads set up the way I want. However, anytime I try to get the 2 knobs or XY to control anything, like pitch or decay, I am not getting anywhere.
The PadKONTROL has assign buttons for the XY pad and 2 knobs. Then it has 8 pads that I can touch plus these mentioned assign buttons to change the XY pad or knobs to 8 different control settings, like pitch, decay, volume, pan, and so on... I want these to work on each selected voice in Ultrabeat individually. Does the settings on Ultrabeats midi controller assignments A, B, C, & D work on a voice per voice basis?
Some of what follows is PadKONTROL jive for any here using it, but Ultrbeat pros, please read on as well:)
On the PadKONTROL I will touch KNOB 1 ASSIGN + <PITCH>. Then in Ultrabeat I will set MIDI CONTROLLER ASSIGNMENT A to PITCH. Then, select ASSIGNMENT A's LEARN function. Then turn KNOB 1 on the padKONTROL and Logic recognizes it and seems to accept it. However when I select the correct voice in UltraBeat, trigger it and turn the knob on the PadKONTROL... I don't see or hear any pitch changes.
Maybe this lies somewhere in Logic's environment (still a noob at that). Maybe I need to assign a specific note to the knobs for UltraBeat to use it as I want. (I haven't located the documentation on this if there was any.)
Does anyone have any insight on using them together as I am trying to do.
THANKS!!
Message was edited by: PlayWhich drum instrument are you triggering with padKontrol?
I assume you've selected whichever it is on an instrument track's input, and that same tracks output is 1-2.
All you need do now is to create a Scene which maps pK's triggers to the instrument, or use one of the default Scenes which most closely matches your instrument, such as DFH or BFD or use one of the GM Scenes - 7 or 8 I think - and that should get you started. Just hold down the scene button and press 7, for example.
I recently purchased a Korg padKontrol MIDI studio controller to use as a drum machine
At the risk of telling you something you already know, you do know that padKontrol in itself doesn't create sounds? It just triggers an instrument installed within Logic. -
I have three Blue Yeti USB Microphones, and when I try to create an aggregate device in Audio MIDI on my MBP it lets me select two microphones but not the third. At first I thought maybe the third microphone was just defected or something but I tested the mic individually and it works fine. It'll let me use two Blue Yeti's and another microphone but not three Yeti's at once.
David Boroditsky wrote:
The problem is that the mac chokes on having 2 identical mics attached at the same time.
Ive had 2 identical USB AT2020 mics connected at the same time on both macbook pro and macbook Air.
The "Yeti" mics, are, lets say undesirable, and low to mid computer consumer mics. -
My phone died last night and when I plugged it in it wouldn't turn on.I tried restarting it but it has yet to turn on since last night,It was just a black screen,i try the on/off and home buttons together but its not working,What should I do?
How long have you had your phone? Because if you've had it a long time, the battery in the phone might of died on you. Or have you dropped it in water, snow, from high up? All those things could of disconnected something internally in your phone, or permentaly damaged the internal hard drive its self, or the sims card.
-
Can anyone help with the blue screen I just got. Tried to power back up like one Apple user suggested by holding the power and screen button together, came back briefly, then shut down. Now nothing. Any help?
Plug your device into the original charger & block in a wall outlet and leave it alone for a couple of hours. Then, while it is still plugged in, restart it by holding down the home button and the power button for 10-15 seconds until you see the Apple, then let go.
-
I'm trying to help a friend record Skype calls using a Blue Yeti mic. Windows 7 and Adobe Audition 5.5. He wants to record both the mic signal and the Skype audio at the same time. I tried selecting 'stereo mix' as the input device, but audition keeps showing a sample rate error. I suspect a conflict between the blue mic and the on board sound card. I'm hoping someone here has a way to make this work!?
The issue is related to Adobe Audition and your Windows audio settings. Nothing really to do with Skype. You might find this thread in the Adobe forums helpful:
https://forums.adobe.com/thread/858016 -
Blue Yeti USB microphone not working in ALSA/PulseAudio
Hi all,
I recently bought a Blue Yeti USB microphone. It is supposed to require no drivers for Windows and OS X, and so far, it works well under Windows, but I cannot seem to get it to function on Arch Linux. As fair warning, although I am relatively experienced with Linux, I don't know much about the internals of ALSA/PA --- up until now, it has just "always worked", so this is my first real foray into the area. I've tried for many days, with no success, to get this thing working.
So, let's start off first with my configuration.
I have a few audio devices:
An on-board audio solution that I don't typically use. For testing, I have connected an old, crappy pair of headphones, but normally I keep this disabled. It has one capture device. (Analog stereo [or 5.1/7.1/etc] duplex)
An external DAC that is connected via USB and is output-only. So, no capture devices on that. (Digital/IEC958 output)
The Blue Yeti itself, which is connected via USB and supports output (it has an internal DAC) as well as input. So, one capture device here. (Digital stereo output and analog stereo input???)
The HDMI-out stuff for nvidia, which I never use
Here is the output of "arecord -l":
**** List of CAPTURE Hardware Devices ****
card 1: Microphone [Yeti Stereo Microphone], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 2: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 2: PCH [HDA Intel PCH], device 2: ALC892 Alt Analog [ALC892 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Here is the the output of "arecord -L":
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default
Default ALSA Output (currently PulseAudio Sound Server)
sysdefault:CARD=Microphone
Yeti Stereo Microphone, USB Audio
Default Audio Device
front:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
Front speakers
surround40:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Microphone,DEV=0
Yeti Stereo Microphone, USB Audio
IEC958 (S/PDIF) Digital Audio Output
sysdefault:CARD=PCH
HDA Intel PCH, ALC892 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
Front speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
Here is the output of "aplay -l" (for completeness):
**** List of PLAYBACK Hardware Devices ****
card 0: Audio [USB2.0 High-Speed True HD Audio], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Microphone [Yeti Stereo Microphone], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 2: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 2: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
If the output of "aplay -L" is needed, let me know, but it's not all that different from arecord -L.
Here is my /etc/asound.conf:
defaults.pcm.rate_converter "samplerate_best"
pcm.!default {
type pulse
fallback "sysdefault"
hint {
show on
description "Default ALSA Output (currently PulseAudio Sound Server)"
ctl.!default {
type pulse
fallback "sysdefault"
# vim:set ft=alsaconf:
I don't remember where the bulk of that came from; maybe it was installed like that or maybe I put it in there. Here is another useful command showing non-commented-out/non-blank lines in the pulseaudio conf:
$ egrep -v '^;|^#|^$' /etc/pulse/*.conf
/etc/pulse/client.conf:autospawn=no
/etc/pulse/daemon.conf:exit-idle-time=0
/etc/pulse/daemon.conf:default-sample-rate = 192000
So, there's not much I've done there. Here's the contents of /proc/asound/cards:
0 [Audio ]: USB-Audio - USB2.0 High-Speed True HD Audio
CMEDIA USB2.0 High-Speed True HD Audio at usb-0000:00:1d.0-1.7, high speed
1 [Microphone ]: USB-Audio - Yeti Stereo Microphone
Blue Microphones Yeti Stereo Microphone at usb-0000:00:1d.0-1.8, full speed
2 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7530000 irq 52
3 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xf7080000 irq 17
And here's the contents of /proc/asound/modules:
0 snd_usb_audio
1 snd_usb_audio
2 snd_hda_intel
3 snd_hda_intel
Now, here is the output of "pactl list sources" (the Blue Yeti is last in the list):
Source #3
State: RUNNING
Name: alsa_input.pci-0000_00_1b.0.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 192000Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes
Volume: front-left: 17972 / 27% / -33.71 dB, front-right: 17972 / 27% / -33.71 dB
balance 0.00
Base Volume: 6554 / 10% / -60.00 dB
Monitor of Sink: n/a
Latency: 610 usec, configured 100000 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC892 Analog"
alsa.id = "ALC892 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "2"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7530000 irq 52"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1b.0"
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card2"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:2"
device.buffering.buffer_size = "76800"
device.buffering.fragment_size = "19200"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC892"
alsa.components = "HDA:10ec0892,10438436,00100302"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-input-front-mic: Front Microphone (priority: 8500, not available)
analog-input-rear-mic: Rear Microphone (priority: 8200, available)
analog-input-linein: Line In (priority: 8100, not available)
Active Port: analog-input-rear-mic
Formats:
pcm
Source #11
State: RUNNING
Name: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
Description: Monitor of Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 192000Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
Latency: 0 usec, configured 100000 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.description = "Monitor of Built-in Audio Analog Stereo"
device.class = "monitor"
alsa.card = "2"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7530000 irq 52"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1b.0"
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card2"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"
device.form_factor = "internal"
device.string = "2"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Formats:
pcm
Source #15
State: RUNNING
Name: alsa_output.usb-CMEDIA_USB2.0_High-Speed_True_HD_Audio-00-Audio.iec958-stereo.monitor
Description: Monitor of USB2.0 High-Speed True HD Audio Digital Stereo (IEC958)
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 192000Hz
Channel Map: front-left,front-right
Owner Module: 8
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: alsa_output.usb-CMEDIA_USB2.0_High-Speed_True_HD_Audio-00-Audio.iec958-stereo
Latency: 0 usec, configured 100000 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.description = "Monitor of USB2.0 High-Speed True HD Audio Digital Stereo (IEC958)"
device.class = "monitor"
alsa.card = "0"
alsa.card_name = "USB2.0 High-Speed True HD Audio"
alsa.long_card_name = "CMEDIA USB2.0 High-Speed True HD Audio at usb-0000:00:1d.0-1.7, high speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-0000:00:1d.0-usb-0:1.7:1.0"
sysfs.path = "/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.7/6-1.7:1.0/sound/card0"
udev.id = "usb-CMEDIA_USB2.0_High-Speed_True_HD_Audio-00-Audio"
device.bus = "usb"
device.vendor.id = "0d8c"
device.vendor.name = "C-Media Electronics, Inc."
device.product.id = "0319"
device.product.name = "USB2.0 High-Speed True HD Audio"
device.serial = "CMEDIA_USB2.0_High-Speed_True_HD_Audio"
device.string = "0"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-usb"
Formats:
pcm
Source #19
State: RUNNING
Name: alsa_output.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00-Microphone.iec958-stereo.monitor
Description: Monitor of Integrated Rate Matching Hub Digital Stereo (IEC958)
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 9
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: alsa_output.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00-Microphone.iec958-stereo
Latency: 0 usec, configured 100000 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.description = "Monitor of Integrated Rate Matching Hub Digital Stereo (IEC958)"
device.class = "monitor"
alsa.card = "1"
alsa.card_name = "Yeti Stereo Microphone"
alsa.long_card_name = "Blue Microphones Yeti Stereo Microphone at usb-0000:00:1d.0-1.8, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-0000:00:1d.0-usb-0:1.8:1.0"
sysfs.path = "/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.8/6-1.8:1.0/sound/card1"
udev.id = "usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00-Microphone"
device.bus = "usb"
device.vendor.id = "b58e"
device.vendor.name = "Intel Corp."
device.product.id = "9e84"
device.product.name = "Integrated Rate Matching Hub"
device.serial = "Blue_Microphones_Yeti_Stereo_Microphone_REV8"
device.form_factor = "microphone"
device.string = "1"
module-udev-detect.discovered = "1"
device.icon_name = "audio-input-microphone-usb"
Formats:
pcm
Source #23
State: RUNNING
Name: alsa_input.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00-Microphone.analog-stereo
Description: Integrated Rate Matching Hub Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 9
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 17775 / 27% / -34.00 dB
Monitor of Sink: n/a
Latency: 949811526 usec, configured 100000 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "USB Audio"
alsa.id = "USB Audio"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "1"
alsa.card_name = "Yeti Stereo Microphone"
alsa.long_card_name = "Blue Microphones Yeti Stereo Microphone at usb-0000:00:1d.0-1.8, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-0000:00:1d.0-usb-0:1.8:1.0"
sysfs.path = "/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.8/6-1.8:1.0/sound/card1"
udev.id = "usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00-Microphone"
device.bus = "usb"
device.vendor.id = "b58e"
device.vendor.name = "Intel Corp."
device.product.id = "9e84"
device.product.name = "Integrated Rate Matching Hub"
device.serial = "Blue_Microphones_Yeti_Stereo_Microphone_REV8"
device.form_factor = "microphone"
device.string = "front:1"
device.buffering.buffer_size = "19200"
device.buffering.fragment_size = "4800"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Integrated Rate Matching Hub Analog Stereo"
alsa.mixer_name = "USB Mixer"
alsa.components = "USBb58e:9e84"
module-udev-detect.discovered = "1"
device.icon_name = "audio-input-microphone-usb"
Ports:
analog-input-mic: Microphone (priority: 8700)
Active Port: analog-input-mic
Formats:
pcm
Honestly, I think that's about all of the configuration info I can give. Here are some screenshots of pavucontrol, though, in case you are not yet sated: http://imgur.com/a/ngyLl
Now, on to the debugging stuff. First: everything except Blue Yeti recording works. The external DAC works, the on-board audio (both input and output) work, using the DAC in the Blue Yeti to play music/monitor the microphone works (so it works as an output). The only thing that doesn't work is actual recording from the Blue Yeti itself.
When I try to record from the Blue Yeti with parecord -v, I get very strange behavior. Essentially, the "latency" of the microphone measured is exactly the same as the time it has been recording. That is, if it has been recording for 5 sec, then the latency is 5000000 usec. Also, if I try to record something in Audacity, I get no result except for a message box that says "Latency Correction has caused the recorded audio to be hidden before zero. Audacity has brought it back to start at zero." Also, pavucontrol doesn't show an input volume bar for the Blue Yeti, as in the above screenshots, whereas it normally will for microphones that are getting input. The Yeti is not muted, either, so it should be picking up ambient fan noise and such.
Does anyone have any ideas? Is there some configuration error I've made? Typically, this sort of stuff simply works out of the box for me, so I am somewhat stuck on what to do. Could it be a driver-level bug?I'm not sure what you mean by "mixed with audio in Alsamixer". Can you clarify?
With that said, my problem did mysteriously fix itself after some update (presumably to alsa). Unfortunately, I noticed it in passing one day while I was changing the volume of something in pavucontrol, so I don't remember the exact update that caused it to work. But yes, my current setup does work now: I can listen to audio through my DAC and use the Yeti for recording. However, I have found that use of the Yeti crashes Google Hangouts, although it works perfectly in every other program I've tried.
As documentation, here is my current working setup (it is very similar to the above): in PulseAudio, the DAC is set to be a Digital Stereo (IEC958) output. The Yeti (called an 'Integrated Rate Matching Hub' in pavucontrol) is set to be an Analog Stereo Input. In the input devices section, I have the Yeti's volume set to around 58% (-14.31 dB), which is past the base volume a fair ways but produces decent levels for recording. The DAC's volume is set to 100% (0dB gain, the DAC takes care of the level). In alsamixer, I have the mic level for the Yeti set to 40.
Edit: This is a long-time-later edit, but let me say that when you have multiple USB audio devices, what USB hub and in what order they are connected seems to matter a great deal. If you can't get your Blue Yeti to work, try moving it to a different set of USB ports (controlled by a different controller) on your motherboard. This magically fixes the issue for me.
Last edited by rwiggins (2014-12-14 00:26:39) -
MacBook Pro hanging with blue screen and spinner after installing Software Update
Hi I was wondering if someone could help me with this current issue. Just a few hours ago I finished reinstalling Mac OS X Snow Leopard in my MacBook Pro. I performed a clean installation as part of a yearly spring cleaning that I do on all my systems to keep them optimized. So there was I downloading some software updates which included the combo update of OSX 10.6.8 and others. The updates finished downloading and the system logged out to install the updates, when the updates finished installing my MacBook proceeded by logging out into a blue screen and show a gray spinner similar to the one seen when you start your Mac. Here's the problem after 2 hours the system is showing the spinner and the blue screen, I think that my computer has just hanged in the reboot process.
I was wondering what should I do? Do a force restart? Or leave it overnight?
Also, where can I find any information on what error is causing this issue?
I appreciate your responses and help.
By the way, I installed Mac OS X from a USB stick that has the original image of the disk installer that came bundled with my computer.Kappy wrote:
Force a shutdown. Do not restart yet, but first do the following:
Repair the Hard Drive
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next, boot into Safe Mode then restart normally.
Hi Kappy,
Checked the hard drive after forcing a shutdown and booting from my Snow Leopard Installer USB Key and the status of the HDD says "Verified". I ran the repair and the volume was repaired successfully. Clicked on "Verify Disk" and it says "Macintosh HD appears to be OK". So I ran a second repair and again no errors were reported.
As suggested I booted back again in Safe Mode and restarted normally. All software appears to have been installed successfully. But I don't understand why my computer hanged and showed the spinner after installing the updates in the blue screen that appears just before rebooting. I am aware that the system shows that spinner after a OS update but the longest it lasts is 30 seconds at the most in my previous cases. -
I'm trying to install windows 8 on mac, but after partitioning and restarting, it stucks on blue logo and i waited 20 minutes but nothing happened, what can i do, please help.
I think there's some remmants left over from when Apple transferred stuff over. We can try a quick fix, but if that doesn't work, I think the only option is to clean install OSX and then install Windows.
open disk utility, confirm that you only have 1 partition (mac journaled)
restart and PRAM reset
open disk utility and repair permissions twice
restart boot camp assistant
Does it work?
If not, I would boot holding command+R, choose disk utility from the menu and completely erase your HD (formatting it as mac journaled again). Then, install OSX on this HD. Once OSX is installed, don't copy your files over from the backup yet. Instead, start boot camp assistant and see if you can get Windows installed. You can copy back your other files after we get Windows installed. -
my ipod screen has went white i have tried plugging it into itunes and pressing the home button and top button together for 10 seconds but it wont work!! this has happened twice before already and i havent even had it a year yet, i should have listened to my sister and never have bought one!!! someone help please ?
- Connect to computer and it it shows in iTune restore via iTunes
- Then try letting the battery fully drain. After charging for an hour try the reset (both buttons) and connecting to computer and restore. -
Blue Yeti / Garage Band / MBP-retina / No audio upon second take.
Hi:
I have a 2012 MacBook Pro retina display (Build 12A269) running OSX 10.8. In "Garage Band" I can record a track using the Blue Yeti with success. Upon play-back of that track I hear no audio. If I then unplug the Blue Yeti from the laptops USB I get the option to "Use Built-in Audio". I select that option. If I then play the track (third attempt) it will successfuly play.
I've done a test with another microphone, the Apogee MiC. With this mic connected (USB - same port) I have no issues. I can record and play-back that track with success.
Can anyone help me get my Blue yeti working?
Thanks
PS: I've made sure that my computer has been updated by searching for updates. None were found.Sure thing, I can help. The problem is that Garageband sees the Blue yeti as an source to output audio when the mic is connected. Here is the fix.
1. Open Garageband.
2. Connect the Blue Yeti.
3. Click your pointer on "Garageband" that is next to the small apple logo at the upper-left on the screen.
4. A dropdown will appear. Click your pointer on "Preferences"...
5. ...then "Audio/Midi"...
6. ...then "Audio Output".
7. Selct the "Built-in Output" option.
If you need more help email me. [email protected] -
Premiere Pro CC won't recognise a Blue Yeti Mic-.but only on an iMac?
Hi There
I have a Blue Yeti Microphone that works perfectly with Premiere Pro CC on my Macbook Pro, but on my new iMac it isn't listed in the dropdown menu in the Audio Hardware settings.
The iMac is recognising the Microphone in system Prefs and Audio Midi setup. It also recognises it in Final Cut Pro and in Adobe Audition so it's definately something to do with Premiere Pro.
Any help would be really appreciated.
Many thanksM3PBoss wrote:
Sorry to dig this back up. but the .pdf link is broken. I have a Blue Eye Ball that I'm using for audio,
and am having the same problem. I've checked it out using other programs, and it's not the mic, so...?
Run the "MIDI Setup" tool on the Mac (comes w/OS X) and create a new Aggregate device. In that agg device, add the Blue mic and whatever sound output you're using (Line Out, Headphones, etc). Close the MIDI Setup App. In Pr, select that new Agg device as your sound device. In order to record from it, you'll need to create a new mono audio track. Once done, you should be free to record from it. -
My ipad mini 2 gets blue screen and then keep restarting over and over again problem
My ipad mini 2 gets blue screen and then keep restarting over and over again problem. I tried to restore to the factory setting but it was not successful to fix the problem. Sometimes I could not even restore. How can I do with this kind of problem?
I'm very frustrated now. Please help me!I have the same issue and have not found a way to fix it yet. I cant even down grade back to 8.2 because it wont stay on long enough.
-
Blue Yeti microphone problem with iPad 2!
I have a Blue Yeti microphone which I connect to a powered hub (Logik LP4HUB10) and an Apple camera connection kit which I then have used through GarageBand on my iPad 2. Due to various reasons I did not use the Yeti for about 9 months or so. Anyway, when I returned to use it today, when I plug in (through recommended connection sequence) and turn on GarageBand, the microphone does not work. The light is on constantly (doesn't even blink when I press the mute button) and GarageBand does not seem to acknowledge the microphones existence (not even an error message of any sort). I have tried the microphone on my PC and it works fine. The Yeti previously worked fine through GarageBand on my iPad 2. Therefore, can anyone provide any help at all? Any help would be greatly appreciated.
Many thanks,
CIt's really hard to say why it's not working since it should not work to begin with.
That's a completely unsupported configuration and could very well damage your iPad.
Maybe you are looking for
-
How to add a child at the top of the z-order(above a mobile textinput field)?
We posted a problem yesterday with PopupManager where in a mobile app, we experience some strange problems, and have had to make our own modal Alert panel to solve the problem. The problem now is that if the alert panel is displayed over a TextInput
-
Incorrect aggregation in parent after deleting data in any child member
Hi Experts, Currently we are facing a problem in which data are aggregating at parent level properly except in cases where data were already present and subsequently has been deleted. For example if '1000' has been entered in a child level member, it
-
Just thought that I should mention that PSE9 stops running when Elements is importing picture files and comes across an accidental MP4 extension. In Windows 7 it needed the Task Manager to restart. This user is stupid enough not to have checked that
-
Handle Process Finish (TS40007947) step of WS40000014 ending in error
Hi, We have implemented a process-controlled workflow for shopping cart on SRM 7. Schema evaluation and corresponding process level configuration has been done, including the responsible resolver and the enhancement implementation. When a shopping ca
-
i have a brought cd that is in the itunes store but when i go to add to to my list is says not on net data base. my own copy i brought! how do i solve it i do not want to type over 50 songs in to computer.