riche wrote:Is there a - no edit - just play mode when using pattern sets.
It seems in pattern mode when you change mutes and other settings while playing a pattern then move to another pattern and back later to the pattern you changed it goes back to the pattern as you had modified it... all mutes etc...
Would be nice if it could rather go back to original settings of pattern set...
This would be a "play" mode... Rather than edit mode it seems to currently operate in.
You should still be able to change settings and mutes for performance... But the pattern set itself remembers the original saved state of mutes etc...
This is particularly important if the pattern set you want to go back to was a strong dynamic change (like a drop)... In performance you may unmute some tracks to build up - move to another pattern then later return to the dynamic change... As it is now you would go to the state the pattern was in after applying changes during performance

thus not getting to the dynamic change the pattern was originally set to...
No, such a mode does not exist. What you have in mind is the behavior that is known from the Electribes, where something like a pattern set does not exist. The Electribes simply map pattern files to different buttons, and everytime you push such a button it just loads that pattern file from the storage. You can achieve the same by loading patterns from the storage.
A pattern set in G-Stomper is a self-containing file that includes everything, patterns, samples, song arrangement, etc., and everything is loaded into memory (rather than using the patterns from storage). The reason why it's all loaded into memory is simple... It's much faster than getting it from storage all the time. What you can do for now is to reload the pattern set, then everything gets back to original.
In order to keep the original pattern while changing its values would mean that when switching to particular pattern it must be copied to its own memory in advance. This is a rather memory and CPU intensive process, therefore it's not handled that way. However, I see the benefit of such a behavior and I'll see if there is a way to make it possible in some future release.