Bug when copying pattern with note offsets [SOLVED!]

I came across an issue when playing with the Pattern Editor. I created a pattern by capturing MIDI notes from an external instrument (live recording), so the pattern contains note with offsets. So far so good, the pattern was recorded and played with the offsets, just as expected.

Then I wanted to copy this pattern to make add some extra notes, so I clicked on the options menu and copied the pattern to a new destination one. The issue is that the note offsets were all set to 0, so the pattern doesn’t really sound like the original one.

I am using the stable Oram version.

I actually opened a ticket when I first detected this issue, but there has been no movement for a few days, so I open this topic here.
What would be the right steps to take to report issues?

1 Like

The bug report looks okay. We just haven’t had time to look at it yet. You could add a snapshot that contains the two patterns to help support diagnosis. I think this is probably due to the fact that note offsets was added a while after the copy pattern feature and we forgot to check the behaviour of copy pattern. Indeed, not too many people use it so thanks for reporting the issue.

FYI In the original sequencer implementation I envisaged much more use of this but the pattern based sequencer workflow is not (explicitly) used much at the moment since we added the zynpad based workflow that most people use. Indeed there are many features that are little used and likely to have grown bugs over the years.

Hi @gregdulli !

I just fixed the bug in vangelis (testing) and deployed the fix to oram (staging). It’s not in stable yet.

Please, update and test.

Regards,

1 Like

Wow, that was quick! Thanks @jofemodo, I’ll give it a try later this week!

@riban What do you mean by “the pattern based sequencer workflow” as opposed to “the zynpad based workflow”? I mean, how do you create/edit patterns in zynpad if it’s not using the pattern editor? Do you mean that most people use an external sequencer?

We’d quite like to hear that…

Zynpad has a sequence triggered by each pad. By default the sequence has a single track and the track has a single pattern so, when you access the pattern editor from zynpad you see just the one pattern. It is also possible to add more tracks and more patterns to a sequence in which case you use the Arranger to modify the sequence and access the pattern editor.

When I wrote the sequencer it was based around the patterns-in-tracks-in-sequences concept and kinda based on 1980’s pattern & song based sequencers but zynpad changed the focus.