Xils-Lab PolyKB III -Official Thread- [v3.5]

[exmatproton]

That would be cool if both Cubase 7 and 9 could be installed on the same machine. That type of thing does happen to work with Sonar, as I have had X3 and the Platinum version on the same PC with no issues. Another thing you could do is get Reaper to use as a secondary DAW. It's not very expensive at all.

I have Reaper. Two problems.

1) I don't know how to use it.

2) It's incompatible with Vocaloid which is how I do all my vocals.

Did you read this?
http://dlz.reaper.fm/userguide/ReaperUserGuide530c.pdf

No more than I read Cubase's gazillion page manual. It isn't how I work through things. I don't have time to sit down and read manuals nor do I have the patience for it. I bit the bullet on Cubase and worked through learning it. Took me a long time. I'm not going through that again with another DAW.

End of discussion.

hahaha...still, you got PLENTY of time to write about stuff here on KVR

Whatever suits you ofcourse! Have a nice one...

[wagtunes]

Believe me, I know that I'm going to have to upgrade some day. I also know that someday the hard drive of this PC is going to go or the OS will fall apart. I dread that even more when I have to reinstall every single VST I own, including Komplete which took like 4 hours. Trust me, I know what nightmares lie ahead. I'm simply putting them off for as long as I can.

Excuse me for asking, are you saying you don't have some kind of backup or clone of your boot drive?

Everything is backed up on an external drive but you still have to reinstall everything when you get a new hard drive.

Or is there some kind of technology that I'm not aware of?

[wagtunes]

Okay, just did a little research on cloning. We've come a long way it seems.

Questions:

1) After I clone my drive, the clone is only current up to that point in time when the clone was made, correct?

2) If so, any programs installed after the clone was made will still need to be reinstalled, correct?

3) Can I clone to a larger drive than I have now or do the drives need to match?

4) Can I change my processor from my I3 to an I7 and the cloned drive will still work? The reason I am asking is because I want to actually upgrade my processor now but my tech says if I do that, I will have to reinstall the OS.

[SLiC]

A cloned drive is literally identical to the original drive in terms of the content (its bit by bit- 0s and 1s level...), I have cloned and upgraded my O/S SSD twice without issue or any software even noticing....

Some copy protection does take a hardware snapshot, but not normally a drive, more likely a motherboard and this may also be a processor.

I cant say if reinstalling an O/S is necessary (I although I would be surprised if it was) but if you are on Windows 10 you can refresh the O/S without loosing programmes etc.

[exmatproton]

Okay, just did a little research on cloning. We've come a long way it seems.

Questions:

1) After I clone my drive, the clone is only current up to that point in time when the clone was made, correct?

2) If so, any programs installed after the clone was made will still need to be reinstalled, correct?

3) Can I clone to a larger drive than I have now or do the drives need to match?

4) Can I change my processor from my I3 to an I7 and the cloned drive will still work? The reason I am asking is because I want to actually upgrade my processor now but my tech says if I do that, I will have to reinstall the OS.

I think you need a different thread/site for these questions. Remember, you are in the Xils-Lab PolyKB III official thread.

[wagtunes]

Okay, just did a little research on cloning. We've come a long way it seems.

Questions:

1) After I clone my drive, the clone is only current up to that point in time when the clone was made, correct?

2) If so, any programs installed after the clone was made will still need to be reinstalled, correct?

3) Can I clone to a larger drive than I have now or do the drives need to match?

4) Can I change my processor from my I3 to an I7 and the cloned drive will still work? The reason I am asking is because I want to actually upgrade my processor now but my tech says if I do that, I will have to reinstall the OS.

I think you need a different thread/site for these questions. Remember, you are in the Xils-Lab PolyKB III official thread.

Understood, except I'm getting all these suggestions on how to make Poly KB III "work" (that is what this thread is about, right?) and it's ultimately lead to this.

I just figured all these people who had all these suggestions on how to make a VST work that, whether they want to accept it or not, has a bug in it, would have some advice on how to get my PC to a point where I can make whatever changes I had to make in order for Poly KB III to "maybe" work as intended, because even with whatever I do, there is no guarantee that it will fix my problem.

[Lotuzia]

Hmmm I'd like to remind people possibly following this thread, and who might be a bit scared by such comments, that 'get PolyKB III to work" here, in this context, only, and simply, means that : After very long sessions (like Daw +project opened for two days long or more)( And everything works OK for less long, or short sessions),in the following configuration : Cubase 7 + Windows 7, 64b, the PolyKB III, might crash Cubase when you exit Cubase.

I'd also like to add that, with the same configuration ( Cubase 7, Windows 7 64b pro), I don't have this problem. However, to be honnest, I more/less had it in some versions of the beta stage (but was in any case always able to save the projects, it only happenned when I closed Cubase) . Since the official v3.0 was released, this problem seemed to have disappeared, for me, and a vast majority of users, as it has been reported only one time by another user iirc (Windows 7 also). So, hopefully, it can probaly still happen, but in very rare cases.

A simple turnaround, for the few people experiencing this, is to make less long Cubase sessions (ie a few hours, or one day long max maybe). Or accept that Cubase will crash on exit ( it will work 100% normally and the project will be 100% ok once you have rebooted your daw). Then, if Xils can find some ways to reproduce this, (and its difficult because it seems to be only for a handfull of people) and ways to better this behaviour, it will be done, and some time will be dedicated anyway to find more about this.

On a side note : Maybe updating Cubase to the last 7.x versions, or 8/9 versions can solve this. Tbh, we dont know. It seems to be Cubase specific, but once again, we can't be sure. And it seems to affect very very few users. We'll see in the future if more infos and feedback help us to have the full picture about this.

[wagtunes]

Hmmm I'd like to remind people possibly following this thread, and who might be a bit scared by such comments, that 'get PolyKB III to work" here, in this context, only, and simply, means that : After very long sessions (like Daw +project opened for two days long or more)( And everything works OK for less long, or short sessions),in the following configuration : Cubase 7 + Windows 7, 64b, the PolyKB III, might crash Cubase when you exit Cubase.

I'd also like to add that, with the same configuration ( Cubase 7, Windows 7 64b pro), I don't have this problem. However, to be honnest, I more/less had it in some versions of the beta stage (but was in any case always able to save the projects, it only happenned when I closed Cubase) . Since the official v3.0 was released, this problem seemed to have disappeared, for me, and a vast majority of users, as it has been reported only one time by another user iirc (Windows 7 also). So, hopefully, it can probaly still happen, but in very rare cases.

A simple turnaround, for the few people experiencing this, is to make less long Cubase sessions (ie a few hours, or one day long max maybe). Or accept that Cubase will crash on exit ( it will work 100% normally and the project will be 100% ok once you have rebooted your daw). Then, if Xils can find some ways to reproduce this, (and its difficult because it seems to be only for a handfull of people) and ways to better this behaviour, it will be done, and some time will be dedicated anyway to find more about this.

On a side note : Maybe updating Cubase to the last 7.x versions, or 8/9 versions can solve this. Tbh, we dont know. It seems to be Cubase specific, but once again, we can't be sure. And it seems to affect very very few users. We'll see in the future if more infos and feedback help us to have the full picture about this.

Would sending XILS the Cubase DMP files help them?

[Lotuzia]

It certainly can't harm.

[wagtunes]

It certainly can't harm.

Does their support contact area handle attachments or do I have to email them?

[exmatproton]

It certainly can't harm.

Does their support contact area handle attachments or do I have to email them?

no, it doesn't;

http://www.xils-lab.com/pages.php?pageid=2

[Lotuzia]

It's only a form. So an email seems more suitable for attachements.

[Ingonator]

So far in Windows 10 64-bit here the eLicenser protected PolyKB III 64-bit VST2 plugin (currently version v3.0.2) worked nicely in following hosts:
Cubase Pro 9.0.1 (this is 64-bit only), Cubase Pro 8.5.20 64-bit, Cubase Pro 8.0.40 64-bit (this update was released in 2016), Live 9.7.1 64-bit, Bitwig Studio 1.3.15, Studio One 3.3.3 64-bit, NI Maschine 2.5.6 (no PolyKB III NKS presets yet)

Details about the PC used:
CPU: Core i5-3350P (4 x 3.10 GHz), RAM: 8 GB DDR3, audio interface: Focusrite Saffire Pro 24 DSP, Midi controller: NI Komplete Kontrol S61

The Cubase 9 license is backwards compatible (even with very old versions like e.g. SX 3) and it is possible to install use multiple versions at once. Steinerg also provides special upgrade installers that e..g upgarde from v8.5 to v9.0 while it also keeps the old version usable.

[wagtunes]

Just wanted to report that after working all day with Poly KB III in MuLab, closing DAW was uneventful. Smooth as silk. In fact, plugin works flawlessly.

It appears that the only people who might have problems are those still on Cubase 7 using Windows 7 64 bit. And since most people have probably upgraded to Cubase 8 or 9 by now, this problem probably effects a very small percentage of people.

In the meantime, I'm really loving programming this synth. It is incredibly flexible. I plan on making a video the first chance I get demonstrating some really cool things you can do with this synth.

So stay tuned to this channel.

[electro]

Is the demo version at 3.02 yet?