Search the Community
Showing results for tags 'm-audio'.
Hi. I have had my pod for about a month now and really like it and have learned my way around it, it's pretty easy to use. I have been using usb with my pod being the input and my audio interface being the output while recording with Logic Pro x. I would like to make use of the spdif and use that instead of usb, I won't get into why unless you want to know. So my gear is my 500x, a m-audio profire 610, and logic prox, I am using spdif now and it's working but I just want to know if I have it set up correctly. The sample rates match and are 44.1 and my interface is set to internal. When my interface is set to internal does that mean my interface is the master? And what should be the master? The pod or interface? Does it matter?
Hi there, I used to connect the unbalanced 1/4" OUT of my HD500X into the line input of my M-Audio M-Track. With this configuration I was able to adjust the gain one the soundcard linearly, using the whole stroke of the knob. Now I'm using the HD500X connected with the M-Track with the XLR balanced outputs and with this configuration the first 3/4 of the gain knob have no influence on the signal, only the last 1/4 daoes, and it's obviously very sensitive. I don't know if it's a soundcard issue or if there are differences in POD signal using balanced vs unbalanced outputs. Can anyone help me? Thanks in advance
I have an extremely weird problem thats been going on for a while but is getting worse. I practice by connecting my M-audio keyboard to garageband. Garageband then outputs the sound to my UX2 which then connects to a PA system. The problem is that sometimes (or very often recently) a large pop goes of and once the pop goes of the keyboard still has its blue lights on to show its connected, but playing it doesn't do anything. Here's the weirdest part; if I turn the keyboard on and off it starts to work but the sustain pedal starts working in reverse! No matter how many times I turn it on and off, whether the pedal is depressed when I do this or not, the problem remains. The only way to solve it is to wait maybe 20 minutes or unplug and plug back in the UX2! Its strangest problem and I don't know what is causing it. The keyboard requires no drivers and all mu UX2 ones are up to date. Please could someone make some suggestions as to what the problem might be?