Why does Cubase NEVER respect the “end of project” setting?
Once you set it, if you make any changes, add a track, or anything else, the configuration is lost again! This has been happening ever since I started using Cubase… I’ll have to check the manual, because maybe it’s for a different situation and I’m missing it.
Although, if I’ve already set the song duration, why would I want to change it if that aspect is fixed?
If you move content to your project that exceed the project end, Cubase will automatically increase the project duration value. It won’t shrink back automatically.
So the value in the project setup dialog is an initial value and later on for reading the current value. Of course, it can also be reduced there manually if desired.
It does NOT set a hard boundary to the project, preventing you from adding anything in access of the entered duration.
Hi Johny, I’m aware of the behavior, but at least in my case, Cubase doesn’t respect it.
In my case, I always use a “guide track,” which is the fuchsia track at the top of the project. It’s always there, and it determines the length of each project I’m working on.
Even when I import 1-second audio files from Media Bay, sometimes Cubase loses the final duration. The thing is, if you add a new file that exceeds that end, ideally Cubase should add the extra time, not just whatever it wants, right?
In my case, it’s unwanted behavior, and I think that if the function to define a “project end” is used, it should respect it, and if it exceeds that limit, it should warn the user (like when you add bars at the beginning, for example).
