« what should happenn » >> No, what you describe is not what « should happen ». you misunderstand virgin territories. When you engage automation and start an automation on a track, it writes a value at the very begining of the project to « remember the value which was before your first change. In virgin territories, cubase is always chasing the last value wroten, if you jump in a virgin territory it looks backwards to see what the value sould be (if you read your project from the start). It’s not a mode to have automation free zones att all, it is a different approach of automation, an one very more convenient for me. The only thing to have in mind is, when you aren’t in write mode, you can do change in virgin territories whithout cubase recall automation… but this will not be saved… as as soon you stop and play it will recall the last value. Virgin territories seems very confusing for a lot of people which seems to want « barriers or frontiers » between diferents automation zone with fresh starts… this is not virgin territories.