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

[JoeCat]

...might also revisit Oxium for a bit...

Always a good idea - that's an underrated synth - quick and easy to whip up a good, usable, analog-ish sound.

[Lotuzia]

it's not in the user matrix. It's only via Midi Cc automation (iirc, I'll check this)

Ah, okay. It helps to read the whole manual. It's one of those hidden features.

Oh my. This just opened up a whole new world of possibilities.

Okay, here is my question. If I create a patch that say has CC 71, 72, 91, and 92 as CC controls for 4 different destinations and save it, will that patch retain those settings if another person imports them into their system?

Second question. I assume these assignments don't show up anywhere and thus I would have to include patch notes in order for the patches to be used correctly. Correct?

I think it's important to understand how it works :

* The Midi Cc/Parameter assignations file is stored in the repertory where the PolyKB III was installed.(ControlMidiPk3 file) It's updated each time you make some changes, and the assignations are valid for ALL presets. It's not different, and saved, within each preset data.
* Therefore, if midi Cc 25 is assigned for Filter 1 cut-off for example, it will perform as such for all your presets.
* The file ( ControlMidiPK3) could be shared/distributed with a soundset, with indications of how to implement it (and indicate that it will replace/erase the possible user midi assignations maps) . But ...

It's mainly intended to allow to map any midi keyboard or controler with lot of sliders, knobs etc, to program the PKB III directly from the midi device, or draw/record automation lines in your daw, including live performance with midi devices, based on Midi Cc, so that your tracks also become Daw independant, and are only based on Midi data, if you want to migrate in other studios or production systems.

Hope it helps,

L.

[Lotuzia]

I had the time to install and test the demo version (which is in fact very generous).
There were certain patches - thanks Lotuzia! - which gave me the shivers while playing. I absolutely love the sound and feel of this software synth. The developers did an awesome job, really feels like an old Jarre synth found in the attic. Thank you all! I only wish my notebook's CPU wouldn't be so sucky.
I look forward to spending more time with it, might also revisit Oxium for a bit...

Thanks a lot ( including for your kind words about the patches )

[Lotuzia]

New Version 3.02 available, wich fixes the 'sustain pedal' not working in certain hosts like Hermann Siebs stand alone minihost.

[sbj]

New Version 3.02 available, wich fixes the 'sustain pedal' not working in certain hosts like Hermann Siebs stand alone minihost.

And it also solved the sequencer problem I had in MuLab (and EnergyXT)

Cheers

[MFXxx]

Good to know. Do users get notified via emails, not seen anything about the update?

[wagtunes]

it's not in the user matrix. It's only via Midi Cc automation (iirc, I'll check this)

Ah, okay. It helps to read the whole manual. It's one of those hidden features.

Oh my. This just opened up a whole new world of possibilities.

Okay, here is my question. If I create a patch that say has CC 71, 72, 91, and 92 as CC controls for 4 different destinations and save it, will that patch retain those settings if another person imports them into their system?

Second question. I assume these assignments don't show up anywhere and thus I would have to include patch notes in order for the patches to be used correctly. Correct?

I think it's important to understand how it works :

* The Midi Cc/Parameter assignations file is stored in the repertory where the PolyKB III was installed.(ControlMidiPk3 file) It's updated each time you make some changes, and the assignations are valid for ALL presets. It's not different, and saved, within each preset data.
* Therefore, if midi Cc 25 is assigned for Filter 1 cut-off for example, it will perform as such for all your presets.
* The file ( ControlMidiPK3) could be shared/distributed with a soundset, with indications of how to implement it (and indicate that it will replace/erase the possible user midi assignations maps) . But ...

It's mainly intended to allow to map any midi keyboard or controler with lot of sliders, knobs etc, to program the PKB III directly from the midi device, or draw/record automation lines in your daw, including live performance with midi devices, based on Midi Cc, so that your tracks also become Daw independant, and are only based on Midi data, if you want to migrate in other studios or production systems.

Hope it helps,

L.

Okay, so then for practical purposes of creating sound libraries for distribution, this is not a viable solution as it could overwrite settings that the end user has made for his own use.

Therefore, again, just for the purposes of patch distribution, there is no way to to control delay mix via say CC 71 without potentially screwing up the end user's setup therefore making that patch unusable as designed.

So as a sound designer, I am still left with the same problem. Therefore, the only practical solution is to add additional destinations to the modulation matrix.

So sure, for my own personal use, I can go crazy with this feature. I have 8 sliders on my keyboard controller. So I can pick out 8 destinations that are not in the modulation matrix and control them via MIDI. But for my future customers, if I do indeed distribute this set along with the file, I would need to warn them about the possible overwriting of their own settings thus making the sound library less attractive to those who don't want to do that.

Again, not the most ideal solution.

[sbj]

To @Lotuzia

On the SpaceXY page there is an effect called Phase. When it is on 0 it says High and on 2 it says Off.

Shouldn't it be 0 = Off and when on 2 = High

[Lotuzia]

New Version 3.02 available, wich fixes the 'sustain pedal' not working in certain hosts like Hermann Siebs stand alone minihost.

And it also solved the sequencer problem I had in MuLab (and EnergyXT)

Cheers

Thanks. The Sequencer problem in Mulab should -normally- have been fixed since the previous update iirc. Anyway, good to know all is now fixed.

[Lotuzia]

To @Lotuzia

On the SpaceXY page there is an effect called Phase. When it is on 0 it says High and on 2 it says Off.

Shouldn't it be 0 = Off and when on 2 = High

hmmm maybe a typo on the mouseover tip. We'll see that. Thanks for the report.

[Lotuzia]

it's not in the user matrix. It's only via Midi Cc automation (iirc, I'll check this)

Ah, okay. It helps to read the whole manual. It's one of those hidden features.

Oh my. This just opened up a whole new world of possibilities.

Okay, here is my question. If I create a patch that say has CC 71, 72, 91, and 92 as CC controls for 4 different destinations and save it, will that patch retain those settings if another person imports them into their system?

Second question. I assume these assignments don't show up anywhere and thus I would have to include patch notes in order for the patches to be used correctly. Correct?

I think it's important to understand how it works :

* The Midi Cc/Parameter assignations file is stored in the repertory where the PolyKB III was installed.(ControlMidiPk3 file) It's updated each time you make some changes, and the assignations are valid for ALL presets. It's not different, and saved, within each preset data.
* Therefore, if midi Cc 25 is assigned for Filter 1 cut-off for example, it will perform as such for all your presets.
* The file ( ControlMidiPK3) could be shared/distributed with a soundset, with indications of how to implement it (and indicate that it will replace/erase the possible user midi assignations maps) . But ...

It's mainly intended to allow to map any midi keyboard or controler with lot of sliders, knobs etc, to program the PKB III directly from the midi device, or draw/record automation lines in your daw, including live performance with midi devices, based on Midi Cc, so that your tracks also become Daw independant, and are only based on Midi data, if you want to migrate in other studios or production systems.

Hope it helps,

L.

Okay, so then for practical purposes of creating sound libraries for distribution, this is not a viable solution as it could overwrite settings that the end user has made for his own use.

Therefore, again, just for the purposes of patch distribution, there is no way to to control delay mix via say CC 71 without potentially screwing up the end user's setup therefore making that patch unusable as designed.

So as a sound designer, I am still left with the same problem. Therefore, the only practical solution is to add additional destinations to the modulation matrix.

So sure, for my own personal use, I can go crazy with this feature. I have 8 sliders on my keyboard controller. So I can pick out 8 destinations that are not in the modulation matrix and control them via MIDI. But for my future customers, if I do indeed distribute this set along with the file, I would need to warn them about the possible overwriting of their own settings thus making the sound library less attractive to those who don't want to do that.

Again, not the most ideal solution.

Like I said, it's mainly intended to make custom assignation maps for your Midi hardware controllers, ar perform automaton via midi data only in your sequencer, and fully adapt the use of PolyKB I/II/III to your gear. So I think it can only be seen as a bonus, as the PolyKB become independant of the daw control and automation wise.( + one can do some sound design faster with remore control, and without using the mouse, ie like on a hw analog synthesizer )

[Lotuzia]

Good to know. Do users get notified via emails, not seen anything about the update?

No. as you can see, there have already been several updates for quick fixes in a short time interval (ie around ten days since the PolykB III was released) Fo users, receiving too much emails in a short time might become counter productive.

Until now, the best way to be aware of updates is to visit the PolyKB III DL page from times to times, or follow this thread (for KVR users only).
Otoh, people only need to update if they are confronted to specific problems. And most users don't afawcs.

The next Xils-Lab newsletter, however, will specify the current version, and the current state of the PolyKB III.

[Lotuzia]

To @Lotuzia

On the SpaceXY page there is an effect called Phase. When it is on 0 it says High and on 2 it says Off.

Shouldn't it be 0 = Off and when on 2 = High

To Sbj : The label will be changed in the next .0x update. Seems more logical, although these are symbolic representations.

[ZeePok]

 
@Lotuzia/Xils

I have to report the updates for 2.52 & 3.02 made it worse .

Although now they do have Sustain Pedal in VSTHost, Mulab, Reaper and Tracktion (all newest versions), however in all DAW's they now have it in reverse!

(eLicenser version in Win7-32)

So for now I reverted back to the previous versions, at least they had normal Sustain Pedal in DAW's.

[Lotuzia]

 
@Lotuzia/Xils

I have to report the updates for 2.52 & 3.02 made it worse .

Although now they do have Sustain Pedal in VSTHost, Mulab, Reaper and Tracktion (all newest versions), however in all DAW's they now have it in reverse!

(eLicenser version in Win7-32)

So for now I reverted back to the previous versions, at least they had normal Sustain Pedal in DAW's.

Thanks Zxant. I'll check this. Should not be hard to fix if we can reproduce it (just a boolean thing probably)