• 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 free Log in
    Want zero display ads or expanded classifieds tools? Compare plans.

Darkglass Anagram Multi FX Announced

#2,341
IvanBassist said:
Hope you guys like it!
Click to expand...
Hi @IvanBassist - thanks for the ongoing community engagement and great YouTuber videos.

One thing that occurred to me as I watched the SWR part of the v1.9.0 video was, with any block's tone controls, why isn't there a Frequency label somewhere as opposed to the generic 'Low, Mid, High' type labels?
I notice you actually mentioned in the v1.9 video what the Low frequency was, and yes, I know you could just run it through any graphical EQ app to see what frequency theses control are set to. I also appreciate many people won't care about the frequency value - Low is, well, LOW, and you can hear the difference when you boost/cut.

But I think as people start chaining multiple blocks together, by NOT knowing what these frequencies are, they often come unstuck as one block might be cutting something and then they are inadvertently boosting it in another block. Now, I appreciate that this can actually be a deliberate 'sound architecture' ploy in some cases, but not for your average user.

I like that in the Swirl-900 block, the Low Mid and High Mid actually have a selectable frequency so you know, and can deliberately set, what frequency you are operating on (just need a Q control now :P ). Then you have Low and High controls that are...? (Yes, I know you mention it in the video, but I'm making a point).
 
  • Like
Reactions: jjo161 and mdalamond
#2,342
AnthonyBe said:
Hi @IvanBassist - thanks for the ongoing community engagement and great YouTuber videos.

One thing that occurred to me as I watched the SWR part of the v1.9.0 video was, with any block's tone controls, why isn't there a Frequency label somewhere as opposed to the generic 'Low, Mid, High' type labels?
I notice you actually mentioned in the v1.9 video what the Low frequency was, and yes, I know you could just run it through any graphical EQ app to see what frequency theses control are set to. I also appreciate many people won't care about the frequency value - Low is, well, LOW, and you can hear the difference when you boost/cut.

But I think as people start chaining multiple blocks together, by NOT knowing what these frequencies are, they often come unstuck as one block might be cutting something and then they are inadvertently boosting it in another block. Now, I appreciate that this can actually be a deliberate 'sound architecture' ploy in some cases, but not for your average user.

I like that in the Swirl-900 block, the Low Mid and High Mid actually have a selectable frequency so you know, and can deliberately set, what frequency you are operating on (just need a Q control now :P ). Then you have Low and High controls that are...? (Yes, I know you mention it in the video, but I'm making a point).
Click to expand...
They just posted on YouTube that frequency labels are coming in the next update
 
  • Like
Reactions: _aguacate_, jjo161, AnthonyBe and 4 others
#2,344
wolffire99 said:
They just posted on YouTube that frequency labels are coming in the next update
Click to expand...
You mean this comment on the release video? If so, I'm not sure the person was asking quite the same question as mine above. They are asking about numeric scale... which in itself doesn't make sense to me... anyway.. maybe the answer below doesn't line up with the question. It's all a bit hard to interpret when people ask, and answer, questions using as few words as possible making them less clear and precise!

1764737782378.png
 
Last edited:
#2,346
AnthonyBe said:
Hi @IvanBassist - thanks for the ongoing community engagement and great YouTuber videos.

One thing that occurred to me as I watched the SWR part of the v1.9.0 video was, with any block's tone controls, why isn't there a Frequency label somewhere as opposed to the generic 'Low, Mid, High' type labels?
I notice you actually mentioned in the v1.9 video what the Low frequency was, and yes, I know you could just run it through any graphical EQ app to see what frequency theses control are set to. I also appreciate many people won't care about the frequency value - Low is, well, LOW, and you can hear the difference when you boost/cut.

But I think as people start chaining multiple blocks together, by NOT knowing what these frequencies are, they often come unstuck as one block might be cutting something and then they are inadvertently boosting it in another block. Now, I appreciate that this can actually be a deliberate 'sound architecture' ploy in some cases, but not for your average user.

I like that in the Swirl-900 block, the Low Mid and High Mid actually have a selectable frequency so you know, and can deliberately set, what frequency you are operating on (just need a Q control now :P ). Then you have Low and High controls that are...? (Yes, I know you mention it in the video, but I'm making a point).
Click to expand...
If you open the Swirl block, you will see that it has frequency values for the Mids :)

I think it’s important to educate the community, regardless whether there’s Frequency labels or not. I would sweep to find which frequency i want to adjust, anyway.
Sound engineers do this all the time, even with super advanced EQ plugins like Fabfilter.

At the end of the day, we have to listen with our ears and not our eyes :)
IMG_0469.jpeg
 
  • Like
Reactions: Superbird, BrentSimons and JesseMalaska
#2,347
IvanBassist said:
If you open the Swirl block, you will see that it has frequency values for the Mids
Click to expand...

Um, Yes. I did acknowledge that point in my post :)

IvanBassist said:
I think it’s important to educate the community, regardless whether there’s Frequency labels or not. I would sweep to find which frequency i want to adjust, anyway.
Sound engineers do this all the time, even with super advanced EQ plugins like Fabfilter.
Click to expand...
As a Recording Studio engineer and producer with many decades of experience - I would agree :)

It is just as important to know what those frequencies are, that you are hearing being cut/boost. That is how you build the 'muscle' of association between what you hear, and what that frequency is. You can't do that if all you know is "I'm cutting Low" :)

Also, if I am documenting what parameters I am tweaking (something that experienced has taught me to do when you have to go back and revisit a piece of work years, or even decades, after you worked on it) then knowing the detail is really important.
 
  • Like
Reactions: Superbird and IvanBassist
#2,348
Latency
I'm sure this has been talked about to death but just wanted to add my own test to the mix.

I was doing some recording last night and couldn't get my timing down and, of course being the fallible human begun to assume that surely it could not be me. Not I. My timing is fantastic. Something something foreshadowing...

So today I did the following test:

Bass -> Seymour Duncan Powerstage 700 Bass -> Amp XLR Out -> Focusrite Scarlet 4i4 Input 1 -> Reaper
Bass -> Seymour Duncan Powerstage 700 Bass -> FX Send -> Darkglass Anagram -> Pedal XLK Out -> Focusrite Scarlet 4i4 Input 2 -> Reaper
Recording both at the same time, Anagram running a fairly loaded up preset (2x eq, 2x compressors, 2x preamps, noise filter, etc).
Pretty much bang on the reported 1.3ms latency, give or take about 0.2ms

I don't really know if there's a better way to test this since it eliminates the whole "round trip latency", computer processing, etc, etc that can be introduced. It's a direct apples to apples comparison.

So this is a great result for the Anagram. Not so much for myself, but nonetheless I wanted to share it. I've seen the reports that it's something like 10ms which is just ridiculous. Maybe if you max out the NAM profiles and run effects loops and do everything you possibly can to clog the thing down but for normal use this is pretty fantastic.

For context, if you're around 6 foot the delay for sound to get from your speaker cab to your ear if you're standing right next to it is about twice as long. (~2.6ms for 90cm)

I'm constantly impressed by this little thing. Absolutely incredible.
 
  • Like
  • Haha
Reactions: SquareWaveSymph, brettonbass, Derek Williams and 4 others
#2,349
Latest update somewhat fixed the Pitch Shifter issues I had the last 2 firmware revisions. It had too much latency before, it was unusable for me, but now it seems it's in a better state. There are slight delays on the current version enough to raise an eyebrow but not totally useless.
 
#2,350
AnthonyBe said:
One thing that occurred to me as I watched the SWR part of the v1.9.0 video was, with any block's tone controls, why isn't there a Frequency label somewhere as opposed to the generic 'Low, Mid, High' type labels?
Click to expand...
I thought the exact same thing 😊
Would be nice to have off course.
Or in the manual maybe.
Though, the blocks reflect originals, the originals often don't show the frequency either, do they?
... possibly in the manual.
 
#2,355
jjo161 said:
The way I understand the video is that the MCx would be able to "replace" an expression pedal by sending the cc automation directly to the anagram in our case.

(of course not really replace, but when you're fine with the LFOs and don't want an expression pedal, it should be able to do the job, am I wrong)
Click to expand...
Is anyone able to tell me if my assumptions are right? Or am I missing a key point here?
I feel like I might be mixing up what midi expression is supposed to be able to achieve.

What I want to achieve is a very slow but simple ramping action triggered by hitting a known. A one shot LFO so to say.
 
#2,356
jjo161 said:
Is anyone able to tell me if my assumptions are right? Or am I missing a key point here?
I feel like I might be mixing up what midi expression is supposed to be able to achieve.

What I want to achieve is a very slow but simple ramping action triggered by hitting a known. A one shot LFO so to say.
Click to expand...
I can only answer from same perspective as you - watching the video and an understanding of MIDI.

I'm thinking same as you.
As long as the controlling device can send a stream of CC values (e.g. mimicking an LFO by oscillating the controller value between, say, 1 and 127), AND
On the Anagram you assign a binding to a parameter that you want to 'automate'.

You could probably verify the Anagram side easily with any DAW, where the DAW is performing the role of the MCx. Just create a MIDI track and draw in a wave form of controller values to an assigned CC, copy & paste that multiple times. There's your 'expression pedal' sending 'waves' of CC values. Then try different effects in Anagram where you assign the CC (Binding on the Anagram) to that Effect Block parameter.

I might have time to setup and test something like this in the coming week... you've got me curious now ;-)
 
  • Like
Reactions: jjo161

Latest posts

Top Bottom
Back