cparmerlee

AT
You can add time to the end of a song bounce for reverb and set the length.

I'm sure there are many work-arounds.  The point is that it shouldn't be necessary. I realize that many of the people here have decades of experience with SONAR and its various quirks. If a company wants to appeal to a larger market share, it is a good idea to work on making the experience as non-tedious as possible.  Cakewalk has made some efforts in that regard, but ultimately I think that is the ultimate difference between the two products compared here. StudioOne is less capable and less tedious.  It need not be a trade-off.
 
And I rarely bounce anything.  It seems to me bouncing is a tradition here, but it just isn't something I find much need to do. Why bounce when what you want to do is export the mixdown?  Isn't that what Export is for?

 
I take a simple approach to rendering tracks - seems to work in both Sonar and Studio One. I do a Control A and render. I would note that in Studio One I had to make sure my markers did not force a "stop" or "end" that might cut the song short.
 
I have both full blown programs. There is much to enjoy with either - however I do most of my work in Sonar. It's more intuitive for me and I get more done. However I will loudly second the echos of loving Studio One's mastering (project) screen! Since using that, my Soundforge 10 has not seen any action.

musicroom
I take a simple approach to rendering tracks - seems to work in both Sonar and Studio One. I do a Control A and render. I would note that in Studio One I had to make sure my markers did not force a "stop" or "end" that might cut the song short.
 

Ctrl-A resets the SONAR ruler, which causes tails to be clipped.  If you are dealing with audio files, I guess you can stretch one of the clips to be long enough to accommodate the tail. But that doesn't work if you are using MIDI.
 
Again, these are all work-arounds.  That is my point with this whole thread. Presonus has made an effort to make the program more intuitive so that work-arounds are not as necessary.  It seems to me a really well designed program would at least include the option to detect the tails and include them in the mixdown. After all, who would ever want the tails to be clipped?
 
Of if that is too much to ask, they could simply do what they have in the Bounce function -- an option to automatically add x.x seconds to the end of the selection.  That would be OK too.
 
I'm not saying StudioOne is perfect. I am simply saying that it would do Cakewlk a lot of good to look at some of the attention to "user friendliness" that Presonus has put into their product.

"Ctrl-A resets the SONAR ruler, which causes tails to be clipped.  If you are dealing with audio files, I guess you can stretch one of the clips to be long enough to accommodate the tail. But that doesn't work if you are using MIDI."
 
After you Ctrl-A, set "thru" to the point you want the render (or export) to end.
 
For quality control I always render before export. That way I can check and correct a mix. Once I am happy with the result I export the Clip. I can't imagine I would do it differently in any other DAW.
 

Base 57
For quality control I always render before export. That way I can check and correct a mix. Once I am happy with the result I export the Clip. I can't imagine I would do it differently in any other DAW.

That is my point.  This is all so unnecessary. When you say "for quality control" that implies if you don't do this double-checking, the results may be messed up.
 
If it sounds right on playback, then I should be able to export it immediately and the exported file should be EXACTLY what I heard in playback 100% of the time. I shouldn't have to double check the software.  Why would I want to bounce the mix down to another track (itself a tedious procedure requiring all the tracks to be checked), then export that track by itself, then go back and delete the track?  What a waste of time.
 
It sounds like you are telling me I shouldn't trust the Export command.  That sounds like a root issue to me.
 
 

cparmerlee
On edit: I note the post above about Studio One fitting on a laptop screen. I use two 27" monitors, plus a third monitor to stash VST windows and other paraphernalia.  It does seem that the StudioOne screen is naturally more compact. For me that is not really an advantage, but I can see how that could make a difference on a laptop.

indeed it it does... and the scaling (zoom) is better too - check out how many tacks you can have visible in the track window at once!

just to add, s1 has the massive advantage of being built from the ground up with the r&d of 25+ years of daws behind the design decisions made... it also feels much "snappier" or "responsive" to me /ymmv
 

No, It's not a waste of time for me. I do all final trimming, (lower case m) mastering FX and fades on that last clip. And I know that I am exporting exactly what I want, without having to take the time to restart the whole process because I once again clicked the wrong option in the export dialog.

I was back using Sonar just yesterday to export some stems and tracks from an old album, and the first thing I noticed coming from S1 is being reminded of just how cumbersome the export is, if you don't have exactly the right audio selected already. It reminds me that the 2 products currently have different philosophies - S1 encourages composition with the arranger tracks and scratch pads, so it's natural that many of your exports won't be of the whole timeline. They provide Start and End markers to facilitate that. Sonar however is very much geared towards the recording musician, who starts tracking at bar 0 or thereabouts, and you'll probably just export the whole lot and trim the ends in mastering.
 
One more thing:

cparmerlee
There seems to be no way to archive tracks. That is a really important feature IMHO.

Right-click on track, choose Disable Track. Seems to be much the same thing.
 

I use Studio One 3 for album assembly, it's great for that...better than CD Architect IMHO. That said, I still have to do certain mastering operations in SONAR and shuttle files back and forth between the two programs, or use the Montage feature in Wavelab (which has its own issues).
 
SOP having DDP export is wonderful, especially since the latest maintenance release fixed the fatal DDP export error (hopefully it also fixes the CD writing problems that required me to switch projects over to Studio One 2 if I wanted to make test CDs for clients).
 
However, the reason I don't use SOP for multitrack projects is because SONAR has features that are essential for what I do, and Studio One doesn't have equivalent features. That doesn't make Studio One inferior. It makes SONAR a better match for the kind of work I need to do. I recognize that no program will ever do everything I want, so I use SONAR because it comes the closest by far.
 
On a different topic, this should have been posted in the Software forum because the thread has nothing to do with helping SONAR users make better music with the program. I don't think the intention of the OP was to be rude to his hosts, but this kind of thread can end up being a magnet for those who are, or who lack common courtesy.
 
(SONAR tip: If you don't select anything and Export with the default settings, everything will be exported without the need to Select All.)

Here is a gripe that drives me nuts about studio one though!
  As I said above and I use it for final mastering/album assembly (like Anderton said), and it's export options... So often times if I record in 24 bit/48k in sonar I then export a 24/48k (no dither) stereo wav file of songs 1-whatever from each song project in sonar.  I often end up with them on my desktop for the moment for ease of access at the moment.
  I start Studio One up, start a new project/album project (whatever the hell they are called) and import these wav.'s, put them in order, adjust final fades, time between songs etc.  enter all the data, the logo, etc.  export a couple master CD's for the band/duplication, export the DDP in case they want that too, then export all the mp3's for them also.  I save the project.  close it.   The band is happy.  2 days later I inevitably delete these mixdown wav's from my desktop or move them into another folder (basic computer house keeping stuff).   Then the band calls and says we want to make this fade longer, or...  change the song order on the album.... ok fine. right?  Open Studio one and find that it doesn't actually store that audio with the project.   It stores WHERE you imported the files FROM instead (my desktop) and is now looking for missing files...   this was frustrating.