Waldorf Attack 3

[hybrid2025]

When I switch to the keyboard mode where a sound can be played melodically across the entire keyboard, Attack 3 shows strange behaviors; Sometimes it reverts to the default sound, changes to the sound are not reflected immediately, and the release gets cut off. The plugin is rather unstable and I have to reload it from time to time. I'm using Mac OS.
Has anyone else experienced the same issue?

[c_voltage]

When I switch to the keyboard mode where a sound can be played melodically across the entire keyboard, Attack 3 shows strange behaviors; Sometimes it reverts to the default sound, changes to the sound are not reflected immediately, and the release gets cut off. The plugin is rather unstable and I have to reload it from time to time. I'm using Mac OS.
Has anyone else experienced the same issue?

Did check couple switching to keyb mode, with loaded couple factory kits, no, did not catch issue yet, seems ok here (Win10)

[hybrid2025]

Thank you for testing

[theoryzero]

Yes, please contact them with some photos to prove you own it. I spoke with them, that you will get an upgrade offer.
The technical problem is, that we do not have a complete list of all V1 licenses which would be necessary to provide an automatic upgrade offer for Attack 3. So, we need to handle them manually.

Rolf,
Thank you for the fast response, support handled it for me quickly and I’ve completed the upgrade. Thank you!!

[Hettoblaster]

Hi Rolf,

Any chance of new presets being added?
I heard this happened with a few previous Wldorf releases..


EDIT: bought already btw

[PhaseTransition]

Hi Rolf,

Any chance of new presets being added?
I heard this happened with a few previous Wldorf releases..

Agreed! More Presets would be great.

[blatanville]

re: LFOs

I was surprised I couldn't do something simple like assign an LFO to the pan knob in the AMP section...

Damn, found lack of automation for some parameters, like Osc waveform shapes (that sad) or "Crack" Length. Whereas in v2 all this was automatable.
Also for dropdown timing lists, like for filter mod sync or delay fx sync.
Ok not saying about new ones - many of them not automatable too (like lfo shapes etc). But sad when there is downgraded elements which works before i mean.

Also noted that automation list organised in v2 more neatly (despite it's VST2) - all nodes sorted to subfolders, divided by synth sections. Whereas in v3 all param's in single huge list, lazy approach lol.

[blatanville]

Bug?
with an instrument SOLOed, selecting a different sound from the sound browser deactivates the SOLO.
auditioning sounds in context is necessary, of course, but auditioning while SOLOed is very useful, too.
I just noticed that changing sounds in the browser also reverts bus selection to BUS 1.
I guess a LOT of parameters and settings are stored with the sound preset...
I think it would be better if those settings that are "downstream" of the actual sound parameters weren't stored, or were stored, but defeatable (like how some drum plugins will let you load a kit + MIDI, or just the kit, or just the MIDI)
ETA: SOLO status shouldn't really be stored in a sound preset, in my opinion.
ETA2: the BUS setting for a sound shouldn't be in the sound preset, either; it should be in the kit.

hope this helps/finds the right person...

[c_voltage]

re: LFOs

I was surprised I couldn't do something simple like assign an LFO to the pan knob in the AMP section...

All 4 knobs in the Mix section automatable fortunately.
The only thing - 2 dropdown lists (for poly and bus) are not.
It seems this is general approach in the new version that all dropdown "selectors" UI elements lack of automation. Some of them is new addition in Attack (which would be forgivable), but another half of them (ok less than half) already was exists in v2, just in other UI form, and was automatable. THAT disappoint.

Similar situation with the "counter" UI type handles (like Semitone\Detune\Phase etc) - but most part of them automatable, but some not (like already mention Crack length "Cycles").

Whereas ALL standard knobs (common circular handles) are automatable, even all knobs of each dropdown effect in Bus'es effects page. This is 6 busses, with 5 fx slots in each, from which 3 slots with selectable x6 fx units. This enormous list of automatable nodes actually, lol. But this is implemented nevertheless. Whereas total automation for fx section, can't say that very popular approach in plugs, right.
This gives hope that the fact that the same approach was not applied to selectors and counters is perhaps just a more or less accidental oversight lol.

[blatanville]

re: LFOs

I was surprised I couldn't do something simple like assign an LFO to the pan knob in the AMP section...

All 4 knobs in the Mix section automatable fortunately.
The only thing - 2 dropdown lists (for poly and bus) are not.
It seems this is general approach in the new version that all dropdown "selectors" UI elements lack of automation. Some of them is new addition in Attack (which would be forgivable), but another half of them (ok less than half) already was exists in v2, just in other UI form, and was automatable. THAT disappoint.

Similar situation with the "counter" UI type handles (like Semitone\Detune\Phase etc) - but most part of them automatable, but some not (like already mention Crack length "Cycles").

Whereas ALL standard knobs (common circular handles) are automatable, even all knobs of each dropdown effect in Bus'es effects page. This is 6 busses, with 5 fx slots in each, from which 3 slots with selectable x6 fx units. This enormous list of automatable nodes actually, lol. But this is implemented nevertheless. Whereas total automation for fx section, can't say that very popular approach in plugs, right.
This gives hope that the fact that the same approach was not applied to selectors and counters is perhaps just a more or less accidental oversight lol.

I just read the entire manual and couldn't find instructions for assigning a modulator to a parameter that isn't on the MOD view of the envelopes.
The AMP section of the manual (pg 25) contains no information about how to assign modulation sources to any of the 4 knobs.
Can you tell me how you've done it?

[budweiser]

Yeah, same here. True to the original, they even pushed the bugs forward to this new iteration !

After extensively comparing V3 with the previous version I tend to agree. I haven’t found anything other than the buss/efx setup that functions or sounds differently between the two. I believe it’s mostly the UI that has changed in a dramatic fashion. Might explain the inexpensive upgrade fee.

All new v3 features regarding the sound engine like new filter and drive types, LFOs, Envelopes etc. are additive, i.e. we intentionally did not change the main sound of Attack which I believe is a good thing.

Thanks, Rolf. Sure it's a good thing, although some kits do not sound exactly the same as in previous versions (Acoustic kit). Any word about the lfo -> enveloppe start thing that do not seem to work if lfo is not a s&h ? From time to time i have the feeling that it's making something, but with such a narrow sweet spot that it have to be tweaked for ages before hearing a result. Am i wrong in seeing this as a bug, maybe i do not understand the thing...

[c_voltage]

I just read the entire manual and couldn't find instructions for assigning a modulator to a parameter that isn't on the MOD view of the envelopes.
The AMP section of the manual (pg 25) contains no information about how to assign modulation sources to any of the 4 knobs.
Can you tell me how you've done it?

No no, i just meant that this 4 knobs can be automated (via host),

All 4 knobs in the Mix section automatable fortunately.

and respectively they able to be modulate externally. (That may vary by DAW capabilities tho).
They does not have way to be modulate internally via lfo.

[blatanville]

I just read the entire manual and couldn't find instructions for assigning a modulator to a parameter that isn't on the MOD view of the envelopes.
The AMP section of the manual (pg 25) contains no information about how to assign modulation sources to any of the 4 knobs.
Can you tell me how you've done it?

No no, i just meant that this 4 knobs can be automated (via host),

All 4 knobs in the Mix section automatable fortunately.

and respectively they able to be modulate externally. (That may vary by DAW capabilities tho).
They does not have way to be modulate internally via lfo.

Well, thank you for confirming that I hadn't missed anything in the manual and interface!

[PapaDee]

I am having some issues here and there. Some of my user samples don't load. Not sure why some do and some don't. On top of that after a long session, even the factory samples won't load as it claims "not found" even though i had been using them earlier. I mean, i know it is a drum synth and that is what i bought it for, but the sample section (which i mainly use as transients) is super buggy at times. Even the intant load sample function goes haywire from time to time. Anybody else having this?

[rafa1981]

I haven't been doing music lately, but I could easily make the whole audio engine die in seconds by just switching samples fast. If there is something multithreaded there in the sample loading or whatever it's really wrong.

So I answer a partial yes to your question.