I've got several old projects that have all been recorded at 44.1 and I'd like to convert them all up to 48 without having to use the destructive processes outlined here :
Basically I don't want to lose all of the individual clips and the ability to go back and adjust crossfades etc.
 
After some research I found this thread discussing a workaround - - I need to use 48khz for pretty much the same reason - my axefx 2 only operates over spdif using 48khz.
 
So I've managed to convert the sample rate of all a project's wav files up to 48khz and reload it and everything seems fine at first. But what I've worked out is that Sonar's project files would seem to have stored in them the exact sample length of each wav file it uses, and it ends up truncating anything beyond that. Its ended up that I have several silent parts at the end of each section of the song throughout.
 
How to reproduce: - I start a project at 44.1khz, and record lets say 48 seconds of audio, which equals 2116800 samples. Save and close the project, convert the wav file from the Audio folder to 48khz using voxengo r8brain, then reopen the project which is now running at 48khz. Playback is fine to start with, but audio ends at 44.1 seconds in (which at 48khz is 2116800 samples), and you can see it in the computed waveform picture for the clip.
 
Is there any way or workaround to get Sonar to recheck and recalculate based on the current wav files what these lengths are?
 
I know that saving to a bundle file will trim the actual wav file so that doesn't work. Copying the clip and pasting into a new project doesn't work either. Its like I need the opposite of the 'Apply Trimming' command.
 
Does anyone at cake have a solution to this? It'd be so great if there was a second dropdown box under the 'change bit depth' in the utilities/change audio format menu to change sampling rate.
 
Using Sonar Platinum btw
 
Thanks!
 
Glenn
 
 

Hmmm... I don't recall running into that with the conversions I've done. Possibly the clips in question are slip- edited, and you need to Bounce to Clips at 44.1kHz first to get rid of the fixed slip-edit boundaries...?

Yeah I've tried messing with slip edits, bouncing to clip - no result. This is what happens when starting a new 44.1 and converting to 48 - I've dragged and dropped the wav file linked to the clip in track 1 into track 2 for comparison

Hmmm... maybe a new Platinum "feature". I'll check it out when I get home.

Okay, I guess I was all washed up on this technique having worked correctly previously. I'm seeing the same truncation now. It seems that SONAR stores the number of samples in each clip, and only reads that many back from the file. And it's not just Platinum, I checked back to S8, and it did the same.
 
Right offhand, I don't really see a way around that short of dragging and dropping or importing the converted files into the project.
 

Thanks for checking brundlefly. I've actually had to do this in the past and it worked fine *but* it was going the other way. Running at 48khz was causing superior drummer to load really slowly and to me there was no sonic advantage recording at the slightly higher rate so I downsampled to 44.1, and logically there was no problem of truncated clips.
 
I guess I'll submit a feature request and for the time being resort to some laborious manual processing! :)

Update - just tested converting from 48 down to 44.1. On open of the project I get this message

 
And if I slip edit the clip longer it reveals the added silence, which would be an extra (48/44.1 - 1) of the clip's original length as in this screenshot:

The blue clip is the original 44.1 length, and the green is a 48 downsampled to 44.1. The green line of silence extends a couple of bars further than the end of the blue clip which ends around 19:3
 
So it chucks out an error, but no harm/no foul.
 

Also to note, each time I open a project after up or downsampling the wav files, the waveform pictures are recalculated so it looks like some part of the program at least knows that something is different and is doing something about it. It'd be great if that checking could extend to file/sample length.

Changing the wave file format outside SONAR is definitely not recommended. All the regions in SONAR are stored w.r.t the original sample based positions so this will not work.

Yeah I noticed that while most of the clips started at the exact right point throughout the project, there were a few that ended up a second or two out.