Tone2 ElectraX is available!

[cain]

hey Echoes not at home right now but will test as soon as i get home, should be in a couple of hours. will report back

[Ingonator]

Hey Max, it's not a bad synth i just guess im Waldorf through...

Yeah, me too (add Dune and Alchemy to that...) and that's what is holding me back (so far...).

[MaxSynths]

Hey Max, it's not a bad synth

Rob it's not my synth, and if it was my synth I would take care of your opinion because usually I do prefer negative feedback because it's the only way to go on in the process of making things work better

The synth is good like i said but maybe when the bugs are fixed eh?

The bugs: like I saiud before I suspect that the problem is related with the demo. But this something that I can't confirm (Markus?), the only thing I can say is that the full version is not showing the problems described here in this thread (any other user can confirm what I'm saying?). Note that in the beta stage some BIG bugs were found and Markus worked hard to fix them... the problems described here are very "banal" problems, almost impossible to be ignored for beta testers. This is why I suspect the problem is the demo.

[Echoes in the Attic]

Love the sound of the synth and will buy it as soon as the bugs are fixed. It is extremely buggy currently.

As a beta tester I'm surprised by the "bugs" that have been reported here because I never experienced these problems. I'm sure there are some bugs that need to be found yet, this is normal I think, but these problems makes me thing that meybe there's something wrong in the demo version, because I can't reproduce them on my copy of the instrument (well I'm on PC, I never tried the Mac version... but on WinXP the synth is very stable and all functions are working the way they should).

Yes, it's possible these are demo bugs, but it's more likely they are mac related. If it were demo related, I would go ahead and buy. But mac related, not sure. I remember the mac version of warmverb had a bug where it would use about half a decent computer's cpu where it should have used a tenth. Not sure that ever got fixed.

It would be cool if someone with the PC demo could test for a while. Just trying out presets of course will not show these bugs, you have to actually be tweaking and know what to expect from the sound (ie having some understanding of how fm works etc.).

So Max you can confirm even that if you're fm is off and you are only using Osc2, that if you hold a note and raise the osc1>osc2 fm knob you will indeed hear the fm affecting osc2 immediately? And also moving the octave will also affect the fm sound as it should? Well if so, that's good that the bugs are probably down to certain platform and/or demo versions.

[rob_lee]

Rob it's not my synth, and if it was my synth I would take care of your opinion because usually I do prefer negative feedback because it's the only way to go on in the process of making things work better

No negatives from me Max, first thing i noticed was the top notch presets.
I just don't think it suit's me, just yet anyways.

Rob

[MaxSynths]

So Max you can confirm even that if you're fm is off and you are only using Osc2, that if you hold a note and raise the osc1>osc2 fm knob you will indeed hear the fm affecting osc2 immediately? And also moving the octave will also affect the fm sound as it should? Well if so, that's good that the bugs are probably down to certain platform and/or demo versions.

Ok I've initialized the patch and turned off OSC1: moving the FM knob nothing happens; but if I turn on and then off OSC1 you can hear the FM is engaged...

[MaxSynths]

No negatives from me Max, first thing i noticed was the top notch presets.
I just don't think it suit's me, just yet anyways.

Rob

Well I'm against savage buying of software, I think a synth is useful only if you need it and when you need it, TBH

[Echoes in the Attic]

Just to clarify these unresponsive parameter problems (for when others are checking), there are several different things that could happen:

1-Sometimes some buttons like osc on/off simply don't turn them off. I can't find a way to reproduce 100% but it's frequent.

2-Sometimes turning a knob up does not change the sound appropriately until a while after the sound is let go. Perhaps until the release phase is finished. fm is the example I've noticed but someone else noticed drive. Drive seems normal to me). for fm this is only true when it starts at 0 and is raised. No change happens until after the key is released and a new one is pressed. However even if i quickly release a key and press a new one, the fm still does not kick unless a leave enough time in between key presses. This is what leads me to think it kicks in after release phase is through at least (but I don't know, just a guess). If the fm knob is already up and you hold a key and turn it down, the fm decreases appropriately while the key is held (as it should, unlike going up from 0)

3-If an oscillator is off, the fm can still affect another oscillator, however the other parameters have no effect (like octave) unless the source osc is turned off and back on. I thought the osc settings were maybe left as they last were when the osc was on, however sometimes it is impossible to get the same sound from the fm with the source osc on and off. I can't tell the intended behavior here. I assume that when the osc is off, it should still have an effect as an fm source because it does affect the fm target. This is a problem if you only want to hear an osc being modulated by another osc and not hear both oscillators at the same time. The workaround is to have the source osc on but the volume down. Perhaps this is the intended behavior but if so it's strange that fm still affects another osc when the source is off, just without control.

Edit: I have been unable to reproduce the problem someone else mentioned with the drive control not working right away, I only get it with fm.

[Echoes in the Attic]

So Max you can confirm even that if you're fm is off and you are only using Osc2, that if you hold a note and raise the osc1>osc2 fm knob you will indeed hear the fm affecting osc2 immediately? And also moving the octave will also affect the fm sound as it should? Well if so, that's good that the bugs are probably down to certain platform and/or demo versions.

Ok I've initialized the patch and turned off OSC1: moving the FM knob nothing happens; but if I turn on and then off OSC1 you can hear the FM is engaged...

Aha. So something is weird here (as I described above). Either an osc should work as fm modulator when it's off or it shouldn't. Seems now it works when the osc is off, but parameters are unresponsive, it just remembers the states of the source osc parameters from the last time it was on. This one isn't bad because you can keep the source osc on and turn down the volume if you don't want to hear it (but still want it to modulate another osc). Not sure what the intended behavior is there. However the fm not working when turned up until a new key is pressed is unfortunate and I believe a bug. Same with oscillators not turning off sometimes.


Edit: The fm settings do not seem to remember settings from last time the osc was on either. From what I can tell, it seems random. So when a source fm osc is turned off it can sound completely different to when turned on. Sometimes I can't even get the same sound no matter what the settings are. It's impossible to tell what's going on here with the fm.

[MaxSynths]

As said I can confirm the strange behaviour on FM, but the other things works properly here.

[MaxSynths]

Aha. So something is weird here

Yep! Sent a mail to Markus right now. To be honest I would prefer FM to work both with OSC1 turned on or off (just like you say to exclude OSC1 sound if unwanted).

[Echoes in the Attic]

As said I can confirm the strange behaviour on FM, but the other things works properly here.

Cool, can you confirm one other thing?

Again have just Osc2 audible (doesn't matter if osc1 is on with volume down or just off). Have fm knob from osc1 at 0. Now hold a key and raise fm all the way. Any sound change at all? Now release note for a sec and play it again. Now you hear the fm right?

[MaxSynths]

As said I can confirm the strange behaviour on FM, but the other things works properly here.

Cool, can you confirm one other thing?

Again have just Osc2 audible (doesn't matter if osc1 is on with volume down or just off). Have fm knob from osc1 at 0. Now hold a key and raise fm all the way. Any sound change at all? Now release note for a sec and play it again. Now you hear the fm right?

Right... But I hear FM only when I play the note I was pressing when the FM knob was turned to zero... reporting!

[Echoes in the Attic]

As said I can confirm the strange behaviour on FM, but the other things works properly here.

Cool, can you confirm one other thing?

Again have just Osc2 audible (doesn't matter if osc1 is on with volume down or just off). Have fm knob from osc1 at 0. Now hold a key and raise fm all the way. Any sound change at all? Now release note for a sec and play it again. Now you hear the fm right?

Right... But I hear FM only when I play the note I was pressing when the FM knob was turned to zero... reporting!

Ah good, it's not demo or mac specific and I'm not crazy.

The more you play with the fm, the more you'll see strange behavior. Keep the volume of osc1 at nothing and compare different settings of osc1 on the sound of osc2 when osc1 is on vs. off. Sometimes you can not even make it sound the same at all. Can't tell why that is.

[MaxSynths]

Keep the volume of osc1 at nothing and compare different settings of osc1 on the sound of osc2 when osc1 is on vs. off. Sometimes you can not even make it sound the same at all. Can't tell why that is.

Yep already noticed... There is something really wrong with FM...