Wow. Thanks for this. You totally went above and beyond.
2 Likes
That’s a great list.
Something I noticed completely by accident:
One thing that bugged me about sharing kits across projects is that kits are stored within projects, so I kept taking out the card and putting it in the computer to move kits from one place to another.
However, on my unit with 1.6 I found a ‘slight’ workaround, and I hope it’s something they don’t ‘fix.’ (apologies if this has been posted before).
If your projects have less than 64 kits, then…
Say I have a kit I want to share to another project.
If I save that kit to a high number, say 63, and then load a project with FEWER kits than that, then that saved kit is still there until reboot. So I can then save it to wherever I want it to be in my available kit list and have it in that project.
Here’s the crux of it:
It seems that if you load a set of kits via project load and then load a project with a smaller number of kits, the higher numbered kits from the earlier project are still there… until reboot.
I was quite happy to discover this, and never have 64 kits in a single project anyway.
If there are other ways of doing this type of thing without the computer/card file-move thing, I’d like to know.
3 Likes
Well spotted. That is a really helpful workaround.
I think that is due to the fact how storage works (as I described above): there is always a file for each pattern, even if that is empty, but there only is a file for those kits that are actually saved, the default kit appears to be loaded from the firmware, not from file. If the memory slots are not cleared when loading a new project, all kits of the previous projects would remain in memory.
Now I’m curious if your observation about the higher numbered kits would coincide with how you happened to organize your kits.
My assumption is that any kit for which there is no kit in the new project would remain in memory.
Example:
- Project A has Kits
1 2 3 4 5 - Project B has Kits
1 3 5
If you load project A, and then project B, you would still have projects 2 and 4 in memory.
Will test that later.
I’m trying this out on my LXR. I think I’ve seen both “Init” and “Empty” kits. I have a project where I haven’t saved many new kits, but all of the other ones default to “Init”. Perhaps due to this the hack didn’t work. Is there way to delete kits in a project in order for this to work? Will I have to delete them off of the SD Card using my computer?
Still new to this device, getting the hang of it.
Noticed a lag when changing patterns… wondering if anyone else has encountered.
Latest OS.
Made a pattern, duplicated it to pattern 2. Added some per step tweaks to a couple of the drums.
If I cue up either pattern before the other has concluded, and the current pattern hasn’t cycled a few times, it hangs for a micro second before starting the new one. If that makes sense.
I let pattern 1 cycle several times, then cue up 2, it will transition cleanly.
If I cue up the next one immediately it will give a little hang…
Yeah, while testing how saving and memory management works I noticed a few lags like this.
I blamed it on the autosave function, but it might very well be that this is something related to changing the pattern after just one cycle, and totally unrelated to auto save.
Yikes. Ok. I may experiment with turning off Autosave.
12 Likes
Never thought I’d see the day! 
2 Likes
Me too! I installed the update successfully. I’m not sure what behaviour I should see with this new feature though.
- Per-setp parameters displayed now when step is held down and can be changed. Max 2 unique parameters can be saved - if more are changed the oldest per-step param is overwritten
1 Like
Ah bum, you still can’t do sudden transitions of Morph.
I was really hoping they’d fix that in firmware.
Either by permitting cc to control Morph (like in the euro lxr module) or some kind of acceleration or “shift for fast knob movement”.
It moves incredibly gradually otherwise, multiple turns of the knob to go from 0 to 255. It’s fun to gradually change a parameter, of course, but you often want to then snap back to 0 or 255 for a sudden transition.
4 Likes
happy day 
"We have taken over the firmware development from Sonic Potions and after many hours of painstaking effort we are delivering a much needed maintenance update!
LXR-02 V1.7 CHANGELOG:
- Compatibility with Octatrack when sequenced with MIDI
- Per-setp parameters displayed now when step is held down and can be changed. Max 2 unique parameters can be saved - if more are changed the oldest per-step param is overwritten
- Kit morph - when changing the kit, the morph-kit is kept the same. However, is morph set to 255, the morph-kit still slightly changes when swapping to a different kit, but way more manageable
- Delay when routed to an R channel does not crackle anymore
- Fixed MIDI clock going out of sync over time
- Fixed LXR starting sequencer randomly when synced via MIDI
- Added selection between MIDI (MID) or analog clock (EXT) in BPM parameter. MIDI and analog clock no longer work simultaneously
- When BPM selected as MID or EXT, encoder needs to be rotated more for changes to happen. This is to avoid accidental inputs when playing"
14 Likes
Fascinating, and very welcome.
I feel like their quote is almost a tease. That’s a wishful thought for more to come, but it ‘kind of’ signifies a ‘we want to do stuff and you’re not doing it’
Could mean other things of course, but as this is my favorite drum synth, basically ever, I’m happy to have anything that says ‘we still care’ – it’s just so fun to play with.
Also funny that they say ‘many HOURS’ – hours, lol. Like it wasn’t even difficult. But maybe it was 500 hours.
4 Likes
Not sure if you mean the quotation marks that I added to show it was copied from their site?
I guess it’s a start. I think a lot more needs to be fixed/improved to make this machine a joy to use.
1 Like
I wasn’t expecting this . It’s good to know they still are working on it.
1 Like
Agreed. The sound is pure joy but the operation of the thing could still use plenty of massaging.
2 Likes
Totally agree. Now you can’t copy/paste steps, wich for example is an essential one. It’s incredible to see a drum machina that can’t do that (and with so many parameters available). And the workflow isn’t the best.
5 Likes
Hopefully this means fixing/adding in the sample layer feature again that is still sorta in the LXR-02 code…
2 Likes
Hi,
I just installed this latest firmware, and it seems that the euclidian pattern generator doesn’t work anymore : instead of placing random/euclidian triggers on the track, the Function+perf/steps is now filling the track with the selected number of steps, but in a linear way, from first to last, without the euclidian algorythm.
Could anyone confirm this behaviour, or do I miss anything ?
It’s very annoying as I use this function on almost all my tracks.
Happy to see ES working on this wonderful gritty drum synth, but… it seems there’s a twist here.