And just like that, I'm back! I opened a new project with a template I have used dozens of times, then recorded about 10 seconds of audio for a quick check of mic placement. I hit "play" & it keeps going long after the audio is finished, so I check to see if "stop at project end" is checked. It is. So I hit the "go to end" and it shows the project is 22,361 measures long!
 
How did that happen? And wasn't there a "set project length" dialog somewhere on the older versions? (I had X1 until a few months ago, and I'm still on the learning curve with Platinum.) I can't seem to find anything that mentions this online, but I'm sure there was someplace where you could enter the number of measures you wanted your project to be. I can't find it now.
 
I'm going to create a couple more new projects as a test to see if this happens every time or if it is some kind of anomaly with this particular project. I'll check in soon.
 
Thanks in advance,
Clark

There have been some issues reported with templates from older versions, this could be one of them. Maybe try opening in Platinum and then doing a "Save As" so it's in Platinum-speak. But check first to make sure there isn't anything at the end, like an automation node or something. 
 
Or maybe SONAR is just hinting that it wants you to write a really long song.

Thanks, Craig. I have not been able to replicate the issue.Since there was nothing of any importance on this project I am going to just dump it & start over. I would like to know if I am remembering correctly that there once was someplace we could go in & set the length of the project, though. I swear that I did that on some old 8.* or X1 projects, but maybe I'm totally hallucinating that, lol.
 

AndertonOr maybe SONAR is just hinting that it wants you to write a really long song.

Ha ha ha, 12 hours (which is what the 22,000+ measures equals) is too long even for my tastes!  But, maybe I shouldn't rule it out!
 
Clark

I don't remember any way to set a defined stop point. Some people have been asking for that, although with ripple editing available to take out everything past a certain point, Stop at End is probably good enough.

The way I often stop my project is with the spacebar .
Seriously though, Even if the project says its 22,000 measures, its not taking up any more hard drive space.
If I need to set an end point, I use a marker but I rarely if ever use Stop at project end.

I have no idea what I'm (mis-)remembering, 'cuz if Craig isn't aware of it, it probably never was a thing!
 
As I mentioned earlier, I've not been able to replicate the 12 hour project file, so I have no idea how a new project just started out that way. But, just for grins I played around with it before dumping it. I found absolutely no data of any sort on any of the tracks, so there wasn't really anything to delete, but I compacted the view as much as possible, so as to see as much of the 12 hours of nothing as possible. I "selected" from around measure 200 all the way to the end on all the tracks. Then I selected "delete special" from the menu. And now when I hit go to end, it stops at measure 200. Crazy, right?
 
Anyway, thanks for giving this some thought, guys. Let's call it "studio gremlins" and pronounce it solved.
 
Clark

Cool, glad it's working properly now.

When you first open up one of these older projects in Platinum, you could manually select all, then set the From to the beginning of the song, then set the Now marker to the intended end of the song, and set the Through setting to where you intend for the project to stop (maybe leave some extra for any effects to trail off), and that way it will firstly save it under Platinum, and 2ndly will only have the song up to where you intend it to end.
 
Bob Bone

I've ended up with audio slivers so thin you can't see them without zooming in 1000%.
I've had midi data appear in weird places too.
 
Some ways to see the end of a project are:
 
Select "View - Fit project to window" (shift+F)
  You can drag-select the entire area past the intended song end and hit Delete to clear any stuff causing this issue.
 
Open Event List and look at the last note entry (for midi data)
  Delete any data that shouldn't be there.
 
 

Nice tip, Soens.