• SONAR
  • Issue with Changing Sample Rates in X3
2017/08/20 18:05:07
OldJoeClark
Due to new hardware that only supports 48k sample rate I need to convert older Sonar Projects from 48.1k. I successfully converted the wav files using a third party program and the Sonar project reads the files just fine. HOWEVER, on some of the tracks the audio at the end of the clip doesn't display the waveform nor does it play this missing part back. This is a major issue! The overall length of the clip looks fine, there is just no waveform displaying nor playing back on the tail end.
 
I double-checked the wav files independently with a different software and the audio is indeed there. I can also import the wav file into the same project and all the audio will be there. Doing this manually would be painstaking trying to get it placed correctly in time.
 
I tried the "Recompute Picture(s)" command to no avail.
 
Any ideas for nudging Sonar to rescan the original wav files to fix playback and waveform display?
 
Thanks, Paul
2017/08/23 01:34:43
OldJoeClark
Any help on this one? Please, I'm desperate!
 
Here's an illustration I made that explains my issue in a nutshell. Anyone have an ideas how to wake Sonar up and rescan the wav files so they get properly rendered?:

2017/08/23 14:16:25
chuckebaby
I wish I could help you here but I have no idea what is going.
Which 3rd party software did you use ? Was it R8Brain ?
Hope the bump helps.
 
EDIT
I just read R8Brains info From Voxengo's site:
The demo version allows you to evaluate all the features of the software, but its conversion is limited to the first minute of an audio file.  The demo version does not support batch conversions.
 
2017/08/23 14:37:19
Joe_A
Sounds like more info is needed.
2017/08/23 14:55:36
OldJoeClark
I used SOX to convert the files and wrote my own Python script to apply it. I used Transcribe!  to play some of the wav files and the audio is all there on the converted files.
 
I could use more brute methods of doing this, but not without losing all my effect and other track settings. I have a number of files to work on, so my problem is multiplied.
 
I am wondering if there is some number associated with the Sonar Clips based on the previous sample rate that is causing the clips to not render correctly. What is it, and how can I change it?
 
(note: I tried to put links in here, but the SPAM filtering is zapping them)
2017/08/23 15:27:26
Cactus Music
 I use Gold Wave for batch conversion as it seem the easiest to use of all Wave editors.
It's free to try but a life time membership for only $50 is a heck of a deal. It's been around for a long time and they keep it up to date with Windows OS.  
2017/08/23 15:55:19
mettelus
SONAR does Sample Rate Conversion automatically when a file is imported to the project setting, so if you export tracks from the 44.1K project and import them into the 48K project they will be correct.
 
I am not sure what is occurring in your situation above, but it appears that the wav file may have a header on it that SONAR does not recognize... like it was NOT converted, but the 3rd party program told it to "play back at 48K." It looks like SONAR simply imported the samples (so is probably 10% shorter?). Has the audio that does play been pitch shifted up?
2017/08/23 18:16:11
OldJoeClark
mettelus
SONAR does Sample Rate Conversion automatically when a file is imported to the project setting, so if you export tracks from the 44.1K project and import them into the 48K project they will be correct.
 
I am not sure what is occurring in your situation above, but it appears that the wav file may have a header on it that SONAR does not recognize... like it was NOT converted, but the 3rd party program told it to "play back at 48K." It looks like SONAR simply imported the samples (so is probably 10% shorter?). Has the audio that does play been pitch shifted up?


Good food for thought. Don't know much about headers, but I'm pretty sure SOX can manipulate them. I will explore that tonight. Thanks.
2017/08/24 14:25:57
OldJoeClark
So I played around with this a bit last night looking specifically at the header trail and couldn't make it work trying different command line parameters with SOX. I checked the pitch on the resulting clips and it's fine.
 
Here's another possible piece of the puzzle though: going from 44.1k to 48k the resulting 48k will have more samples for the same time duration. What's probably happening is that although Sonar is recognizing the higher 48k sample rate there's probably a clip parameter under the hood that represents the total sample count and perhaps the 44.1k sample count is still associated with the clip instead of the 48k sample count. This is consistent with the symptom I'm experiencing in which the last 10% or so of the audio is missing in the clip.
 
Does this spur any more ideas with anyone?
 
Just to reiterate, if I import one of the underlying wav files into Sonar in a new location there is no problem; Sonar recognizes 100% of the audio in the clip at the correct sample rate. This also supports the idea that the wav files are not the problem, but it's more likely the glue in Sonar that binds the wav files to the Sonar clips.
 
More ideas anyone?
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account