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

[Lotuzia]

Steven : Once all the PolySequencer functions will be back in order, you're right the manual will need some additional infos. As for the video, well, it already exists, and it's a good thing, because if there weren't any, people would not have replicated the process described in it, and the bug will maybe have lived a few more days without people noticing it, or thinking that they did something wrong. Then, the video doesnt cover all cases. So more tutorials, or a more complete one, will be needed at some point.

To all : even if I've found more, and possibly quicker, turnarounds, if you modify the created sequence in the editor, it wont play normally anymore . I didn't even check the save/load functions. At this point, the best is to understand what went wrong, and fix it.

[jbuonacc]

... Also possibly worth checking the ARP 'Playing Mode' parameter in the KB/Arp tab ??

thanks, but that doesn't have anything to do with it (that's related to the PolyArp mode). of course, the arpeggiator's Random behavior (when neither the UP or DOWN buttons are pressed) is plainly mentioned in the manual right where it should be.

[wagtunes]

Have a serious problem. Happens every time. At first I just thought it was unrelated to Poly KB III but this happens every time I have a project with that plugin loaded. Upon trying to close, I get a Cubase fatal dump error.

Is there anybody at XILS who can read Cubase DMP files?

In light of the sequencer bug, this tells me that there is a section of code with some kind of a memory leak. Right now, as it stands, I can't create any projects with Poly KB III because as soon as I try to save and close I get the error. Now it's possible the project itself may be getting saved but I don't know. The dump freezes up Cubase and I end up having to restart my PC.

If it's any help, the demo did not do this. So it's something that was done between the demo and the official release.

[exmatproton]

Have a serious problem. Happens every time. At first I just thought it was unrelated to Poly KB III but this happens every time I have a project with that plugin loaded. Upon trying to close, I get a Cubase fatal dump error.

Is there anybody at XILS who can read Cubase DMP files?

In light of the sequencer bug, this tells me that there is a section of code with some kind of a memory leak. Right now, as it stands, I can't create any projects with Poly KB III because as soon as I try to save and close I get the error. Now it's possible the project itself may be getting saved but I don't know. The dump freezes up Cubase and I end up having to restart my PC.

If it's any help, the demo did not do this. So it's something that was done between the demo and the official release.

I would write to xils directly, instead of using kvr for these kind of problems/bugs.

[wagtunes]

Have a serious problem. Happens every time. At first I just thought it was unrelated to Poly KB III but this happens every time I have a project with that plugin loaded. Upon trying to close, I get a Cubase fatal dump error.

Is there anybody at XILS who can read Cubase DMP files?

In light of the sequencer bug, this tells me that there is a section of code with some kind of a memory leak. Right now, as it stands, I can't create any projects with Poly KB III because as soon as I try to save and close I get the error. Now it's possible the project itself may be getting saved but I don't know. The dump freezes up Cubase and I end up having to restart my PC.

If it's any help, the demo did not do this. So it's something that was done between the demo and the official release.

I would write to xils directly, instead of using kvr for these kind of problems/bugs.

All well and good but if they can't read Cubase crash dumps what exactly am I supposed to send them?

[JonSolo]

Send it to both them and to Steinberg. I had incredibly good results with Tone2. Steinberg contacted them and they got onto a fix (if I remember correctly Tone2 did not play well with UVI). Call them what you will but Steinberg DOES help devs sort through those sorts of issues.

[wagtunes]

Send it to both them and to Steinberg. I had incredibly good results with Tone2. Steinberg contacted them and they got onto a fix (if I remember correctly Tone2 did not play well with UVI). Call them what you will but Steinberg DOES help devs sort through those sorts of issues.

Okay, I'll give it a shot.

[Roman76]

So to the poster who reported this, don't worry, you're not crazy and you're not doing anything wrong.

Thanks for the confirmation, wagtunes.

[Lotuzia]

So to the poster who reported this, don't worry, you're not crazy and you're not doing anything wrong.

Thanks for the confirmation, wagtunes.

Thanks again to all for all the warnings, and to you Roman, and Wag.

A new PolyKB III version will come very soon that will fix this, and return the Polysequencer to it's normal behaviour. (Also, it seems it was a Windows only bug).

[Lotuzia]

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

[sbj]

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

[wagtunes]

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

Looking good so far. Will test this thing thoroughly today.

Have I mentioned how much fun this synth is to program? Deceptively complex because it really doesn't look it. But dig into that matrix and fun stuff can be found by the oodles.

[wagtunes]

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.

[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.

[Lotuzia]

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)