@Christian Marcussen said:

Got I hope your wrong! I despise the Kontakt GUI - both its design, and speed (or lack thereof)

Yeah, it's one ugly interface OK...hard to read, etc.

But I realize it's popular so what do I know[;)]

TH

Whats wrong with converting the gig files to nki's with kontakt?

@Banquo said:

Whats wrong with converting the gig files to nki's with kontakt?

There not 100% accurate and theres so much more comvienent programming possiblities with K2 and scripting... [:)] Rich

I want to throw a monkey wrench into this discussion (just for the fun of it). In the past year, I produced an orchestral library for E-MU. I found that I really liked EmulatorX for the programming features and the resultant sound you could get since the company packages the program with a high quality audio card.

Now, I'm no programmer, but what I did like was that for each patch, 16 controllers were available. So if you want to control attack, release, and volume you can do it all in one program without having to have separate instruments to do this.

From a developer's perspective, you need less samples, much less than what you need in GigaStudio (at least the 2.54 version) which means fewer DVDs for duplication.

At any rate, if there are any here using EmulatorX maybe you'd consider adding your input separate from Kontakt.

The one thing I learned from previously doing a program in Kontakt, is that while Kontakt is really a great program, the heavy purchasing is with Kontakt player packages rather than the actual Kontakt program itself.

One other thing about EmulatorX I found rather appealing was that it easily imported the VSL GS 2.54 files. I haven't had time to really test this out, but what I tested sounded quite good.

PA

@Peter Alexander said:

From a developer's perspective, you need less samples, much less than what you need in GigaStudio (at least the 2.54 version) which means fewer DVDs for duplication.

The EXS version of Opus 1 contains 25 GB of samples (+ 120.5 MB of instruments data), the Giga version is 27.1 GB in size (said Martin ) and both, EXS and Giga version ship together on 4 DVDs. It wouldn't save one DVD here, nor on all the other distributors who are also most pressing all different sampler versions on their DVDs... And most libraries around are smaller than Opus 1...

PolarBear

and please don't forget (at least that happened with the version of EMU-X i've tested) the samples are converted into a proprietary format. so additionally to the .gig and .wav files we had another 50% more disks if one would add an EMU version of a library (but possibly i've missed something)

just to mention: the difference in size for giga and exs is related to the fact, that some .gig files contain the same wave files (eg. release) due to the design of a gig-file, whereas an exs file can point to wave files in any folder of the samples hierarchy

christian

@Peter Alexander said:

From a developer's perspective, you need less samples, much less than what you need in GigaStudio (at least the 2.54 version) which means fewer DVDs for duplication.

The EXS version of Opus 1 contains 25 GB of samples (+ 120.5 MB of instruments data), the Giga version is 27.1 GB in size (said Martin ) and both, EXS and Giga version ship together on 4 DVDs. It wouldn't save one DVD here...

PolarBear

I was working on a larger library where it did.

@cm said:

and please don't forget (at least that happened with the version of EMU-X i've tested) the samples are converted into a proprietary format. so additionally to the .gig and .wav files we had another 50% more disks if one would add an EMU version of a library (but possibly i've missed something)

just to mention: the difference in size for giga and exs is related to the fact, that some .gig files contain the same wave files (eg. release) due to the design of a gig-file, whereas an exs file can point to wave files in any folder of the samples hierarchy

christian

I didn't find that in this project. The files we worked with were imported from a GS2.54 version and we didn't experience a 50% increase in size. A while back I sent you the programmer's e-address, so feel free to write and ask. Again, I'm not a programmer so I'm just passing on my observations.

What does seem to be true, though, is that because of E-P/X street pricing and audio card bundling, you can develop products which can be copy protected without paying licensing fees. That should surely help out some developers!

sorry peter if i wasn't clear enough - what i wanted to say is, the size does not increase for the library, but the amount of data to be pressed on a DVD would be 50% more if an EMU-X version had to be additionally on them.
christian

@cm said:

sorry peter if i wasn't clear enough - what i wanted to say is, the size does not increase for the library, but the amount of data to be pressed on a DVD would be 50% more if an EMU-X version had to be additionally on them.
christian

Well, again, we didn't have that experience. But I'll check with someone who knows more than me about this because it's an important point.

Still, even if the EMU version is only 10% of the EXS size (which I hardly believe, because hmm, lossless compression can only do about 50% so far) there still has to be pressed 110% of the current data on DVDs if the additional format is considered. of course, if you do 101 variations of the same sample in programs you could push the comparison to one side... Anyway, it's not lowering the numbers of DVDs to press at all. And my guess is that most developers ship on multi-format discs for a reason, maybe it just costs too much to hold the proprietary discs in stock in a reasonable number for a good price?

And also, I can count the libs that are larger than Opus 1 with my 2 hands here...chances aren't high developers aren't researching the field themselves with such a beast for release IMHO. And if they don't, well... no comment.

PolarBear