Opening VOB files in VV

RoyS wrote on 1/19/2003, 9:15 PM
It was possible in VV3 to open VOB files (although not actually a supported media). However, it seems the V4 has now removed that hidden gem. Could this be just becuase the beta of V4 does not support MPEG formats, or is this something the V4 will be removing from the "hidden" list.

Hopefully now that V4 will support AC3 audio, that it will be able to open the VOB file, audio and all! .. Even if it's still a "hidden" feature.

Comments

rstein wrote on 1/19/2003, 10:50 PM
I asked this question a few days ago and was told "no."

I do not understand the logic of this, considering that VV supports the native MPEG-2 stream contained within the .VOB, and that Vegas 4 will also support the AC-3 audio.

Clearly, from the tone of some here, it's almost forbidden to discuss the use of .VOB files.

Bob.
RoyS wrote on 1/19/2003, 11:25 PM
I also find it intresting that it will open the VOB file, and not the M2V files.

For now, I just use DVD2AVI to create an intermediate file (D2V) that is used for TMPegEnc, and then use another program called VFAPIConv that will take that D2V file and create a proxy. Using this proxy creates an AVI file that allows me to open it in VV3 (but without the audio). Then I have to use another program to convert the AC3 file into 6 seperate WAV files.

Sort of a round-about way to get to the audio/video, but it works great. I was just hopeing that SoFo would see that it just makes sense to allow us to do it in VV in the first place.
mikkie wrote on 1/20/2003, 10:00 AM
Windows is set to use whatever codec to play back video files, whether they're mpg1, 2, or DIVX etc. THis is interesting, since after installing the beta stuff, windows thinks it's supposed to use the mainconcept codec every time it encounters a vob file on my system -- NOT the way it was set up, since I could use the ATI file player or windows media player in the past & now both are broken. Something else to fix @#$$!**@#!!!! NOT cool since I've got to go through and start reinstalling software.

Anyway, since windows is now set to use the mainconcept stuff, it of course won't work in the VV4 beta since that doesn't include anything mainconcept. And the Mainconcept codec won't work outside of Sonic Foundry apps.

At any rate, VV3 will open the quick test vob I just created but it has to be imported through the file menu -- windows doesn't know what a vob file is anymore (check your windows file associations from windows explorer) so obviously Vegas doesn't recognize the file extension & neither does anything else. When I did import it, Vegas 3 showed it as a mainconcept file. @#$$!**@#!!!!

So that's the problem folks - if you had decoder files installed, have to figure out which ones windows used and put it back or reinstall your other stuff to set the associations back to where they should be.

For what it's worth... Using vfapi and similar use the decoding software on your system outside of Vegas & then send the decoded images (the video stream) to your video editing software -- Vegas in this case just thinks it's dealing with a plain jane avi file.

I wouldn't call this a hidden feature, whether you're talking about breaking my system or opening vob files, since if things are set up properly, Vegas treats a vob file the same way it treats something DIVX - just uses the proper decoder. It doesn't know, or shouldn't, that a vob file is mpeg2. And as most have found, the mainconcept stuff does not open every mpeg2 file. I assume the ability to open any of the related files extensions (m2v etc) is also dependant on whether Vegas uses the built in decoder or not.

Anyway, hope this helps someone -- hope that SOFO notices this thread! -- wish the mainconcept folks weren't so @#$$!**@#!!!! arrogant to assume we don't use anything else, that there's not other (BETTER!) encoding/decoding software - & BTW, @#$$!**@#!!!! means every nasty word in my vocabulary that would get me kicked off. ;)

mike
mikkie wrote on 1/20/2003, 7:11 PM
I apologize for going over the edge up above, but I still think the beta install screwed up my system's vob file handling. I went into detail about what I found etc. in a new post, hoping I guess to divorce myself from the anger I initially felt when I posted earlier.

Thanks for pointing something out to me -- otherwise wouldn't have known my system had problems until in the middle of a project.

mike