Is this normal?

sicijk · 2014-04-23T17:03:59.000Z

Try to press the trig for little longer…i think this is due to avoid unintentional trigs (so p-locks) erasing

science · 2014-04-23T17:35:44.000Z

nope it is not a feature to stop accidental trig removal.
it is very responsive and always turn off a trig when the A4 is not receiving a clock. every time without fail.

but when it is receiving a clock there is a big chance of failure to remove a trig.
just like you can loose your undo if you are receiving a midi clock.

Projectile. when using Maschine there is an option under for MIDI Clock, it turns it off and on. i don’t use Machine stand alone anymore though.
I switched to Ableton.

sicijk · 2014-04-23T17:58:49.000Z

have you experienced this also using other Elektron as Master Clock?

projectile · 2014-04-23T19:45:22.000Z

I’m thinking it has to do with something Logic is sending to the Analog 4. Going to sit down and see if I can figure it out. I’ll report back.

science · 2014-04-23T22:09:46.000Z

""sicijk"":

have you experienced this also using other Elektron as Master Clock?

Did you mean "have you experienced this also using other Elektron gear as a Master Clock?"

I do not own any other Elektron gear unfortunately. But it does the same thing with Ableton Live. Sequencer on and A4 will not turn off trigs every time. Turn it off and trigs remove every time.

apeirophobe · 2014-04-24T01:22:46.000Z

I have the exact same problem. I am clocking the A4 from the Octatrack so it definitely has nothing to do with Logic/Ableton.

subq · 2014-04-24T01:49:47.000Z

I run into this all the time as well…OT is my master for everything.

sicijk · 2014-04-24T05:37:13.000Z

ooh yes now i remember this weird behaviour when the A4 was clock slaved…
infact now it doesnt receive clock, only transport (for the other reason that updates the UNDO buffer)

this should definetely submitted to HQ

projectile · 2014-04-24T07:30:11.000Z

Hey everyone-

I think i found a fix for this problem.

Under the Global Menu on the A4 go to MIDI Config and then to MIDI Sync and turn off “clock receive” and just have “transport receive” checked. It cleared the problem up for me. Let me know if this doesn’t work for some people.

hope that helps…

bluewolfse7en · 2014-04-24T08:15:51.000Z

^ problem with this is that even tho transport will function! tempo won’t be locked.
I sync my A4 to the OT & often Cirklon too & I’ve never experienced this.
It sounds like it could be a midi loop issue. Are you feeding the A4 midi out back into Logic? If so, try disabling soft thru in Logic.

projectile · 2014-04-24T08:25:38.000Z

Yeah you’re right… just figured that out after i had typed this.

No i don’t have my out on the A4 going back into logic…

So confused… is this a legitimate bug?

bluewolfse7en · 2014-04-24T08:57:46.000Z

Hmm, doesn’t sound like a bug. Is there anyway you could take a Logic out of the equation & try clocking from another source? If that’s fine you know its something to do with your Logic settings.
Also, try sending transport & clock FROM the A4 to Logic, & set Logic to receive instead of send. What’s the outcome then?

projectile · 2014-04-24T19:54:19.000Z

""bluewolfse7en"":

Hmm, doesn’t sound like a bug. Is there anyway you could take a Logic out of the equation & try clocking from another source? If that’s fine you know its something to do with your Logic settings.
Also, try sending transport & clock FROM the A4 to Logic, & set Logic to receive instead of send. What’s the outcome then?

Just hooked it up to my Roland R-8 and it’s doing the same thing. When i have the A4 as the master clock though everything is fine.

subq · 2014-04-24T20:07:15.000Z

turning off receive clock isn’t a fix, it is a bug that needs to be fixed for real

it should be fully functional when receiving clock

I’ve also run into the other issue mentioned related to same thing when A4 is receiving clock

biologik · 2014-04-24T22:46:02.000Z

Confirmed that this happens over here as well (A4 slaved to Ableton). This must be a universal bug. Has anyone submitted it to HQ?

projectile · 2014-04-24T23:01:51.000Z

""biologik"":

Confirmed that this happens over here as well (A4 slaved to Ableton). This must be a universal bug. Has anyone submitted it to HQ?

I just sent a message to support with a link to this thread.

dimi3 · 2014-04-25T03:07:38.000Z

I get it sometimes but is seems to happen when the sequencer is about to pass over that trig.

bluewolfse7en · 2014-04-26T09:06:08.000Z

I’ll be most interested to see what the final out come is here.
Midi clock is a standard, (24 ppqn as far as I’m aware).
If it’s a bug, I’d expect a lot of people to be suffering from this & I’m amazed it didn’t rear it’s head during the beta phase! But , stranger things have happened

coreyappleby · 2014-04-28T01:32:31.000Z

Does it still happen when you have Clock Send and Receive Send turned off on the A4? I’m wondering if it’s sending a clock to Logic/Ableton/Etc and depending on what you’re using it rebroadcasts that clock signal back to the A4.

Not sure why it would only affect trig deletion though and not recording trigs as well, although it’s possible the trig deletion is slightly more difficult to calculate and takes just a bit longer for the CPU to compute which is just enough time for the multiple clock signals to confuse it.

I live in fear of midi loops, so anytime I want something to be just a slave I turn off all the other options it has to be a master, sometimes tracking that stuff down can be a nightmare.

biologik · 2014-04-28T02:24:08.000Z

""coreyappleby"":

Does it still happen when you have Clock Send and Receive Send turned off on the A4? I’m wondering if it’s sending a clock to Logic/Ableton/Etc and depending on what you’re using it rebroadcasts that clock signal back to the A4.

Not a midi loop problem. I’m only using clock in and transport in on the A4 for sync.