-
Notifications
You must be signed in to change notification settings - Fork 29
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
Better sequence editing #225
Comments
Yeah, it does. Thing is, why it isn't the default? |
It's a matter of taste. The a-z thing comes from Buzz and I liked it. I can
see why someone doesn't, especially since the patterns are shared by all
tracks (in Buzz you can't use the same pattern for multiple tracks), so
that the pattern numbers quickly grow past 0-9.
2018-01-05 14:53 GMT+02:00 darkhog <notifications@github.com>:
… Yeah, it does. Thing is, why it isn't the default?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#225 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCK6WX0jtckQL_9xEeJ_k7LRqGUAahJks5tHhtRgaJpZM4RSK-E>
.
|
I know. But the majority of users will come from more traditional trackers like AHX, FT2, FamiTracker, ImpulseTracker, etc. than from Buzz. Those who use Buzz rather wouldn't hold much of interest in Klystrack because of entirely different philosophy of use (machine graph) - they'd would be more interested in soft like SunVox or Psycle if they were looking for Buzz alternatives. So I think it should default to more traditional approach. |
Happy? ;) |
Why it can't be more like e.g. in Famitracker, which also uses single track pattern, freeform style (perhaps better fit yet would be Jeskola Buzz's sequence editor)? What I'm getting at is that inputting patterns 0-9 is easy enough, but after that it gets tricky because subsequent pattern numbers are mapped in a weird way to letter block and you can't input specific pattern ID in the similar way you can input e.g. effects or volume commands.
The text was updated successfully, but these errors were encountered: