- #Mbox 2 pro manual how to#
- #Mbox 2 pro manual manual#
- #Mbox 2 pro manual pro#
- #Mbox 2 pro manual free#
i do this so i can leave the source track alone to blend in w the samples and or just so i have it to go back to if needed. If latency caused from other plugs for sampling or sample replacement, i always duplicate the track i am replacing (shft alt d) and then nudge the track i am replacing back by the needed amount of samples. from here i ALWAYS note my nudge amount in the comments section on that track. obviously choose to nudge it earlier, then enter number of samples from your dly reading in the samples heading and hit ok. if latency caused by plugs for dynamics such as eq and compression, you could select (hilight) the entire track (all regions) and then hit alt h, this will pull up a window that will allow you to give exact parameters to nudge the selected regions. but is typically the best starting point and depending on the user might be fine.įrom here, would be situation dependant. The previous post about clicking on the numerical vol readout while holding control is correct and go to the dly reading. Where do you even get that kind of information.
#Mbox 2 pro manual pro#
I have MacBook Pro late 2011, Mbox 2 Pro and Mavericks 10.9.4.
#Mbox 2 pro manual how to#
I of course understand how to apply delay to a track (or use nudge), but I don't know anything about calculating values or determining values of delay. Im Pro Tools 10/11 user who is willing to switch to logic pro x for producing dance music. I'm always reading about ADC, and lots of LE users talk about how they are used to making delay calculations by hand, and then implimenting those delays on the tracks that need them.Ĭan anyone give me any insite as to how to start understand calculating plugin delay by hand.
#Mbox 2 pro manual manual#
I'd love some insite as to how to calculate the delays of various plugins (I use a lot of Waves stuff) to creat manual delay compensation. Hey.if it was easy.every useless article (including me.of course) would be doing it.I guess at some point every mid level user askes this question. around until it works ok.pain in the butt. EMU 0404 USB good and Tascam US144 not so good apparentlyīottom line is it's probably not just Digi's products (although it might be a bit worse in their case) and you just have to d. Manufacturers often dont tell us about this and SOS have measured it in a number of tested interfaces. Have read articles in SOS regarding USB Interfaces and so-called output buffering which is in addition to recording latency. Have also recorded Gtr and Vox track audio (overdub situation) and no problem with all the tracks, audio and MIDI lining up fine.Ī royal pain in the ass.but it seems to work.so far.
Have recorded MIDI track using virtual piano and it 'plays' OK (rec and p back).
MBox2 ASIO buffer size 256 samples and recording input manual offset -505 samples (using Schwa's figs 256-761) gives me a reap latency (top line) of ~22/16ms ASIO. Have been messing with this for couple of days. Well thats kinda useless.another question:is there a differet latency for midi and for audio?what i mean is if i have the latency set right for audio is it possible for the midi latency to still be off, when using a midi keyboard for example?
#Mbox 2 pro manual free#
Now my only question is will this need to be readjusted if i add more tracks to a recording or say if i add more effects to a particular audio track while recording?īasically what im asking is is this a reliable way of doing things or is this all gonna go out the window once i actually start doing some work.i really dont wana find out after putting half a song together that this hasnt work, my free time is kinda scarce if not valuable
So on 512 buffer size i set the manual offset to either -1333 or -1330 i cant decide which is more accurate maybe ill post some screen shots, but i am guessing that 3 samples is negligible to the human ear right? i mean im doing this visually by zooming in not by ear and my ear cant tell the difference between the two. Ok so ive tried to manually adjust the "input offset" to make things line up correctly, i did this by playing a simple midi beat and recording it onto and audio track and making sure that they synced up, and then i took the differnce and added it to the manual offset,