COCKOS
CONFEDERATED FORUMS
Cockos : REAPER : NINJAM : Forums
Forum Home : Register : FAQ : Members List : Search :
Old 12-22-2012, 09:21 AM   #1
WinstonG
Human being with feelings
 
Join Date: Dec 2012
Posts: 3
Default POD HD 500 Latency

Hello,
I'm currently using Ninjam with my POD HD 500 as a sound card. I know that the unit has no latency, because I've recorded with it on several occasions and it never lags. But as soon as I connect to a server in Ninjam I can hear the difference: it's not really lag, because the signal is on time, the problem is that the signal is doubled with a few milliseconds between the two sounds. I've set the I/O system to ASIO - the driver to ASIO POD HD500. I don't know what Input Range and Output Range does, but I've tried every combination and I still have the problem. There's another button "ASIO Configuration" where I've kept the ASIO Buffer size to 128 samples. The higher the buffer size gets the greater the latency between the two signals gets. But the first signal will still be on time.

How do I get rid of that second signal ?
Thank you.
WinstonG is offline   Reply With Quote
Old 12-22-2012, 04:13 PM   #2
Ollie
Super Moderator (no feelings)
 
Ollie's Avatar
 
Join Date: Dec 2007
Location: On or near a dike
Posts: 9,733
Default

Welcome to the forums! Did you try turning off input monitoring (the button with the little loudspeaker symbol) on the input track in REAPER?
Ollie is offline   Reply With Quote
Old 12-23-2012, 02:19 AM   #3
pljones
Human being with feelings
 
pljones's Avatar
 
Join Date: Aug 2007
Location: London, UK
Posts: 597
Default

Do not use "zero latency monitoring" with NINJAM - you get two signal paths to your ears that way, one direct, one through NINJAM.

See http://forum.cockos.com/showpost.php...4&postcount=45
__________________
Quote:
Originally Posted by Tony Williams
...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world.
pljones is offline   Reply With Quote
Old 12-23-2012, 11:26 AM   #4
WinstonG
Human being with feelings
 
Join Date: Dec 2012
Posts: 3
Default

Quote:
Originally Posted by Ollie View Post
Welcome to the forums! Did you try turning off input monitoring (the button with the little loudspeaker symbol) on the input track in REAPER?
Hello.
I'm not using it through Reaper.
It's Guitar -> HD500 -USB-> Computer -> Ninjam. And something I forgot to mention before: I'm using a guitar amp plugged into the HD500's 1/4 OUTPUT. Thus every sound from my computer comes out through the amp. Could this be causing the doubled signal problem ? and what should I do ?

@pljones I don't even know what "zero latency monitoring" is. But if it's turned on by default in Windows or Ninjam or whatever, I'd like to know how to turn it off.

Thank you both.
WinstonG is offline   Reply With Quote
Old 12-23-2012, 04:03 PM   #5
pljones
Human being with feelings
 
pljones's Avatar
 
Join Date: Aug 2007
Location: London, UK
Posts: 597
Default

Zero-latency monitoring is where the signal you're putting into your HD500 USB is routed directly to the HD500 USB outputs without going through the computer. It'll be something you set up on the HD500 USB.

Effectively, when it's on, you're hearing yourself through that route, plus through NINJAM "a few milliseconds later" (i.e. the input and output buffer size delay on the HD500 USB).

When recording, you probably never hear what you're playing, played back from the computer whilst recording -- you'll only be hearing the direct route. Which isn't the same thing as the HD500 USB having zero latency from the computer's perspective, of course.

For NINJAM, you need to hear yourself playing mixed in time with the NINJAM signal, and the one your computer is sending out is the correct signal, rather than the direct one that misses out the computer.

One of the critical success factors for NINJAM is that the only route for your signal to your ears is through NINJAM.
__________________
Quote:
Originally Posted by Tony Williams
...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world.
pljones is offline   Reply With Quote
Old 12-23-2012, 04:48 PM   #6
WinstonG
Human being with feelings
 
Join Date: Dec 2012
Posts: 3
Default

So I take it the on-time signal is the one that doesn't pass through Ninjam and the second one coming with a bit of latency is the one passing through Ninjam.
That leads me to believe that muting the channel would be the best fix, allowing only the direct HD signal to be heard through my amp. That is if only the mute applies to my output and the rest of the users will still be able to hear me play.
In this case I would hear the direct HD500->amp signal and the other users would hear the signal processed by Ninjam.
...right?
WinstonG is offline   Reply With Quote
Old 12-24-2012, 02:28 AM   #7
pljones
Human being with feelings
 
pljones's Avatar
 
Join Date: Aug 2007
Location: London, UK
Posts: 597
Default

You want to hear ONLY EVER the NINJAM signal, with the click, and play so you can hear yourself in time with that -- i.e. THROUGH NINJAM. If you think you're in time with the click because you can hear the click but you're hearing yourself at a different time, everyone else will think you can't play in time.

One of the critical success factors for NINJAM is that you're listening to what's happening in NINJAM (and you're part of that, aren't you?).
__________________
Quote:
Originally Posted by Tony Williams
...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world.
pljones is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:51 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.