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

Routing: Transpose happens to late #358

Open
bemtec opened this issue May 7, 2022 · 2 comments
Open

Routing: Transpose happens to late #358

bemtec opened this issue May 7, 2022 · 2 comments

Comments

@bemtec
Copy link

bemtec commented May 7, 2022

When I route a transpose by a track CV, then the first step of the transposed track is most of the times not transposed yet. This happens also when I set the first track as the transpose track. Can you prioritise routings?

@jgoney
Copy link

jgoney commented Oct 26, 2022

@westlicht I'm facing this as well it seems. I wonder if this is related to issue #167. I have track 1 routed internally to transpose tracks 2, 3, and 4. Everything works on time at 75 BPM and lower, but the transposition is about a 16th note or so late at any BPM higher than that. I know there are limitations with regards to processing power and this project's architecture, but is this something that could be reasonably addressed?

@Solar-X
Copy link

Solar-X commented Feb 5, 2023

Hi,
I tried the following - and it works:
I doubled the steps, set my sequence (has to be at most 32 steps) on step 2, 4, 6, 8, etc., put no gate at the new steps (1, 3, 5, 7, etc.) and doubled the speed of the sequence.
So the point of transposing comes on the empty step one and has already changed at the beginning of the real sequence (step two).

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

No branches or pull requests

3 participants