AR Bugs thread

DanJamesAUS · 2019-09-20T08:03:45.009Z

changing and loading samples is slowing down everything to the point it almost freezes for me at the moment

guga · 2020-03-21T17:15:08.655Z

found a little something the other night: with the AR synced to the OT, when i stopped the sequencer on the OT, the AR kept playing a pattern but showing the pause symbol on the display, tried few times but was not able to reproduce it though so not sure what caused it, MKI - OS 1.31; this may or may not apply to the new models/OS

also noticed that lately i can smell the PCB flavour coming from the machine more, both from the top (pads side) and the side vents…got to be somewhat distant from the machine as it’s actually strong
had a look inside but things looked ok apparently, main PCB was getting hot with the machine on but i would say at a normal level. anyone else or is it just me?

guga · 2020-03-28T15:33:58.786Z

tried to reproduce the one above and apparently it is something that happens when:

direct jump is active
changing pattern soon after stop message is sent from OT

as i’ve not seen this mentioned elsewhere, it probably doesn’t happen too often/not many have come across it/doesn’t create much of a problem; thought i would report it anyway

finalform · 2021-01-17T13:25:16.316Z

I’ve done a search on this and not found anything, apologies if it’s a known issue.

Today on a certain pattern/kit I wasn’t able to prevent sounds being sent to the main outs. I made a new global slot setting, didn’t work. Different pattern, different kit, it was ok.

It’s not down to FX sends (ie hearing the FX on the mains). I had my kick with no delay or reverb that I was not able to prevent from sounding on the main outs.

Anyone experienced this?

Merijn76 · 2022-10-21T15:03:24.194Z

Hi all, new here, as I finally swapped my MPC4000 for an Analog Rytm MK2, loving it so far!

I do have a question with regards to the start point settings and recording of pad play with start points greater than 0. On my machine it seems the start point is not always observed correctly, and sometime the AR jumps to a point before the set start point, so sample length is not always the the same. and this is recorded into the sequencer as well, is this me, or a bug?

https://www.youtube.com/shorts/2OAHqIq9BiI

Kosmology · 2022-10-21T15:29:59.662Z

I think that’s possibly due to envelope retrigger mode which I think is located on the Trig page. Not sure if this is what it is but the envelope behaviour is legato by default I think and so doesn’t behave as you’d expect. In the past that had me scratching my head when I first got mine a few years ago. I suppose one way to determine if it’s that is to make the amp envelope release time zero.

Take this with a pinch of salt, I don’t use samples very often on mine so it could be something else.

Merijn76 · 2022-10-21T16:18:39.139Z

Ah thanks, tried that, I have setting for env on zero release, same for attack, and the shortest hold time allowed to make sure the envelope doesn’t exceed the chosen length between start-end points, but not much luck so far. Can’t see any options on trigger page to change env behaviour (other than for filter reset), the search continues…

Kosmology · 2022-10-21T16:25:56.623Z

Just looked to see where it is and there is a specific setting for retriggering the sample SMP

image1842×1782 471 KB

Merijn76 · 2022-10-21T16:34:48.736Z

Isn’t that just triggering rather than retriggering? with SMP off the sample doesn’t trigger at all

Merijn76 · 2022-10-21T16:47:43.511Z

Ok, no idea what i just did, but now it works fine, as expected…, annoying I have no idea why, perhaps I had some trigger locks on the track, though couldn’t see any.

Thanks for your help though Kosmology!

Merijn76 · 2022-10-21T16:49:48.433Z

Well, i ran a calibration, but thought that was only for analogue part…

Kosmology · 2022-10-21T17:06:36.326Z

Glad you got it sorted

MightyMightyPJ · 2022-10-30T00:06:25.287Z

Encountered a glitch where the sample and it’s settings from a particular kit/pattern take effect are played whenever the track is triggered, regardless of which kit or pattern is active.

Schnork · 2023-02-28T16:22:12.739Z

Anyone ever seen this?

20230228_1347261460×615 139 KB

20230228_1346551607×637 151 KB

20230228_1346271362×619 160 KB

20230228_1345571298×591 156 KB

I turned the filter cutoff on track 3 and then noticed the trigs didn’t play anymore. Checked if I had live rec on, no live rec, held the trig down to check for locks. All parameters except trig page locked to 0.

A bit weird, isn’t it?

I think I’m on 1.61B.

Schnork · 2023-03-15T00:30:29.296Z

Noone ever seen something like that?

Btw, the screen on my AR mk1 starts to lag under heavy load, like many incoming midi CCs. Leds and encoders don‘t seem affected, but I guess this could lead to buggy behaviour.
How is the behaviour on the mk2?

alechko · 2024-06-10T17:28:54.621Z

not sure is that’s a bug or always was there… was running DN into the EXT IN today for the compressor, and if you push MUP enough the Symmetry param on the distortion page taking effect, I thought that Symmetry os only for the distortion and that EXT IN bypassing it straight to comp, so anyone noticed it before or it’s a new thing?

Bloop · 2024-06-10T19:47:14.651Z

My ext in also responds to SYM, but DIST seems to only apply to internal mains

Are you saying if you turn MUP up enough it automatically activates SYM? Or are you already using SYM in the kit?

alechko · 2024-06-10T19:52:57.095Z

no, I already had it on something very minimal like +3 but when I turned up the MUP I heard it engage and was really surprised, I’m not sure if comp also activates the distortion (or maybe they share a circuit component) or it’s a software issue

btw adding distortion did nothing, only SYM had effect

Bloop · 2024-06-10T20:22:59.630Z

I can’t quite figure out where SYM sits in the chain, the UI implies it’s part of distortion but the signal architecture diagram and my ears make me think it’s part of the compressor

alechko · 2024-06-11T03:46:52.475Z

yep that’s what I’m trying to understand too, according to the diagram EXT IN comes after the distortion and before the compressor, in my mind no parameter on the distortion page should affect the compressor, so it might be a software bug, I can’t remember from before 1.70 encountering this so I thought maybe someone remembers if that’s always was the case or it’s a new thing…

maybe @avantronica knows?