Hey … No, I really use the Rytm standalone so far (not even Overbridge) …
Well, then your BD pad is haunted. And that should come as no surprise to anyone.
*insert link to soundpacks here
Though the pad can’t be the problem since I did not went into the performance mode ![]()
… My soundpack (rytm sounds) is almost done though ![]()
so finally I’ve decided to try the page loops and encountering weird behavior, not sure if bug or not but something is weird.
I’ve setup 4 pages, every page has 8 trigs 1-8, the trigs are on condition 2:2, so I expect them to play every second run no matter if I lock onto a specific page, instead I get weird behavior when the locked page plays 4 times and skips 4 times.
sounds like this:
looks like this:
anyone else experiencing this?
I think it’s just the nature of the way the Page structure works. The Condition is for all Pages, and doesn’t work independently per Page (even when locked). Thus the four repetitions.
At least that’s how I understand it.
yeah I though that it’s something like that, probably stretches out the locked page over the 4 pages in total and considers it as a full run of 4 pages and not a single page, I guess it doesn’t work as I expected, I wonder if it’s the same on DT2…
theoretically, if I’m working on a single page out of 4 it should consider it as a single page and not run the full steps, otherwise it’s only good for pages without trig conditions…
Great observation!
On point!
I imagine the good people at elektron getting simultaneously very proud and very frustrated (more work!) about the commitment some of us have here
true true, anyway, it should be easy to code, so no biggie ![]()
i think i encountered a bug. dont know if its mentioned.
i had selected some tracks to not go to main outs and now i cannot turn it back as it was.
Any resolution with this?
My AR froze today. Sequencer stopped and all encoders buttons unresponsive. Delay feedback continued and Ext In audio still passed through. Upon restart, current pattern & kit were saved.
1.70, 0 errors in Test mode, 2023 Rytm MKII. Reached out to Elektron support but wanted to drop a note here too ![]()
I’ve had some random freezes before and after 1.7 on my MK2. If I had to rely on the AR for a live gig, I wouldn’t feel comfortable at all.
I had it only one time since that post. But I, too though … „what if I were on stage right now“ …
Ah, thanks for the replies! Hoping it’s not too often, as I bought the Rytm with the thought of playing out with it
So far, Elektron has just asked if it was connected via USB (which it was to the computer, but no interaction was happening in that moment)… I’ll share any updates I receive!
Another quirk I noticed: I switched to an old pattern (or I guess really it’s the kit) and the velocities on the all the TRIG pages were set to 1. That was a headscratcher as to why by beat was so quiet but the pads were loud af 
Lastly, I dived deep into why an LFO was affecting the parameter on 0 depth before finding there was a velocity mod set to LFO depth … morale of the story: be careful just loading sounds 
a really weird thing happened to me today, I was dialing in PERF macros and I accidentally messed up something, for some reason the track I was focused on (3/RS) lost audio completely, I’ve triple checked the audio routing, trig menu and all volumes but zero sound coming out of that track, tried change the synth machine, sample, whatever, it’s simply muted, feels like in someway I triggered a mute for it and no parameter can reset it back.
I saved the kit anyway, and as soon as I reload the kit to default or switch to another kit everything works, but on that specific kit no audio comes out of that track either from mains or individual out.
any idea what could that be? or is this track is forever sacrificed to be muted?
Ideas to check:
Track volumes and filter, Trig Page, Mutes, Perf / Scenes, Track to Mains, LFO, Velocity Mod
nope, nothing like that, I’ve tried full resetting the track, loading different machines, all filters are open, no mods, it’s just not outputting any audio, full send to fx, nothing… other tracks fine, same track on other kits fine
edit ok fixed it, the culprit was track level, although it was on 100 initially after track reset once I moved it to 0 and then back to 100 sound appeared, yay! not sure what happened though, somehow the level probably got locked on 0, I thought it’s something like that but it was definitely on 100 when I checked, anyway, dropping it to 0 and then bringing up fixed it!
Anyone have behavior where the AMP Attack parameter sometimes does not affect the sound? I get it kinda often and if I wiggle the Hold/Decay parameters then it will start working again … and then stop. I’ll try to make minimal reproducible steps / video
This one’s the ultimate feature.
The amp env doesn’t reset on trig, only when it closes.
Many a raised voice and italics laden post lay in its wake. But you get used to plocking the hold and dec for various lengths.
in addition to what @waftlord said, you should also know than choke tracks envelopes also affect each other, for example if your sound on CY track does not close before the CB is trigged, the attack on CB envelope won’t work either…
