Adjusting Render Clock?

brandondrury1 wrote on 3/4/2006, 10:10 AM
After doing some tests, I've concluded that Vegas must use it's own clock when rendering down an audio mix.

Is it possible to change this?

As you may have read in other articles, I accidently recorded a band at 48K on my Mytek master clock. However, the Vegas session was set for 44.1k. I used the batch converter to change the headers in the wave files to 48K, but if I render a 48K session to 44.1K (using 48K master clock) I get a file that is way too slow when I burn it to a cd.

I have the feeling that if I could adjust the internal clock of Vegas, I could fix this maybe.

Any ideas?

Brandon

Comments

Chienworks wrote on 3/4/2006, 5:33 PM
Ideally, you should not have to do anything at all. Vegas is format agnostic. It doesn't care what sample rates the various audio files on the timeline are. It will use them all at the proper rate (at least according to what it sees in the file header) and properly resample to the output file rate on the fly. If you have results at the wrong speed then you have source files with improper headers. The problem isn't with Vegas, but with whatever is producing the original files.

When you say you used the batch converter to change the headers, may i ask why you did this? Did you determine that the sample rate is actually 48K while the header mistakenly reports 44.1K? When you converted them, did you resample them or only change the header? Have you tried using the files without converting them?

As long as your recording hardware properly marks the file with the actual sample rate used, it doesn't matter if it's 48K, 96K, 44.1K, 27.948K, or whatever. Vegas will play it and use it at the rate it was recorded regardless of the project sample rate.
pwppch wrote on 3/5/2006, 8:59 AM
Please fill out your system specs, specifically the audio hardware you are using in your PC.

The sample rate you select for rendering tells Vegas' engine what sample rate the data should be created at. It is independent of the hardware rate you have set up to stream/play audio out of your audio hardware.

If your audio sounds different when you playback compared to when you render, then you most likely have an external clock that is doing something to the streaming/real-time audio data.

Peter

Geoff_Wood wrote on 3/6/2006, 12:22 PM
Try deselecting any digital inputs on your audio interface when not actually recording. Leaving enabled had SF playing back at wrong speed several versions ago.

Though that's probably nothing to do with your problem , which seems to stem from not having read or understood the basics of the Vegas manual or help. Or, evidently, taking note of the advice offered in other threads.

Again, It DOESN'T MATTER what sample rate or bit-depth the source media is. Go back to your original media file. Chuck it on the Vegas timeline, set your project properties to whatever you like, and Toos|BURN CD. Or it you prefer, Tools|Render To New Track, and select 44k1/16/s .

geoff
brandondrury1 wrote on 3/7/2006, 10:30 AM

"When you say you used the batch converter to change the headers, may i ask why you did this?"

Because when I rendered the files in the usual fashion, the burned cd was obviously playing at too slow of speed.




"Did you determine that the sample rate is actually 48K while the header mistakenly reports 44.1K?"

Yes, this is exactly what happened. After a mobile gig, I rushed to hook up my system in my studio for a session. I apparently bumped the sample rate button on my Mytek which provides master workclock to whole system and recorded the session at 48Khz even though Vegas was set to record at 44.1Khz. This would explain why the files had the wrong headers and would also explain why the burned file plays to slow. If I put my clock on 44.1 to mix, it will also play too slow.



"As long as your recording hardware properly marks the file with the actual sample rate used, it doesn't matter if it's 48K, 96K, 44.1K, 27.948K, or whatever. "

This is consistent with my research. Maybe I didn't change the header properly in Soundforge. I'll try again. In Soundforge, I only changed the sample rate (which should have only changed the header). I did not resample the files. Actually, as an experiment, I tried resampling the files and it still acted the very same.



"Please fill out your system specs, specifically the audio hardware you are using in your PC."

Done.



"The sample rate you select for rendering tells Vegas' engine what sample rate the data should be created at. It is independent of the hardware rate you have set up to stream/play audio out of your audio hardware."

Right. My theory was maybe there was an option somewhere to change the clock of their internal engine, but this may be a little over my head.



"If your audio sounds different when you playback compared to when you render, then you most likely have an external clock that is doing something to the streaming/real-time audio data. "

Sure. You are most certainly right. The external clock is "fixing the sound" when monitoring only so I could at least mix the songs. Normally, setting the clock to 48k would make the song too fast. In this case, it sounds as it should.



"Though that's probably nothing to do with your problem , which seems to stem from not having read or understood the basics of the Vegas manual or help. Or, evidently, taking note of the advice offered in other threads."

The Vegas manual is a joke. I read it in 3 minutes. It did not address any real issues a studio owner might face. The Vegas manual was more of a quickstart than a detailed explanation of how the core system works. I've tried ALL advice given to me in other threads. The problem is bigger than I had thought. As for my understanding of Vegas, I've been using the same piece of software since 2001. I've recorded nearly 60 records (about 700 songs) in that time. There are probably people who have spent more time with Vegas than I have, but not many. My problem stemmed from getting in a hurry and bumping the master clock switch and not because I didn't read the manual or haven't followed the advice in the forums.



At the moment, I'm going to assume that my headers are still incorrect. It's possible that I'm not doing the header changes properly. I was recommended a software that acts more like notepad which will allow me to go in and manually change the headers. I'll try this on a few files and see if it fixes my problem.

Thanks for all of your help!

Brandon
brandondrury1 wrote on 3/7/2006, 12:30 PM
Okay, I HAVE FIXED IT!!

Instead of using Soundforge to do what I thought was changing the headers, I used this:

http://www.railjonrogut.com/HeaderInvestigator.zip

It worked perfectly, except for a small glitch that I'm going to need to work out that messed all my edits up.

Brandon