It ended up bugging me so much that I bought a new one. I’ve owned the bad button one for years so no warranty coverage. But the LXR has become such a beloved member of my setup that i couldn’t do without it. I did take advantage of the Labor Day sales here in the U.S.
Bummer for the QC issue though. I’m such a fanboy of this machine that i hate to see its reputation tarnished. For what it’s worth, for years the bad button unit was rode hard and put away wet. She scaled mountains.
I use the Xone 23 DJ mixer. It’s definitely bigger but not as expensive and is does wonders for the sound. The 3 band EQ and filter gives me all the sculpting I need and is very performative.
I run my OG LXR through an EHX Platform comp/drive pedal. It’s got a tone control on the drive circuit so you can engage drive circuit but turn drive down to zero, and use the tone control (it’s just an LPF) to knock down the highs a bit. And the compressor also has a limiter mode. Really does wonders to the raw LXR tone.
I use the same pedal with my LXR-02, which works like a charm!
I sold my AH mk2 bc generally I wouldn’t say I liked the sound; the filters were somehow boring and clinical, the resonance sounded empty like cardboard and the distortion was regularly going nowhere, so I wouldn’t recommend AH. Now i can’t unhear that boring cardboardness it in their analog line, even in ST which i generally like; something about Elektron + analog doesn’t work to my ears. The best thing about AH was the fact it’s stereo.
Yeah this is also a great shout - the A&H mixers DJ mixers sound fantastic and the filters are lovely. Even the cheaper options are a worthy addition to any setup imho.
No compressors tho… And the OG LXR lacks that feature - not sure about the newer version.
I’ve been interested in the EHX Platform for a while now, but haven’t heard many useful demos. Was curious how the drive might sounds on drum machines and synths (normal guitar drive pedals suck all the bass out).
I just got a cheap B stock Mackie 1202 which also works nicely with the LXR. The EQ of course to tame the heights, but also driving the preamps adds a nice touch and the jam factor is raised to another level with the 2 aux sends. Bigger than an AH but still quite compact.
I have this weird issue on my LXR-02, latest firmware.
When I activate the auto save kit with pattern - KCM option to Auto - then when I load the patern the drum1 volume is wicker than the original kit. It’s particulary noticeable because the drum1 channel always carry my kick. I have to manually load the SAME kit to get back the original drum1 volume.
Any idea ?
UPDATE:
After some testing, I found it is related to the filter drive and only affect the DRUM1 channel.
With KCM option to Auto in config, when you load a pattern the associated kit will have its filter drive reset to 0 (internally, the screen does display a value (eg. 63) and if you move the drive encoder it will jump to that displayed value). I supose it’s a bug.
Can some other persons test it on their LXR, please ?
It’s easy to reproduce : load the Initkit, set some drive value in DRUM1 filter, save kit, save pattern (with KCM on Auto), reload the pattern again, filter drive is gone !
I really really would love to be able to morph kits more quickly. It’s multiple turns of the knob. So no way to suddenly transition back to one extreme or the other.
If they’d only make it cc controllable that’d be perfect. It is on the eurorack version!
I don’t have mk2 (I’ve got an OG with BC firmware) but isn’t the kit morph addressable either as a macro target and/or straight up mod wheel from a midi keyboard? If you can have it on a macro maybe you can cc it that way?
To answer my previous post about the DRUM1 filter drive parameter, Erica Synths just contacted me today to say that it’s a known issue : “it’s added to our developpers’ to-do list for the next update.”
from Erica (few days ago): " While an update is planned, it won’t be very soon, as the firmware of the LXR-02 was created and developed entirely by a single developer (Sonic Potions) who lives abroad. Due to the distance and communication issues, our developers are in the process of taking over the firmware, but this isn’t a process that will happen overnight as they have to familiarize themselves with someone else’s code."