This is an "unexpected behaviour" or possibly a bug query.
I am a beta tester for AATranslator, we make an app that can convert between many DAW & NLE formats, and Vegas script is one of them..
I have found if I give Vegas v10 a XML (Vegas script file) say a 48kHz session, that has mostly 48k audio sample rate media files, but with one 44.1k sample rate file, there is some very unexpected "ruler" or time display behaviour in Vegas.
1) time expressed as FPS, is fine
2) change the time display to "Samples" and the sample count is correct only for a 44.1kHz sample rate.
IE it is at odds & in contradiction to the, I thought, underlying session sample rate, and the sample rate that must be used to make the FPS numbers correct.
Ok, Vegas can do some clever stuff, with regard to handling media with sample rates other than the session rate, but the behaviour I have found looks more like a bug, than a clever feature to me.
John L
I am a beta tester for AATranslator, we make an app that can convert between many DAW & NLE formats, and Vegas script is one of them..
I have found if I give Vegas v10 a XML (Vegas script file) say a 48kHz session, that has mostly 48k audio sample rate media files, but with one 44.1k sample rate file, there is some very unexpected "ruler" or time display behaviour in Vegas.
1) time expressed as FPS, is fine
2) change the time display to "Samples" and the sample count is correct only for a 44.1kHz sample rate.
IE it is at odds & in contradiction to the, I thought, underlying session sample rate, and the sample rate that must be used to make the FPS numbers correct.
Ok, Vegas can do some clever stuff, with regard to handling media with sample rates other than the session rate, but the behaviour I have found looks more like a bug, than a clever feature to me.
John L