How to access Lossless codecs, no "Video for Windows" in my Render As page. Nothing in manual either. Thanks in advance for any advice here.
First thoughts, would MAGIX have had this removed (?) but do make sure you haven’t got any Filters active.
No filters active.
I'm running Vegas Pro 15 latest build
Video for Windows means Avi.
It's just an earlier framework than DirectX. It originated with 16 bit Windows.
Dv-avi is vfw, for instance.
I'm not near my laptop, but suspect it is listed under Avi, not a separate category for vfw. Dv-avi is vfw, as is Uncompressed.
Like third to the bottom on my render as screen, current release V15
Grazie, the other two Windows choices appear, but not Video for Windows
No, no filters checked. My list is completely truncated, on my other computer (computer 2) I have many more options, both computer's Vegas Pro 15 File I/O folder has the same list - so I'm stumped...I have also looked at my Windows services to see if any services disabled that would effect, comparing my two computers, and that has been copied and still no go.
My complete list, (computer 1), and filters OFF
OK, that is what I did, reinstall, and now it is mysteriously back, thanks for your patience and dilligence!! Ciao.
zdogg wrote on 6/20/2018, 3:23 PM
Long time, I build them actually.... I was holding off on the reinstall as last resort because of my settings.
.Sony Vegas user since ver. 4....
... the problem is the somewhat well known avi.dll workaround plug, imported into the File I/O folder - replacing the default -- which allows me to import most AVI files, one problem AVI video in particular shows Sony DV as the codec, (ironic that that would not load)...but anyway, that replacement dll plug, won't work alongside the default avi.dll, so in disabling the default, you lose the Windows endoding, and it remains now, the other dilema - which avi.dll plug to use, or find some other workaround
One solution:
Would you happen to know where one can find the sony dv codec? Or why I am having to choose now, decoder or encoder, but not both. Thanks again in advance.
Oh, so you messed around with the programs' .dll files and then ended up with a problem. Well, that's not too surprising really, is it?
Well, the program works fine, It worked fine with that plug,
and only when I was toying with the idea of an uncompressed file did the issue arise,
some would never deal with uncompressed files, so for many who use this plug, there is not even an issue....
why is it that a Windows based and formerly Sony product cannot handle really any and all AVI files, especially a Sony DV codec...(Can ANYONE answer THAT question, and please do, before other finger wags)....
.that should be where your smarm is directed, not to this longtime user and supporter of Vegas, who is a bit - and righteously so -- miffed at the amateurish "gotchas" in still left in this program, after so many years -- and looking for better support this time round from Magix, which produces some pretty awesome media software.
Never had a problem with any AVI I threw at it. From the previous discussion about this, it appears your files were quite rare (ADS Pyro ?)
I don't even know what "righteously miffed" means, but it made me laugh. Thanks!
I am glad I can provide, as per usual, untrifling mirth among otherwise barren and droll human existences.
Here's my media info. I don't think Pyro is the culprit here. I think I went to a video store for a transfer - was a while ago.
You may have had better luck with AVI, but there are certainly people who have complained about it over the years, not unique to me, not at all.
Just curious, if you only need to decode, do other DV codecs can do the job?
I have never captured anything to DV (probably I'm too young for this), only opening such avi files from time to time and free Cedocida DV codec do the job (it might be quality issues, however such issues are exists on encoder part usually).
Well, ffdshow - that little free codec pack, fixed it, after a day of................NO NO NO sorry, was too hasty here.
AMMENDED,,,,no did not, I had inadvertantly moved back to the alternate aviplug.dll
So, I am back to square one.