Vincent Gates Posted January 17, 2014 Report Posted January 17, 2014 Does anyone know the travel time from analog input to analog output of the Nomad 10? Is there any latency? I'll run a test at some point, but just wondering if anyone has this info already. -Thanks Vincent Quote
John Blankenship Posted January 17, 2014 Report Posted January 17, 2014 All digital audio processing circuits have some latency. It's the nature of the beast. Quote
studiomprd Posted January 17, 2014 Report Posted January 17, 2014 (edited) VG: " is there any latency " yes " wondering if anybody has this info already " Zaxcom... is there a problem..? Edited January 17, 2014 by studiomprd Quote
Vincent Gates Posted January 18, 2014 Author Report Posted January 18, 2014 no problem. knowledge is power! I'm going to run a test now……….. Quote
Vincent Gates Posted January 18, 2014 Author Report Posted January 18, 2014 in case you're gig ever requires you knowing the latency of you're Nomad 10: Travel from XLR Analog IN to XLR Analog OUT 162 samples (+ or - a sample or two) 3.375 milliseconds Quote
pindrop Posted January 18, 2014 Report Posted January 18, 2014 in case you're gig ever requires you knowing the latency of you're Nomad 10: Travel from XLR Analog IN to XLR Analog OUT 162 samples (+ or - a sample or two) 3.375 milliseconds Thanks, how did you measure it please? Quote
Jeff Wexler Posted January 18, 2014 Report Posted January 18, 2014 Thanks, how did you measure it please? I just count the samples as they go by... you've got to be quick though. Quote
pindrop Posted January 18, 2014 Report Posted January 18, 2014 Unless I just count the samples as they go by... you've got to be quick though. and Jack seems to be beta testing a new Zaxcom device that can help ∞8 Quote
studiomprd Posted January 18, 2014 Report Posted January 18, 2014 VG: " 162 samples (+ or - a sample or two) " that isn't accurate enough... Quote
Vincent Gates Posted January 19, 2014 Author Report Posted January 19, 2014 VG: " 162 samples (+ or - a sample or two) " that isn't accurate enough... Ha! Quote
Vincent Gates Posted January 19, 2014 Author Report Posted January 19, 2014 Thanks, how did you measure it please? Analog click OUT of protools and fed back analog IN to protools. Record a track on the timeline. This is our control, the time it takes for a click to make the round trip from Protools OUT to Protools IN. This records the latency of Protools. Now, MUTE that track. Next, add the Nomad to the analog click chain and record click on another track in Protools. Measure the difference between track 1 and track 2. Didn't seem to matter wether compressors and HPF's etc were engaged on the Nomad or not, still got 162 samples. Re-ran experiment with an SD 552, and there was no latency…which is to be expected with an analog path. Quote
Marc Wielage Posted January 19, 2014 Report Posted January 19, 2014 3 milliseconds is also about the same latency with a Lectrosonics 400-series wireless. Roughly 1/10th of a second -- not worth worrying about, in my opinion. Quote
John Blankenship Posted January 19, 2014 Report Posted January 19, 2014 3 milliseconds is also about the same latency with a Lectrosonics 400-series wireless. Roughly 1/10th of a second -- not worth worrying about, in my opinion. a Marc typo (is that a Marco?) Marc meant to say "Roughly 1/10th of a frame" not "Roughly 1/10th of a second." ...and like he said, nothing to be concerned about. It's the equivalent of being about 3.4 feet from the sound source. Quote
John Blankenship Posted January 19, 2014 Report Posted January 19, 2014 thanks, John... You're welcome. Glad I could educate you. Quote
Vincent Gates Posted January 24, 2014 Author Report Posted January 24, 2014 3 milliseconds is also about the same latency with a Lectrosonics 400-series wireless. Roughly 1/10th of a second -- not worth worrying about, in my opinion. True, but definitely something to be aware of and add up from time to time in this world of wireless and digital-ness. Quote
Jeff Wexler Posted January 24, 2014 Report Posted January 24, 2014 "add up from time to time" regarding latency spec --- what does this mean? Latency in any of these digital devices is what it is --- it doesn't change over time. Are you saying that you need to ask the question every once in awhile just to reassure? Quote
Wandering Ear Posted January 24, 2014 Report Posted January 24, 2014 I think Vincent may be referring to adding up the delays of multiple digital devices in a signal chain, for example if using the Nomad in the studio with another interface. Knowing the latency in the signal path can be useful in that situation. I agree that it is irrellevent in the field. Quote
Vincent Gates Posted January 26, 2014 Author Report Posted January 26, 2014 "add up from time to time" regarding latency spec --- what does this mean? Latency in any of these digital devices is what it is --- it doesn't change over time. Are you saying that you need to ask the question every once in awhile just to reassure? I'm referring to adding up latency in the chain. I started the thread because a client requested latency info on the Nomad, and as it turns out, 3ms is too much latency in HIS signal path for live TV broadcast. For other purposes and my field work, I'm happy with the Nomad, so no worries here. Quote
rich Posted January 26, 2014 Report Posted January 26, 2014 3ms is too much??? realising these questions are kind of pointless because im not asking your client, but is he not confusing ms with frames? is he using only analogue cameras, as i am sure that digital cameras will add latency. but then as you said, it is HIS signal path. Quote
John Blankenship Posted January 26, 2014 Report Posted January 26, 2014 Like Rich thought, they probably confused ms for frames. You should tell him, "I just found out that the latency is actually only about a tenth of a frame" and see if that makes a difference. Quote
Wandering Ear Posted January 26, 2014 Report Posted January 26, 2014 Did you tell your client that you can't use modern wireless because they have a 3ms delay too? Guess you have to use cabled lavs Quote
Max Futterman Posted January 27, 2014 Report Posted January 27, 2014 3ms? That's not even perceivable. I can't believe there is any application where that would be a problem. Quote
Izen Ears Posted February 4, 2014 Report Posted February 4, 2014 Fascinating. Did everyone see my cat in the latest Pro Sound newsletter? Dan Izen Quote
Vincent Gates Posted February 4, 2014 Author Report Posted February 4, 2014 Fascinating. Did everyone see my cat in the latest Pro Sound newsletter? Dan Izen Dont tease. Please post! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.