• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Darkglass Anagram Multi FX Announced

Anyone have a Helix that could capture NAM files of the billy sheehan modified pearce preamps on it?

“Busy One Brt” and “Busy One Jump”

To be a beggar...
I believe @archisland has the real hardware unit. Maybe he can help ;)
 
have any of you landed on a good envelope filter block ? all of the ones I have tried for the Anagram so far do work, kind of, but they are pretty wimpy (IMO of course) in that the filter does not really open up a whole lot ... I guess I'd characterizer it as not a lot of "wah". For reference, I am used to using the MXR Bass Envelope Filter pedal which does get pretty pronounced in terms of the filter opening up with the right settings. I guess there is also the expression pedal, but I'm not really looking to add another piece of physical hardware just to get that sound.

Is there some technical reason that envelope filters are hard to model ?
 
Last edited:
have any of you landed on a good envelope filter block ? all of the ones I have tried for the Anagram so far do work, kind of, but they are pretty wimpy (IMO of course) in that the filter does not really open up a whole lot ... I guess I'd characterizer it as not a lot of "wah". For reference, I am used to using the MXR Bass Envelope Filter pedal which does get pretty pronounced in terms of the filter opening up. I guess there is also the expression pedal, but I'm not really looking to add another piece of physical hardware just to get that sound.

Is there some technical reason that envelope filters are hard to model ?
I think the free Smultron III in the marketplace is great. Found a couple great, wet/fat sounds after just 15-20 minutes of toying with it.

Also, as noted in this thread, throwing a boost in front of the Anagram’s proprietary EF blocks makes them sound pretty good and a bit less ‘wimpy’.

I know this will be taken as maybe a ‘dickish’ thing, but I feel like I see/hear this with lots of envelope filter commentary (not just the anagram blocks)… I think a lot of people struggle to dial in envelope filters with more in-depth controls, because they’re so touch sensitive and interactive. I think all three of the blocks I mentioned are very serviceable if you spend time with them and get to know their intricacies. It’s the same with the analog filters I have/had.

The more controls and the more interactive the filter, the more time is usually needed to find the sweet spots that work with your playing, dynamic, and tastes.
 
have any of you landed on a good envelope filter block ? all of the ones I have tried for the Anagram so far do work, kind of, but they are pretty wimpy (IMO of course) in that the filter does not really open up a whole lot ... I guess I'd characterizer it as not a lot of "wah". For reference, I am used to using the MXR Bass Envelope Filter pedal which does get pretty pronounced in terms of the filter opening up. I guess there is also the expression pedal, but I'm not really looking to add another piece of physical hardware just to get that sound.

Is there some technical reason that envelope filters are hard to model ?
Have you tried any of the blocks on the Marketplace yet?

There's the SmulTron III Envelope Filter which is free - Anagram Marketplace
I didn't notice any radical difference to the DG Env Filter blocks, but then again, I rarely use them so I wouldn't be looking for the nuances that you might be.

Nembrini Audio also have an Auto Wah block (20 Euros) - Anagram Marketplace
 
have any of you landed on a good envelope filter block ? all of the ones I have tried for the Anagram so far do work, kind of, but they are pretty wimpy (IMO of course) in that the filter does not really open up a whole lot ... I guess I'd characterizer it as not a lot of "wah". For reference, I am used to using the MXR Bass Envelope Filter pedal which does get pretty pronounced in terms of the filter opening up. I guess there is also the expression pedal, but I'm not really looking to add another piece of physical hardware just to get that sound.

Is there some technical reason that envelope filters are hard to model ?
There's also our Cognate Kinetic block in Marketplace, an envelope filter designed for everything from slow and smooth to snappy and synth-y. It has intelligent auto sensitivity so you don't have to adjust a sensitivity control when changing technique, volume or even basses.

There's a video (not by us) comparing it to the MXR.

 
thanks to all the envelope comments and suggestions. I'll definitely take a look at these options. I don't use an EV all the time, but I have a couple of regular gigs where I've used the MXR to good effect, and like I said in my post, I just have not been able to dial in a similar funky auto wah sound on the Anagram options similar to the MXR.

@Phagor ... thanks for that vid demo with the MXR. If I can get that type of sound I'll be a happy EV camper!
 
  • Like
Reactions: Phagor
Damn, this is pure gold! Thanks a lot!

I wish if we could have those for all other blocks, or a native DSP load meter in the next KosmOS version.
Thanks.

Yeah, we could, and the methodology could improved, etc. but I personally would prefer Darkglass to concentrate on more pressing features and issues. This could end up being a time sucker to keep updated and might also create misunderstandings and false expectations.

Perhaps a global and/or per block DSP meter would be a more sustainable thing they could do, yet not high priority IMO.
 
I'm new to the anagram and struggling with the settings currently.

We are covering quite some songs with different tunings. I need like 3-4 base sound and then some pitch shifting for different songs.
My Idea was now was to have a preset each for the 3-4 sounds. The scenes I wanted to use for up to 3 different tunings per preset (e.g. Standard, -1, -3). For effects I want to use the Stomp mode.

I'm planning on changing preset and scene via midi with Ableton running our click and stay mainly in the stomp mode.
When I now have an effect activated via stomp mode and I switch the scene and back again, the scene still has this effect on.

Is there anyway to stop anagram from saving which stomp is active?
Or should I use a totally different approach?

I really like the anagram, but this is quite annoying tbh.

Edit:
I just found this setting for midi in the manual:

1777616402475.png


But it doesn't seem to be applicable without midi.
 
Last edited:
I'm new to the anagram and struggling with the settings currently.

We are covering quite some songs with different tunings. I need like 3-4 base sound and then some pitch shifting for different songs.
My Idea was now was to have a preset each for the 3-4 sounds. The scenes I wanted to use for up to 3 different tunings per preset (e.g. Standard, -1, -3). For effects I want to use the Stomp mode.

I'm planning on changing preset and scene via midi with Ableton running our click and stay mainly in the stomp mode.
When I now have an effect activated via stomp mode and I switch the scene and back again, the scene still has this effect on.

Is there anyway to stop anagram from saving which stomp is active?
Or should I use a totally different approach?

I really like the anagram, but this is quite annoying tbh.

Edit:
I just found this setting for midi in the manual:

View attachment 7485659

But it doesn't seem to be applicable without midi.
I was just about to point you to that setting (When I use MIDI to change Scenes, Stomp changes I made are being retained?) :)

I'm a bit confused because you say "I'm planning on changing preset and scene via midi with Ableton" but then "But it doesn't seem to be applicable without midi."? Unless I'm mis-reading/mis-understanding something, these statements are contradictory? From your initial post, this setting should deliver the result you want when using Ableton to change Presets, Scenes, and even Scene to Stomp so you can enable/disable slots via MIDI, but when you switch Scenes, they will discard any Stomp changes.
 
During personell practice I will not be using midi via Abelton and also I need a fallback if something goes wrong with Ableton.
In that case, as you surmised, you can't use that setting and you just have to make sure before you exit or change Scenes, that any Stomp mode changes you made in a Scene you 'revert'. Alternatively, change to another Preset, then return, and you'll be back at your original saved Preset and Scenes.

If you want the flexibility of being able to do every via MIDI and fallback to non-MIDI, then you may need to avoid using Stomp mode for anything (if using Scenes) unless you are prepared to remember to revert your Stomp changes when not using MIDI. Or, don't use Scenes and try to stick with Stomps/Macros for consistency across MIDI and non-MIDI scenarios.
 
Hmm that's quite annoying to be honest.
I just played around with the midi. In my understanding when setting Ignore Redundant PC to off, it should reload the preset, when sending a PC message for the preset that is already activated.

So I setup a midi PC command to change to a preset, then I manually activated in the stomp mode the first stomp. Afterwards I send another PC message for the same preset and the devices activated with the stomp mode don't deactivate, although the preset should be reloaded, according to the manual.

Feels like, I have to use a separate midi controller to have the functionalities I want, and control everything only via the controller for a reliable fallback.
 
Last edited:
It's actually weird behaviour with Ignore Redundant PC set to off:
I manually go into a preset, manually activate a stomp, afterwards I send a pc message to load the same preset. The preset is reset and the stomp is deactivated.
Now I activate the stomp manually again and send the PC message for the same preset and it doesn't work (stomp stays on) and stops working until I change to another preset and back again.


Edit: Actually it was Ableton, that was filtering out double program changes ....
 
Last edited: