• SONAR
  • to find why doesn't stop at the project end (p.2)
2017/04/12 15:22:31
henkejs
slyman
If you set Sonar to stop at the end of a project, it does. Period.
Every single time I had this happen in my projects, I was able to find some data/event/ghost() between both mesures.
The down side is that you have to look everywhere (and I mean everywhere) to find it. But it's there.
 

 
I still have this problem on certain projects. I've searched everywhere I can think of -- event lists, automation lanes, etc. -- and can't find what's causing it. I've checked all the MIDI piano roll views to make sure there isn't a note that extends past the end. I've tried doing a "select all" and then selecting the region on the timeline between where the project should end and where it actually stops before pressing "delete". No luck.
 
To those of you who've been able to fix the problem, is there someplace else I should be looking? Thanks.
2017/04/12 16:30:58
tenfoot
henkejs
slyman
If you set Sonar to stop at the end of a project, it does. Period.
Every single time I had this happen in my projects, I was able to find some data/event/ghost() between both mesures.
The down side is that you have to look everywhere (and I mean everywhere) to find it. But it's there.
 

 
I still have this problem on certain projects. I've searched everywhere I can think of -- event lists, automation lanes, etc. -- and can't find what's causing it. I've checked all the MIDI piano roll views to make sure there isn't a note that extends past the end. I've tried doing a "select all" and then selecting the region on the timeline between where the project should end and where it actually stops before pressing "delete". No luck.
 
To those of you who've been able to fix the problem, is there someplace else I should be looking? Thanks.




 
When you use the timeline ruler to select the region after where the song should end, do you choose edit > delete> special and then choose everything in the delete dialogue, including automation, whether you have used it or not? Using the ordinary delete does not always work, but this method has every time for me. 
2017/04/12 17:56:49
henkejs
tenfoot
When you use the timeline ruler to select the region after where the song should end, do you choose edit > delete> special and then choose everything in the delete dialogue, including automation, whether you have used it or not? Using the ordinary delete does not always work, but this method has every time for me. 



Good point. I'll pay attention to this next time.
2017/04/12 18:13:01
chuckebaby
The Grim
chuckebaby
 
Besides your thread, the last thread I've seen with this problem was 2012.




that is simply not true and i think you know that, really disingenuous actually, a quick (very quick) search shows
 
http://forum.cakewalk.com...39stop39-m3483542.aspx
http://forum.cakewalk.com...Stopping-m3409611.aspx
http://forum.cakewalk.com...p-Solved-m3405480.aspx
 

Hey Grim,
Did you happen to notice a recurring theme with all these links you left ?
 
They are all solved and due to operator error. Much like the many others that pop up
 
The Grim
or perhaps you have been to busy changing your avatar for the 11teenth time every day and missed them

 
I haven't changed my avatar in over 4 years ....I have no idea what you are rambling on about.
 
The Grim
shame on you

 
You got that right.. Shame on me for not blocking you earlier.
Good luck.
 
 


2017/04/12 19:03:44
AT
There are workarounds when this happens but a user shouldn't have to spend any time looking for ghost nodes etc.  If a project - for whatever reason - doesn't stop at the supposed end, you should be able to put in a stop project command simply and neatly.  Over years this problem can cause all kinds of wasted time, operator error or not.  It seems like a simple request, but maybe I'm wrong since it still ain't fixed.  A lot of new users get tripped up w/ this one.
2017/04/12 19:26:55
soens
Far be-it from me to disagree with anyone, as I can neither confirm nor deny the issue at hand.
 
However, here's what happened to me today using SPALT 2016.12:

 
All areas after the magenta line were selected and deleted.
2017/04/12 19:31:27
Anderton
When I want the project to stop playing or recording, I press the space bar or click on stop.
 
The main annoyance for the issue referred to by the OP is when doing an export, because you need to select a range in the timeline. It would save a few seconds if you could just Select All, and the timeline would automatically extend no further than a "this is really the end" marker.
 
It is true that ghost data, typically involving automation or controller data, causes the problem. You can generate ghost data if you let recording continue past where you want the project to stop, because SONAR doesn't know whether you're recording something intentionally or not. 
 
Most of the time Delete Special, selecting all options, and selecting the timeline region past the "real" end point takes care of things, but not always. I'm not sure what renders this ineffective (I don't have this problem often enough to chase down the issue). However one possibility is a hidden track that extends past the expected point.
 
A "this is really the end" marker would be convenient, but at least for me it's not a showstopper to Select All and drag across the timeline to define the area I want exported. It's easier than opening up the automation lanes and deleting the rogue node.
2017/04/12 20:02:36
synkrotron
True, not a show stopper, and it is rare that this happens. Sometimes simply closing a project and re-opening it fixes the issue.
 
Of all the projects I have worked on over the last twelve months or so, around forty or so, only one rendered out at twenty minutes, when it was only a ten minute piece. I just let it render, had a cup of tea, and then opened the WAV in SF to trim to length.
 
I realise that I could have set a region, but I never do, normally, and it is only after you render a project that you realise you have a "problem."
 
Stop marker though? Yeah, I'd vote for that, just for the convenience. Although, as Craig says, a quick tap of the space bar does the trick
2017/04/12 20:14:09
soens
The whole point of having it stop at the end is so you don't have to stop whatever else you're doing to manually stop the play routine where it should stop. BTW, how many of you can hit the spacebar precisely at project end?!
 
Stopping a few measure beyond the end normally won't matter. It's when it keeps going never stopping that something is really wrong.
2017/04/12 21:10:05
lapasoa
After doing control + A and selecting the space from the supposed project's end until the real project's end, I tried Delete special checking all the objets to remove, but Delete special didn't work meaning that nothing at all was in that space.
So I decided to use a workaround: I've chosen a previous version of the same project verifying that in this version "stop at the project's end" was OK.
I added some tracks from the very last version and verifyed if the project's end should still be OK. Yeah super OK.
This means that the project that made me crazy had a bug. Misterious bug, but a real bug.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account