I don’t know if you’re the only one, but for me there’s no level drop. If anything there’s a slight level increase. I use that chorus on almost every gig.
Enjoy the benefits of a premium membership!
Upgrade Account
-
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
- Thread starter Elmstreet
- Start date
I have the chorus on several presets and haven’t noticed any volume changes. I have however found that moving the position of the chorus around to different places in the block chain do create some different tonal results. Also, I’ve tried placing effects on the lower block chain to allow for parallel processing which you may want to try. You can even place the gain block on the parallel path if needed for volume adjustments on that path only. Many options I’ve experimented with like these that give various results
I'm curious whether anyone has run into this problem with 1.11 of OS. I've got a patch that uses the send and return blocks where I have my MXR Bass Synth pedal plugged in. With the update to 1.11, the Send/Return is functioning on ALL of my patches - regardless of whether Send / Return blocks are in that particular patch.
I'm wondering is Send / Return is now "global" without blocks being present - or maybe I've hit a bug in 1.11?
For reference - I was previously on 1.07 and it behaved as expected where the Synth only sounded where explicit Send / Return blocks were deployed in a patch.
Thanks for any help / guidance. Jeff
I'm wondering is Send / Return is now "global" without blocks being present - or maybe I've hit a bug in 1.11?
For reference - I was previously on 1.07 and it behaved as expected where the Synth only sounded where explicit Send / Return blocks were deployed in a patch.
Thanks for any help / guidance. Jeff
I haven't tried it yet, but I cannot really imagine, that it is intended to be like that. That would mean an effectloopblock would be mandatory, when a pedal is connected (assuming the loop actually gets turned off).
... which is highly inefficient off course but it would be a workaround until it gets fixed.
What happens when you put send/return blocks into the presets that don't have any yet?
I use the FX loop in a solid half of my presets and did load the latest update, no issues. I can't help but wonder if there was an issue jumping so many updates like that. Wasn't there an update a couple months back tweaking the compressor blocks that had a few people having to rebuild presets from scratch?
Hadn't thought about that. Unsure how to go back and "step up" release by release. I guess I can try doing the update all over again - but that will have to wait as I'm playing two services tomorrow at church. Will just have to trigger the Synth from its foot switch for now.
That wasn't a bug, though. The updates to the compressors meant that the V1 compressor blocks would sound different compared to V2 at the same settings, because increasing the amount of compression on tap, adding metering, etc. was the point of the update. So people had to either go in and try to 'rematch' their V1 compressor sounds on those blocks or they took advantage of the new 'range' and then adjusted other blocks in those presets to gel with the new compression tone they'd dialed in.
Did some reamping of a studio bass track last night using Anagram. I put new nickel rounds on my Dingwall SJ and then tracked a part for an indie pop tune through a Revive Audio M12 (API 312 clone). It sounded great, but I wanted an option with more grind to blend in. I reamped my take using a Radial X-Amp into Anagram (HPF, Bus compressor, B3K set for pretty apparent grind), then into a Trickfish B1K powering a Bergantino NV115 that I mic’d with a U47 FET. Absolutely killer results. Definitely added what the direct track was lacking.
IvanBassist
Commercial User
- Jun 8, 2008
- 3,744
- 11,128
- Disclosures
- Content Manager at Darkglass Electronics, Dingwall Guitars Artist
I think I need some help with interpreting or translating this part of the anagram manual:
What does float + int. mean?
I interpret it as: if you bind multiple parameters to a knob in a macro, the only function is "on/off".
Am I interpreting this correctly?
At least it seems to be the way it is. But then I ask myself? Why is this? I mean, for stomp binding it is possible to bind specific values for each block in the macro, why not in knob binding?
What does float + int. mean?
I interpret it as: if you bind multiple parameters to a knob in a macro, the only function is "on/off".
Am I interpreting this correctly?
At least it seems to be the way it is. But then I ask myself? Why is this? I mean, for stomp binding it is possible to bind specific values for each block in the macro, why not in knob binding?
I find it odd they are using programming terminology in the manual. Float and int are data types. Not very user friendly. A float is a floating point number or simply a number with a decimal point in it. An int is an integer or simply a whole number.
I read that as knob binding macros with multiple parameters only allow the parameters to include whole numbers, numbers with a decimal point or one or more toggles (on/off).
Last edited:
thanks, @viobass.
okay, I see. so what is not working is compression ratio, attack and release probably as well.
In the end only continuous values. fair enough.
Then, list type parameters are the things like 2:1, 4:1, ... / 1 ms, 3 ms, ... / (comp and drive type in Entropia) and so forth
but that all doesn't explain why I can't switch between values in the knob bindings. especially because I can set start and end values.
Is it a bug after all? Maybe @IvanBassist knows how it is supposed to be?
okay, I see. so what is not working is compression ratio, attack and release probably as well.
In the end only continuous values. fair enough.
Then, list type parameters are the things like 2:1, 4:1, ... / 1 ms, 3 ms, ... / (comp and drive type in Entropia) and so forth
but that all doesn't explain why I can't switch between values in the knob bindings. especially because I can set start and end values.
Is it a bug after all? Maybe @IvanBassist knows how it is supposed to be?
IvanBassist
Commercial User
- Jun 8, 2008
- 3,744
- 11,128
- Disclosures
- Content Manager at Darkglass Electronics, Dingwall Guitars Artist
I just figuered out that all my initial assumtions were wrong. It actually switches between the values I set in the binding.
a use case, for example:
knob 3 binding where drive for alpha Omicron is 2.0 as start and 10.0 as end value and the same for the MOOD.
okay I see now that this works, my bad.
what brought me to this is probably a more special MIDI case. But now I figured out even this works. I just need to switch to value toggle logic for this.
the use case here:
some midi controllers are able to trigger LFOs via MIDI, for example a slow ramp.
when triggered while having set the device to toggle logic, the knob binding jumps between 1.0 and 0.0 very quickly.
And I think I know why I got confused by this:
when having only one parameter in a binding, then the LFO works, regardless of the toggle logic setting.
I was a bit surprised when I realised it does, I did not really understand it and questioned myself: I am probably misunderstanding MIDI toggle logics.
In the GIFs you see both examples, toggle logic is set to toggle in both cases. Left is with two parameter bound to knob 6 (LPF+MOOD), right is only one (LPF).
After all there is no real issue here, we can all go to sleep now. Thanks for stopping by
(apart from maybe the toggle logic not acting logically, or am I still missing sth?)
Attachments
I've had mine 2 months and I have had it die in the middle of a show 2 times. Both times I was using the included power cable, no midi and had a power conditioner and was running the latest updated software. In the Anagram facebook group this seems to be a recurring issue. Honestly, it is my second dissappointing experience with a Darkglass pedal. (I have a vintage microtubes pedal that failed and has basically become a neat paperweight)
I’ve had mine die 4 times in a single day on v1.10.x. and again a fifth time on v1.11.0 
Won’t be abandoning my QC quite yet, which has never once failed me in several years. Honestly, I don’t feel comfortable taking this thing to a gig. (Powered by Cioks DC7)
Won’t be abandoning my QC quite yet, which has never once failed me in several years. Honestly, I don’t feel comfortable taking this thing to a gig. (Powered by Cioks DC7)
Last edited:
For some reason I’ve seen issues with the stock power supply. Makes no sense. Mine’s powered off the Cioks Crux which is powered from my DC7 with zero issues after a couple months and over forty gigs plus rehearsals and home use.
This sounds great but is adding like 400 extra dollars to an already expensive unit. At roughly 1200 they should be able to get the power supply right.
Agree absolutely! I haven’t used the stock power supply so can’t speak to that but unfortunately, as I mentioned, have seen comments from others here and on other forums describing issues using it which is very surprising. I have several other Darkglass devices and have never had problems with any of them. I already had several of the Cioks DC7 units plus the Crux when I was using an HX Stomp XL and others requiring more juice so was a no brainer to use it rather than have it sitting on my shelf.
