I renamed the .wav and the mpeg2 the same (not sure why V5 won't automatically do this but) and put them in there own folder, clicked on the mpg and it loaded the .wav ...great, but now it wants to recompress the audio...can anyone tell me why?
TIA,
Randy
Thanks Bob, I figured it was user error, I chose 44K knowing that is CD quality and was erroneously thinking that it would be what DVDA wanted. Now, however I have a new problem: I choose to replace the 48K file and get an error (an error occured...the file could not be created) so I deleted first and then tried but got the same error. Here's the mind boggling thing (for me): I go into Windows Explorer and delete it and it still shows up in the folder using V5, it asks me if I want to replace it and when selecting yes I get the same error( rgt click shows it is indeed a .wav). I go back into Windows Explorer and all that is there is the MPEG 2 DVDA video (only) stream. A restart made no difference. Any ideas as to what's going on?
Thanks again,
randy
In case anyone is interested this issue didn't go away on the particular folder and drive I mentioned...weird huh? However I put it in another folder on another drive with no problem. Now I realize how bored you may be by now but I just wanted to say thanks to Bob, you were right about using 48K instead of 44K my friend.
Thanks again,
Randy
A couple of things to watch out for. If a file is still in the Vegas media pool you cannot delete it using Windows Explorer. Even if the file isn't on the TL, Vegas keeps it open so Windoz can't delete it. If that's whats happening you have to clean the media pool in Vegas (or close the project).
Now the other issue is that the Explorer in Vegas only reads directory contents on startup by the look of it, so if you delete a file in Windoz Explorer you'll still see it in Vegas. Even if Vegas creates a file at times Vegas doesn't see it until you shift focus to the explorer window and hit F5.
All this caused me major confudation for a long time with ghost files that weren't there and ones that were but couldn't be seen. Easy enough to deal with when you know what's happening.
>>"Easy enough to deal with when you know what's happening."<<
I still don't know what's happening but I think it had something to do with the "other issue" you mentioned...oh well, all is well now : )
Thanks Bob,
Randy