Hi everybody,
maybe is a topic that already has been discussed of , but when i use the arpeggiator , it always start with a little delay from the moment i trigger the note . Has anybody noticed the same problem?
Thanks
Arp behavior
Re: Arp behavior
Do you trigger the note on the Moog keys or is the note triggered by a DAW (Midi)?
Moog One 16/NL C15/Waldorf Iridium/Prophet XL/Prophet 10 D/Prophet rev2 16/OB-X8/OB 6 D/2600/VC 340/Kurzweil PC3K7/Kurzweil 2500R/Access Virus TI2/Reason/NI Ultimate/Logic X
Re: Arp behavior
And what sync settings are you using?Do you trigger the note on the Moog keys or is the note triggered by a DAW (Midi)?
Re: Arp behavior
Of course i am triggering the note on the keyboard and no daw is opened . And on the receive midi clock, i tried off, din and usb but nothing changes . There is still a delay
-
- Posts: 30
- Joined: Fri Aug 02, 2013 5:21 pm
Re: Arp behavior
Yes, I am seeing the same thing. Even with sync off.
It is easily tested by doing the following:
1) Turn on Arp and open Arp page
2) Turn Sync off
3) Set the note division to long note like 1/2
Unless you get very lucky hitting a key will sound quite noticably after you strike the key.
My guess is that this happens because even with sync off, the arpeggiator is using a clock to decide when to fire notes off, and the clock is not getting reset to 0 when you hit a note.
And, I just figured out the solution: go to the next row and turn on Note Reset. That will reset the clock when you hit the first note. Let me know if that works!
It is easily tested by doing the following:
1) Turn on Arp and open Arp page
2) Turn Sync off
3) Set the note division to long note like 1/2
Unless you get very lucky hitting a key will sound quite noticably after you strike the key.
My guess is that this happens because even with sync off, the arpeggiator is using a clock to decide when to fire notes off, and the clock is not getting reset to 0 when you hit a note.
And, I just figured out the solution: go to the next row and turn on Note Reset. That will reset the clock when you hit the first note. Let me know if that works!
Re: Arp behavior
Try the following:
1.) Init a sound with Shift+Compare
2.) Switch ARP to On
In the ARP Menu:
3) Switch SYNC off
4) Set CLOCK DIVISION to 1
5) Set GATE LENGTH to 1 %
6) Set NOTE RESET on
7) Set FOLLOW SWING OFF
Play some notes an the Moog keys (1/8 notes e.g.)
8.) Turn SYNC on
Play some note in the same speed as before.
Switch SYNC on/off while you are playing some keys.
There is a difference.
With SYNC on play a note and hold a key, repeat this.
Is this the delay?
1.) Init a sound with Shift+Compare
2.) Switch ARP to On
In the ARP Menu:
3) Switch SYNC off
4) Set CLOCK DIVISION to 1
5) Set GATE LENGTH to 1 %
6) Set NOTE RESET on
7) Set FOLLOW SWING OFF
Play some notes an the Moog keys (1/8 notes e.g.)
8.) Turn SYNC on
Play some note in the same speed as before.
Switch SYNC on/off while you are playing some keys.
There is a difference.
With SYNC on play a note and hold a key, repeat this.
Is this the delay?
Moog One 16/NL C15/Waldorf Iridium/Prophet XL/Prophet 10 D/Prophet rev2 16/OB-X8/OB 6 D/2600/VC 340/Kurzweil PC3K7/Kurzweil 2500R/Access Virus TI2/Reason/NI Ultimate/Logic X
-
- Posts: 33
- Joined: Sun Feb 24, 2019 4:08 pm
Re: Arp behavior
I see this behaviour when the ARP clock is synced (delayed start of ARP after pressing a key).
I see a similar problem in the Sequencer when triggering the sequencer with a key. More often than not, the first note of the sequence is missed. If I press start in the sequencer, it is fine. Start with a key press...not fine.
I have reported this to no avail.
I see a similar problem in the Sequencer when triggering the sequencer with a key. More often than not, the first note of the sequence is missed. If I press start in the sequencer, it is fine. Start with a key press...not fine.
I have reported this to no avail.
-
- Posts: 3
- Joined: Sun Apr 24, 2022 9:55 am
Re: Arp behavior
Just out of curiosity: which synth are we talking about here? I realise this is an old thread, but I am experiencing exactly the same problem with my Moog Grandmother and was wondering if anyone has found a solution