Got ya, wasn’t aware it wasn’t multi track capable. Agreed with Kevin on the Behringer. I have the UCM404HD if its still $99 then a good deal for price vs features and no drivers needed on OS X. Also hear good things about the UMC202HD and UMC204HD. Though I’d suggest grabbing them from sweet water since they have their own built in 2 year warranty. > On Apr 17, 2017, at 10:47 AM, Kevin Reeves <reeves...@gmail.com> wrote: > > That won't work because you're multimix is not a multi track recording > interface. What it's doing is summing both channels into one. Ditch themixer > and go get yourself a Behringer UMC 202. It's only 80 bucks on Amazon, and > has the same microphone preamp's that are on the X 32, which are fantastic. > > Sent from my iPhone > > On Apr 16, 2017, at 8:48 PM, Christopher-Mark Gilland <clgillan...@gmail.com > <mailto:clgillan...@gmail.com>> wrote: > >> OK. I'll give that a try next time I'm near my rig, then will report back. >> Thank you for the help. I very greatly do appreciate it! >> --- >> Christopher Gilland >> Co-founder of Genuine Safe Haven Ministries >> >> http://www.gshministry.org <http://www.gshministry.org/> >> (980) 500-9575 >> ----- Original Message ----- >> From: TheOreoMonster <mailto:monkeypushe...@gmail.com> >> To: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com> >> Sent: Sunday, April 16, 2017 8:36 PM >> Subject: Re: seperate inputs into multiple tracks, I'm in a predicament. >> >> Try recording to a stereo track using the input 1/2 option. Then after you >> are done right click on the track and choose the split to two mono tracks >> option. Can’t remember the exact wording but pro tools allows you to split a >> stereo track into two mono tracks >> >>> On Apr 16, 2017, at 5:03 PM, Christopher-Mark Gilland >>> <clgillan...@gmail.com <mailto:clgillan...@gmail.com>> wrote: >>> >>> OK, so let me try to explain my situation, and what I'm trying to do. >>> >>> So, I have ProTools 12, not sure the exact build, I need to look, but it is >>> 12. That much, I do! know, and OSX Siera, although I seriously doubt that >>> matters. >>> >>> I'm currently for this project using a Blue Bluebird microphone which is >>> directly connected with an XLR cable one end in the bottom of the mike, the >>> other end into the mike input 1 on my interface which is an Alesis >>> Multi-Mix 4. Then, obviously, the multi-mix 4 is simply just going into the >>> mac via USB. >>> >>> With the way that this interface works, and being it uses the native USB >>> codec OSX drivers, none specific to the board, PT only sees one IO path in >>> or out. Therefore, I had no choice but to combine both the in and out via >>> the ProTools agrigate device, then use it as my playback engine. This has >>> posed absolutely no problems whatsoever. NO latency, nothing. So far, it's >>> worked beautifully this way. >>> >>> So, I want to explain from two angles what my IO path which is super super >>> super easy looks like. IN fact, it's so easy, you're probably not gonna >>> believe how easy it is! >>> >>> For a mono audio track, under the input path popup button, if I go to >>> interface sub menu, I have 2 things. >>> >>> Main in 1 >>> and Main In 2. >>> >>> If I do the same thing on a stereo audio track, I only have one thing: Main >>> in 1/2. >>> >>> I've not totally yet determined what input 2 is used for. My guess is that >>> if I was using a stereo track, 1 would be left, and 2 would be right, but >>> since I'm normally with a mike using a mono track, that wouldn't really >>> matter as both channels would be unity. >>> >>> OK. That all said, here is what I'm trying to do. >>> >>> Normally, when I record with my mike, I set the input on a mono track to >>> main 1. I practically never have had a need to use input 2 on a mono track. >>> Again, on a stereo track, 1 and 2 are combined, but that's here not >>> rellavent. >>> >>> So, what I want to do is, I'm trying to make an audio demo which will have >>> me speaking in my mike, but then, I want to take through another channel >>> on my interface. Probably channel 2, and plug a patch cable, one end into >>> the second input on the multi-mix 4, then the other end to the headphone >>> jack of my iPhone. This way, I can patch Voiceover directly into the mixer >>> rather than miking it, which would sound God aweful! >>> >>> If I do this however, and plug that cable into the phone/second input >>> channel on the board, I then on the multimix 4 turn up my output volume >>> dial, and turn up my trim and get a good signal from the phone, what's >>> happening is, then, in PT, when I add a mono audio track, set its in to >>> main 1, and it's output to main 1/2 stereo, then arm the track, if I then >>> record, that one mono audio track is then capturing and recording both! my >>> mike, and! the input 2 from the multi-mix 4 with my iPhone. Technically, >>> this is fine, but I'd really really like to get it where somehow my mike >>> would be on one mono audio track, and my iPhone's audio would be on another >>> mono audio track. This way, I could mix each signal seperetly. >>> >>> If I set the input on a mono audio track to Main 2, then try recording, I >>> get no audio at all. Just dead silence. >>> >>> Before you say, check the configuration in the multi-mix 4's software >>> panel, I can't. There is none. This interface doesn't have any software, no >>> drivers, nothing. You just plug it in, and it just simply works. Or, shall >>> I be a smart ass and say... doesn't work. LOL, in this case. >>> >>> So, is there any way to do this, based on the info I've provided? >>> >>> Chris. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com >>> <mailto:ptaccess+unsubscr...@googlegroups.com>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com >> <mailto:ptaccess+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com >> <mailto:ptaccess+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ptaccess+unsubscr...@googlegroups.com > <mailto:ptaccess+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>.
-- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
