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

[Lotuzia]

Hi Lotuzia!
i still have the MIDI "bug" on version H
StiX only responds on MIDI channel 1 on the selected drum pad. No signs of life fro MIDI channels 2-16.
bests
a.

Hello Lalo, sorry to hear this, this is really unfortunate . Well, as you know, we spent a lot of time with you to try to replicate and understand this problem. We exchanged some project files, and the project files you sent us were working totally OK in our systems ( Same Daw/etc) We sent you some files that we knew were working in the host you use, and it unfortunately happens that they were not working for you. So that we cant see what we can do atm ( Midi automation of StiX parmaeters by Midi Ccs is also working in all the daws where we have tested it)

So, I suggest the following, a different approach :

1/ Make sure you run the last version of your Daw
2/ Post on the forum of your daw and explain the case, and see if other people can help, or have encountered similar problems, with StiX or with other plugs.
By this I mean, it might be something to configure on the daw, and maybe specialists can help there.
3/ Exchange files with people using your daw and StiX, and see if someone can find a solution, or at least more elements that could help to the understanding of the problem.

If someone else reading this has the same problem, or at the opposite doesn't have it, or can make further tests in Reaper, please feel free to post here, and contact Lao and/or us. Thanks in advance.

[Lotuzia]

Suggestion:

Provide another column of OSC controls specific to noise. so there would be 4: osc 1, osc 2, noise, sample. for the noise column, the controls are: TONE, TYPE, LEVEL. Type includes noise types such as white, pink, brown and possibly noise bursts that simulate percussion attacks and maybe even a way to load in a sample of a noise attack.

Also provide another set of ENV knobs specific to noise VCA.

This would enable full-ish control over noise as a way to add and control attacks and other uses of noise with drum sounds.

You can have more 'noise oscillators' with the following :
1/ Put one oscillator in Sine Mode 2/ Modulate this osc by itself in the Macro Matrix. (Source = Noise/Smp Target : Osc Pitch )

The interesting thing is that you can get a lot of Noise 'colours' by doing that.

So you can have up to 3 *noise* oscillators simultaneously, in StiX. One of them possibly beeing any *Noise sample*, burst, sweep, transcient, well, anything you like really.

[Lotuzia]

Hey Lotuzia - now I couldn't replicate the bug, either. Yesterday, when it occurred, I had made sure to do a rescan of the plugin before using it. Then I tried adding multiple copies of the multi-out version, and it crashed Live. Today, nothing of the sort happened, everything works fine although I've changed nothing in the interim.

Maybe my computer was having a bad day, who knows? I'll post again should it occur again.

Thanls for the Report, Ariston. And for the details about the 'rescan'.

Well its the second time in a few days that some users report problems in Live, then the next day everything is running fine. Maybe it's safer to reboot the computer after installing a new version ? Seems weird, but it might be a/one *logical* explanation ???

Then, obviously it depends on something else, because we could add several instances of StiX in Live, on different OS, different Live versions as well, without problems. So maybe a bad day you're right

Anyway, glad to see all is back in order now. And I wish you it will continue to be like that !

[pekbro]

Thats not bad looking, and at first sight, it's pleasant . I'm a fan of 'ol LCD display' and, in the very StiX 1rst incarnation I designed some for all the preset name zones ( though there were more the Yamaha type, black on green -nostalgia-, wich was ok with the black look -Also the knobs and buttons were completely different, with a flat non vintage look )

But ... the problem is that, in your example, the labels become heavily blurred, and much harder to see. We spent a lot of time to ensure that people with visual problems could use StiX .... with no -or minimum- problems. This approach prevent us to make too much fantasies like this one I'm afraid (or a more neutral one anyway)

Then, yes, I enjoy such a look ( with a less pronounced effect), just because, for me, it's somewhat related to the genesis of StiX : I wanted from the start to make an XoX drum machine. A 2016 XoX drum machine actually.

Im pleased you like, regarding the blurring, that's just because all I did was color it for
a quick previz. If I had drawn everything out there would be no blurring, much as with
a real LCD display. The labels simply go on the top layer. Honestly, if you wanted, you could achieve
an LCD look just by changing the background.

The reason I like it, is that it makes more sense to me visually, as it is now, you've got
colored animation without a realistic basis for it. I mean, that sequencer display is
just on the flat side of an apparently plastic component housing. There are no buttons,
video display or anything to make my brain accept it. Simply because, things don't
work that way in real life.

For me anyway, this is distracting...

*I should note: The only reason I feel this way is because you've gone to the
trouble of making it look like a piece of hardware, which I like allot. I just think
the sequencer doesn't quite fit with the concept of the UI.

Anyway, its hardly an issue...

-Cheers

[plexuss]

I still think the list of track names on the left should be replicated on the right between the track cells and the track functions. this will make it easier to scan the row and keep your eye on the track you want to apply a function to.

So I was thinking kind of an old-school LCD look would be good for the sequencer.
Anyway, I lazily whipped one up. Thought I would post it for the heck of it,
or incase someone else had been thinking that.



I do think you should add some more contrast to the sequencer transport
control or whatever...

-Cheers

*Edit: added lighting effects...

[plexuss]

Another issue: I just worked on a set of patterns and got a good patch going. I clicked Save As and filled out the form and clicked Save As. then closed the form and saw the bank and patch was set as I entered them. however everything in the patch was deleted. it was blank. re-selecting it from the menu resulted in a null patch, erasing all the work I did on that kit and pattern set.

[ariston]

Well its the second time in a few days that some users report problems in Live, then the next day everything is running fine. Maybe it's safer to reboot the computer after installing a new version ? Seems weird, but it might be a/one *logical* explanation ???
!

Well, since the rebooting of Windows has been the catch-all solution ever since 3.x, I wouldn't be surprised! Thanks for staying on top of things here.

[sacer]

are there any plans for midi and wav drag and drop? I wasn't able to activate the midi output in live 9.6 on win 10 when playing a sequqence and the wav file loading by browsing through folders isn't up to date compared to other drums.
Or maybe to integrate sample folders as soundbank for kicks, snare etc like the integratet xils lab folder.
And a button to clear the sequqence like the buttons to fill.

[stardustmedia]

I still think the list of track names on the left should be replicated on the right between the track cells and the track functions. this will make it easier to scan the row and keep your eye on the track you want to apply a function to.

I think that would become messy very fast. But I agree with your idea. I'd like to expand your idea into a new one, that I'd prefer: Make a scalable independent pop up window just for the sequencer, that can contain more details such as plexuss mentioned. Even better if the user can make that full window.

In a live or jam situation, where the sound is already set, the sequencer is the "last" and most important thing I'd like to see. So if the sequencer then can be huge and has a little more information going on and still has non-cluttered overview, that'd be EXCELLENT

I know this opens a very big can of worms... but imagine how that would separate that product from others

[mac16174]

When I try to read the writing in the DRUM PRESET field, I think I need glasses.

When I look at another plugin (eg Battery 4), I realize that this is not true.

[Lotuzia]

I still think the list of track names on the left should be replicated on the right between the track cells and the track functions. this will make it easier to scan the row and keep your eye on the track you want to apply a function to.

Actually there's simply no room left for this on the sequencer pane. And I prefer to spare any possible room for future functions. I dont want to eat the space of the XoX sequencer itself neither.

Then,

As on traditional XoX harware sequencers, you'll see that your brain/eye will be trained very quickly to distinguish between the different lines if you use StiX on a regular basis. It's there that giving generic names (BD, SN, etc) makes also sense : Its much easier to make a representation of the sequencer for the mind. The relative place of hits etc, indicates you on what line you will act. And there's always the sound to give the most valuable feedback.

Also : If you want to make sure that you edit, this line, and not that line, it's always possible to switch to the inline editor.

[Lotuzia]

Another issue: I just worked on a set of patterns and got a good patch going. I clicked Save As and filled out the form and clicked Save As. then closed the form and saw the bank and patch was set as I entered them. however everything in the patch was deleted. it was blank. re-selecting it from the menu resulted in a null patch, erasing all the work I did on that kit and pattern set.

Hi Plexuss,

Could you please indicate what host/os/versions you use, so that we try to replicate this. (also maybe export your preset and send it to Xils-Lab while using the form on the site )

Also : Could you make some other tests with saving dummy presets, to see if this happens each time, or if it was just a onee shot displeasure. - just make 'dummy presets' with a few hits at random, dont loose time for that)
Thanks in advance.

[Lotuzia]

are there any plans for midi and wav drag and drop? I wasn't able to activate the midi output in live 9.6 on win 10 when playing a sequqence and the wav file loading by browsing through folders isn't up to date compared to other drums.
Or maybe to integrate sample folders as soundbank for kicks, snare etc like the integratet xils lab folder.
And a button to clear the sequqence like the buttons to fill.

Hello, Sacer. No plans for midi drag'ndrop. Atm you can use the Midi Out function in the VST versions. We'll try to replicate the dysfunction in Live.( Sometimes just rebooting the PC seems to solve many problems in Live -see above-, but ... maybe not that one )

SINGLE Sample Loading : Only requires to use your browser to load a file. You can preview the sound with your browser. And you can tagg the sound. More than this, the sample will be incorporated in StiX library with zero risk to suffer from : Missing sample, broken link -if the sample was moved in another location-, etc. It makes alkso things much easier when migrating to a new machine, sharing files for projects with other users etc. Well, this systems obviously has pros and cons. Pros : Security and work in all quietness, benefit of the database system to search/find the right sound for your track quickly. Cons : Less fast than simple drag'n'drop

MULTIPLE Sample Loading : Please, use the Options menu/Misc/Import Multiple Wave Files function. It wil integrate your samples in StiX, and your can tag the soundbank, author, Category, subcategory ( Snares / Clap for example ) etc.

[Lotuzia]

When I try to read the writing in the DRUM PRESET field, I think I need glasses.

When I look at another plugin (eg Battery 4), I realize that this is not true.

Yes, you're right. We'll consider this request. ( Battery has no sequencer though, and is heavily tabbed. -But I love it nevertheless- It compliments very well StiX imho )

[lalo]

Hello Lalo, sorry to hear this, this is really unfortunate . Well, as you know, we spent a lot of time with you to try to replicate and understand this problem. We exchanged some project files, and the project files you sent us were working totally OK in our systems ( Same Daw/etc) We sent you some files that we knew were working in the host you use, and it unfortunately happens that they were not working for you. So that we cant see what we can do atm ( Midi automation of StiX parmaeters by Midi Ccs is also working in all the daws where we have tested it)

So, I suggest the following, a different approach :

1/ Make sure you run the last version of your Daw
2/ Post on the forum of your daw and explain the case, and see if other people can help, or have encountered similar problems, with StiX or with other plugs.
By this I mean, it might be something to configure on the daw, and maybe specialists can help there.
3/ Exchange files with people using your daw and StiX, and see if someone can find a solution, or at least more elements that could help to the understanding of the problem.

If someone else reading this has the same problem, or at the opposite doesn't have it, or can make further tests in Reaper, please feel free to post here, and contact Lao and/or us. Thanks in advance.

Thanks Lotuzia,
A few thoughs about it...

1. My DAW(s) is(are) updated at the very last version.
2. I have the same bug in other hosts (Max 7, Usine, Ableton Live) and i can send project files for you to check.
3. I guess is something "system" related at the time of my first StiX install?
4. All other MIDI CC controllable plugins i have reacts correctly in all the host (i did not checked other XILS stuff i own as Xils4 and the vocoder).

(5. All this MIDI mess is a nightmare, please invest some time to implement proper VST automation in all Xils stuff. I have other companies' stuff with tons of parameters like u-he Zebra and i have no flaws in my hosts. )

6. I find the "MIDI channel 1 to the selected drum pad" thing pretty illogical and can lead to some confusion when producing tracks with lots of modulation/automation goin' on.
Would be more logical for the channel 1 to be a global one and affects all the i.e. filter cutoffs of all the drum pads at the same time (respecting relative values).

7. I use to run all my hosts with Administrator rights beacause jBridge (wich i need to use) requires it. Could it be related to the bug?

Anyway my CC assignment is right beacuse on channel 1 StiX reacts correctly. Channels 2-16 are not workin' at all.

In the meantime i try to unistall and reinstall StiX.

i really hope we can solve this issue.
can you make a test case for other windows users?
thanks a lot and all the best
a.