Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.3.0] (Beat Slice) Slices already written on pattern shift in consonance with the pad roots note. #594

Closed
LetsSeeIfWeSolveThis opened this issue Dec 26, 2020 · 3 comments
Assignees

Comments

@LetsSeeIfWeSolveThis
Copy link

@LetsSeeIfWeSolveThis LetsSeeIfWeSolveThis commented Dec 26, 2020

I was on C3 (pad root note) and Chromatic scale, I used beat slice mode and wrote the pattern as I wanted.

But once I tried to select the scale of my song on project settings, from C3 pad root note I moved to C#3 (+1 semitone), then, for example, a Kick on C3 slice and Snare on C#3 slice moves to C#3 and D3 respectively. (+1 slice).

  • How often does this bug happen? (every time, often, "it only happened once")
    Everytime.
  • Does this bug happen in previous firmware versions?
    No.
  • Does this bug happen in every project?
    Yes.
@LetsSeeIfWeSolveThis
Copy link
Author

@LetsSeeIfWeSolveThis LetsSeeIfWeSolveThis commented Dec 26, 2020

#589 Could be the same? He didn't mention beat slice mode but... sounds close enough.

@PiotrAleksander
Copy link

@PiotrAleksander PiotrAleksander commented Jan 5, 2021

@LetsSeeIfWeSolveThis It is not the same bug.
Here, the beat slices are moved up a semitone which causes issue with already programmed patterns (e. g. kicks becomes snares and snares something else).
I've updated from 1.2 and had noticed it too. I think beat slices shouldn't be moved or all already programmed beat notes should be altered on root note change (does not sound feasible though).
@andrzejmagierski2 I preferred the old way, so after choosing scale I was changing beat slices with the jog wheel, but played notes with the pads.

@LetsSeeIfWeSolveThis
Copy link
Author

@LetsSeeIfWeSolveThis LetsSeeIfWeSolveThis commented Jan 5, 2021

Yep, I rushed to the conclusion, thank you for pointing out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants