I am new to sequencers and looping. I would like to use zynseq for live looping with a MIDI controller, and the Akai APC Key 25 mk2 is very helpful for this. I need the quantized recording setting for each pattern. The default setting for quantized recording is false, so when I create a new pattern, I have to go into the menu and check the box next to the setting. In theory, this can be done before starting the recording, but it’s quite a lot of work. The big problem is that if I delete a pattern, I have to set quantized recording in the menu again for the new pattern that is created in its place. Would it be possible to make this a global setting?
Please, create a feature request in our tracking system:
Thanks!
1 Like
Thanks, done!
Do you think that this may be a problem of the workflow with the APC Key25? Or do you see something that may simplify it?
We’re open to suggestions… 
I clear a sequence by pressing the track button and the sequence pad on the Akai. This is a pattern delete, it also generates a new pattern. Maybe something like the clear method in the Pattern manager (with the same or other shortcut) would be better, it removes all notes but the pattern remains.
I feel more settings are of the kind you’d want to apply to more than one pattern. Such as number of beats in pattern, swing, etc.
Maybe remembering last entered values to apply to new patterns could be something.
Or a workflow of copy + clear, using distinct patterns as templates. EDIT just saw this was the solution @gilrain just proposed.
All that said, I am not in the vicinity to any Zynthian right now, that I know of, so I cannot really think through what this would mean, especially for the first option.
Thank you @gilrain and @niels for your valuable feedback! 
@gilrain I see what you mean, and the current implementation has an explanation: patterns are shared (you can have the same pattern on another track, on another sequence or even on another chain). If you clear the pattern, if will be cleared in all places, and that may not be what you want. I can think of another key combination for “removing all notes in pattern”.
@niels I think I can implement the second option, so you can create a pattern, adjust it, and use it as master copy for new patterns. I think that could easily be done (at first glance at least).
Let me create a pair of issues on github, so we don’t forget this…
UPDATE: These are the feature requests, just if someone wants to add something…
2 Likes
@jofemodo made a similar suggestion to me recently regarding having a pattern from which derived patterns may or may not change the parent. It soon becomes complicated to design UI. We could give an option to edit parent or branch, creating a copy of the parent. It would be supercool and horrendously challenging to keep some up/down link between the two!
2 Likes
I think, then, that an easiest approach would be to mark a pattern more as a template, instead of creating a relationship like master-linked patterns. Thus, when a new pattern is created, the template (if defined) is copied, but any future change in the template will not affect the patterns already created from it (only the next ones).
I’ll try to implement this approach in the APC Key25 Driver, and see how well integrates in the workflow.
1 Like
I have a working implementation of the “pattern template” feature described above.
Now, you can set a pattern as the template by opening it in StepSeq (SHIFT + Sequence PAD) and then pressing SHIFT + REC ARM. The REC ARM button will blink indicating that this is the template. When a new pattern is created in the StepSeq / SeqMan modes, or when you clear a sequence in MixPad mode, if a template pattern is defined, it will be copied to the newly created one. It copies all settings, and also all the notes in the template. You can change the template pattern just opening a new one, and setting it. Also, if the pattern is already the template, and you press SHIFT + REC ARM again, it will be unset.
I still need to save the template in the snapshot, and make a PR to vangelis. I’ll update this thread when ready!
1 Like
Ready! The PR is this:
@gilrain Do you use vangelis, and are confident enough to apply a not-yet-accepted PR to your installation? If not, then we need to wait until the PR is accepted… 
I’ll update the Wiki to include these changes, but only when they become available.
I will try to apply the PR.
2 Likes
Sorry, I’ve been really busy after my vacation. I tested the feature, and it’s basically a very good solution, thank you!
I don’t think we should copy the notes of the template as well, because if we copy the same template to new patterns of different chains, we’ll get unexpected results. If each chain could have its own template, this wouldn’t be a problem, but even then I don’t think it would be necessary.
1 Like
Perhaps we could take config values from “last pattern” in the group (chain)?
2 Likes
Yes, what you say is very reasonable. I can remove the pattern notes after cloning it. Until then, you can just use a clear pattern as “template” 
That also could be a good solution. The problem I see is what happens when you setup a pattern and switch to a new chain, without a properly setup pattern. Shall the user configure at least one pattern per chain? Nevertheless, the current implementation allows you to change the “template”easily, so you actually can have several patterns with different settings, one for each chain (for instance).
Sorry, I don’t understand why you want a template that has none of the source info??? Why not include notes in the template derived pattern?
I think @gilrain just wanted to have the settings of the pattern (specifically, the quantisation), not the notes. That could be accomplished with a pattern with zero notes on it. Nevertheless, I’m talking in the name of him, I may have misunderstood it as well 
Soz! I just looked back to see what @gilrain’s request was. It does not actually involve templates. (I think templates may have been a development of an implementation idea. The request is to clear notes from a pattern whilst leaving its struture intact and to remember quantized recording. Clear pattern notes is already implemented in the main UI so presumably, the request is to provide same funtionality in the device driver.
I don’t know whiy “Quantized recording” is per pattern. It makes no sense to me. It does not change the behaviour of the pattern, only the live recording which relates to the pattern editor, not the pattern. I suggest this needs changing. I could understand if it were a quantize pattern option - so that all patterns are live recorded without quantization but have an opton to (un)quantize the pattern during playback. Maybe that was the intention but it does not seem to be the implementation.
That was the original request
Implementation resulted more challenging than expected. The problem was that notes in the second half of the step must be moved to the next step. I would like to review this and implement the intended functionality.
So yes, this flag has sense for each sequence.
Regards
1 Like