Re: Feature Request JAMin

John Rigg <[email protected]> Sun, 3 Feb 2013 21:19:30 +0000
Newsgroups gmane.comp.audio.jamin.devel
Message-ID <[email protected]>
On Mon, Feb 04, 2013 at 06:38:17AM +1100, Patrick Shirkey wrote:
> 
> On Mon, February 4, 2013 3:55 am, John Rigg wrote:
> > Personally I would hesitate to use JAMin for live sound as it has quite
> > a lot of latency - certainly enough to cause problems for performers if
> > used on monitor sends, and possibly also enough to cause phase problems
> > between direct sound from the stage and the PA speakers.
> >
> 
> I guess the question is what kind of live performance use is the intention?
> 
> It's also possible to use Jamin as an fx box instead of a mastering tool...
> 
> IIRC internal latency is about as good as it gets but maybe there are
> improvements or tradeoffs that could be added for live use?

I haven't measured the latency, but operating the bypass button does
make the timing jump by enough to make me think it could be a problem for
live musicians. Anything much over 10ms total can cause timing problems
for some musicians. That's about the time it takes sound to travel 10 feet,
which might appear insignificant, but I do know musicians for whom this
could be an issue. Increase that to 20ms total and it's potentially a
problem for just about any musician trying to play in time with others on
a small stage. That much delay between back line sound and PA speakers
could also be quite noticeable. 

Without measurements this is all conjecture of course. If I get time I'll
try to do some tests.

There's nothing unreasonable about the OP's feature request BTW. It could
be useful in situations where latency isn't a problem, like playing
pre-recorded music, but that isn't what I usually think of as live
sound ;-)

John

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan