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

[Lotuzia]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

I have the same issue as Roman Empire and the new update does unfortunately
not solve this.

I am on Win 10 64

D.A.W = MuLab

I hate to say this, but I have found that a lot of the newer VSTs do not work well in MuLab. That particular DAW is very picky for whatever reason, which is why I don't use it.

Thnaks Wag & Sbj for the reporting ( Sorry for the Mulab thing though, sbj). We'll wait for more feedback from people using it in major daws, and we'll see at that point if additional decisions should be taken.

[aMUSEd]

Would be good if there was some improvement to the patch management though - it's just taken me an hour just to rename 50 odd patches in XILS3 - and looking at PKBIII it looks like there is no change apart from a bug being fixed in patchname entry (that is broken in XILS3). Still no way to easily rename patches, or move or delete them other than one by one.

Yes. This would require custom multiselection of patches, wich is not currently implemented. As the preset system code is shared between all Xils-lab instruments, this can only be thru a major update. A major overhaul of the preset system might see the birth in the future though, wich might fix all these details, at least, I've proposed one to Xils-lab, but well, time will tell. The current system offers a lot of power though, even if, I agree, it is not capable of the function you describe : Multicriteria hierarchised search, custom tags, custom projects and banks that you can export/import in one click, crossplatform compatible, and once again, something important for me, but maybe not as important for all users : You'll never loose a patch, because you can even have two different presets that have the same name, but different data (impossible to achieve with traditional systems relying on OS browsers)

Actually I just noticed there is one thing that has changed for the worse PolyKB III no longer reports the patchname to the host, in fact PKBII doesn't either now, not sure when this changed. Syn X2 still does, so does XILS4. This is essential.

[exmatproton]

Would be good if there was some improvement to the patch management though - it's just taken me an hour just to rename 50 odd patches in XILS3 - and looking at PKBIII it looks like there is no change apart from a bug being fixed in patchname entry (that is broken in XILS3). Still no way to easily rename patches, or move or delete them other than one by one.

Yes. This would require custom multiselection of patches, wich is not currently implemented. As the preset system code is shared between all Xils-lab instruments, this can only be thru a major update. A major overhaul of the preset system might see the birth in the future though, wich might fix all these details, at least, I've proposed one to Xils-lab, but well, time will tell. The current system offers a lot of power though, even if, I agree, it is not capable of the function you describe : Multicriteria hierarchised search, custom tags, custom projects and banks that you can export/import in one click, crossplatform compatible, and once again, something important for me, but maybe not as important for all users : You'll never loose a patch, because you can even have two different presets that have the same name, but different data (impossible to achieve with traditional systems relying on OS browsers)

Actually I just noticed there is one thing that has changed for the worse PolyKB III no longer reports the patchname to the host, in fact PKBII doesn't either now, not sure when this changed. Syn X2 still does, so does XILS4. This is essential.

Which host?

[aMUSEd]

Any

[jbuonacc]

... yes, you can have the last PKB II v 2.1.14 installed and working simultaneously with v 3.0 on your system. This actually is what I use myself, as I had to test the compatibility of my AnaogVille soundset with this version.

installed v2.16 last night. noticed that there are some different patches that i hadn't seen before ("Acid Bass" being one of them, there's definitely at least a few others). i thought i noticed this at another time, patches being different/changed from version to version. who knows how many of the others that i've lost through updates.

what's the story? any way to get ALL of the patches that have been released with different versions over the years?

** also, i noticed that (at least) the "Acid Bass" patch didn't show up in Komplete Kontrol. maybe it's not tagged for NKS or something?

[Lotuzia]

Any

This will be fixed in one of next updates

[aMUSEd]

Awesome thanks

[Lotuzia]

... yes, you can have the last PKB II v 2.1.14 installed and working simultaneously with v 3.0 on your system. This actually is what I use myself, as I had to test the compatibility of my AnaogVille soundset with this version.

installed v2.16 last night. noticed that there are some different patches that i hadn't seen before ("Acid Bass" being one of them, there's definitely at least a few others). i thought i noticed this at another time, patches being different/changed from version to version. who knows how many of the others that i've lost through updates.

what's the story? any way to get ALL of the patches that have been released with different versions over the years?

** also, i noticed that (at least) the "Acid Bass" patch didn't show up in Komplete Kontrol. maybe it's not tagged for NKS or something?

All this is perfecly normal : Acid Bass, made by my friend Tzadi, is one of the new patches of the PolyKB III factory., so it's there since PolyKB III v1.0.

Like I previously said, but it's worth to mention it again, PolyKb II and III share the same preset library with the following differences :

* PKB II/II.5 presets are 100% compatible with PKB III ( Upward compatibility)
* PKB III presets will load, and be read, in/by PKB II/II.5, but missing data will simply be ignored ( Possibly resulting in no sound at all depending on the preset data)
* PKB III and PKB II will share the same licence.
* PKB III will be installed in the same directory than PKB II ( if PKB II has been previously installed on the machine) They will share the same preset directory.
* PKB II & III will however still be seen as two distinct synthesizers by your host

So : Acid Bass has chances to sound different in the PolyKB 2.16 than in PolyKB III. ( some pkb III presets loaded in PKB II might not make sound at all btw, depending on how they are programmed) Until PolyKB III is NKS compatible (eta end January 2017), and all presets integrated, it's normal it doesnt show in Komplete Kontrol.

Hope it clarifies things.

[Roman76]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

Now the sequencer is working. Tested in Cubase 9 and Max 7 on Win 7 64x.

[Lotuzia]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

Now the sequencer is working. Tested in Cubase 9 and Max 7 on Win 7 64x.

Yes ! I made a lot of tests today, and the PolySequencer is fully working OK again ::::::::::::::::) (Win 7, 64b hosts)

-----------____________

So, maybe we will be able soon to begin to talk ... sound, possibilities, features, & music

[wagtunes]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

Now the sequencer is working. Tested in Cubase 9 and Max 7 on Win 7 64x.

Yes ! I made a lot of tests today, and the PolySequencer is fully working OK again ::::::::::::::::) (Win 7, 64b hosts)

-----------____________

So, maybe we will be able soon to begin to talk ... sound, possibilities, features, & music

Except it still crashes my DAW on close. And since Cubase 7 is no longer supported by Steinberg, they're not even going to waste their time looking at crash logs. So unless XILS can look at these and figure them out, I'm just going to have to live with it.

Shame, because I'm really loving programming this thing.

[exmatproton]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

Now the sequencer is working. Tested in Cubase 9 and Max 7 on Win 7 64x.

Yes ! I made a lot of tests today, and the PolySequencer is fully working OK again ::::::::::::::::) (Win 7, 64b hosts)

-----------____________

So, maybe we will be able soon to begin to talk ... sound, possibilities, features, & music

Except it still crashes my DAW on close. And since Cubase 7 is no longer supported by Steinberg, they're not even going to waste their time looking at crash logs. So unless XILS can look at these and figure them out, I'm just going to have to live with it.

Shame, because I'm really loving programming this thing.

Euhh,,maybe it is time to update your DAW?

[Lotuzia]

Hmmm my main Daw is also Cubase 7 64b/Win 7 and it doesnt crash on exit ( I use eLicencer also) (and before -ie some betas versions-, tbh I had a few crashes on exit, but only during veryyyyyy long sessions -like daw opened for 2 days etc-). Are you on Windows ?

[wagtunes]

Hmmm my main Daw is also Cubase 7 64b/Win 7 and it doesnt crash on exit ( I use eLicencer also) (and before -ie some betas versions-, tbh I had a few crashes on exit, but only during veryyyyyy long sessions -like daw opened for 2 days etc-). Are you on Windows ?

Yes, on Windows and YES, on long sessions. If I open and close shortly after, no problem. So yes, I'm having the same problem as you were having with the betas.

As a QA tester, I can say with 99% certainty that this is a memory leak in the software. I could explain what causes these but it would probably make your eyes roll around in your head so here's the Reader's Digest version and yes, Windows is as guilty a culprit as the software because of how they handle cleanup.

Reader's Digest Version

Software performs an operation and there is a bug in the code that doesn't quite cause a crash but leaves what we call a "mess."

At this point, Windows "sees" the mess but doesn't clean it. It places it in a corner of the room until the session is over and then cleans up. If this is the only mess, no problem.

But then the software performs another function that, again, doesn't cause a crash but leaves a mess. Windows again sees it but doesn't clean it and leaves it in another corner of the room.

This continues either until a function is performed that causes a crash or until the session ends.

At that point, as Windows is attempting to close things down, it first has to locate the various messes and clean them first. But what happens is that Windows loses track of where these messes are because of the memory leak in the software and cleans something it's not supposed to. This can cause any number of things. In the case of Vocaloid, it actually attempts to close the entire system down. Fortunately, this only happens if I close a project with Vocaloid and try to open another project in the same session. If I completely close down Cubase, no problems.

In the case of Poly KB III, Windows causes a fatal error in the Cubase project itself. So it doesn't matter if I am going from one project to another or trying to close down Cubase. Even saving the project will cause the error if it's been opened long enough.

So the only way to prevent the crash is to shut all other programs down and then shut down Windows with Cubase still open. However, that means losing all my work.

This is the only plugin I have, besides Vocaloid that does this. That's why I don't upgrade my Cubase. I know what headaches I have now. I don't know what headaches I'm going to have going to Cubase 9.

Tomorrow, I'm going to do my patch programming exclusively in MuLab and see what happens when I go to close down at the end of the day. If it doesn't blow up, then I'll know for certain that it's a problem between Poly KB III and Cubase. If it does blow up, then the problem is deeper than we're expecting and people simply haven't triggered it yet.

My years in QA taught me a lot about programming and programs.

In short, they are very fragile beasts and a bug free program is a myth simply because of all the variables that a software developer cannot possibly account for.

Case in point. We had a problem with our software that only occurred on Windows 98 with internal modems.

Talk about trying to find a needle in a haystack.

Bottom Line: There is definitely a problem in Poly KB III that is causing this because bug free programs don't blow up for no reason.

[Examigan]

Version 3.0.2 is live ( For Windows users only) Most, if not all, PolySequencer bugs should be fixed.

Now the sequencer is working. Tested in Cubase 9 and Max 7 on Win 7 64x.

Yes ! I made a lot of tests today, and the PolySequencer is fully working OK again ::::::::::::::::) (Win 7, 64b hosts)

-----------____________

So, maybe we will be able soon to begin to talk ... sound, possibilities, features, & music

Except it still crashes my DAW on close. And since Cubase 7 is no longer supported by Steinberg, they're not even going to waste their time looking at crash logs. So unless XILS can look at these and figure them out, I'm just going to have to live with it.

Shame, because I'm really loving programming this thing.

Euhh,,maybe it is time to update your DAW?

Yes, especially if it isn't supported any more.