OXIUM -New Xils-lab synthesizer- [ Jp8 Comparison :) ]

[carrieres]

yes the virtual keyboard
Nielze is right : i have some lag

[Lotuzia]

Hmmm maybe you can try " Option : Gui Refresh : Fast "

Edit : Here the virtual keyboard is instantaneous.(Cubase and Chainer ) And assigning the cut off to one of the novation Kb works ok. Sometimes theres a kind of inertia if I do very fast movements, like the knob keep on moving a bit after I have released it, but what I recorded is OK its exactly what I played.

[Kriminal]

@Kriminal

The sound you submitted is quite weird, that's why I asked Laurent to ask you what you did.
Sorry, I don't have a lot of time to write and read here at this time.
A lot of people (including you) here, gave some nice and useful comments that I must take into account for the final release (but not all will be integrated ! )

So if you just took the init patch, removed an osc, changed the wave form, modified the pulse width, opened the filter and reduced the resonance, I must admit I don't understand how you get this glitch.
That's why a screen shot of your patch could be useful (Poly/Monophonic ? How many voices unable ? Syncho between osc On/Off ? )
It may be a bug I would be glad to fix, but I need to know what happened to reproduce it and fix it !

Anyway, this glitch make me think of some CPU overload, as if the latency was very very low, but maybe I'm wrong.


BTW : Thanks for you kind and useful report, I should consider some points (especially the words of some labels).


Best regards
Xavier

thanks for replying xavier

i can send you an .fxp file, my host will save a preset like that..?

basically tho, i openbed the synth, turned up sustain to full and decay and release to zero on envs, turn up filter freq to full reso to zero, env amt to zero. Tuned down osc2 vol so only osc 1 is heard.Drift is set to zero, its a basic raw osc init patch really. A single note, C4, is played over one bar which is looped in the playlist. The nasty sound is when the bar starts again.

no modulations, no fx, just a single saw wave playing.

Dave

[Nielzie]

Hmmm maybe you can try " Option : Gui Refresh : Fast "

I tried that, but still the same. No big problem for me though, because it's only GUI lag, the audio changes are on correct speed. It just looks a but "sluggish"

And I also miss the label of the filter section. Would be more consistent to have one imo

[carrieres]

Hmmm maybe you can try " Option : Gui Refresh : Fast "

Edit : Here the virtual keyboard is instantaneous.(Cubase and Chainer ) And assigning the cut off to one of the novation Kb works ok. Sometimes theres a kind of inertia if I do very fast movements, like the knob keep on moving a bit after I have released it, but what I recorded is OK its exactly what I played.

thanks you ! the fast option was necessary
for the knob, did you try with a heavy cpu load like 50 % (cpu indicator from ableton) ?

[kx.001]

I've just been trying Kriminals patch (or similar) and get the same - does the wave reset to zero each time? Saying that, slowing the attack only got rid of it when the attack became noticably slow..

Will definately be having a bit of a play though. I may find the learning curve to this one more approachable than your others

[xavier]

@Kriminal

The sound you submitted is quite weird, that's why I asked Laurent to ask you what you did.
Sorry, I don't have a lot of time to write and read here at this time.
A lot of people (including you) here, gave some nice and useful comments that I must take into account for the final release (but not all will be integrated ! )

So if you just took the init patch, removed an osc, changed the wave form, modified the pulse width, opened the filter and reduced the resonance, I must admit I don't understand how you get this glitch.
That's why a screen shot of your patch could be useful (Poly/Monophonic ? How many voices unable ? Syncho between osc On/Off ? )
It may be a bug I would be glad to fix, but I need to know what happened to reproduce it and fix it !

Anyway, this glitch make me think of some CPU overload, as if the latency was very very low, but maybe I'm wrong.


BTW : Thanks for you kind and useful report, I should consider some points (especially the words of some labels).


Best regards
Xavier

thanks for replying xavier

i can send you an .fxp file, my host will save a preset like that..?

basically tho, i openbed the synth, turned up sustain to full and decay and release to zero on envs, turn up filter freq to full reso to zero, env amt to zero. Tuned down osc2 vol so only osc 1 is heard.Drift is set to zero, its a basic raw osc init patch really. A single note, C4, is played over one bar which is looped in the playlist. The nasty sound is when the bar starts again.

no modulations, no fx, just a single saw wave playing.

Dave

You're welcome, thanks for your explanation.

I didn't noticed it was a single note loop. So I tried this and obviously got the same behaviour you and kx.001 described.

The init patch you used is a polyphonic, circular mode, using 7 voices.
So each time a new note ON comes, a new voice is activated while the previous voice ends (with the release at 0, this is doing very quickly, no time for phasing effect).
So the glitch comes from the fact that the audio abruptly changes its source.

If you want to keep the same oscillator (voice) running, so keeping a regular sound without any glitch or modification when the Note Off/On happens, then either you choose "MONO" (whatever the priority) either you choose "POLY reset" which keeps the same voice when only one note is activated.

I hope that helps

Best regards
Xavier

[kx.001]

If you want to keep the same oscillator (voice) running, so keeping a regular sound without any glitch or modification when the Note Off/On happens, then either you choose "MONO" (whatever the priority) either you choose "POLY reset" which keeps the same voice when only one note is activated.

I presumed there'd be an option like that but only had a quick play amonst other tasks so didn't notice did have a look mind, so pilot error!

[Crackbaby]

"Layers locked at launch" in the misc menu .. what does it do, it's not in the manual

[Kriminal]

Thanks xavier, i'll test that out tomorrow.

[Lotuzia]

"Layers locked at launch" in the misc menu .. what does it do, it's not in the manual

It doesn't do anything, we just forgot to remove it. You can forget this one. It will be gone in the next update.

[glokraw]

Poor old George got raked over the coals, because light gray was too bright for the
peanut gallery testing the Corona demo

No he got taken to task because the Corona background is too white and not light grey....too harsh. If you consider potential customers the"peanut gallery" then I don't know what else to say.....

When you add enough pigment to white, to notice the difference,
you have made light gray. When you buy the product, you can exit
the peanut gallery, if desired.
Cheers

[Lotuzia]

.... either you choose "POLY reset" which keeps the same voice when only one note is activated.

I hope that helps

Best regards
Xavier

Exactly what I suspected.

[Kriminal]

.... either you choose "POLY reset" which keeps the same voice when only one note is activated.

I hope that helps

Best regards
Xavier

Exactly what I suspected.

....but never mentioned.....funny that.

[Teksonik]

Poor old George got raked over the coals, because light gray was too bright for the
peanut gallery testing the Corona demo

No he got taken to task because the Corona background is too white and not light grey....too harsh. If you consider potential customers the"peanut gallery" then I don't know what else to say.....

When you add enough pigment to white, to notice the difference,
you have made light gray. When you buy the product, you can exit
the peanut gallery, if desired.
Cheers

Wow what's your problem lady? We can't make a comment until we buy the product? Besides this isn't even the right thread, wrong product. You went way off topic and you were wrong as well....