This topic contains 6 replies, has 3 voices, and was last updated by 
alien_brain 9 years, 1 month ago.
-
Posts
-
is there a way to avoid having to save patterns? can zaquencer be made to autosave?
Hi ALien,
I have already thought about this option, and while it would be great to have, I have decided against inplementing it for a very specific reason.
All existing flash chips, and so also the one in the BCR, only have a limited life in terms of writes (usually a couple 100.000). While through regular use you are hard-pressed to ever reach this limit, with an Autosave function it would definitely be reachable, and it´s hard to say how fast. If you picture using Autosave in conjunction with pattern chain, you can imagine that you can get heaps of writes in a very short time. While I could just put the info into the manual, I doubt that it would reach every user of the Zaquencer, so I decided not to provide the function in the first place.how are tr-909s and the like from the 80s able to survive? they dont use flash memory?
They don’t have to scan and constantly save because it’s just regular memory with a battery backup.
meaning they dont save as often? and zaquencer would need to save if changes or not when loading the next pattern? is there no way to ask if the pattern has changed and only then write?
is there no way to ask if the pattern has changed and only then write?
good idea! I´ll think about how hard that would be to implement.
You must be logged in to reply to this topic.