Page 4 of 4

Re: Hooray for Pattern Lock!

Posted: Sun Nov 01, 2015 8:08 pm
by Pygmy
Neon Seizure wrote:OK, I wish it would just put up a message asking if I want to save edit changes before changing the pattern
That would be completely awful.
There's a very good reason why you actually manually have to 'write' your pattern: for live performance you want to use your "base" patterns and tweak and change on the fly without permanently damaging your base patterns - and you want to be able to quickly change pattern without actually having to answer any silly questions about whether or not it should do the thing you just bloody told it to do.

Re: Hooray for Pattern Lock!

Posted: Sun Nov 01, 2015 8:27 pm
by SMK
Pygmy wrote:
Neon Seizure wrote:OK, I wish it would just put up a message asking if I want to save edit changes before changing the pattern
That would be completely awful.
There's a very good reason why you actually manually have to 'write' your pattern: for live performance you want to use your "base" patterns and tweak and change on the fly without permanently damaging your base patterns - and you want to be able to quickly change pattern without actually having to answer any silly questions about whether or not it should do the thing you just bloody told it to do.
Agreed, that would be a disaster! "No messages, Korg, thank you!"

Posted: Mon Nov 02, 2015 8:24 am
by Pygmy
The other way to implement it would be like the Roland TR8, where everything you do is instantly stored / changed, and you have to manually "lock" the pattern so that changes are NOT stored to it.