This question came from our site for engineers, producers, editors, and enthusiasts spanning the fields of video, and media creation.

I could tell you to check your outputs, check your meters, check your inputs, check your device console, etc etc etc. What you are trying to do is the very nature of the device you have. It sounds like you've failed to RTFM. Also, why are you not outputting sound via the mbox? Lastly, as a question. You just said in many words that you are clueless. Try to at least formulate a question if you want some help.
–
d-_-bMar 7 '11 at 7:46

3

"Lastly, as a question. You just said in many words that you are clueless. Try to at least formulate a question if you want some help." - Please try to treat people here with respect, and make sense with your own comments.
–
Sam GreeneMar 7 '11 at 21:05

@sims The last two sentences in your comment aren't really helping anything and are just calling the poster out. There are plenty of polite ways to say the same thing - in fact, you said it plenty well in the first two sentences and didn't need anything past that.
–
Warrior BobMar 9 '11 at 20:04

Doing a bit of study yourself shows respect for other people's time. I don't respect anyone who doesn't put in any effort to solving their own problem first. If you guys have time to walk someone through something, that is fine. However, this is a site for questions and answers - not really "I'm really screwed up, please help me" kind of questions. Is it not? How is this question going to help someone else? It's not. Are we trying to fill this site with useless entries? Or are we trying to catalogue useful knowledge?
–
d-_-bMar 11 '11 at 1:26

@sims, I agree its easier to have a question that is cut and dry and has a simple answer. I apologize if my question was off the mark here. But I have to admit, that a checklist answer of things to make sure are running is sufficient, and that your relpy is rude. The true answer to this question is that the stand alone drivers offers for mbox do not work on mac os x snow leopard. Once I installed proTools full version, everything worked appropriately.
–
TripMar 11 '11 at 13:55

3 Answers
3

At first I'd assume your soundcard was messed up, but the test tone works, so it has to be fine.

In Ableton Live, there are two convenient ways to see how far the audio is getting in the program. The first is to use Session view, and enable the mixer section. You'll get a meter that shows the level of audio leaving the track (so, post-effects, post-mixer). If you're getting signal here, but you aren't hearing anything, then check your master track - see if the same level shows up here when you only have that one track passing audio. You have the track outputting to Master, so it's not that setting - though I've seen that be the culprit penty of times as well.

The other way is to pull down the "Audio From" chooser for your track and look at the list of possible options. There is a tiny meter next to each one which will show you the level of audio on each input. So even if your track isn't set up right, you can see which inputs are receiving audio. It's common to simply have not enabled the correct inputs - you can see a full list of the available ones in Preferences->Audio.

The way that I would try first is plug headphones directly into your mbox, and change output settings to your mbox. Then try recording a test track and see if playback comes through your headphones. Usually for me the problem lies in sending audio to your built in output.

If you are running your speaker through your internal sound card try running them from the speaker outs of your mbox. The mbox is taking the place of your sound card.

If you are completely sure that your MPC is outputting audio on your outputs plugged into your soundcard, you may have selected the wrong inputs. Change the inputs to 3-4 or plug your MPC into the other set of inputs. It should be pretty simple - MPC -> MBox Input -> Ableton.