StiX : MultiSynthesis Drum Machine (v1.6 Released + Flash sales)

[woodsdenis]

Just trying the iLok demo, in Studio One 2.65 it will just stop,outputting sound after a while, reinstating the plugin will fix it. CPU usage seems a lot on certain presets. Needs to be a separate FX bus fader, when pulling down all faders in Gang mode FX bus does not reduce, or option to make FX post fader.

Thats a limitation of the type of demo version you use I think : *Needs to be reloaded every 25 minutes* ( quoted from the site)

A full featured demo version ( but limited to two months after you have activated it) can also be asked for on Xils site.

Fx send : A pre/post toggle will be there in the next version.( Already implemented on 0.98 G iirc) But defifinitely there in the beta version I run ( v 0.98 H, soon public)

I have the full featured demo, works fine in Cubase. In S1 it will mute if a I change a preset sometimes and way before 25 mins. It will output a faint clicking sound.

[CinningBao]

Good looking update.. found a GUI issue: the 'Created' and 'Modified' dates cannot be altered.

And if the 'Created' date should be today, it is incorrect.

Thanks,

Yes these two dates are 'display only information' they cant be changed. We lack info on the conditions in wich your screen was made. Was it before what appears to be a factory preset -due to the date- was Saved with function 'Save As' ( inthis case I think it's normal behaviour as it's related to the preset state before it was changed) . Or was it after it was Saved, and using the 'show info' function ? (factory presets cant be overwritten iirc, or maybe, to be more precise, you should not be able top overwrtite them, but should use the 'save as' function to create a new preset derived from one of them)

Ok, understood. Yes, that was based on the _init preset. I think I thought it was a display of meta-data associated with the preset about to be saved.. It's not entirely intuitive but I expect we'll get used to it

[CinningBao]

and I just got a crash fiddling with filters - are the OSX report logs of any use to you?

Thanks ,

Yes, crash logs can be very important sometimes to fix bugs, or at least understand when something happenned. I had a bug also yesterday, and it was related to some extreme filter mangling, so maybe these two events are somewhat related.

Ok, thanks - attached here. 2 Report logs both from when I was fiddling with the filter.

[CinningBao]

I have a couple of GUI bugs to report:

the Modulator sources are not quite right - I would have expected the osclillator entry here to in fact be the LFOs:

Screen Shot 2016-02-13 at 22.36.00.jpg

And the entry for Modulation Source Envelope 2 Attack is inconsistent:

Screen Shot 2016-02-13 at 22.33.41.jpg

[Lotuzia]

Good looking update.. found a GUI issue: the 'Created' and 'Modified' dates cannot be altered.

And if the 'Created' date should be today, it is incorrect.

Thanks,

Yes these two dates are 'display only information' they cant be changed. We lack info on the conditions in wich your screen was made. Was it before what appears to be a factory preset -due to the date- was Saved with function 'Save As' ( inthis case I think it's normal behaviour as it's related to the preset state before it was changed) . Or was it after it was Saved, and using the 'show info' function ? (factory presets cant be overwritten iirc, or maybe, to be more precise, you should not be able top overwrtite them, but should use the 'save as' function to create a new preset derived from one of them)

Ok, understood. Yes, that was based on the _init preset. I think I thought it was a display of meta-data associated with the preset about to be saved.. It's not entirely intuitive but I expect we'll get used to it

Yes. After the preset you were editing was saved, if you open the 'info' area again, you'll see that your -newly created- preset will have the right date, ie the date at wich you have saved it. This info might be usefull to make sure a preset was aved for this or that project, ifyou're not sure, and if the dates ( project-preset) match. Or for other things.

[Lotuzia]

I have a couple of GUI bugs to report:

the Modulator sources are not quite right - I would have expected the osclillator entry here to in fact be the LFOs:

Screen Shot 2016-02-13 at 22.36.00.jpg

And the entry for Modulation Source Envelope 2 Attack is inconsistent:

Screen Shot 2016-02-13 at 22.33.41.jpg

I'm not sure I understand your request regarding the 1st picture.

Picture 1 : Oscillator 1 as source is very usefull. You can use ti to perform all kinds of cross synthesis actions for example ( modulating osc1 by osc 3 while sample has been choosed for osc3), and, also, one thing for wich it's very usefull is to assign osc 1 or 2 to sine, then modulate it by itself (or the other oscillator) in the macro matrix : This is the way to get a wide variety of *noise* oscillators, and it's especially handy if you have osc 3 assigned to a sample, and still wish to have one or two additional *noise* oscillators.

Then, you're right, while the two LFOs have already a good choice of targets in the first matrix, it's true that they could have been added to the sources in the macro mod (under the modulators group of sources ) We intended to do that for ages, but it just went under the pile for whatever reason, sorry for that.

Pic 2 : yes it should be labelled Env2 At, instead of EnvAt. It's quite obvious it's related to EV 2 ( the filter EV ) due to its position in the list, but it's a typo for sure. Thanks for finding it

[Lotuzia]

and I just got a crash fiddling with filters - are the OSX report logs of any use to you?

Thanks ,

Yes, crash logs can be very important sometimes to fix bugs, or at least understand when something happenned. I had a bug also yesterday, and it was related to some extreme filter mangling, so maybe these two events are somewhat related.

Ok, thanks - attached here. 2 Report logs both from when I was fiddling with the filter.

Thanks a lot. We fixed a bug recently about some modultions crashing the filter. With a bit of luck, this problem will be fixed as well

LtZ

[Lotuzia]

Just trying the iLok demo, in Studio One 2.65 it will just stop,outputting sound after a while, reinstating the plugin will fix it. CPU usage seems a lot on certain presets. Needs to be a separate FX bus fader, when pulling down all faders in Gang mode FX bus does not reduce, or option to make FX post fader.

Thats a limitation of the type of demo version you use I think : *Needs to be reloaded every 25 minutes* ( quoted from the site)

A full featured demo version ( but limited to two months after you have activated it) can also be asked for on Xils site.

Fx send : A pre/post toggle will be there in the next version.( Already implemented on 0.98 G iirc) But defifinitely there in the beta version I run ( v 0.98 H, soon public)

I have the full featured demo, works fine in Cubase. In S1 it will mute if a I change a preset sometimes and way before 25 mins. It will output a faint clicking sound.

Thanks Woodennis. That's interesting to see that it works well in Cubase, and less in S1. Yes, we recently found some bugs because hosts werent reporting the same events in the same manner. Might explain your bug as well hopefully.

[HardSinc]

We have very few gamers for the contest atm . So maybe some of you are working undercover on it atm ... or maybe drum synthesis ( category 2) is regarded as a bit too special (actually it's certainly a bit specific), but you can still make a demo track (category 3), or make global presets, ie sequences/rythms mainly (category 1) . You guys should really take your chance now. Lot of prizes to win, few participants, I'd say zero risk to at least try ...

Been really busy, definitely going to put some bits in for all apart from the song, not enough time. I love drum synthesis, don't go removing that section

[CinningBao]

Picture 1 : Oscillator 1 as source is very usefull. You can use ti to perform all kinds of cross synthesis actions for example ( modulating osc1 by osc 3 while sample has been choosed for osc3), and, also, one thing for wich it's very usefull is to assign osc 1 or 2 to sine, then modulate it by itself (or the other oscillator) in the macro matrix : This is the way to get a wide variety of *noise* oscillators, and it's especially handy if you have osc 3 assigned to a sample, and still wish to have one or two additional *noise* oscillators.

Then, you're right, while the two LFOs have already a good choice of targets in the first matrix, it's true that they could have been added to the sources in the macro mod (under the modulators group of sources ) We intended to do that for ages, but it just went under the pile for whatever reason, sorry for that.

Ah, I see - Oscillators are a great source for filter and pitch modulations so I understand why they are there. I just expected to see the LFOs there as modulation sources as well. Thanks for re-considering them

Feature Request 1: If you could duplicate the MacroModulation frame in itself (possibly an A/B type tab like you added for the LFOs) this would give is even more expressive ability within the drum sounds.

Feature Request 2: Currently the NOISE source cannot be modulated by pitch; can we please have the ability to modulate the speed of this noise?

Love this (virtual) box!

[CinningBao]

I have found an interesting bug -

Loaded the 'init kit' (after a heavily modulated kit)
Selected Sine on OSC1, expected pure tone, got white noise

After digging around I see this in the MacroMod target menu

Screen Shot 2016-02-15 at 17.32.17.jpg

Perhaps there is some improvement to be made to the management of the Modulation targets - it seems that although the GUI doesn't show the previous configuration, the MacroModulation slots do point to an incomplete over write of the current modulations. Sorry for saying it so strangely.

edit----
I think the pertinent point in the attached graphic as that both None and actual target resources are 'ticked'

edit2---
the same problem exists in the MacroMod sources - None is selected as is OSC1, and I can't seem to remove the modulation. If you need a more detailed path to recreate, please let me know

[CinningBao]

It's getting pretty tight in the GUI now, but I would like to request an LFO phase adjustment knob.
Please?

[Lotuzia]

Picture 1 : Oscillator 1 as source is very usefull. You can use ti to perform all kinds of cross synthesis actions for example ( modulating osc1 by osc 3 while sample has been choosed for osc3), and, also, one thing for wich it's very usefull is to assign osc 1 or 2 to sine, then modulate it by itself (or the other oscillator) in the macro matrix : This is the way to get a wide variety of *noise* oscillators, and it's especially handy if you have osc 3 assigned to a sample, and still wish to have one or two additional *noise* oscillators.

Then, you're right, while the two LFOs have already a good choice of targets in the first matrix, it's true that they could have been added to the sources in the macro mod (under the modulators group of sources ) We intended to do that for ages, but it just went under the pile for whatever reason, sorry for that.

Ah, I see - Oscillators are a great source for filter and pitch modulations so I understand why they are there. I just expected to see the LFOs there as modulation sources as well. Thanks for re-considering them

Feature Request 1: If you could duplicate the MacroModulation frame in itself (possibly an A/B type tab like you added for the LFOs) this would give is even more expressive ability within the drum sounds.

Feature Request 2: Currently the NOISE source cannot be modulated by pitch; can we please have the ability to modulate the speed of this noise?

Love this (virtual) box!

FR1 : Adding another pair of Macro Knobs would also mean adding a pair of Macro knobs on the Eazy Synthesis page, and I just dont know atm where we could put them, but also adding more -possibe- Cpu charge, so for the moment we'll stay at two macro mods with each 4 targets. At the moment we have what we think is a good balance between CPU and zero compromise sound quality.

All in all, in StiX, you have the classic matrix mod (14 hardwired mod paths), the Macro Modulations ( 2x4 mod paths ), the per step modulators ( 2*1+1*1 mod paths), the Polystep Modulators ( 4*1 XY pad), and all the Fixed Macros of the eazy page, especially suited for precussive sounds ( Stretch, Global Pitch, Divergent, Convergent, all velocity driven mods etc)

And, you can still automate the Macros and all synthesis parameters via midi Ccs. Then, the macro mods can also additionally be driven by the sequencer steps etc. So it's not so bad to make a drum sound. There could be more, I agree, and indeed, I have a couple additional ideas for some other *never seen* modulators. But I dont know when/if they will come. I feel like we still havent pushed StiX to the limits of what it can do, and, for me at least, a lotttttt of things remain to explore.

FR2 : Noise contains all frequencies. Therefore it has no pitch. So, we could use the 'tune' knob to 'make something' when noise is selected. There are many many options here (actually, probably too much options ). But this will have to wait also, because atm, we're rushing to get a bullet proof v1.0, before we can even think of adding something else.

Also for your filter crash : Could you please indicate us what beta version you run atm ? The log seem to rindicate an older beta version ( you can verify the version with the about button in StiX. Current public beta version is 0.98 G). Thanks in advance.

[Lotuzia]

I have found an interesting bug -

Loaded the 'init kit' (after a heavily modulated kit)
Selected Sine on OSC1, expected pure tone, got white noise

After digging around I see this in the MacroMod target menu

Screen Shot 2016-02-15 at 17.32.17.jpg

Perhaps there is some improvement to be made to the management of the Modulation targets - it seems that although the GUI doesn't show the previous configuration, the MacroModulation slots do point to an incomplete over write of the current modulations. Sorry for saying it so strangely.

edit----
I think the pertinent point in the attached graphic as that both None and actual target resources are 'ticked'

edit2---
the same problem exists in the MacroMod sources - None is selected as is OSC1, and I can't seem to remove the modulation. If you need a more detailed path to recreate, please let me know

Hmm just to be sure : When the GUI is not reflecting exactly what you hear, could you please try to 1/ select another drumpad, then 2/ return back to the one exhibitiong some problems. It's possible that some matrix nodes are not properly reinitialised when changing presets, but I'd like to be sure that this is not only a kind of 'graphic bug'. Almost every time I was confronted to such things, selecting another drumkit, then reverting to the edited drumpad fixed it. ( Worth also sometimes for the sequencer in line editor )

[CinningBao]

Feature Request 1: If you could duplicate the MacroModulation frame in itself (possibly an A/B type tab like you added for the LFOs) this would give is even more expressive ability within the drum sounds.

Feature Request 2: Currently the NOISE source cannot be modulated by pitch; can we please have the ability to modulate the speed of this noise?

FR1 : Adding another pair of Macro Knobs would also mean adding a pair of Macro knobs on the Eazy Synthesis page, and I just dont know atm where we could put them, but also adding more -possibe- Cpu charge, so for the moment we'll stay at two macro mods with each 4 targets. At the moment we have what we think is a good balance between CPU and zero compromise sound quality.

All in all, in StiX, you have the classic matrix mod (14 hardwired mod paths), the Macro Modulations ( 2x4 mod paths ), the per step modulators ( 2*1+1*1 mod paths), the Polystep Modulators ( 4*1 XY pad), and all the Fixed Macros of the eazy page, especially suited for precussive sounds ( Stretch, Global Pitch, Divergent, Convergent, all velocity driven mods etc)

And, you can still automate the Macros and all synthesis parameters via midi Ccs. Then, the macro mods can also additionally be driven by the sequencer steps etc. So it's not so bad to make a drum sound. There could be more, I agree, and indeed, I have a couple additional ideas for some other *never seen* modulators. But I dont know when/if they will come. I feel like we still havent pushed StiX to the limits of what it can do, and, for me at least, a lotttttt of things remain to explore.

FR2 : Noise contains all frequencies. Therefore it has no pitch. So, we could use the 'tune' knob to 'make something' when noise is selected. There are many many options here (actually, probably too much options ). But this will have to wait also, because atm, we're rushing to get a bullet proof v1.0, before we can even think of adding something else.

Also for your filter crash : Could you please indicate us what beta version you run atm ? The log seem to rindicate an older beta version ( you can verify the version with the about button in StiX. Current public beta version is 0.98 G). Thanks in advance.

FR1: Yup - fair enough. I'm not saying there aren't enough modulators at all, perhaps I haven't fully explored the other modulation possibilities yet!

FR2: At it's purest, my suggestion would simply have 'slowed down' the rate of change in the white noise source.. if from an uncompressed source, slowing down the playback rate (slowed-down noise is a great thing) and if the noise is a proper sample and hold design then simply sampling points further apart..

The two crash files I sent _are_ from different versions - the earlier dated file from the release prior to 0.98, and the later dated file is from the current release. It crashed, I captured the Report, realised there was a new release, downloaded and installed, fiddled around, got the crash fiddling with same knobs.