Here's what I'd like to see...unless you can already do this.  In which case, hip me, will ya?
 
A way to save a project that includes the audio sample buffer size.  So...you could have a "tracking" mix with super low latency and a "mix" mix with super high latency.  So when you opened that project it would change your audio settings on startup in the background and then revert them to a "default" setting on exit.
Or is this already possible??
 
PS: It's been so long since I've been upstairs I may need to re-introduce myself to the young'uns...
Hidy, I'm Doghouse...and I'm one windy and lazy sum****.  A rare and delicate combination.  Pleased to make yor acquaintance.
 

Thats a global property and not a per project property. If you use WDM drivers its real easy to change the buffers. 

I was thinking about this yesterday. It would be convenient to have "mixing latency" a per-project setting defaulted to the global setting. But I have not bothered to submit a feature request for it.

Yea...I'm constantly changing between tracking an mixing buffer sizes...on many projects.  And while it's not hard to do...I'm just too dang lazy to enjoy doing it.  Shirley there's a way Cake could give us a way to tie the latency settings to a "per project" thingy.

yorolpal
Yea...I'm constantly changing between tracking an mixing buffer sizes...on many projects.  And while it's not hard to do...I'm just too dang lazy to enjoy doing it.  Shirley there's a way Cake could give us a way to tie the latency settings to a "per project" thingy.

I wonder, if given that (in ASIO mode) you changed your settings of your sound card outside of SONAR to say 64 buffers but SONAR's global setting was 1024, after opening SONAR would you be at 64 or 1024?
 
I'm not at my DAW to try it.
 
Assuming you were at 64 (from changing outside of SONAR) then SONAR could probably handle per project settings. 

yorolpal
Yea...I'm constantly changing between tracking an mixing buffer sizes...on many projects.  And while it's not hard to do...I'm just too dang lazy to enjoy doing it.  Shirley there's a way Cake could give us a way to tie the latency settings to a "per project" thingy.

I have a similar problem olepal, but mine is constantly changing bit and sample settings. I'm constantly changing and sometimes I forget to change back to my normal 24/48. Other times I leave my 24/48 when I should have changed to something else....grrr!
 
Anyway, there's only one way to fix your problem...which won't fix it, but will cut down the times you have to change a buffer size. This is one of the cool things we can do in PT...but that's about it lol. But they do allow for a tracking buffer AND a mixing buffer size.
 
But though there is no way to solve it right now, the slight fix would be to use a mixing console. The reason being, you'd be bypassing your input monitoring. Now, if you are recording soft synths in real time, the console won't help...but for all audio stuff, it works perfect.
 
Unless someone is really heck-bent on using a VSTi live, I can get away with using my Roland V Drums module for drums, any of my piano/keyboards like my Korg, Roland or Yamaha, leave my buffer size at 2048 all through, and add any VSTi's later...which would not require a lower buffer size.
 
Going through a console gives you real time "what you hear" as well as playback...so you never need to touch a buffer. You could do this if you used an outboard pre-amp as well...as that is all I use my consoles for. I don't eq using them unless I absolutely have to and use very little pre. Just enough to push my signals to -6 dB peak.
 
I use a Tascam DM 4800 and have no problems and also have an old Mackie 32x8 that works well too. But the console route is the only way I can think of until we have that duel engine PT has...or whatever they officially call that. It's really one of the only things I like about PT these days. But even there, I do not believe it can be locked per project or saved as a template. I'll have to ask my engineer at my other studio as he's the PT guru when we need to use that. I can barely look at it let alone work in it. LOL! Good luck brother. :)
 
-Danny

If latency when tracking becomes an issue for me, I bounce the current full mix to a new track in the project, bypass all the fx bins and use my mix track for tracking purposes. It's not ideal, but I prefer it to messing with the buffers - they stay on fastest setting all the time.
 
Thinking aloud and quite possibly talking out of my backside, in terms of the original question - would opening the project in either 32 bit or 64 bit be a workaround way to have the same project with different global settings applied if you really want to go that way ?

Perhaps it could be implemented by having a global setting for mixing which only changes when you engage recording with input echo enabled.

paulo
If latency when tracking becomes an issue for me, I bounce the current full mix to a new track in the project, bypass all the fx bins and use my mix track for tracking purposes. It's not ideal, but I prefer it to messing with the buffers - they stay on fastest setting all the time.
 

I do this too.

This would make Sonar capable of changing the global sound settings on your sound source.
 
I don't know if I want that.
 
As it stands now, if the current Sonar settings are outside the parameters of your sounding device, you'll get a message stating such and you won't get any output until you adjust your settings either way to match.
 
As bothersome as this can be sometimes, it keeps me in control of what's going on.
 
Maybe make it an option? But then I'd be forced to have to remember which option I chose. Hmmm.
 
 
>>...and I'm one windy and lazy sum****. <<
 
"... of all my parts"? is what yer wuz gonna say, no?