what was the bug in 1.70?
A4+AR are an amazing cmbo
2 Likes
Does anyone know if this AR OS is compatible with older versions of Overbridge? (Iām running OB 2.0.60.2)
I have a mac mini thatās stuck at OS 10.14, so I canāt upgrade to the latest version of Overbridge. Iād like to have the enhancements and bug-fixes with the new AR OS, but Iād hate to lose the Overbridge integration that I currently haveā¦
EDIT: No, as you might have guessed, Overbridge and the various devicesā firmwares have to be upgraded togetherā¦ So I decided Iād rather have the new enhancements, and I upgraded
Thanks Elektron team for the continued refinement! Will install for ST tonight.
1 Like
I guess whether or not you call it a bug is up for debate, but: after upgrading to OS 1.70 the SAMPLE START/END parameters no longer jumped to increments of 8 when you push and turn the encoder.
Instead, the encoder was more granular and allowed for more precision when scrubbing through a sample, which is good for some cases like working with a sample recorded into the machine.
However, this was very frustrating to work with if you use sample chains, since you could not quickly select specific samples in a chain.
Now, we have the best of both worlds, we can select the level of granularity we want and the push+turn moves in increments of 8.
Hope this makes sense.
5 Likes
There was also a really bad bug in 1.70 that would record TRIG>VEL knob movements on any track all to Track 1. Very annoying, but fixed in 1.71āthough I heard some bad luck stories on the 1.71 upgrade.
I never used chains (yet) but I am super happy for people who now have those back.
Now, what would be amazing and not at all impossible (as there is a weird and inflexible workaround) would be pingpong looping. And 12-VEL levels as an alt mode to CHROM. And and and and.
Nitpicks and bright-ideas besides, the Rytm is like nearly a perfect machine for me.
1 Like
Looks like the minor ST bug I reported got fixed! (LFO destination names showing up abbreviated)
As always, nice to have equipment with long term bug fixes and improvement support, itās very much appreciated here.
3 Likes
thank you, understood now, I never used sample chain and I was looking for the high res for Start End, so when it was implemented I was very happy.
Notwithstanding now Implemented, I do not like it much on Rytm, I think the resolution is not quite precise like other samplers are.
1 Like
Ping Pong looping would be wonderful.
Amazing work, thank you!
2 Likes
Any Syntakt users updated yet? Looking for user reports that fx track issues have been ironed outā¦ They still confuse me every time the fx track stops outputting sound for no reason whatsoeverā¦ And Iād kinda need it to work 100% if I am to use the Syntakt input for sound processing during gigsā¦
If your ST is broken, it needs repair, not a Firmware update ā¦
2 Likes
I dont think itās broken. Sometimes after powerup or changing projects, the fx track remains mute until triggedā¦ I still dont quite know whyā¦ is it user error or is there an issue somewhereā¦
Itās not related to the audio inputs, this much I know, because the fx track might be mute also on pattns which do not use exteranl sounds.
Iāve owned Elektron boxes since the Rytm MKI came out, so have developed some semblance of feel for how these boxes operate. Rytm mutes also used to contain issues in the beginningā¦
In any case, I thought I saw some mention about a fixed issue regarding the fx track in the 1.30 release notes, so am hopefulā¦
Are your FX block parameters applied on the track level or trig level in its sequencer (via p-locks)? You mention external audio - are you sure this is not related with reverb/delay send function? As those require a trigger of any of the internal Syntakt tracks to activate after double stop or power-on state.
1 Like
Usually all fx track params are made on the track level, unless I specifically want to modulate said track via plocks, which is when I do add some in.
Wait, fx tracks require a trigger? What do you mean? I have pattns which send rev/dly into the fx track, you are saying these will remain muted until I trigā¦ what exactly?
thanks
On other gear I think ā¦ if everything is stopped , external audio wonāt be heard going through the device
You need to press a pad to trigger the audio engine and then itāll be heard
I guess , typically the main device is playing and other equipment is also playing so youād hear everything working.
Basically if you canāt hear external audio and everything looks setup correctly , press a pad on Syntakt.
I donāt remember if it in the Syntakt manual, but for Digitakt & Digitone I know the behavior is as follows:
After you load/reload a project, or after pressing [STOP] + [STOP], you must trig or play an audio track to activate the effects for the External in mixer.
Specifically, an amp envelope has to be triggered on one of the internal tracks for FX to kick in on external audio coming in. Muted tracks will not count as a trigger.
2 Likes
I see. However, this doesnāt account for the issues where my fx track remains mute even with patterns where no ext audio is coming in, nor plugged into the inputs. On these pattns, I have some specific ST track going into the fx block in order to add texture to it (overdriving digi machines further with the fx block would be a typical use case). Iām not sure if those pattns also send dly/reverb into the fx track, I will need to checkā¦
Thereās a some routing menus on Syntakt that I donāt understand. The fx track is also unique from what I can tell.
Maybe someone else can help. Iām out of ideas.
Maybe thereās also a more suitable Syntakt bug thread rather than filling up this thread.
1 Like
yes, apologies. I already asked this in the ST bugs thread. Either Iāll get to the bottom of it, and realize I just didnāt āget itā, or Iāll submit a bug report there
Carry on ā¦
2 Likes