Analog Rytm OS 1.7x: bug reports

check that CHROMATIC enabled for synth and samples on the tracks in SOUND SETTINGS menu [FUNC+FLT] or [FUNC+MUTE] > SOUND SETTINGS

3 Likes

Unfortunately I did not try that as it did not occur to me before I went ahead and attempted to recreate what I had done. I will definitely make that my first troubleshooting step next time such a thing happens. Thank you kindly for the suggestion. Cheers!

1 Like

This was what I had hoped would be smoothed out

when I push record then play to record with red led blinking

I can record velocity value on track 1 BD moving the velocity knob but not on another track.

Do you have the same issue ?

I believe it’s already posted (not sure it was quantified as working on Tr1 though, so that’s a useful point to share in a support ticket)

https://www.elektronauts.com/t/analog-rytm-audio-routing-bug/158305/55

Here might be a solution. Have not tried it yet.

Does not seem to be a 1.7 bug

I also have this Problem. But even more so.

Not only can I not record Velocity, Note and Length on any of the tracks anymore.
But when ever I try to, it records all my knob movements to the BD Track, no matter which Track I’m currently on.

3 Likes

Hello, i made a calibration and it looks like it work well. I will keep doing some tests and see what happen.

Thanks.

samples won’t start playing after boot for some time.

I never encountered such behavior before 1.70, but now when I power up the rytm and press play it takes some time for the samples to start playing. nothing wrong with the trigs or anything like that, for samples that layered on top of a synth engine - I can hear the synth part playing but not the sample for at least couple of bars, after some time they start playing without issues.

Sample start and end parameters have no audible effect on the sound. Does anyone else have this?

2 issues I have noticed only since 1.70
I have the grey Mk2

1: Loading a sample via the new shortcut method (pressing Yes for the track in sample mini RAM menu) results in loading two of the same sample.

2: While in Euclidian sequencer, pressing FUN and a step, seems to mute or cancel that sequence from that point onwards in the sequence. This is actually quite useful, the issue however is there is no indication either on a pad or on the steps buttons that any mute/cancel exists, so it’s impossible to tell what step or what track might be muted/cancelled.

2 Likes

MK2 Black user here.

I loved the random sound Feature ( src+yes) with the different Kick machines.
Every 3rd try there was a usefull kikdrum Sound but after the 1.70 Update
only every 10th sound is useful. It seems to me the pitches are going crazy using sound randomization after the update =less usefull.
I think the reason is the different/ finer pitch values for the machines after the Update.
Please check this out and fix it,this would be great.

Greetings
Viker

1 Like

If you look at the Trig page whilst holding the EUC step in question you’ll see that you created a Trigless Lock - holding the EUC step is basically like holding the source sequencer trig in the respective relative position, so all the things you are used to doing can be done in the EUC mode, except that the trig isn’t showing up Yellow in EUC mode - but you can track its locks as before

Clear a pattern
In grid edit mode place a Trig on 1 a Trigless Trig on 2 and a Trig on 3
Go into EUC and when you vary pulse density the second Pulse will be ‘silent’
Now in EUC mode, do as you did on the Third pulse (Fn+TRIG)
Exit Euc mode
You’ll see Trig 1 is red and both 2 and 3 are now yellow

I think coloured or flashing info on EUC mode might get too complicated, there are all manner of p-locks that can be hidden … maybe submit it as a Feature request to make it somehow more visible that a Trig is set to Trigless ?

3 Likes

Ah ok that’s useful to know, i will investigate what you described.
You’re probably right about the confusion if too much info, i did wonder if it did show somewhere but obviously didn’t find it, although didn’t look to hard haha.

Thanks for this :black_heart::+1:

2 Likes

it’s randomizing the specific parameters so it kinda makes sense that things might not sound good else it won’t be a proper randomization. maybe try and finetune the parameter(s) manually after having randomized a specific page, at least that’s what i tend to do, maybe slightly changing the filter cutoff or the tune for instance, could make a difference :smiley_cat:

1 Like

maybe there could be a way of setting randomization depth on the machines…? something like in the global menu? even if it’s just as simple as a percentage…

1 Like

I cannot overstate how inconvenient and disruptive this new Page Loop function is on the MKI. It cripples performance in all modes for anyone who uses fills (and who wouldn’t?) This should be accessed by a combo. TRACK + PAGE or RETRIG + PAGE have been suggested in another thread.

Please fix ASAP. When the upgrade came I was preparing a live set and this is throwing me off quite a bit.

7 Likes

Im having the following issues:

-When live recording parameter changes on the track page of a track other than track 1, by rotating the encoders, then the change are always recorded to existing trigs on track 1. This also doesn’t create lock trigs(yellow) anymore (also not on track 1)

-Parameter locks on the track page don’t make the trig button blink anymore.

I’m on a new project

2 Likes

Exactly the same problems here. MkII grey version. I hope it gets fixed. Otherwise this would be the first update making an Instrument worse.
Besides that I really love the new machines they added.

1 Like

My comment is not a bug, but the fact that the new Page Loop cannot be used properly for live performance.

Page Loop parameters must be saved in the kit or pattern !!!

The way it currently works is good for working on a pattern, but suffers from shortcomings for live use.

For live use, it allows variations to be made on several parts. But the big problem is that, as the parameters are not saved in the kit or pattern, when you call up a new pattern no Page Loop parameters are applied. If you want to use this feature for live performance, you need to program it when you open the pattern. You then need to remember which of the 12 parts have been programmed for use with the Page Loop, and then the part or parts of the pattern to which they apply. It’s impossible to remember all your parameters for every pattern, and it’s an added stress during live performances to have to reprogram the Page Loop every time you change pattern.

I really loved this new feature (and the new oscillators), I immediately implemented it on my new project. But when I saw that its settings were not recorded it surprised me that Elektron missed that.

If anyone from Elektron could see this message, please consider this and thank you very much in advance for unleashing the creative potential of the Page Loop!

1 Like