SYN'X 2.5 Released - Xils-Lab - (Multitimbral Synthex - intro discount-)

[Lotuzia]

Was about to try the demo, but then I saw that a USB dongle is required for the full version. I won't even bother trying the demo now. Sorry.

PS: The price offer looked tempting though...

Demo is dongle less and you can choose the soft ilok version for protection to the full version ( means no physical dongle required, and more of a c/r protection )

[az82]

Hm. Thanks. Soft iLok sounds like an OK compromise to me. I know the demo does not require a dongle, it's just that when you know that the full version requires to have an USB port occupied, is not fun.

[wagtunes]

I'm not sure I totally understood, but I think you can do what you want (if this doesn't need more than 16 voices/8 layers )

Let see for instance.

Sequencer 4 tracks are using layer 1, 2, 3, 4 (voices 1,2,3,4)

Keyboard lower is using layer 5,6,7 (voices 5,6,7,13,14,15, poly circular for pads)
Keyboard upper is using layer 8 (voice 8, 16, unison 2 for lead)

I must agree you need a quite powerful computer (up to 12 voices playing at the same time) , but that's possible (there is still 4 voices left for anything you would need. Unison for the sequencer for instance)

Inside the limit 8 layers, 16 voices (each layer controlling always the same two voices) everything is possible.

Using the Copy/Past/Exchange between layer can help you. But as assigning a voice is quite obvious too, for exchanging layers.

Best regards
Xavier

Okay, whatever you did with the new EXE seems to have fixed the problem. I will keep testing and if I can recreate anything odd, I will document the steps and send them to you so that you can recreate them yourself.

Then, if this is the way it's actually supposed to work, just let me know.

Right now, I think the problem I was having has been solved.

[XILS-lab]

Hm. Thanks. Soft iLok sounds like an OK compromise to me. I know the demo does not require a dongle, it's just that when you know that the full version requires to have an USB port occupied, is not fun.

If you are asking for a time limited demo, using the full version, the code you will receive doesn't allow the soft location (the full commercial code will do, of course)
So If you want a time limited iLok demo with the soft enable, just contact us, sending your iLok account name, we will deposit manually the time limited license.

Best regards
xavier

[KingTuck]

This is a really nice synth, Xavier. And a free upgrade. Really digging the way Xils is being run.

[zerocrossing]

Just picked this one up yesterday. Between my pre-sale price and loyalty coupon, it was a great deal for an amazing sounding instrument.

[wagtunes]

Well, I had one of those ah-ha moments with this synth tonight after going through the manual just one more time.

Suffice it to say, my sequencer split problems are over. Yeah, it takes a little bit of work and some outside the box thinking but I've figured out how to do just about anything with this software.

Xavier, I have a feeling I'm going to have a lot of sleepless nights with this thing. LOL.

[KingTuck]

Xavier, this thing is great. Really nice work man. Keep it up!

[wagtunes]

Xavier, this thing is great. Really nice work man. Keep it up!

Isn't it though? And honestly, it took me by surprise. I had no idea how deep this thing is. I think it's even more versatile than the Matrix 12.

I may have to put my Synthmaster bank on hold. LOL.

[Lotuzia]

....Thank you, yes. I pretty much have this thing under control. Took me 2 whole days and that's after 36 years of using Synths.....

Primarily, when creating patches in advanced mode where you're modifying each OSC by hand one at a time, getting instant feedback isn't so straight forward because of how voice allocation works. For example, working on layer A (voices 1 and 9), with all the other OSC's turned on, it's hard to hear what's actually happening to those 2 voices. However, if you solo layer A, it doesn't shut off the other voices, just the other layers. So as you play, you're going to get lots of silent notes when the other voices are triggered. So what you need to do in order to rectify this is go down to the advanced section and actually turn off voices 2, 3,4, etc. And then, when you're finished with layer A and move on to layer B, you have to turn voices 1 and 9 off and turn on voices 2 and 10. And you need to continue doing this throughout the process.

But here's where it gets tricky.

After you've programmed all 8 layers, you then have to listen to them all back on to see if anything you've done clashes. If something doesn't sound right, as you play, you need to watch the voices as they're sounding to see which voice is actually causing the problem.

Needless to say, I have never performed such surgery with a synth in my life, including every modular I've ever worked on. But the end result is astonishing if you get everything just right.

.......................

For both cases : There's a turnaround for the voice allocation I often used for complex patches. Instead of turning voices off, just solo one layer then increase the Unison value, as much as necessary so that each note triggers the layer you're soloing. It's often quicker.
Else welcome to the beauty of the Syn'X 2 : By making *weird* voices allocations, like one of the voices of a layer for one Keyboard, and another one for the other keyboard, you can get some really otherwordly patches. Simon Ball ( Sounds Divine ) used this for some of his patches, and the results speak for themselves.
Else, those who have performed with an Oberheim Matrix 12 for example will be more familiar with this kind of Voices/Card architecture. Once you're into it, it's incredibly powerfull, inspiring, and full of fantasy. This is the sense of the 'matrix12/Synthex hybridation imho. It brings something new in the synthesizer world.

The problem with using Unison mode is that you don't really get a true sound as the unison does alter the timber even if just slightly. But yes, that is the beauty of this synth, and I have allocated voices of layers split between both keyboards. The results, as you will eventually hear, are nothing short of surreal.

Don't remember the last time I had this much fun programming a synth.

Hmm there are two different ways to consider Unison in the Synx'2, first case is when all layers have the same sound. Unison works like in traditional way. But when the layers are different, like in the *multiple card* preset, Unison is also there to guaranty each layer will be triggered by a new midi note. In any case zeroing or reducing the Unison spray will make sure the sound is almost identical to a if there were no unison settings.

[Lotuzia]

Examples :

Multiple card

In this example Unison is used to make sure each layer/synthesizer will be triggered by each incoming note ( so to make huge stacks )

Ld SuperBSaw

In this example Unison is used in the traditional sense : All layers/Synths have -slightly- the same settings. It's one of the possible incarnations of the SuperSaw a la Syn'x 2 ( Note that its a *true* unison )

[paulbreeze]

I get PWM mode Error! with a lot of presets (factory and also miniWork). Any Idea what that could be?

[penguinfromdeep]

I get that PWM error too, and still chorus and other effect seem to be 100% wet all the time when I engage them and the dry / wet control doesn't work.. Ableton Live 64 bit, OS X Audio unit ..

[Lotuzia]

dbl post

[Lotuzia]

The pwm flag was implemented in the beta to trace some slight pwm denormal errors iirc. I get this also, especially after browsing a lot of preset, and with presets that don't use pwm as well.( probably because the Pulse oscillator is always active, as you can stack oscillators at any time ) afaichear, it doesnt affect the sound itself in 99% of the cases.( I even made some rendering to compare sounds). To PFD : Chorus works ok here, maybe you should file a report to Xils thru their site utility.