I’m in the middle of an important project and can’t afford any glitches so I’m about a week away from being comfortable with loading v3.3.0.
Has anyone tried the new Dumble ODS model or captures yet? I’ve never had the opportunity to play through one of these elusive amps but I love the tones I’ve heard on recordings and live (R Ford, Santana, SRV, Mayor). I’ve tried Dumble models in several processors over the years but never felt like they were able to capture the buttery-yet-articulate sound that Dumbles are known for. I’m hoping that Neural has been able to capture the magic in their Dumble model and captures. If anyone has tried them, could you give us a review?
With a used ODS selling for the price of a well-equipped Lamborghini, slim chance of finding one of us commoners who’s played through one. The fact that Mr. D custom voiced each one to the buyer’s needs means no two sound exactly alike. Regardless, glad NDSP found one to model and capture. Thanks for your assessment, Jackattack.
Haven’t tried the captures yet but the modelled version is an absolute delight I think I don’t generally like using amps with too much gain on board and tend to stack drives and boosts, but I think this one sounds great and is very dynamic…
Dear friends,
Yesterday I downloaded CorOS 3.3.0 and noticed problems with the Dumbbell modeling. I was using the model in clean mode, without preamp, and in jazz mode. Suddenly the sound simply changed to a drive. I opened the block screen and it was exactly as I had set it: clean, preamp off, and jazz mode. I saved it as it was, turned the Quad off and on again, and then the sound went back to clean. After some time it happened again: drive sound without any parameter changes. Does anyone know what might be happening?
One more thing: a HUGE output volume difference between Clean and OD. I had to set the master and output settings to 8 or 9 to match the OD volume set to 5. As I never played or seen live a real Dumble I don’t know if this is normal.
Bummer! So the channel switch is staying on the Clean setting but you have overdrive? Would you mind sending a bug report to NDSP? Once they’re aware of it, they’ll probably issue a fix pretty quickly.
Hi Pete! Just to clarify, I set the clean channel, it stays clean for some time, and just out of nowhere stars overdriving. But the sound is absolutely different from the OD setting. When it happened I turned on the OD and then the sound came with much more drive than the regular OD. I switched back to clean, and that overdrive was still there. So I rebooted QC and the clean sound came back.
That’s a strange one. You can email them at support@neuraldsp.com and describe the issue. I’ve only needed to contact them once but they were very responsive. Thanks for letting NDSP know and making the forum aware.
I’ll shall keep an eye out on that myself played that amp for around 4/5 hours lastnite and did not notice anything funny with it… but done some v2 captures today and they sounded fantastic when comparing referencing, and noticed after capturing my input level had jumped up from 0.0 to 37.00 and I didn’t change it.. Did you check if your input level maybe went up
Yes I used the dumble ods last night the modelled one and as said for 4/5 hours and everything seemed perfect… but today I done some captures and during the capturing everything sounded great but when I loaded the finished captures into a preset my input level had changed but I did not change it… so in the last messaged I asked did check his input level and had that changed… if so it could be the problem possibly
I have just built a number of patches using the Dumbbell ODS. I did not have any issues with the OD switch changing on its own. I did have an issue were the QC input became inactive, as did the power button. I think this may have been caused by macOS 2026 going to sleep with Cortex Control connected, and didn’t recover from sleep properly, but I’m not sure.
As for the Dumbbell ODS, this is a great model with a wide range of very usable tones. It has a Fenderish overall tone but with better bass control so it’s not overly bassy or flubby when it starts distorting. The bright and mid switches are very nice and help with single and double coil pickups (bright off, mid on for single coils, the opposite for double).
The OD channel is still impacted by the Volume control, while the OD Content controls the preamp saturation, and the OD Volume can be used to balance the clean and OD levels with the same master volume level.
What I found is that the cab you paired it with, as expected, had a major impact on the tone. I ended up liking the 412 CA Dagger A V30 01 or the 412 Cornfield V30. I then added the Micro Processor in place of the Enhancer block for a little widening in IEMs.
The end result what a very significant improvement in my tones and they referenced well with the similar patches in FM9.
Just came here to find if anyone else is having weird issues with the dumble model. I keep finding the EQ section stops working - I can move the dials, but they don’t seem to affect the sound at all. Sometimes all 3, sometimes just mids. Deleting and reloading it on the grid seems to fix, but after a while it stops again.
It keeps getting stuck on a great tone though, so I’m not too mad…
That would make sense. I have a Brown Note combo which is their interpretation of a dumble ODS. The “boost" function is simply a tone stack bypass. A real ODS probably operates the same way.
I noticed the same problem here with the Dumbbell ODS model while in the ‘clean’ channel and ‘jazz’ eq mode:
Create a new preset
Add a Dummbell ODS (MODEL)
Set the Channel to ‘Clean’ and the ‘EQ’ (page 2) on ‘Jazz’
Add a Cab (for instance a 212 Too Rock)
change the CAB several times (most of the time 3 to 5 changes trigger the bug) : sometimes the Channel seems to go to ‘OD’ by itself , sometimes there’s simply no sound
When it happens, simply change the ‘Channel’ to ‘OD’ then ‘Clean’ (or the EQ to ‘Rock’ then ‘Jazz’) and the sound is normal again
This loss of sound may have happened to me too. But in my case, there was no input showing on the I/O view. Reboot fixed it. I think my case may have been related to macOS waking from sleep when Cortext Control was connected.
I’m not sure, but I think there may be cases where changing these switches effectively loads a different capture in the block. In other cases, the switch state changes might be input into the training set. If switching the OD state did load another capture, then that gives a hit that somehow the capture in the block is getting lost or corrupt and needs to be reloaded.