Thks guyz sorry for the late reply (interent connection via phone here) 
 
Chuck you're absolutly right , the end of the clips are missing stuff ....
 
Bit , i made a bacth convert thingy with soundforge and voxengo , and my issue was happening , i then tried using sonar by opening a new porject , importing those files , exporting them @ 96K and then placed those in the audio folder of the project ....
 
I didn't imported them in a new project , this might be the thing but i don't wanna go this road since all the project are pretty advanced and just want to switch to 96K existing projets ....
 
Bakers should try to make us a batch command or some to allows this (like they did with the bit rate) THIS is the kinda of feature i personnaly look for ....

Zo

scook
Here is the documented method

The project is mixed and i have plugins so i wanted to convert raw files that are in the AUDIO folder  , for keeping space ...if you export them via the project this will create big clips as for the project duration...

You can export a file for each clip. That way nothing is saved other than the data you want saved. There's also a third way to save, as explained in The Big Book of SONAR Tips where you save only those files that are actually referenced by data.

Anderton

Zo

scook
Here is the documented method

The project is mixed and i have plugins so i wanted to convert raw files that are in the AUDIO folder  , for keeping space ...if you export them via the project this will create big clips as for the project duration...

You can export a file for each clip. That way nothing is saved other than the data you want saved. There's also a third way to save, as explained in The Big Book of SONAR Tips where you save only those files that are actually referenced by data.

Thks , may i ask how to export a file per clip ? anyway i'm able to export and convert those fils into 96K the problem is opening an existing project originally made at 44K with 96K converted audio data is a no go ....don't know why ....since it opens easily , changes on its own the samplerate to 96K , soundcard fallows normally ...but then strange clips behavior as i said ....

I understand why recording at a high sample rate can beneficial. But if a projects audio files are already recorded, what is the benefit of mixing at a higher sample rate given that SONAR has plug-in upsampling? 
 
 
 

Zo
 
Thks , may i ask how to export a file per clip ?

 
Save As to a new folder, then check the box that says "Create one file per clip."

 

ZoBakers should try to make us a batch command or some to allows this (like they did with the bit rate) THIS is the kinda of feature i personnaly look for ....

 
I think there are VERY few people who record a project at one sample rate and then decide it needs to be at a different sample rate, let alone be able to justify any reason for doing so. As Base 57 says, "I understand why recording at a high sample rate can beneficial. But if a projects audio files are already recorded, what is the benefit of mixing at a higher sample rate given that SONAR has plug-in upsampling?"
 
He is correct. Any foldover distortion that would be eliminated by recording at 96 kHz will have been "baked into" the 44.1 kHz audio, and once recorded, there's nothing you can do about it other than use upsampling if you plan to use virtual instruments or subsequent processors while mixing. But that won't help the original audio.
 
In other words, you're wasting your time with this, and your hard drive space. If a client insists on 96 kHz delivery, then sample-rate-convert the 44.1 kHz project's stereo mix. They won't be able to tell the difference anyway 
 

OK, I have a dumb question for you:  Why do you want to increase the sample rate for mixing?  You're not really increasing information, right?  Like scanning a 300dpi picture at 600dpi will not make it any sharper.  So... please educate me on this.  Thanks.

bitflipper
Nino, we've talked about this...

That's funny.....

wruess
OK, I have a dumb question for you:  Why do you want to increase the sample rate for mixing?  You're not really increasing information, right?  Like scanning a 300dpi picture at 600dpi will not make it any sharper. 

 
That's correct, but only for recorded audio. If audio is generated inside the box, either through virtual instruments or signal processors (in particular amp sims) where any elements of the audio reach above the clock frequency, then foldover distortion can occur. SONAR's upsampling function addresses this so you can obtain the benefits of higher sample rates with 44.1 and 48 kHz projects.
 
To hear an audio demo that will blow your mind about how sampling rates can affect the sound of virtual instruments, check out the following video.
 

Thks Guyz 
 
Craig , i produced the tracks at 44K ....and yep i do use the X2 option in sonar witch is great ...i wanted to make a comparaison between the 44 and X2 and the full 96K , the other thing i wanted to check is the ipact on summing (sends , busses ect handling) ....also some plugin act weird when X2 engaged ....( TC VSS3 is one of them that i use a lot .... i have a volume jump when engaged )
 
I'm thinking about switching all 96k but i need to finish actual work .... and wanted to run some tests .. 

The TC VSS3 may not like working at 88. Try setting the oversample to 96 for that plug-in.