JAMin

Daniel James <daniel@...> writes:

> I tried really hard to screw it up, but I couldn't find any bugs at 
> all. The only thing I noticed is that it's possible to connect the 
> outputs of Jamin to the inputs of Jamin in the ports menu - could 
> sound nasty if you have active speakers connected.
>
> I guess you could grey the Jamin entries out from the list of ports to 
> protect people from a slip of the mouse. Or you could allow users the 
> freedom to use feedback creatively : )

I thought about that (briefly), and opted for the latter.  ;-)

Do you think it a serious problem?
-- 
  joq

On Tue, Feb 15, 2005 at 05:36:27PM +0000, Daniel James wrote:
> Hi Steve,
> 
> > > > Can you past the line from make that causes this
> > > > error?
> > >
> > > I'll try to track that down - there's a ton of errors.
> >
> > Mail me the whole lot if you like.
> 
> Er... you know when you try to break something on purpose, and it just 
> won't go wrong? A CVS checkout from today built and ran perfectly on 
> this Debian Pure 64 box against liblo 0.1.6...

Ok, it was problably just your LD cache or something.
 
> I tried really hard to screw it up, but I couldn't find any bugs at 
> all. The only thing I noticed is that it's possible to connect the 
> outputs of Jamin to the inputs of Jamin in the ports menu - could 
> sound nasty if you have active speakers connected.
> 
> I guess you could grey the Jamin entries out from the list of ports to 
> protect people from a slip of the mouse. Or you could allow users the 
> freedom to use feedback creatively : )

I have actually done that, when JAMin had variable latency it made for
some really interesting noises. JAMin -> FreqTweak -> JAMin is also good.

- Steve