omni/native latency vs mbox pro latency

[chrisdee]

Originally Posted by Shan

[URL="http://img844.imageshack.us/img844/5315/llmh.png"] keep the buffer at 1024(Except MIDI production)

I mostly compose so i use VIs in every session.

[filosofem]

The latency besides MBox Pro direct monitoring is far superior with PCIe based Native card. Check this latency graph out if you have not seen that already. Running a Nehalem based Extreme processor or Sandy Bridge based Extreme processor with a Native card at H/W Buffer sizes of 64 or 32 Samples with large audio and MIDI track counts is very achievable. RTAS VI's aside running VSTi's with VEP is still preferable. It's my opinion that VEP will still have it's place in the new era of 64-bit Pro Tools.

[chrisdee]

Hi again.

Im thinking about upgrading to hd from my mbox 3 pro.

Im close to buying an Native + Omni for my home studio but just wanted to clear up something
i feel i didnt get an direct answer to last time i asked.

Does the omni have DM(direct monitoring) so i can track a vocalist with almost zero latency
(like i can with my mbox pro direct monitoring) ?

[filosofem]

Originally Posted by chrisdee

Does the omni have DM(direct monitoring) so i can track a vocalist with almost zero latency (like i can with my mbox pro direct monitoring)?

Hey Chrisdee, I believe there are only two latency options LLM or H/W Buffer.

[Greg M]

You can directly monitor your input to an Omni. Or, you can use LLM, or use a low buffer setting.

Greg

[chrisdee]

Originally Posted by Greg M

You can directly monitor your input to an Omni. Or, you can use LLM, or use a low buffer setting.

Greg

Great. So omni has direct monitoring.

Have you tested when tracking vocals, guitars etc if direct monitoring sounds much different from LLM or buffers size of 32 samples ?

[Greg M]

Yes and there is no discernible delay in any of the 3 methods. Using the Omni and an HD I/O 16x16 with an HD|Native card is way faster than any firewire interface. I still have an 002r rig and I can tell you that a buffer of 64 with HD|Native is way faster than 64 with the 002r. With the low buffer setting or LLM you just can't do something unreasonable like put a mastering plug with 10,000 samples of latency on the 2 bus when you track.

Anyone who is getting discernible latency with an HD|N rig and a powerful computer has got something else going on.

Hope this helps,
Greg

[chrisdee]

Thanks Greg.

Does it work with PT 10 and is it possible to playback also outside PT like in windows media player, vlc , streaming, youtube , etc ?

[Greg M]

I have no problems with Omni and PTHD10.0.1. It works just fine with apps such as Sony Vegas and ACID as well as Reason 6 via the Avid ASIO driver. What I do for streaming media and other outside apps is use the SPDIF output from the MoBo on board sound to SPDIF in on the Omni - and it works seamlessly. I don't think Avid provides a Windows Classic Wave driver for PTHD10, really no need for it.

Greg

[chrisdee]

Originally Posted by Greg M

I don't think Avid provides a Windows Classic Wave driver for PTHD10, really no need for it.

Greg

Well, it would be nice to have a wave driver for times when I want to go out on youtube or itunes, etc to listen to other music to get ideas/compare to my own. But maby Omni is more a tool for the recording/mixing engineer than the recording/mixing artist ?