Re: [Linuxsampler-devel] NI Kontakt vs Halion performance (voice count)

[Robert J. <rob...@da...>]

Hi ho,

> > ---
> > To be truthful, I don't even believe LS has to match the performance of
> > Kontakt anytime soon.
>
> Why not ? our code is very simple, modular and configurable.
> For example when playing those large libraries that are sampled
> key by key we could turn off interpolation completely, or use linear
> (linear is quite a bit faster than cubic).
> Or use SIMD instructions if those are beneficial in certain situations.

Yes, indeed. What I meant is that it doesn't matter ;~). 

The killer feature of LS isn't that it's the fastest, biggest, baddest in town 
(well, it may be someday :-).
The killer features are in my opinion that it's an open implementation based 
on linux and that it supports GIG to some reasonable extent.
These three things are the basics that make it awsome. The rest can wait a 
littlebit.

>
> > Hardware is cheap and since they won't support 64bits
> > for a long time coming, LS will run circles around it!!
>
> That's true, but we need to act fast to beat the the competition,
> otherwise meanwhile uncle bill will fix his crappy Windows :-)

I think we have a headstart of atleast 2 years. Before that there won't be any 
drivers, and definitely no 64bit samplers for windows :)

But eeeeven if we/you guys fail to deliver a topnotch sampler in that time 
they STILL can't top LS's killer features, 
- open implementation 
- based on linux.

So ... you win however you do it :)

>
> Hmmm Mark, release+sustian on 64bit boxes ?
> I'm going to get persuaded in following your suggestions :-)
>
> > Pinky: Brain, what are we going to do today?
> > Brain: The same thing we do every day. Try and take over the world.
>
> Sounds good, just like LS :-)
;)

>
> PS: technical question about Linux on amd 64:
> Are pointers 4bytes (32bit = 4GB address space) or can you
> use 64bit pointers too ?
This is just a guess, but I would be disappointed if pointers wheren't bigger 
than 32bits. 

> If the second case is not possible it would a bit sad because
> it would mean you can manage more than 4GB but you would still
> have the 4GB per process limit which would hurt LS.
> ok we could fire up multiple instances and load some sample libraries
> in each instance thus maxing out the RAM anyway but it would not
> be as cool as doing all within one instance plus it could lead to
> some performance problems.

Worry about it when the time comes :)

>
> Can someone of you shed some light here (or look up the stuff on google
> and post links to the relevant stuff eg kernel ML etc) ?

This interests me so I will check at a later time... But right now I got some 
coding to do, muse is going through a major revision, go go Werner! :)

/Robert