I think the answer is that only the video is matched. You have to set the audio yourself.

Usually all the audio recorded with the video is at 48k while the music in the project is at 44.1k. You are going to be doing a smaller rate conversion no matter what.

No Fred, I'm seeking a simple answer: Match Settings to Media. If I have 48, should the Audio match to 48 too? I'm not thinking of down rezing the audio, just have confirmation that it should match.

TIA

- G

If I set the project default to stereo and then match project media to a video clip with 5.1, the video is reset but the audio stays stereo, and vice versa if the default is 5.1 and you match to stereo, the audio stays at 5.1

If I set the project default audio to 48 kHz sample rate and then match to a DV AVI file that has 32 kHz sample rate, the project stays at 48 kHz.

Ok, the plot thickens.....

When I render to MP4 the Cinescore WAV gets scrambled. So I matched the audio sampling and now spoken word gets quicker?!! CS is good, but the spoken/captured verbals go up a notch. Ugh.....

There is something really dickie going on.

- g

Whether you use the match media or not shouldn't cause any funnies to the audio. If they differ, Vegas should convert on the fly for preview playback, and convert only as necessary for the render. The audio should always sound sensible no matter what. If you are getting something funny then it is a bug, not anything you are or are not doing.

Thanks Peter. When rendered to MP4 I'm getting EITHER breakup in the CineScore WAV, OR the captured Audio is getting a higher register. The play time is the same as the Selection length so it isn't flowing faster.

Ugh . . ..

- g

Plays on the timeline fine.

That sounds like a different problem to the question you originally posted.

Do you have your Resample Quality set to Best, that might get you around the problem you're having.

Bob.

Try rendering an audio mix track @48k. "Tools> Render to New Track" Then mute or remove the original tracks.

Bob?: "That sounds like a different problem to the question you originally posted."

How? I was asking if Matching brought an Audio match. What "Problem" did you get from me asking that simple question?

- g

Thanks rraud. But I think I'm getting somewhere now. Just rendering to make sure.

- g

"Bob?: "That sounds like a different problem to the question you originally posted."

Original question:

"Should Match Project to Media include Audio"

Now you say:

"When rendered to MP4 I'm getting EITHER breakup in the CineScore WAV, OR the captured Audio is getting a higher register. The play time is the same as the Selection length so it isn't flowing faster."

It should not matter what your project's audio sample rate is set to, Vegas will (or should) automatically resample all audio to the project's settings and send that to the audio device during playback.

During playback with your new audio box you might have a problem if the box's audio clock doesn't match what Vegas is using, been there, done that. If that was the case one cause is those boxes have a switch to select external or internal clock, make certain it is set to Internal. This probably only applies if your box has a SPDIF input.

EXCEPT you're now saying the problem is in a rendered file and your audio box is not involved in rendering so I discount that. From your vagues description I have assumed your rendered file contains audio from sources with different audio sample rates.

Bob.

Bob, you've completely lost me....,

- g

Always better if is does match, but the short answer is "No".

Which is yet another place where VP p*sses all over PT etc.


*** Later edit : OK, so not 'a general' enquiry, but relating to an actual problem.

VP converts everything on-the-fly to the project SR/bit depth. This also happens when rendering. If the audio is being altered spontaneously, then something is broken.

Always leave resample quality on Best.

Where are the source WAVs from - mayve they have erroneous file header info (wrt SR).

geoff

And here's the clincher, Geoff, those WAVs are Sony's own, generated in CineScore. I've done this countless times previously.

- g

While the topic title is initially intriguing, it is actually a complete non-issue.

Why?

Because the purpose of project properties is to let you simulate, exactly, what the final video will look like and, I suppose, what the audio will sound like. However, the actual video produced will, with the exceptions noted below, depend on the render settings and not the project settings. As for audio, since the difference between 44.1 and 48 sampling rates is sonically near-impossible to detect, the project setting simply doesn't matter for playback. Also, unlike video where resampling to project settings that don't match the source video can slow things down, there is no such issue (it is too slight to be noticed) in not matching the audio.

So, you can set the audio project properties to anything you want, and as long as you render using the correct sample rate, that is what will be used. So, there really isn't any need to match audio to source sample rates.

Finally, here is my general summary (probably not complete) of why and when setting the project properties matters:

1. You want to see exactly what the final video will look like. This is the initial purpose of this feature, I think.

2. You want the fastest timeline performance. To get this, you must match the project properties to the source media. Even if you are going to render to a different resolution or framerate or PAR, this is sometimes useful just to get faster timeline performance. Of course you can get burned doing this.

3. You are going to frameserve. The video that gets frameserve depends (I think) on the project settings.

4. You are going to record audio. In this case the project audio setting is CRITICAL. This is the one thing I can think of where you absolutely, positively need to set it the value you want. This doesn't necessarily mean it must match some input media; it simply has to be set to whatever you want to use for audio capture.

5. You are going to generate media (titles, backgrounds, etc.). All Vegas media is generated using the Project settings. I can't remember without looking whether there are any tone generators in Vegas, other than the one used when printing to tape (for the test pattern leader), but if there is, it would probably use the project setting.

John, with respect, my simple question was to assertain whether matching to media, that Icon to Match Media, was meant to match media, including Audio or not. My experience with my MXF 48 rate was not being matched. I asked a simple question. Now, how you can interpret that that as being a non-issue, for me, it was and is still not a non issue. I wished simply to ascertain if matching would also include the Audio. Now, certainly your long description as to the efficacy, suitability or even relevance of having matching audio, indubitably has its merits and I'll take your advice and direction in the kind manner it was undoubtedly meant - thank you.

Be all that as it may, the verbals were up-register and when not, the CineScore WAV has getting scrambled. Most odd. And it was solely this that made me venture out on this quest to assure myself I had set up my project correctly. From what you are saying it would appear, not a lot.

- g

"my simple question was to assertain whether matching to media, that Icon to Match Media, was meant to match media, including Audio or not"If that was the question, I can, indeed, verify that the "Match Media Settings" Wizard only matches the video properties of the source footage. My Panasonic TM700 shoots in 5.1 audio. When using the "Match Media Settings" wizard, it matches the Video settings w/o problem, however I need to manually set the audio to 5.1

The title of this thread was "Should Match Project to Media include Audio?" I interpreted that as "Should I Match Project to Media include Audio?" rather than "Does the Match Media Settings Wizard match both video & audio settings?"

...Jerry

John, with respect, my simple question was to assertain whether matching to media, that Icon to Match Media, was meant to match media, including Audio or not. At the risk of being very blunt, but to make sure you understand where I am coming from, I am not particularly happy with the tone of your response.

I was honestly trying to help you, and I receive, for my efforts, a rather snippy reply.

First, your initial question was different from what you are now saying. Your initial question was: "Should Match Project to Media include Audio? Simple question. Simple answer needed."

What you actually asked -- whether you meant to or not -- was whether, perhaps, Sony should change the match media feature so that audio was also included in that matching process. There is no other way to interpret this question because even a casual ten-second test reveals that the match feature does NOT include audio.

What you are now asking is whether the match feature "was meant to match media." This question is asking whether the feature of changing the audio properties to match is actually contained in the Vegas match function, but somehow is malfunctioning in your version. This is a totally different question.

We all sometimes don't clearly write what we intend to say, so I am not upset by the confusing initial post (although sometimes trying to be too terse or too "cute" makes it difficult to communicate clearly).

Your next sentence: "Now, how you can interpret that that as being a non-issue, for me, it was and is still not a non issue. I wished simply to ascertain if matching would also include the Audio." is not only snippy -- basically telling me that by my saying that it isn't an issue (which it isn't) that I am somehow dismissing your problem -- it also fails to really understand not only your own failure to communicate, but also the content of what I said and how it applies. You are also not listening very well to what Bob has been trying to say.

Let me be quite clear: I don't doubt that you are having a problem -- a problem by the way that you didn't even mention in the initial post -- but you are having a problem that has nothing to do with the match media feature. That is the essence of what various people have been trying to get across.

Finally, yes I did offer a "long description" in answer to what I thought -- obviously incorrectly -- was the question as you initially worded it. The fact that you chose to include the word "long" as an adjective means that you obviously found it boring, tiresome, and obviously completely irrelevant. You should know by know that I tend to be a little long-winded, and I would hope you would cut me a little slack.

Perhaps I sound, in this post, a little prickly, but by now you of all people should know that I always do my best to help people here. In fact, as you may remember, I did a lot of extra work years ago on my versions of the Deshaker script just to satisfy your particular requirements.

I am truly sorry not only that I failed to find a solution to the quite different problem that you eventually described in your later posts, but that you took obvious offense to the way in which that long post was worded.

I really try hard -- always -- not to offend anyone, and so let me first apologize, without qualification, for inadvertently having done so in my post above. Finally, to avoid any possibility of further problems, I will never take the risk of offending you again.


[edit]Jerry posted at the same time and said much the same things -- although more briefly -- about the confusing nature of the initial post.

I answered the original question in the third post! (And expanded it in later posts.)

After Grazie's response, I then interpreted his question to really be, "I am getting a bizzare audio effect. Is this because I have not matched my project audio to that of my source?"

I then answered, "No, it looks like a bug".

I (and I presume Grazie) was then hoping that the experts here (because I am not one), would come up with a workaround or a way of identifying the cause of the problem.