status of kontakt-player-powered libraries

Locked New Topic
RELATED
PRODUCTS

Post

Hi muse,

it has been stated several times that a solution for the kontakt-player problem would be near. However, there were no news during the last months. Are there new problems? What is the current status? I am sure, many people are very interested...

thanks in advance
-mat123
Top

Post

Right after they decide whether to use the word "Source" or "Input" :roll:
Top

Post

What I don't get is it appears that certain KP2 libraries are already supported, like Ocean Way Drums, First Call Horns and Evolve. So how hard can it be to make Acoustic Legends HD or VI.One work?

projektio
Top

Post

projektio wrote:What I don't get is it appears that certain KP2 libraries are already supported, like Ocean Way Drums, First Call Horns and Evolve. So how hard can it be to make Acoustic Legends HD or VI.One work?

projektio
Argh.. I feel your pain. It seems like such a simple problem, but it is actually horrendously complex. The problem is that Service Center is used to be based on Flash, and it would run on Receptor 1.7 no problem. Except for the fact that Service Center was updated to be non-flash, and that particular version will not run on Receptor 1.7, but the necessary resources are available for it to run on V1.8.

So, if there was a way to get all the Service Center authorization scripts into the Flash-based version of service center, we'd be cool, except there isn't. We've discussed this with NI, and they've suggested somethings, but we've been unable to solve the problem.

So the best solution, we think, is to simply support the non-flash based version of Service Center that supports ALL K2 player install scripts, but taht leaves the problem of 1.7 versus 1.8.

Good news there is that we will soon be releasing 1.8 for Rev C and earlier Receptors. The bad news is that it will require a hard drive swap (or completely reformatting the drive)...

I know this is perplexing, but the good news is that there is a path out of this situation and we hope to get there very soon. As always, thanks for your patience.

Specifically with regard to BFA plugins like VI.One and ALHD, we will most certainly be supporting those libraries... they are awesome.

Cheers

Groovology
Top

Post

So without a hard drive swap or reformat I won't be able to run something I bought that was listed as compatible with Receptor (i.e. Addictive Drums)? And I won't be able to run things that you preinstalled on a branded IK Rev C version (Amplitube products) unless I swap to a hard drive or reformat to use system software that did not even exist when you released said branded Receptor? Nice.

So if I have to reformat to support your upgrade will you be contacting IK and other devs about upping my authorizations I'll have run out of on software I've already installed on it that will now need to be reauthorized? Didn't think so. Hours of work for what should have already worked.
Top

Post

Hi Brian,

So if OS 1.8 can support the non-flash based K2 Lib installer scripts now, can current Receptor 2 users install these libs now?

Also, is there any 'look-ahead' such that this won't also be a problem with Kontakt 3 player (upcoming) based libs?

Thanks, Regards,
Kevin L
Top

Post

looneytunes wrote:Hi Brian,

So if OS 1.8 can support the non-flash based K2 Lib installer scripts now, can current Receptor 2 users install these libs now?

Also, is there any 'look-ahead' such that this won't also be a problem with Kontakt 3 player (upcoming) based libs?

Thanks, Regards,
Kevin L
Our expectation is that if you are Receptor 1.8 SO with the Flash based version of Service Center installed, all the scripts to install future libraries will be populated in the Service Center Database, therefore it's just a matter of us populating the DI database with the appropriate names of the executables.

At least in theory, that's how it goes...

Groovology
Top

Post

Thanks for the update despite the ugly details for REV C owners.
Top

Post

yes, thanks for the update!

After years of heavy experience with computing, I am always aware of the possibility of a hard-drive crash. So, unless muse is going to release a RAID-powered receptor, one should be prepared for complete reinstall anyway. I know this is hard for some users, but the most important thing is: muse, go on! I need k2player compatibility and I need version 1.8, so the earlier it comes, the better!

BTW: I don't understand the FLASH-story. I understand that the new version of service center is not receptor compatible. But I do not understand why this should be related to the fact that NI wants to become independent from FLASH. I mean NOT using FLASH can NOT be the reason for NOT being compatible, can it?

-mat123
Top

Post

Prepared but not forced for a dot-release of software, sorry I have to disagree with you there. I've been at this for many years and this is quite different than your normal "be prepared" backup (not to mention we're not given an easy solution to do backups) so you have your right to your rationalization, I have right to my thoughts that it is quite inconvenient being forced to track down vendors and lots of other legwork because they couldn't make a dot release work on their existing hardware (did you see the part about software CURRENTLY WORKING on Rev C's but only branded versions - proving certain things CAN work on 1.7 and/or current hardware without a swap as proved by the IK-branded Rev C but regular 1.7 Rev C's with the hard drive that came with it will never see it). No, RAID wouldn't be a good solution anyway, we should be able to hook up an external drive (again something that should be easy) and take a backup image ourselves so we're not burdened by any real-time backups to hinder performance.

Unless, of course, they'll be offering us this swap on their dime. Let me know when we can set up cross-shipping if that is the case :)
Top

Post

buscemi wrote:Prepared but not forced for a dot-release of software, sorry I have to disagree with you there. I've been at this for many years and this is quite different than your normal "be prepared" backup (not to mention we're not given an easy solution to do backups) so you have your right to your rationalization, I have right to my thoughts that it is quite inconvenient being forced to track down vendors and lots of other legwork because they couldn't make a dot release work on their existing hardware (did you see the part about software CURRENTLY WORKING on Rev C's but only branded versions - proving certain things CAN work on 1.7 and/or current hardware without a swap as proved by the IK-branded Rev C but regular 1.7 Rev C's with the hard drive that came with it will never see it). No, RAID wouldn't be a good solution anyway, we should be able to hook up an external drive (again something that should be easy) and take a backup image ourselves so we're not burdened by any real-time backups to hinder performance.

Unless, of course, they'll be offering us this swap on their dime. Let me know when we can set up cross-shipping if that is the case :)
We're going to try to make this as painless as possible for everyone involved. And we have looked in to various ways of backing up and reinstalling plugins, but in almost all cases it triggers anti-tampering measures in the copy protection of various plugins.

As for the dot release, tell you the truth that was me. I felt that if we are going to increment the integer in a release, it had better be because of huge new features, and not because all of the underpinnings have changed. The fact is 1.8 is not very similar to 1.7 at all with respect to Linux... it has all been upgraded and changed and modified, although the feature set has not changed considerably... maybe that was a mistake, but I think we would have received complaints either way: things like "YOU CALL THIS 2.0??? come to mind... ;-)

PLEASE bear with us... we'll try to come up with an equitable solution that gets everyone into the latest software with the least amount of pain and bother.

We've sent out the 1.8 for Rev C hard drives to a couple of beta testers... let's make sure everything works fine and then we can work with you all on coming up with a way to get everyone into 1.8 with the least amount of hassle. lots more new to come as we get through beta.

Thanks

Groovology
Top

Post

Thanks for the explanation. Sorry to be harsh but I'm sure you guys wouldn't want us all just blowing sunshine up your you-know-whats :) I think I'd be a bit more forgiving if I was in the situation where I had lots of cash to throw around to cover this unexpected twist of events at the moment AND the 1.8 release actually had usable Syncrosoft but at least it is in there.
Top
Locked

Return to “Muse Research and Development”