Google can be good...............so there is 164 samples of latency on any
track recorded with Digi's M Box...............regardless of whether you're
monitoring with zero latency. Am I understanding correctly?



My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm

No. When you're monitoring the input, there is ZERO latency, just mute your
record enabled tracks and use the mix knob until the balance works.

F.W.I.W. - I think the Mbox sounds great, I use it for all my pre-production
recording.

Jack

"Mondoslug1" wrote in message
...
Google can be good...............so there is 164 samples of latency on any
track recorded with Digi's M Box...............regardless of whether
you're
monitoring with zero latency. Am I understanding correctly?



My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm

No. When you're monitoring the input, there is ZERO latency, just mute your
record enabled tracks and use the mix knob until the balance works.


Okay I thought everything was off by that amount which may not be a problem for
some.



F.W.I.W. - I think the Mbox sounds great, I use it for all my pre-production
recording.

Jack

"Mondoslug1" wrote in message
...
Google can be good...............so there is 164 samples of latency on any
track recorded with Digi's M Box...............regardless of whether
you're
monitoring with zero latency. Am I understanding correctly?



My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm















My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm

Okay I thought everything was off by that amount which may not be a problem
for
some.


I won't be off by that amount if you choose to listen direct through the mix
knob. Also the latency you where monitoring through protools software will
change based on the buffer size. None this the changes the 164 sample thing
though. At


---------------------------------------
"I know enough to know I don't know enough"

There was some heavy discussion about this in the DUC.

The zero latency monitoring is zero latency because it's a direct feed from
the input - no A/D - D/A conversion, but the resulting recorded signal is
xxx samples late. The workaround is to always shift the track you just
recorded that many samples up, which from what I hear gets pretty ingrained
after a while... Just set it up to some sort of hot key.

Visit the DUC & look up latency.

* DUC = Digidesign Users Conference go to Digidesign.com, I think it's in
the support area.

Regards,
Mark

--
http://www.marktaw.com/

http://www.prosoundreview.com/
User reviews of pro audio gear

http://duc.digidesign.com/cgi-bin/ub...ubb=forum;f=32

This is the link to the conference on Windows issues.

I visited DUC and there are many articles on latency. Too many to go
through. Do you remember a key word from the subject of the DUC thread most
likely to be helpful here?

In the meantime, I found this. I have no idea whether this is true or not.

Teleplayer on DUC wrote:

The latency is purportedly 164 samples - but PTLE 5.3.3 for Windows corrects
for it, so if you use the Mbox mixer for zero-latency monitoring, latency is
a complete non-issue.

Do NOT follow any advice to slide tracks back 164 samples, it's not correct
for 5.3.3 Windows Mbox, and it will screw up your timing.

I'm pretty sure PTLE will use whatever MIDI ports are installed on the
system - I know it does on my 002. I only had an Mbox for a few days, and
didn't get around to trying MIDI.

Input monitoring is on the headphone jack ONLY, if I recall correctly.

I highly recommend Mbox to all my friends. It's very cool.
----------------------------------------------------------------------------
----

I assume latency is a different number if you patch in a different AD
through the spdif input.

--
___
Rick Knepper
MicroComputer Support Services
Knepper Audio
Ft. Worth, TX
817-239-9632
413-215-1267 Fax
PC Tech Support & Equipment Sales
CDR Duplication & Audio Mastering
Recording
http://www.rknepper.com

"Mark T. Wieczorek" wrote in message
...
There was some heavy discussion about this in the DUC.

The zero latency monitoring is zero latency because it's a direct feed
from
the input - no A/D - D/A conversion, but the resulting recorded signal is
xxx samples late. The workaround is to always shift the track you just
recorded that many samples up, which from what I hear gets pretty
ingrained
after a while... Just set it up to some sort of hot key.

Visit the DUC & look up latency.

* DUC = Digidesign Users Conference go to Digidesign.com, I think it's in
the support area.

Regards,
Mark

--
http://www.marktaw.com/

http://www.prosoundreview.com/
User reviews of pro audio gear

Rick Knepper wrote:

http://duc.digidesign.com/cgi-bin/ub...ubb=forum;f=32

This is the link to the conference on Windows issues.

I visited DUC and there are many articles on latency. Too many to go
through. Do you remember a key word from the subject of the DUC thread most
likely to be helpful here?

In the meantime, I found this. I have no idea whether this is true or not.

Teleplayer on DUC wrote:

The latency is purportedly 164 samples - but PTLE 5.3.3 for Windows corrects
for it, so if you use the Mbox mixer for zero-latency monitoring, latency is
a complete non-issue.

Do NOT follow any advice to slide tracks back 164 samples, it's not correct
for 5.3.3 Windows Mbox, and it will screw up your timing.


Thanks, this is what I mean. Depending on who you talk to the answer is
different...yes 164 samples or no. I like this answer though. Thanks.



I'm pretty sure PTLE will use whatever MIDI ports are installed on the
system - I know it does on my 002. I only had an Mbox for a few days, and
didn't get around to trying MIDI.

Input monitoring is on the headphone jack ONLY, if I recall correctly.

I highly recommend Mbox to all my friends. It's very cool.
----------------------------------------------------------------------------
----

I assume latency is a different number if you patch in a different AD
through the spdif input.

--
___
Rick Knepper
MicroComputer Support Services
Knepper Audio
Ft. Worth, TX
817-239-9632
413-215-1267 Fax
PC Tech Support & Equipment Sales
CDR Duplication & Audio Mastering
Recording
http://www.rknepper.com

"Mark T. Wieczorek" wrote in message
...
There was some heavy discussion about this in the DUC.

The zero latency monitoring is zero latency because it's a direct feed
from
the input - no A/D - D/A conversion, but the resulting recorded signal is
xxx samples late. The workaround is to always shift the track you just
recorded that many samples up, which from what I hear gets pretty
ingrained
after a while... Just set it up to some sort of hot key.

Visit the DUC & look up latency.

* DUC = Digidesign Users Conference go to Digidesign.com, I think it's in
the support area.

Regards,
Mark

--
http://www.marktaw.com/

http://www.prosoundreview.com/
User reviews of pro audio gear













My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm

In Article ,
(Mondoslug1) wrote:
Google can be good...............so there is 164 samples of latency on any
track recorded with Digi's M Box...............regardless of whether you're
monitoring with zero latency. Am I understanding correctly?



My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm


The way digidesign explained it to me, yes. They also have a solution; a few
keystrokes, somewhere on their site.

After you lay the track, you slide it back.

Regards,

Ty Ford

For Ty Ford V/O demos, audio services and equipment reviews,
click on http://www.jagunet.com/~tford

In Article , "Jack"
wrote:
No. When you're monitoring the input, there is ZERO latency, just mute your
record enabled tracks and use the mix knob until the balance works.

F.W.I.W. - I think the Mbox sounds great, I use it for all my pre-production
recording.

Jack

Jack,

I'm not sure he's talking about monitoring. I think he's talking about where
the audio lands on the new track, relative to the preceding track.

Monitoring the source has nothing to do with where the audio ends up on the
track.

Regards,

Ty Ford

For Ty Ford V/O demos, audio services and equipment reviews,
click on http://www.jagunet.com/~tford

Ty wrote:

In Article ,
(Mondoslug1) wrote:
Google can be good...............so there is 164 samples of latency on any
track recorded with Digi's M Box...............regardless of whether you're
monitoring with zero latency. Am I understanding correctly?



My tunes at:
http://www.soundclick.com/bands/5/andymostmusic.htm


The way digidesign explained it to me, yes. They also have a solution; a few
keystrokes, somewhere on their site.

After you lay the track, you slide it back.

Regards,

Ty Ford


But then somebody said there's a fix for this in the new LE software. Wonder if
that's true.

(Mondoslug1) wrote in
:

Thanks, this is what I mean. Depending on who you talk to the answer is
different...yes 164 samples or no. I like this answer though. Thanks.

How about this. Route your line out to your line in and record a click
track... be extremely careful not to monitor what you're recording or
you'll get serious feedback and might even break your mbox.

If this works, you will know exactly how far back the recorded track is
from the track that ways played and you'll know once and for all how many
samples you're dealing with.

Regards,
Mark

--
http://www.marktaw.com/

http://www.prosoundreview.com/
User reviews of pro audio gear

"Rick Knepper" wrote in message
...

[...] PTLE 5.3.3 for Windows corrects for it, so if you use the Mbox
mixer for zero-latency monitoring, latency is a complete non-issue.

This is correct.



Input monitoring is on the headphone jack ONLY, if I recall correctly.

This is incorrect. Monitor mixing (playback vs. source) is available at
the output jacks as well as the headphone jack.

--
"I got into audio because I like pushing buttons...
...never figured on all this freakin' wire!"
- Lorin David Schultz