rog857


Hi Folks, I've got the same problem. When exporting, the song runs past the end point for about 7 seconds. I've checked the events list and piano roll--nothing past the end point. When I go to export I deselect "fast bounce", thinking I'll just hit the space bar at the end point. Trouble is the program keeps going 7 seconds past the end point. I'm not sure how to "set the timeline selection before bouncing" as perfectprint suggested. Any ideas? Many thanks! Mike

Select all (ctrl + a)


Then with your mouse, swipe across the time ruler in Track View to narrow your selection down.

Just curious (and I get the same problem of Sonar playing forever or the opposite, truncating a verb trail)... How does Sonar know what the end of a project is? What event does it use to stop? Would be cool to be able place a stop point in purposely.

What you're missing is, end of project is not end of track. If you're working on a track in a project that is shorter than the longest track in the project, Sonar keeps going until the end of the project, not the track. Select the tracks, the individual clips you want, and it won't happen. That's the seperation method.

deved.com


Just curious (and I get the same problem of Sonar playing forever or the opposite, truncating a verb trail)... How does Sonar know what the end of a project is? What event does it use to stop? Would be cool to be able place a stop point in purposely.

Sonar knows what the end of a project is by the end of any performance data in the project. By selecting individual peices of the project, you are telling Sonar to stop at a certain point. Look at your global settings, there's a checkbox for stop at end... something. Check that box.

deved.com


Just curious (and I get the same problem of Sonar playing forever or the opposite, truncating a verb trail)... How does Sonar know what the end of a project is? What event does it use to stop? Would be cool to be able place a stop point in purposely.

It goes on the last event written to the project, and that could be one a not small number of things


Many, if not most, have been talked about on this thread already:

• Clip/Midi event
• Audio event
• Envelope node (synth or automation)
• Time signature
• Tempo
• "Shape Event"

I'm sure that's not an exhaustive list

Bristol is right. Sonar look for the last event in the project and stops when it arrives at that point. 

The best way to find an errant event is select all tracks and open the Event List View. Go to the very bottom and look for an event outside the normal time of the project. It should be the very last one. 

The Event List is not just for MIDI it will show all events audio or otherwise. 

Bristol, Thanks so much! It was all about selecting the correct length of tracks to record by, as you say, swiping across the time ruler. Works great now. Thanks again! Mike

This has happened to me a few times too.  What I do now is....click on the right arrow of the scroll bar right under the transport.  This jumps you to the very end of the project so you make sure your project ends where it's supposed to, or it can let you see what is causing the "conflict" if there is something past the end.

I have rendered a mix before of a song with a length of say...3:00 and end up with a 6:30 file.  There is ALWAYS something at the end of the timeline that causes this...at least with my experience.  It might just be a volume node or something simple like that.  But anything on the timeline will definitely cause the project to go past the expected end.

Another quick way to jump to the end of a project is simply to hit ctrl + end. ctrl + home does the opposite

As far as mixdown goes the physical end or beginning of the project is not always what is wanted. The best practice when doing a final render is to explicitly select the region between the start and end point you want as well as all relevant tracks.

To simplify this process I add explicit markers called begin and end to the project. Then when its time to export I do this:
- open the markers view
- CTRL-A to select the entire project
-  Click the begin marker in the markers view
- clrl-click the end marker (this selects only the region that you wish to render)
- export

As far as SONAR not stopping at the end, if you don't make any selection SONAR assumes the project length is up to the last event across all tracks in the project. You most likely have some event, an automation node, a MIDI event or a tempo change that is extending the project beyond the last audio visible event. There are many ways of using bounce since SONAR supports exporting specific selections so with that power comes some complexity. In a future version we'll consider improving the workflow for the more basic operations.


PS: A word of advice. Always listen from start to finish to your final mix before showing it to a client to avoid surprises like this. With any automated process there is always a chance for user error or something unexpected happening - fade's truncated, effects bypassed or something like that.